Very simple HC3 LuA scene doesn't work correct

[funnyboy4711 0]

Hello,

 

I have create a very simple LUA scene, but this doesn't work reliable:

Condition/Trigger:

{

  conditions = { {

      isTrigger = true,

      operator = "<",

      property = "Einspeisung",

      type = "global-variable",

      value = "-300"

    } },

  operator = "all"

}

Action:

hub.call(274, 'turnOn')

 

So here is a global variable "Einspeisung" which changes its value every 5 minutes, if the value less then -300 then trigger a device on.

But trigger will be fired when the value change from + to - the value does not matter then.

I try also set the value without "":

{

  conditions = { {

      isTrigger = true,

      operator = "<",

      property = "Einspeisung",

      type = "global-variable",

      value = -300

    } },

  operator = "all"

}

But this doesn't work at all. 

 

Why does this simple scene not work?

 

Best Regards

[10der 832]

Not sure what comparing values (I am talking about global vats)  in left block a good idea 

[Lode 19]

Use equal -->"==" or not equal --> "!=" to compare the values from a global variable in a condition.

Result is a boolean.

Then in your scene do the rest.

I don't know why you have only those two options (tested in a blockscene) but i guess it has something to do with the two types of variables or it is a bug ??

Edited May 18, 2022 by Lode

[funnyboy4711 0]

I think this is a functional limitation that a global variable could not be an numeric (integer) type.

But why is that not documented on the LuA documentation page  

 

So for me it is a feature request

 

 

 

[cag014 731]

When you compare strings it works by comparing character by charcater..

for example 

"-99"<"-301"  is true because first character "-9" less than "-3"  and so on...

You will have a lot of cases were this statement is true  ( less than "-300" )

 

It could be a good idea to run this scene [see fibaro.scene(...)] when value less than -300, were you update  the global "Einspeisung". May be you don't need the global at all.

 

Edited May 18, 2022 by cag014

[Lode 19]

9 hours ago, funnyboy4711 said:

But why is that not documented on the LuA documentation page 

There is so much not documented, this is a "bug" in Fibaro !

[m.roszak 763]

I am pretty sure its documented, see for yourself

Please login or register to see this link.

If you like you can use the docs build in the gateway -> in Swagger:

Please login or register to see this attachment.

[Joep 200]

Yes it's a string type in the Global Variable.

I would trigger on every change and check in the Lua code. First convert the Global Variable to an int with tonumber(var)

Edited May 19, 2022 by Joep

[jgab 2,642]

Documentation or not, it would be user friendly if something like

Please login or register to see this code.

generates an error if it's not allowed so people would quicker understand what the problem was...

[m.roszak 763]

But you can compare strings that way, it is not an error. Lua compares strings in alphabetical order.

Also in block scene only != and = operators are available to avoid confusion.

 

I am not sure why you are searching for a problem where there really isn't one.

 

 

 

[jgab 2,642]

22 minutes ago, m.roszak said:

But you can compare strings that way, it is not an error. Lua compares strings in alphabetical order.

Also in block scene only != and = operators are available to avoid confusion.

 

I am not sure why you are searching for a problem where there really isn't one.

Sorry, I stand corrected. I thought that it wasn't allowed in a condition and that it didn't work for him. 

...but still, no error message for .

Please login or register to see this code.

Seems to be no validation for conditions besides them having to be Lua tables.

[m.roszak 763]

I fully agree that we have a lot of work to do in the system.
I just assume that we are going in right direction if we are arguing about this kind of issues