Tutorial: Single scene instance / Event model

[jgab 2,642]

On 5/11/2021 at 10:42 PM, Sjakie said:

Jan,

I have  a problem again.

Curtains operating for months without any problem today curtain (gorijnOpRit) did not close.

Please login or register to see this code.

According debug the command was given. The curtain was just a tad not complete open I dont know if HC3 started to close for  a part of a second???

The Rule is:

Please login or register to see this code.

I added to prevent again malfunction      wait(00:00:05); woonKamer.gordijnOpRit:close;

Any idea what I can improve or is this Fibaro? This happends also a few days ago with a HUE light

Thanks,

//Sjakie

It seems like a device issue - maybe blame Fibaro

I was thinking that you could send another #eveningCurtain event a few seconds later so it tries to close the curtain again if it's not closed?

 

Please login or register to see this code.

Here we post another 10s later (assuming that curtains close in less than 10s). If the curtains are closed it will be ignored (woonKamer.gordijnOpRit:value > 0) and if not it will try to close again.

 

Beware, if the curtains start to close and you change your mind and manually stops, and open it, it will try to close again after 10s...

[Sjakie 156]

Stupid me! I was relaying on your excellent error reporting of HC3, now it did not show any error (HC2).

Sorry Jan

Thanks!

//Sjakie

[Sjakie 156]

Jan,

"Beware, if the curtains start to close and you change your mind and manually stops, and open it, it will try to close again after 10s... "

 

This will not be a problem because we dont have any manual switch. Thanks for the warning.

