Tutorial: Single scene instance / Event model

Sjakie · July 25, 2019

Guys I noticed also some strange things.

Its or me or the update. I can understand that if I work on the scene an error is my mistake. I am only working on one scene

Suddenly some devices are with error now in other scenesAfter @FrankT. remark I was restoring back

I am back on 4.54 to be stable again.

For example error >>could not find it copied it in a similar scene error gone!!

jgab · July 26, 2019

12 hours ago, FrankT said:

@jgab may be it's the heat giving me headache but my scene for blinds does not receive answer from NodeRed anymore. Now I have tested this

rule("remote(_myNodeRed,#echo{data='test'})")
rule("#response{data='$d'} => log('Got back:%s',d.data)")
rule([[remote(_myNodeRed,#wetter{})]])
rule([[#wetter => moln=env.event.data.clouds; log('moln= %s',moln)]])

Works ok in ZBS but when running on HC2 there is nothing:

[DEBUG] 16:26:20: NodeRed - EventRunner v2.0 B65
[DEBUG] 16:26:20: Fibaro software version: 4.550
[DEBUG] 16:26:20: HC2 uptime: 52 hours
[DEBUG] 16:26:20: Sunrise 04:54, Sunset 21:36
[DEBUG] 16:26:20: Hue system inited (experimental)
[DEBUG] 16:26:20:
[DEBUG] 16:26:20: Loading rules
[DEBUG] 16:26:20: Rule:1:#response{data='$d'} => log('Got back:%s',d.data)
[DEBUG] 16:26:20: Rule:2:#wetter => moln=env.event.data.clouds; log('moln= %s',moln)
[DEBUG] 16:26:20:
[DEBUG] 16:26:20: Scene running

Node Red debug shows:

2019-07-25 16:26:21node: Outgoing payloadecho : msg.payload : Object
object
args: array[2]
0: "%7B%22type%22:%22response%22,%22data%22:%7B%22data%22:%22test%22,%22type%22:%22echo%22,%22_from%22:397%7D%7D"
1: "%%ER%%"
2019-07-25 16:26:22node: Outgoing eventecho : msg.payload : Object
object
type: "response"
data: object
data: "test"
type: "echo"
_from: 397
2019-07-25 16:26:23node: Incoming event1echo : msg.payload : Object
{ data: "test", type: "echo", _from: 397 }
2019-07-25 16:26:24node: Incoming event1wetter : msg.payload : Object
{ type: "wetter", _from: 397 }

Could it be Fibaros new software 4.550?

I'm running 4.550 and it's working for me - just tested 'echo'.

Because it's working on ZBS, could it be that your HC2 has changed IP address? Or have you changed name/password?

Have you checked the HC2 node in the node-red flow? Mine look like below.

jgab · July 26, 2019

7 hours ago, Sjakie said:

Guys I noticed also some strange things.

Its or me or the update. I can understand that if I work on the scene an error is my mistake. I am only working on one scene

Suddenly some devices are with error now in other scenesAfter @FrankT. remark I was restoring back

I am back on 4.54 to be stable again.

For example error >>could not find it copied it in a similar scene error gone!!

So it's worked fine for me with 4.550 (knock on wood) but you guys are all running much more advanced ER scenes than I do these days...

In any case, I do keep an eye on if the Lua environment seems to change between releases, and fortunately Fibaro is very slow to make changes to

the basic Lua framework. Much more likely then that devices start to act up in various ways. More likely then ER's logic starting to fail due to a new release.

On my todo list is to build up a more extensive test set of rules (a test scene) to run on the HC2 to verify the logic. Now I only run some on the ZBS.

Sjakie · July 26, 2019

Hello Jan,

IOS locator did not work for me in 4.55

Since update I did not see the disarm by IPhone.

This morning I was pleasant surprised to see in debug "disarmed by IPhone" I will keep track of it.

FrankT · July 26, 2019

Checked IP, name/password in HC2 node - all ok. Rebooted PI running NR, influx and Grafana. Rebooted HC2. Rebooted PC running ZBS, Firefox. Working now, really mysterious.

jgab · July 26, 2019

During my "vacation" I have enjoyed myself with a rewrite of EventRunner. I have not released it yet and I will probably need some

parallel release model so you can continue with the old version. Because even if I'm trying to test everything I may have introduced new bugs....

A release like EventRunner3.lua will appear next week (It's version 3) and I will announce it and hope some of you will try it out.

Main changes

- Restructured the code so it is more modular

- Re-written the parser and compiler for EventScript

- New runtime for EventScript "code" based on a home-made coroutine implementation.

Most of old EventScript rules will work as is, but there are a few changes.

- 'for' ... 'repeat', has changed to 'trueFor' ... 'again'.

Rule.eval("for(00:10,55:isOn) => log('Hupp'); repeat(3)")

needs to be changed to

Rule.eval("trueFor(00:10,55:isOn) => log('Hupp'); again(3)")

- :armed will return true/false and be set with true/false.

 Rule.eval("66:armed=='1' => 77:armed='1'")

needs to be changed to

Rule.eval("66:armed => 77:armed=true")

There are some new EventScript functions and commands:

-- dusk and dawn, works like sunset/sunrise.

  Rule.eval("@dusk => 55:on")  
  Rule.eval("@dawn => 55:off")

-- if-then-elseif-end. (|| >> still exist)

   Rule.eval("@dusk => if 55:isOn then 55:on end")     
   Rule.eval("@dusk => if 55:isOn then 55:on else 44:on end")   
   Rule.eval("@dusk => if 55:isOn then 55:on elseif 44:isOff then 44:on elseif 33:isOn then 33:on end")

- while-do end, and repeat-until

   Rule.eval("@dusk => while 44:isOn do 44:off; wait(00:00:02) end")
   Rule.eval("@dusk => repeat 44:off; wait(00:00:02) until 44:isOff")

- for-do

   Rule.eval("lamps1={44,55,66}")  
   Rule.eval("lamps2={kitchen=44,bedroom=55,hall=66}")
   Rule.eval("@dusk => for index,id in ipairs(lamps1) do log('Turning on lamp %s',id); id:off end")   
   Rule.eval("@dusk => for name,id in pairs(lamps2) do log('Turning on lamp %s',name); id:off end")   
   Rule.eval("@dusk => for i=1,size(lamps1) do log('Turning on lamp %s',lamps1[i]); lamps1[i]:off end")

- Rule local variables. In the past, all ER variables where shared between all rules. Variables not declared local are shared as before.

  Rule.eval("local a,b=5,6; begin local a,c=10,6; log('%s',a*b") end;  log('%s',a*b")")

will print 60 and then print 30. All rules have an implicit begin-end (local block) around them.

for-do, while-do, repeat-until, and if-then-else have local blocks so iteration variables and local declaration stay in scope like "normal" programming languages.

- Lua "object oriented" function calls supported.

   Rule.eval("@dusk => fibaro:call(55,'turnOff')")

<name>:<name>(...) is assumed to be a object oriented function call. <name>:<name> is a property call like before

- New function 'pack' that captures multiple return values

  Rule.eval("@dusk => r=pack(fibaro:get(55,'value')); log('55 last changed %s',osdate('%c',r[2]))")

The new runtime for EventScript code allows for future interesting extension. Already now, making async functions synchronous is very easy.

  function foo(a,b) return {['<cont>']=function(cont) setTimeout(function() cont(a+b) end,5000) end} end
  rule("log('%s',foo(3,4))")

So, the Lua function 'foo' that gets called from the EventScript returns {['<cont>'],fun}. The runtime will then call the fun with a continuation (thanks to the coroutine implementation) that 'foo' will call with the result when finished (here after 5 seconds), and the runtime will continue executing from that point with the value returned (which is here given to 'log' and printed)

The advantage with this is that we can functions calling handlers in other scenes without having to post an event and wait for the returned event. We can hide that now in something that looks like a synchronous function call... more to come on that topic

Hopefully some improvements on error handling making it a bit easier to understand what have gone wrong when an error occurs.

Lots of small bugs where detected and corrected - some that impact the HC2 emulator too so it will also have a new release.

Sjakie · July 26, 2019

Hello Jan,

Thanks for your effort and looking forward to go with the new flow.

FrankT · July 26, 2019

Cool, I will test asp but away from aug 3 to aug 14. I like ”IF then ”

jompa68 · July 26, 2019

3 hours ago, jgab said:

I will announce it and hope some of you will try it out.

Count me in @jgab

Sjakie · July 27, 2019

Good morning Jan,

I am a bit lost. See this message for the first time. Later on it is executed, see debug in yellow!!

Now I also get the next error>>this cases the light is not switched off.

Rule.eval("for(00:05, woonkamer.televisie:power < 15) => log('TV off, power is now %s',woonkamer.televisie:power); woonkamer.televisie:off; log('TV uit indien hij 5 min op standbye staat')").start()

Disregard the other error message>> I am playing with it (hue rechts was marked with --)

Please advice

jgab · July 27, 2019

42 minutes ago, Sjakie said:

Good morning Jan,

I am a bit lost. See this message for the first time. Later on it is executed, see debug in yellow!!

Rule.eval("for(00:05, woonkamer.televisie:power < 15) => log('TV off, power is now %s',woonkamer.televisie:power); woonkamer.televisie:off; log('TV uit indien hij 5 min op standbye staat')").start()

Please advice

Yes, it's indeed strange. Actually, it doesn't seem like it's the "televisie" rule that is the problem. The error message complains about doing <deviceID>:on where <deviceID> is nil. I don't understand why it points at the "televisie" rule that doesn't have any :on command (only :off)... Do you have any rule nearby that does <deviceID>:on ?

jgab · July 30, 2019

Ok, I have uploaded EventRunner3.lua to GitHub. It can exist in parallell with the old version and will auto-update only v3 version.

There are some changes to make old rules run.

"for - repeat", need to be changed to "trueFor - again"
<deviceID>:armed returns true/false instead of '0'/'1'. And is set to true/false to arm and disarm
A bit changed Node-red flow. All events from node-red arrives as {type='NODERED', value=<event>}. To be compatible in the old EventRunner just add
Rule.eval("#NODERED{value='$val'} => post(val)"). In EventRunner3 that is the default behaviour. However, we need the 'NODERED* wrapper to catch synchronous nodered calls (see below).

New node-red flow

Spoiler

New stuff:

dawn/dusk. Like sunrise/sunset but the time it actually gets light and when it actually gets dark. It Stockholm it's now almost an hour difference.

  rule("log('Difference between dusk and sunset is %s',osdate('%H:%M',dusk-sunset))")
  rule("log('Difference between dusk and sunset is %s',osdate('%H:%M',sunrise-dawn))")

function nodered(<event>[,<req>,<node>]). Sends event to node-red. Uses local _defaultNodeRed as node but can be provided as third argument <node>. If <req> is false or excluded it just sends a standard asynchronous event to node-red as with 'remote' in the past. With <req> set to true it will return the resulting event synchronously...
```
rule("log('Echo returns '%s',nodered(#echo{test='Hello'},true).data.test))")
```
#echo returns {type='response', data={test='Hello'}}. With <req> set to true nodered(...) will return that event. And we access the test field with .data.test. This means that we hide the asynchronous nature of communicating with node-red and make it look like calling regular functions that returns values.
Only set <req> to true if the nodered flow returns an event, otherwise you will get a timeout error.
if-then-else-elseif-end. if-then-else is a statement and can only be used on the right-hand side of rules.
repeat <statements> until <test>. Statement and can only be used on the right-hand side of rules.
while <test> do <statements> end. Statement and can only be used on the right-hand side of rules.
local variables in rules. Temporary variables only active when rule executes.
capture of multiple values from lua functions returning multiple values using function pack().
```
rule("a = pack(fibaro:get(99,'value')); log('Last changed %s',osdate('%x',a[2]))")
```
Calling of "object oriented" lua functions using ':'. Mostly useful for calling fibaro functions (see previous example).

Auto conversion of values from fibaro globals.
If a fibaro global is set to the strings "true"/"false"/"True"/"False"/"TRUE"/"FALSE" it will automatically be converted to a boolean when accessed. If it contains a time string ex. "10:00" it will be converted to number of seconds. Otherwise it will return just the string.

rule("$Test=true") -- fibaro global will be set to string "true"
rule("$Test==true") -- fibaro global auto converts back to boolean and test will be true
rule("$Test=='10:00'") -- fibaro global set to string "10:00"
rule("$Test==10:00") -- fibaro global auto converts back to number and test will be true
rule("$Test='t/10:00'") -- fibaro global set to time string (epoc today at 10:00)
rule("$Test==midnight+10:00") -- fibaro global auto converts back to number and test will be true

Oh, and please update to the latest HC2.lua if trying it out on ZBS. You may need to regenerate the HC2.data file. (complaining about 'settings/network' missing)

Things to do.

provide a synchronous httprequest function similar to nodered (like it works in VDs)
improve error messages
more test-cases

Edited August 9, 2019 by jgab

jompa68 · July 30, 2019

@jgab you have an working example of and puslish rule?

rule("pirSensor.hallNere:value => publish(#VirtualSensor{deviceID=pirSensor.hallNere,value=pirSensor.hallNere:value})")

jgab · July 30, 2019

35 minutes ago, jompa68 said:
@jgab you have an working example of and puslish rule?
rule("pirSensor.hallNere:value => publish(#VirtualSensor{deviceID=pirSensor.hallNere,value=pirSensor.hallNere:value})")

I need more info on what you want to achieve.

You publish the virtual sensor from one scene and subscribe to it from another scene. What else would you like it to do?

jompa68 · July 30, 2019

2 minutes ago, jgab said:

I need more info on what you want to achieve.

You publish the virtual sensor from one scene and subscribe to it from another scene. What else would you like it to do?

Yes, pub/sub to turn on/off devices

or is it better just the normal way?

got an error now in ZBS on first publish rule

Edited July 30, 2019 by jompa68

jgab · July 30, 2019

2 minutes ago, jompa68 said:

Yes, pub/sub to turn on/off devices

or is it better just the normal way?

So it's not a "real" fibaro device? A fake device (Event._registerID) ? A wrapper for some node-red accessed device?

Edited July 30, 2019 by jgab

jompa68 · July 30, 2019

No, a real device

Sjakie · July 30, 2019

Hello Jan,

I will try!

IOSLocator

I came home at 11:55 No post

If I change something in the scene and save it will post.

Please advice,

jgab · July 30, 2019

Just now, jompa68 said:

No, a real device

But I guess you can just call <deviceID>:off from the subscribing scene then? or fibaro:call(<device>,"turnOff"). or?

If you i the subscribing scene do

rule("#VirtualSensor{deviceID='$deviceID',value='$value'} => post($property{deviceID=deviceID,value=value,propertyName='value'})")

you should be able to do

rule("pirSensor.hallNere:breached => log('Sensor breached')")

jompa68 · July 30, 2019

2 minutes ago, jgab said:

But I guess you can just call <deviceID>:off from the subscribing scene then? or fibaro:call(<device>,"turnOff"). or?

If you i the subscribing scene do

rule("#VirtualSensor{deviceID='$deviceID',value='$value'} => post($property{deviceID=deviceID,value=value,propertyName='value'})")

you should be able to do

rule("pirSensor.hallNere:breached => log('Sensor breached')")

try to explain better, sorry for lack of info.
This is the error i get in ZBS, only started with my first V3 scene (publish scene)

[31mTue/Jul/30,12:03:40:[32:1] Error in 'pirSensor.hallNere:value => publish(#VirtualSensor{deviceID=pirSensor.hallNere,value=pirSensor.hallNere:value})': EventRunnerPub.lua:1752: attempt to index local 'res' (a nil value)[0m
[31mTue/Jul/30,12:03:40:[32:1] 
Line 1750:    end
Line 1751:  end
Line 1752:>>>  function self.eval2(env) env.cp=nil; env.locals = env.locals or {}; local _,res=self.eval(env) return res[1] end
Line 1753:  return self
Line 1754:end
[0m
[31mTue/Jul/30,12:03:40:[32:1] Error loading rules:EventRunnerPub.lua:1916: EventRunnerPub.lua:1752: attempt to index local 'res' (a nil value)[0m
[32mTue/Jul/30,12:03:40:[HC2 ] Scene [32:1] terminated (thread: 0x02d45550)[0m

Tutorial: Single scene instance / Event model

Recommended Posts

Sjakie 40

Link to post

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Posted Images

jgab 901

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

Sjakie 40

Link to post

Share on other sites

FrankT 0

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

Sjakie 40

Link to post

Share on other sites

FrankT 0

Link to post

Share on other sites

jompa68 121

Link to post

Share on other sites

Sjakie 40

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

jompa68 121

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

jompa68 121

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

jompa68 121

Link to post

Share on other sites

Sjakie 40

Link to post

Share on other sites

jgab 901

Link to post

Share on other sites

jompa68 121

Link to post

Share on other sites

Join the conversation