Tutorial: Single scene instance / Event model

[jgab 2,642]

2 minutes ago, Sjakie said:

I did it again and copied from github hehe its running

 

Great!

then we can deal with all the other problems.

I saw that you already defined a lot of rules. I would advise to comment out most of them and test and try out small subsets so you know they are ok. It's much easier to spot rules behaving badly that way.

[Sjakie 156]

I opend my Eventrunner (copied into Zerobrane) and no errors

Yep I created almost all my rules I need and will follow your advice.

What is preferable usage for time related rules? GV  or also direct time trigger @08:00 instead of $DayTime

please advice

 

[Sjakie 156]

Hi jgab,

I think :isClose does not has effect

If I change the trigger the curtainfront  close

the others does not follow

 

--Gordijnen sluiten lux 60
  Rule.eval("once(lightSensorBuVoor:lux < 2100) & once(16:35..23:00) => curtainFront:close")  
  Rule.eval("curtainFront:isClose => wait(00:00:10); curtainSideCar:close")   
  Rule.eval("curtainFront:isClose => wait(00:00:15); curtainSideBicycle:close")  
  Rule.eval("curtainFront:isClose => wait(00:00:20); curtainBack:close")
  Rule.eval("curtainFront:isClose => wait(00:00:05); curtainBackSide:close")

 

[jgab 2,642]

1 hour ago, Sjakie said:

Hi jgab,

I think :isClose does not has effect

If I change the trigger the curtainfront  close

the others does not follow

 

--Gordijnen sluiten lux 60
  Rule.eval("once(lightSensorBuVoor:lux < 2100) & once(16:35..23:00) => curtainFront:close")  
  Rule.eval("curtainFront:isClose => wait(00:00:10); curtainSideCar:close")   
  Rule.eval("curtainFront:isClose => wait(00:00:15); curtainSideBicycle:close")  
  Rule.eval("curtainFront:isClose => wait(00:00:20); curtainBack:close")
  Rule.eval("curtainFront:isClose => wait(00:00:05); curtainBackSide:close")

 

 

My problem is that I don't have any roller shutters and I'm a bit unsure how they work.

On the HC2. if you do fibaro:call(21,"open") and you have declared %% properties 21 value

vill the scene receive a sourceTrigger of type {type='property', deviceID=21, propertyName='value'} ?

If so, I have uploaded a patched version of EventRunner.lua ("2.0","B25") that make your rules work on the emulator (I hope)

[Sjakie 156]

Hi,

 

fibaro:call(50, "setValue", "100");   >>>open
    fibaro:call(52, "setValue", "0");   >>>>close

There are 3 commands  also "stop"
 

[Sjakie 156]

sorry but what is than exactly the rule?

 Rule.eval("once(lightSensorBuVoor:lux < 100) & once(16:35..23:00) => curtainFront ,value, 0")  

gives no error but does not work sorry

[jgab 2,642]

1 hour ago, Sjakie said:

sorry but what is than exactly the rule?

 Rule.eval("once(lightSensorBuVoor:lux < 100) & once(16:35..23:00) => curtainFront ,value, 0")  

gives no error but does not work sorry

You're rule should look like

Please login or register to see this code.

if you want to close the curtainFront:close

...and wrap the whole condition in once(...), otherwise you don't get the logic you most probably want.

[Sjakie 156]

97 lux front  curtainFront closed

front 51 back 81 lux  side car and back closed

front 28   back 45    side closed

 

  Rule.eval("lightSensorBuVoor:lux < 150 & 16:35..23:00 => curtainFront:close")  

    Rule.eval("lightSensorBuAchter:lux < 180 & 16:35..23:00 => curtainSideCar:close")  

    Rule.eval("lightSensorBuVoor:lux < 180 & 16:35..23:00 => curtainSideBicycle:close")  

    Rule.eval("lightSensorBuAchter:lux < 180 & 16:35..23:00 => curtainBack:close")  

    Rule.eval("lightSensorBuVoor:lux < 180 & 16:35..23:00 => curtainBackSide:close")  

Between front and back lux value difference can be 100 lux

Weird spread must check again tomorrow

 

 

[Sjakie 156]

Hi jgab,

Is this not to much? Only 14-16 are comming short after each other.

Please login or register to see this image.

/monthly_2019_04/image.png.600de4cb939c68d5ed3371ef79d2f2df.png" alt="image.png.600de4cb939c68d5ed3371ef79d2f2df.png" />

[Sjakie 156]

Good morning jgab,

Outside lights where off this morning and the curtains open (99%)

Now I want to add my Hue lights I have read the part about Hue and have some questions

ER is sending the signals to HC2

I am not sure if I am understanding right the rule there for I made a small table

Please can you check?

 

Please login or register to see this attachment.

 

this is the command to adjust all the parameters???

=> hueKastRechtsSpot:on") & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='bri', value=65} & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='hue', value=75} &
{type='property', deviceID=<hueKastRechtsSpot>, propertyName='sat', value=55} & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='col', value=35}
& {type='property', deviceID=<hueKastRechtsSpot>, propertyName='sat', value=15}

Thanks in advance

[jgab 2,642]

11 hours ago, Sjakie said:

Hi jgab,

