EventRunner 5

[Sjakie 138]

Jan I have a problem how to tackle? I do one cycle deur OPEN and Nachtslot

than I press an press and press............................no action only false.

I have 3 HUE switches who act all the same. I also tried HoldDown same result.

In history I see every push on the button

 

 

Please login or register to see this code.

 

[jgab 2,083]

2 minutes ago, Sjakie said:

Jan I have a problem how to tackle? I do one cycle deur OPEN and Nachtslot

than I press an press and press............................no action only false.

I have 3 HUE switches who act all the same. I also tried HoldDown same result.

In history I see every push on the button

 

 

Please login or register to see this code.

 

How are these Hue switches integrated with the HC3? Using childrenOfHue?

[Sjakie 138]

Yes in your COH 1.22

Pressed followed automaticaly by released,  HoldDown >> shows in history

[jgab 2,083]

There is also the approach that one builds a more complex tree of devices, like

local HT = {

   kitchen = { lights = { tableLight=88,  roofLamp=99 }, sensors = { sensor1 = 53, sensor2 = 51 }},

   hall = { lights = {  roofLight1 = 101, roofLight2 = 109 }},

   bedroom = { lights = { roofLight = 201, bedTableLight1 = 204, bedTableLight2 = 205 }}

}

 

One could also generate this table by leveraging the rooms and sections that devices are placed in.

 

Anyway, I'm sharing a feature that comes up in next version, a new property called :leaf 

The reasoning is that the hometable, (or other ER defined variable with deviceIds) can be seen as a tree,

where ex. kitchen in this example has 2 leafs, tableLight and roofLight.

 

This is a good structure, but it also means that we can't do

Please login or register to see this code.

because kitchen.lights is not a list of devices, it's a key-value table, so it doesn't work.

Well, :leafs takes an arbitrary complex key-value table and returns a list with the leafs (removing duplets)

so, we can now do

Please login or register to see this code.

...and it turns on all lights in the kitchen, without the need for a duplicate list variable.

 

I'm also thinking how to filter out appropriate devices from the list , ex. only the lights or only the sensors...

[jgab 2,083]

6 minutes ago, Sjakie said:

Yes in your COH 1.22

Pressed followed automaticaly by released,  HoldDown >> shows in history

 

I'm not sure I understand what you want to do. The log show that the rules trigger on 1:Pressed and 4:Pressed

What is not working as expected?

[Sjakie 138]

Jan with the lights on/off I don't have a problem.

I have aproblem withGV's sometimes they don'follow the rule fa

Please login or register to see this code.

If I check it's still $Verl_Dagdeel = 'Middag_Vroeg' so it skipped two other parts???

 

the false in the log are also press the button

but no respond in QA it show the action in History

[Sjakie 138]

Jan I never used those HUE dimmers in HC3.

Here in ER% I got the idea to use them for enable arming if we go to sleep and to open manual by this switch the Dana lock, both a WAF project.

So no experience how it should behave

For HUE lights I have the grouped them in HUE app and don't often use a single light, if Ido it's to set different valus for brightness

 

Edited November 25, 2023 by Sjakie
add HUE

[jgab 2,083]

9 minutes ago, Sjakie said:

the false in the log are also press the button

but no respond in QA it show the action in History

The false in the logs are "Released" or "HeldDown" or the wrong keyId and thus false as far as I can see.

[jgab 2,083]

14 minutes ago, Sjakie said:

Jan with the lights on/off I don't have a problem.

I have aproblem withGV's sometimes they don'follow the rule fa

Please login or register to see this code.

If I check it's still $Verl_Dagdeel = 'Middag_Vroeg' so it skipped two other parts???

 

Well, using an interval like this as a trigger is not so good.

An interval like 12:00..16:15-1

will trigger the rule at 12:00 and at 16:15-1+1

The first trigger will be true, because it's 12:0, the second will be false because the time is > 16:15-1

So, in effect, your rules trigger at 12:00, 16:15, and 18:00 respectively.

That means that if you restart the QA at 18:15 it will not trigger and change the variable.

You could add a .start() at the end of the each rule to trigger them at restart so that the varible is set accordingly.

[Sjakie 138]

Please login or register to see this code.

All button pressed after 19:53:32 are false!!!

In history I see 

Please login or register to see this code.

Losgelaten>>Releasedbut I also press before I can release??

It's the same device

[ChristianSogaard 61]

5 hours ago, ChristianSogaard said:

When using tryArm like this

Please login or register to see this code.

seems to work fine -ALARM cancel the arming if a windows is opened.

But next step is post a message, which windows is opened. and i was expecting that below rule would give me that,.

from the log, it seems that it newer triggers ?

 

 

Please login or register to see this code.

 

 

 

Its strange

Trigger of the rule works.

But even if my 3 alarm zones already are armed, it always run the !0:armed >> 0:tryArm.

It sould be a toggle function enable/disable the alarm.

 

Please login or register to see this code.

Please login or register to see this spoiler.

 

[Pica2017 2]

Jan error posting scene events. I have added "sceneEvent" to self:enableTriggerType

 

I use scene event, the scene itself is empty and used as a trigger that ER can read to do its thing (your code aswell  )  I can then also use an apple shortcut to set an alarm dynamically called sunrise nursery to call the same scene.

 

I'm getting this error

 

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:28:3]>> TRUE #sceneEvent{id=11,.. -> #sceneEvent{id=11,value='started'} => ..

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:28:3]>> Posting #sceneEvent11{} at Sun Nov 26 13:33:01 2023

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:29:3]>> TRUE #sceneEvent11{} -> #sceneEvent11 => 60: value = 0; 60:on;..[