I already had a post(#morningCurtain,+/00:20) for in case one of the curtains did not open.

I will adapt yours too.

Thanks

 

I open locally HC3 and I see from QA's all debug windows are empty????

HA was functioning.

Did a restart

 

 

 

 

[jwi 53]

2 hours ago, jgab said:

I'm happy to answer basic/easy questions - they are the best - so keep them coming

Thanks Jan, I'll do that. It is a little difficult to search over 150 forum pages for an

answer, but I try hard and am willing to learn. Hope the stupid questions get less and less.?

[Sjakie 156]

Jan, I still try to find a way to boost my bathroom scene.

door sensor and  PIR in-and outside.

$Bathroom='Occupied'  and = 'Free' to switch light and suction on.

I tried to combine both deftriggers but that is not perfect too

Second person in makes trouble! Light switch off.

So action occupied or Free should be taken short after door is closed by bathroom.pir

Please login or register to see this code.

 

Can I add some time with bathroom.pir:last<=3 to improve? I dont mind if bathroom light stays on for let say 1 minute longer to tackle this problem?

I hope you have a good work around?

Thanks in advance,

//Sjakie

 

 

 

 

[Momos 103]

Any idea please why Rule 4 sometimes does not trigger ? I have to wait 20-30 sec and then it triggers the lights.  Both times the rule is evaluated as true but sometimes it just doesnt fire the action.

 

The rule is : 

 

rule("PIRFibaroBirou:breached  => LightSensorBirou:lux < 20 & PlafonieraBirou:on & ScafaBirou:on ")

 

Thank you  

 

Please login or register to see this attachment.

[systemfel 21]

On 5/13/2021 at 1:23 PM, Sjakie said:

Jan, I still try to find a way to boost my bathroom scene.

door sensor and  PIR in-and outside.

$Bathroom='Occupied'  and = 'Free' to switch light and suction on.

I tried to combine both deftriggers but that is not perfect too

Second person in makes trouble! Light switch off.

So action occupied or Free should be taken short after door is closed by bathroom.pir

Please login or register to see this code.

 

Can I add some time with bathroom.pir:last<=3 to improve? I dont mind if bathroom light stays on for let say 1 minute longer to tackle this problem?

I hope you have a good work around?

Thanks in advance,

//Sjakie

 

 

 

 

 

5 hours ago, Momos said:

Any idea please why Rule 4 sometimes does not trigger ? I have to wait 20-30 sec and then it triggers the lights.  Both times the rule is evaluated as true but sometimes it just doesnt fire the action.

 

The rule is : 

 

rule("PIRFibaroBirou:breached  => LightSensorBirou:lux < 20 & PlafonieraBirou:on & ScafaBirou:on ")

 

Thank you  

 

Please login or register to see this attachment.

 is ther 2 lights ? 

 

 

rule("PIRFibaroBirou:breached & LightSensorBirou:lux < 20 => PlafonieraBirou:on & ScafaBirou:on ")

[jgab 2,642]

11 hours ago, Momos said:

Any idea please why Rule 4 sometimes does not trigger ? I have to wait 20-30 sec and then it triggers the lights.  Both times the rule is evaluated as true but sometimes it just doesnt fire the action.

 

The rule is : 

 

rule("PIRFibaroBirou:breached  => LightSensorBirou:lux < 20 & PlafonieraBirou:on & ScafaBirou:on ")

 

Thank you  

 

Please login or register to see this attachment.

The first log 20:17:09 tells us that rule4 triggered (PIR). The lights are not called to turnOn so I must assume that the lux was not < 20.

20:18:00 it is triggered again (PIR) and now the lights are turned on, which means that the lux is < 20.

Can it be that you open the door and light comes in to make the lux sensor give a higher value? Also, lux sensor are quite slow devices in their reporting.

I would add to the rule

Please login or register to see this code.

just to see if the lux is what you expect. If it's < 20 and the action is not called then I investigate further.

You could also move the lux test before the '=>'. That way you will see if the conditions are ok also.

Please login or register to see this code.

 

[jgab 2,642]

On 5/13/2021 at 1:23 PM, Sjakie said:

Jan, I still try to find a way to boost my bathroom scene.

door sensor and  PIR in-and outside.

$Bathroom='Occupied'  and = 'Free' to switch light and suction on.

I tried to combine both deftriggers but that is not perfect too

Second person in makes trouble! Light switch off.

So action occupied or Free should be taken short after door is closed by bathroom.pir

 

Can I add some time with bathroom.pir:last<=3 to improve? I dont mind if bathroom light stays on for let say 1 minute longer to tackle this problem?

I hope you have a good work around?

Thanks in advance,

//Sjakie

So, you have 3 sensors. One PIR and one door sensor to the bathroom and one door sensor to the shower?

badKamer.pir

badKamer.deur

badKamer.doucheDeur

...and if it's occupied keep the lights on and if it's free start the fan?

Is that correct?

[Sjakie 156]

Jan,

The badKamer.doucheDeur:safe, this shower is in the bathroom and is having a door so if shower being used NO movement detected by PIR bathroom.

So I seperated the rules one set with:

-badKamer.doucheDeur:breached => lights and fan on. 

Devices inside bathroom:

-badKamer.doucheDeur:safe always in combination with:

badKamer.pir

badKamer.deur

overLoop.pir>>outside bath room

 

I hope its clear now,

//Sjakie

[jgab 2,642]

14 hours ago, Sjakie said:

Jan,

The badKamer.doucheDeur:safe, this shower is in the bathroom and is having a door so if shower being used NO movement detected by PIR bathroom.

So I seperated the rules one set with:

-badKamer.doucheDeur:breached => lights and fan on. 

Devices inside bathroom:

-badKamer.doucheDeur:safe always in combination with:

badKamer.pir

badKamer.deur

overLoop.pir>>outside bath room

 

I hope its clear now,

//Sjakie

but this badKamer.doucheDeur is a door sensor? That is safe if the door to the shower is closed?

I guess it's closed when someone takes a shower, but I also guess that it can be left either open or close when the shower is over and the person leaves? (I'm trying to understand the "significance" of the badKamer.doucheDeur sensor)

[Sjakie 156]

Good morning Jan.

I understand the "confusing"  badKamer.doucheDeur is a door sensor.

If door is closed >>>safe

if door is open>>breached>>>normal position door is always open till somebody takes a shower.

Let me include the rules I have at this moment.

Please login or register to see this code.

Thanks for your time and support,

//Sjakie

[jgab 2,642]

Pushed v52 (no beta schema yet)
Alarm handling has been improved.

 

Arming
rule("2:alarm=true")  -- arm partition 2
rule("0:alarm=true")  -- arm all partitions
Disarming
rule("2:alarm=false")  -- disarm partition 2
rule("0:alarm=false")  -- disarm all partitions
Check/trigger if armed
rule("2:armed => log('partition 2 armed')")
rule("0:armed => log('house armed')")