Is this not to much? Only 14-16 are comming short after each other.

Please login or register to see this link.

 

Yes, welcome to power event storms.... Many on the forum have reported this for other scenes too... it's nothing ER specific. 

What you can try to do is to change the power change threshold for the device before it reports a change. I don't remember the number of the parameter.

I have had issues with devices that flooded me with power events even when I upped the threshold. 

[jgab 2,642]

On 4/26/2019 at 9:10 AM, Sjakie said:

Good morning jgab,

Outside lights where off this morning and the curtains open (99%)

Now I want to add my Hue lights I have read the part about Hue and have some questions

ER is sending the signals to HC2

I am not sure if I am understanding right the rule there for I made a small table

Please can you check?

 

Please login or register to see this attachment.

 

this is the command to adjust all the parameters???

=> hueKastRechtsSpot:on") & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='bri', value=65} & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='hue', value=75} &
{type='property', deviceID=<hueKastRechtsSpot>, propertyName='sat', value=55} & {type='property', deviceID=<hueKastRechtsSpot>, propertyName='col', value=35}
& {type='property', deviceID=<hueKastRechtsSpot>, propertyName='sat', value=15}

Thanks in advance

 

Almost  

Please login or register to see this code.

The table of properties given to hueKastRechtsSpot:value=<table> is just passed on to the Hue lamp. If you give a number  hueKastRechtsSpot:value=<number>, then it sets the brightness to that value. Note that the brightness is 0..99 to be compatible with fibaro dimmers. If you pass brightness in the table {bri=50}, it is Hue's range that is 0..254

 

There is some documentation here how to initialize the Hue system on ER and map up the devices.

Something that is not well documented with Hue is the 'startup.customsettings' settings. If you have Hue lamps that sits in normal light sockets and where the power is turned on/off, the lamp always starts up in "default" mode. If you want your lamps to start up in the night with a specific brightness or color this is a problem.

There is a 'startup.customsettings' property that can be set to the properties a lamp should start up with (came with one of the last firmware upgrades for Hue).

In the recent Hue app one can set color and brightness but with the api all properties can be set.

Please login or register to see this code.

If the switch is toggled rapidly more than once the lamp will revert to default values and brightness. This is a Hue security things so people don't set a low brightness startup and when there is a fire all lamps startup with almost no light. Flicking the switch more than once will give default (full) brightness.

 

Edited April 27, 2019 by jgab

[petrkl12 228]

@jgab

this rule is calling 2x during first run (after 2 minutes). It should be call only 1x after 2 minutes. Thanks for correction.

Please login or register to see this code.

 

 

[jgab 2,642]

4 hours ago, petrkl12 said:

@jgab

this rule is calling 2x during first run (after 2 minutes). It should be call only 1x after 2 minutes. Thanks for correction.

Please login or register to see this code.

 

 

 

Fixed, ("2.0","B27"  -- Apr 27, 2019  )

[petrkl12 228]

It works. Thanks

[petrkl12 228]

On 4/24/2019 at 8:52 PM, jgab said:

In theory I could make ER scenes "autostart" when they get their first trigger but I like to have better control when to start them. Maybe an configurable option in the future.

 

 

It could be perfect also for me   Thanks!

 

[Sjakie 156]

Hi jgab,

If I download 27 and run it it gives error thta mu rules are having a nil value

blanked out 10 still same error

[jgab 2,642]

1 hour ago, petrkl12 said:

 

It could be perfect also for me   Thanks!

 

 

Ok, there is a new version B28 where you can set _STARTONTRIGGER=true

...experimental, let me know how it works.

 

11 minutes ago, Sjakie said:

Hi jgab,

If I download 27 and run it it gives error thta mu rules are having a nil value

blanked out 10 still same error

 

Need some more info, which rules? and copy me the error messages.

[Sjakie 156]

If I blanc tghem it will start with  the next rukes

--Woonkamer
  --Gordijnen sluiten lux 60
    Rule.eval("lightSensorBuVoor:lux < 100 & 16:35..23:00 => curtainFront:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:10) & 16:35..23:00 => curtainSideCar:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:15) & 16:35..23:00 => curtainSideBicycle:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:20) & 16:35..23:00 => curtainBack:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:25) & 16:35..23:00 => curtainBackSide:close")  

 

 

 

Please login or register to see this image.

/monthly_2019_04/image.png.fde0094b612b29a9965f851f0522c428.png" alt="image.png.fde0094b612b29a9965f851f0522c428.png" />

[jgab 2,642]

10 minutes ago, Sjakie said:

If I blanc tghem it will start with  the next rukes

--Woonkamer
  --Gordijnen sluiten lux 60
    Rule.eval("lightSensorBuVoor:lux < 100 & 16:35..23:00 => curtainFront:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:10) & 16:35..23:00 => curtainSideCar:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:15) & 16:35..23:00 => curtainSideBicycle:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:20) & 16:35..23:00 => curtainBack:close")  

    Rule.eval("lightSensorBuVoor:lux < 100 & wait(00:00:25) & 16:35..23:00 => curtainBackSide:close")  

 

Can you post me the first half of your scene like last time, and I will have a look at it?

There was probably a problem when you moved youre rules over to the new version.