Tutorial: Single scene instance / Event model

[iTibor 1]

Hi

 

If I use multiple conditions why doesn't work?  In EventRunner4 

  rule("@sunrise+07:00 & @sunset+00:10 & @@00:00:05 => log('apple ')")

 

this line in my interpretation must send messages between  sunrise +7 hours and sunset+10 min in every 5 seconds but,  only in this periods. But the sunrise and sunset criteria isn't applied. Why ?

 

 

Edited August 31, 2023 by iTibor
complete text

[Sjakie 156]

You request & so it will never be true!

sunrise+07:00..sunset00:10  this is between the two values

[iTibor 1]

This conditions mean between 13.40 and  20.40  - or something like this, but this rule("@sunrise+07:00 & @sunset+00:10 & @@00:00:05 => log('apple ')")  now in 11.50 doesn't have to show on the debug line de log message Alma , but does , in every 5 sec.

 

My initial goal it is to run a scene in every hour but only between sunrise +3 hour and sunset 

Edited August 31, 2023 by iTibor

[Sjakie 156]

Please login or register to see this code.

This shows every hour between sunrise + 3 hour and sunset

[iTibor 1]

3 hours ago, Sjakie said:

Please login or register to see this code.

This shows every hour between sunrise + 3 hour and sunset

Thank you very much . It's working.

How can I run a scene instead of printing a log message?

 

 

[Sjakie 156]

sceneID:start

[lux 14]

@jgabIs this still usable？
 

 

On 7/9/2022 at 3:25 PM, jgab said:

New version 0.81 with a new experimental feature - user action events.

 

When someone interacts with a device in the app there are events emitted with the device and userid.

Ex. a com.fibaro.multilevelSwitch device with id 756.

When the user with id 917 turn on, off and changes dimming we get the events

Please login or register to see this code.

 

Which means that we can create a rule like

rule("#user{id=917,value='action',data={id=756,actionName='turnOn'}} => log('Ann turned on the light')")

 

Beware that the normal event 

Please login or register to see this code.

is also emitted.

Also the order of the events seems to not be predictable. I've seen the #device event being fired after the #user event.

 

Anyway, will experiment more with it to see how it can be used.

 

 

Edited September 3, 2023 by lux

[iTibor 1]

On 9/1/2023 at 9:15 AM, Sjakie said:

sceneID:start

Thanks!

[Neo Andersson 230]

I have experimented some strange behavior. If someone can take a look at it?

 

Please login or register to see this code.

 

[lux 14]

 

@Neo Andersson

Please login or register to see this code.

 

Edited September 10, 2023 by lux

[jgab 2,641]

11 hours ago, Neo Andersson said:

I have experimented some strange behavior. If someone can take a look at it?

 

Please login or register to see this code.

 

Yes, the once(ext_lux_sensor:lux < 720) effectively disables the rule until the lux goes above 720 again (or you restart the QA and the rules start afresh again)

You need 'once' less than you think...

3 hours ago, lux said:

 

@Neo Andersson

Please login or register to see this code.

 

Yes, the || >> is an syntactic way to express if-then

Please login or register to see this code.

 

[Neo Andersson 230]

Hello guys

 

How can we access the value coming from an event on the action side of the rule?

In case of log function it is evidently like

Please login or register to see this code.

I have tried event like this

Please login or register to see this code.

 

On 9/10/2023 at 5:02 AM, lux said:

 

@Neo Andersson

Please login or register to see this code.

 

Yeah that is similar to 

Please login or register to see this code.

Thanks anyway

[jgab 2,641]

Please login or register to see this code.

The $ tells the engine that it's a variable you want to match against. But then the variable is used without the '$' in the rule. It becomes a rule local variable bound to the matched value

[Neo Andersson 230]

1 hour ago, jgab said:

Please login or register to see this code.

The $ tells the engine that it's a variable you want to match against. But then the variable is used without the '$' in the rule. It becomes a rule local variable bound to the matched value

Thanks, meanwhile I figured it out, that strings can not be concatenated on the right side of the rule...

Also found two examples in this topic, how to catch who accessed a door lock. I tried both, but none of them work. Is this a deprecated function, or i just didn't get the point?

Please login or register to see this code.

 

[jgab 2,641]

9 hours ago, Neo Andersson said:

Thanks, meanwhile I figured it out, that strings can not be concatenated on the right side of the rule...