rule("{...}:armed => log('at least one is armed')")
rule("{...}:allArmed => log('all armed')")
rule("#alarm{id='$id',property='armed',value=true} => log('partition %s armed',id)")
rule("#alarm{property='homeArmed', value=true} => log('house armed')")
Check/trigger if disarmed
rule("2:disarmed => log('partition 2 disarmed')")
rule("0:disarmed => log('house disarmed')")

rule("{...}:disarmed => log('all are disarmed')")
rule("{...}:anyDisarmed => log('at least one is disarmed')")
rule("#alarm{id='$id',property='armed',value=false} => log('partition %s disarmed',id)")
rule("#alarm{property='homeArmed', value=false} => log('house disarmed')")

Watch/trigger if partition is enabled (starting 'exit delay')

rule("2:alarm='watch'; log('watching partition 2')")
rule("0:alarm='watch'; log('watching all partitions')")

rule("2:willArm => log('partition 2 will arm in %ss',env.event.value)")

rule("0:willArm => log('house will arm soon')")

rule("#alarm{id='$id',property='willArm',value='$secs'} =>  log('partition %s will arm in %ss',id,sec)")

Getting name of partition

rule("log('partition 2 name is %s',2:alarm.name)")

Check if a partition have breached sensors

rule("log('partition2 has %s devices breached',2:alarm.devices:breached & 'some' | 'no')")

 

Some more examples here

 

 

 

Edited May 17, 2021 by jgab

[Sjakie 156]

Jan, I asume armed should be disarmed?

Please login or register to see this code.

Busy to change my arming scene,

//Sjakie

[jgab 2,642]

yes

[Momos 103]

On 5/15/2021 at 8:23 AM, jgab said:

On 5/14/2021 at 8:27 PM, Momos said:

Any idea please why Rule 4 sometimes does not trigger ? I have to wait 20-30 sec and then it triggers the lights.  Both times the rule is evaluated as true but sometimes it just doesnt fire the action.

 

The rule is : 

 

rule("PIRFibaroBirou:breached  => LightSensorBirou:lux < 20 & PlafonieraBirou:on & ScafaBirou:on ")

 

Thank you  

 

Please login or register to see this attachment.

Please login or register to see this link.

The first log 20:17:09 tells us that rule4 triggered (PIR). The lights are not called to turnOn so I must assume that the lux was not < 20.

20:18:00 it is triggered again (PIR) and now the lights are turned on, which means that the lux is < 20.

Can it be that you open the door and light comes in to make the lux sensor give a higher value? Also, lux sensor are quite slow devices in their reporting.

I would add to the rule

Please login or register to see this code.

just to see if the lux is what you expect. If it's < 20 and the action is not called then I investigate further.

You could also move the lux test before the '=>'. That way you will see if the conditions are ok also.

Please login or register to see this code.

 

Nope the lux was the same in both instances.  Door stays always opened. I just walked in , rule triggered but nothing happened, then i just waited next to the Motion sensor to trigger again. Second time lights turned on. Added the log rule anyhow and will report back next time it happens.

 

I moved the lux part after the '=>' as per your suggestion some 1-2 pages back.  Because if the lux is on the left side (where i think it should be)  i can not switch the lights off from the switch next to the door. (sensor trips while i walk out the room , i close the lights, sensor trips again after if closes - Fibaro motion sensor - lights turn on again ?)

 

Cheers  

 

 

 

[Sjakie 156]

Jan,

Curtain is still acting up, now its another one!

THe post curtain delayed does not functioning

This works at the moment:

Please login or register to see this code.

In debug the curtain was closed.

If I try to open wth a rule it did not do anything.

With above rule I hope problem will be solved. Wierd this is hapening after 4,5 months working without any problem.

NOTE:

If I save the QA curtain goes open en closes again and its not the new rule??????????????

Please login or register to see this code.

//Sjakie

[Sjakie 156]

We lost isUnsecure2 and Secure2 in fix 53?

//Sjakie

[kuauka23 0]

Hola, muchas gracias por la info ... aunque soy nuevo en este mundo asombroso, lo voy a aplicar en uno de mis proyectos.

¡Saludos! 

Please login or register to see this link.

?

Edited May 17, 2021 by kuauka23

[jgab 2,642]

7 hours ago, Sjakie said:

We lost isUnsecure2 and Secure2 in fix 53?

//Sjakie

Secure2 has never been part of ER4. Only ER3, and still is.