26.11.2023] [13:33:01] [ERROR] [ER311]: [Rule:29:3]>> [Rule:29:#sceneEvent11 => 60: value = 0; 60:on; 60:dim = {00:15:00, 'up', 00:00:01, 'Li..] Runtime: ./include/utils.lua:319: attempt to call a nil value (method 'post') putprop
#sceneEvent11 => 60: value = 0; 60:on; 60:dim = {00:15:00, 'up', 00:00:01, 'Linear', 0.99}; log('sceneEvent11 Sunrise nursery started')

[minsad79 19]

hi jan

 

EventRunner 5

In

   -- Bathroom, uses a local flag (inBathroom)
   rule("trueFor(00:00:20,Livingbath_sensor:safe & Livingbath_door:value) & !inlivingBathroom => Livingbath_light:off")
   rule("Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Livingbath_light:on")
   rule("Livingbath_door:breached => inlivingBathroom=false ")
   rule("Livingbath_door:safe & Livingbath_sensor:last<=3 => inlivingBathroom=true")

Doesn't this rule support this action?
 
Normal in ER4, error in ER5

[jgab 2,083]

3 hours ago, Pica2017 said:

Jan error posting scene events. I have added "sceneEvent" to self:enableTriggerType

 

I use scene event, the scene itself is empty and used as a trigger that ER can read to do its thing (your code aswell  )  I can then also use an apple shortcut to set an alarm dynamically called sunrise nursery to call the same scene.

 

I'm getting this error

 

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:28:3]>> TRUE #sceneEvent{id=11,.. -> #sceneEvent{id=11,value='started'} => ..

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:28:3]>> Posting #sceneEvent11{} at Sun Nov 26 13:33:01 2023

[26.11.2023] [13:33:01] [TRACE] [ER311]: [Rule:29:3]>> TRUE #sceneEvent11{} -> #sceneEvent11 => 60: value = 0; 60:on;..[

26.11.2023] [13:33:01] [ERROR] [ER311]: [Rule:29:3]>> [Rule:29:#sceneEvent11 => 60: value = 0; 60:on; 60:dim = {00:15:00, 'up', 00:00:01, 'Li..] Runtime: ./include/utils.lua:319: attempt to call a nil value (method 'post') putprop
#sceneEvent11 => 60: value = 0; 60:on; 60:dim = {00:15:00, 'up', 00:00:01, 'Linear', 0.99}; log('sceneEvent11 Sunrise nursery started')

Sorry, this was a bug in the dim code. Next version today will have a fix.

[jgab 2,083]

11 hours ago, ChristianSogaard said:

Its strange

Trigger of the rule works.

But even if my 3 alarm zones already are armed, it always run the !0:armed >> 0:tryArm.

It sould be a toggle function enable/disable the alarm.

 

Please login or register to see this code.

Please login or register to see this spoiler.

What error do you get?

[minsad79 19]

3 minutes ago, jgab said:

Sorry, it was a bug in 0:armed (whole house). Fixed in next version.

What error do you get?

[2023-11-26] [03:23:10 PM] [ERROR] [QUICKAPP2300]: Last err: [Rule:2:Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Li..] Parser: left hand side of assignment unsupported Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Livingbath_light:on ^

[jgab 2,083]

45 minutes ago, minsad79 said:

[2023-11-26] [03:23:10 PM] [ERROR] [QUICKAPP2300]: Last err: [Rule:2:Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Li..] Parser: left hand side of assignment unsupported Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Livingbath_light:on ^

Yes, there is a change in ER5 language.

In ER4

a & b = c & d

was interpreted as

a & (b = c) & d

in ER5 it is interpreted as

(a & b) = (c & d)

because & has higher priority than =

To fix you rule add parenthesis around the assignment

 

Please login or register to see this code.

 

[jgab 2,083]

v0.34 pushed

Fixed bugs causing problems for @Sjakie and his key rules

Also, a general bug for trigger handling so I recommend all to update.

Fixed 0:armed bug ( @ChristianSogaard )

dim bug fixed ( @Pica2017 )

 

 

Edited November 26, 2023 by jgab

[Sjakie 138]

Good morning and thank you verry well!

[jgab 2,083]

4 hours ago, minsad79 said:

hi jan

EventRunner 5

In

   -- Bathroom, uses a local flag (inBathroom)
   rule("trueFor(00:00:20,Livingbath_sensor:safe & Livingbath_door:value) & !inlivingBathroom => Livingbath_light:off")
   rule("Livingbath_sensor:breached => Livingbath_door:safe & inlivingBathroom=true; Livingbath_light:on")
   rule("Livingbath_door:breached => inlivingBathroom=false ")
   rule("Livingbath_door:safe & Livingbath_sensor:last<=3 => inlivingBathroom=true")

Doesn't this rule support this action?
 
Normal in ER4, error in ER5

When I got this problem report from @minsad79 I tried to run it, but I figured out quickly that it was an issue with the new language in ER5.

 

However, to debug this kind of rules, one can setup a simple simulation of the devices involved.

Please login or register to see this code.

Redefine the sensors and lights 'Livingbath_x" with simulated binaryDevices.

er.createBinaryDevice() creates a simulated binary device and returns the assigned deviceId.

 

Then we have the bathroom rules as usual - now using our simulated devices.

 

Then I setup a remote/keyfob so key presses toggles the door and motion sensor and logs a message what new state they have.

I also setup debug options so the console output is not so noisy

Please login or register to see this code.

 

Then I can lean back, press the remote to toggle the state of the door and the sensor and see how the rules are triggered...

WIthout having to run to the bathroom and open and close any door or breach any sensor  

 

Edited November 26, 2023 by jgab