Yes, they can, but the operator is '++' not '..'

'..' is reserved for time intervals.

 

9 hours ago, Neo Andersson said:

Also found two examples in this topic, how to catch who accessed a door lock. I tried both, but none of them work. Is this a deprecated function, or i just didn't get the point?

Please login or register to see this code.

 

It seems that it kind of depends on the lock.

Can you provide me of the log of the whole event. Like

Please login or register to see this code.

and see what it reports when you lock/unlock it?

 

The format

Please login or register to see this code.

don't work (anymore), the event that should be generated is

Please login or register to see this code.

and what's available after myLock:access... are the properties in value

 

[Neo Andersson 230]

4 hours ago, jgab said:

Yes, they can, but the operator is '++' not '..'

'..' is reserved for time intervals.

 

It seems that it kind of depends on the lock.

Can you provide me of the log of the whole event. Like

Please login or register to see this code.

and see what it reports when you lock/unlock it?

 

The format

Please login or register to see this code.

don't work (anymore), the event that should be generated is

Please login or register to see this code.

and what's available after myLock:access... are the properties in value

 

Jan, we have some other unexpected behaviours here. Custmer asked as to play some welcome message when directors arrive to office, once a day, when the first person arrives. So we created a rule like this.

 

Please login or register to see this code.

 

Edited September 13, 2023 by Neo Andersson

[Neo Andersson 230]

6 hours ago, jgab said:

Yes, they can, but the operator is '++' not '..'

'..' is reserved for time intervals.

 

It seems that it kind of depends on the lock.

Can you provide me of the log of the whole event. Like

Please login or register to see this code.

and see what it reports when you lock/unlock it?

 

The format

Please login or register to see this code.

don't work (anymore), the event that should be generated is

Please login or register to see this code.

and what's available after myLock:access... are the properties in value

 

This is what a recieved

Please login or register to see this code.

 

[jgab 2,641]

3 minutes ago, Neo Andersson said:

This is what a recieved

Please login or register to see this code.

 

Then you don't get an accessControlEvent from the lock - just a property change (and no user id)

Please login or register to see this code.

 

[jgab 2,641]

2 hours ago, Neo Andersson said:

Jan, we have some other unexpected behaviours here. Custmer asked as to play some welcome message when directors arrive to office, once a day, when the first person arrives. So we created a rule like this.

 

Please login or register to see this code.

 

Well, if you at the right hand do <expr> & <expr> & <expr> ... it will stop when the first expr becomes false.

My guess here is that broadcast() return nil - i.e. false, and the expression terminates and the CEO flag never gets set.

Make broadcast return true or rewrite 

Please login or register to see this code.

or alternatively

Please login or register to see this code.

or alternatively

Please login or register to see this code.

 

The second error doesn't make sense and I can't repeat it. You have some invisible unicode characters in that string?

[jgab 2,641]

19 minutes ago, jgab said:

Well, if you at the right hand do <expr> & <expr> & <expr> ... it will stop when the first expr becomes false.

My guess here is that broadcast() return nil - i.e. false, and the expression terminates and the CEO flag never gets set.

Make broadcast return true or rewrite 

Please login or register to see this code.

or alternatively

Please login or register to see this code.

or alternatively

Please login or register to see this code.

 

The second error doesn't make sense and I can't repeat it. You have some invisible unicode characters in that string?

 

The use case to do something once a day when something happens is quite common and there are different ways to solve it. Using a global variable to remember if it's done like you do is on approach.

One could also use something like

Please login or register to see this code.

Here we use a time period 6-9 and wrap it in a once(). This means that one time during the time period when the sensor is breached it will play the message.

The problem we have with once is that if there is no more sensor breach until 6-9 the next day, it will not play as the once is waiting for the condition to be false before triggering again (that's why once is tricky to use...)

We solve it by sending an event at midnight that "bypasses" the sensor and test the time interval, which will be false at 00:00 so it's enabled to return true again the next morning. 

 

In fact, @Sjakie and I spent some time on this some time ago and we come up with two solutions. There is an optional extra argument to once that is a time when the state should be cleared.

Please login or register to see this code.

so this also works.

There was also the "invention" of the time interval that is only true once a day, using 3 dots '...'

Please login or register to see this code.

It's kind of a forgotten command but I checked and it's still there.