Logical Rules....

[Mike Yeager]

I'm sure this has likely been covered but I'm not finding the info I'm looking for. I'm trying to set up a logical rule that looks at a luminosity sensor and if it's below a certain level, turns on a dummy device (binary on/off switch). When I set up the rule, nothing happens. When I come back to look at it, the state option for the dummy device is blank (neither option selected) and it is telling me the field is not optional. I set it, but it isn't holding. Am I not doing something right or is there a glitch here? I'd think if it was a glitch, I'd have found reference to it already. Using latest release version as of a few weeks ago.

Thanks and GREAT work since I first got into this....

[pz1]

Don't know if I am getting your problem. I did add a dummy device on command to one of my rules. After saving, I found the setting to be correct on reopening. I remember there has been an issue with some settings and rules recently. Maybe my version 2.0.2-rc1(at the moment of this writing do not use any of the newer beta releases) has that fixed.

[Mike Yeager]

Hmmm.... Interface shows me at 2.0.1 so I'll try and update. Maybe that will get it worked out...

[Mike Yeager]

Ok. That fixed the settings issue. Here's what I have...

I have a logical rule that reads :

Start scene on any change in condition...

Conditions :
Multilevel ->Luminosity >= 300
Actions :
Switch -> Dining Outlet = On

But even with the condition being equal to 1000 at the moment, nothing is happening....

[pz1]

What units does your device use for luminosity. I'm old school, so I'm more familiar to lux measurements. What does your log say? (/var/log/z-way-server.log) Do you see any response?

[Mike Yeager]

It's actually LUX from a multisensor. I have it working now. Going to play with it to see if I can get the conditions set right to control a light based on LUX and motion. Would like to be able to delay turning the light off for a few minutes after the motion sensor deactivates but not sure how to do so without causing problems if the motion sensor re-activates. I can see where these rules could be very powerful once one figured them out. Do these transfer during an upgrade or will I have to copy them over?

[pz1]

Some binary switches do have the option to specify (ExpertUI configuration) the amount of time before it is automatically switched off. This delay starts at the last received "on" command.
Alternatively there is the "Delayed Scene" module that might help

Suggestion: Describe your final solution in the first post of this thread once everything is working fine. That may help others

[toomuo]

looks like something was fixed for logical rules switch actions in 2.0.2-rc2

[pz1]

There was a fix on 2015-07-01, so I expect it has gone into 2.0.2-rc1 that was released on July 5th.
Once again do not use any of the later v2.0.2 beta releases.

[Mike Yeager]

v2.0.2-rc1 here. Looks like my earlier message didn't post. I'll be sure to post what I come up with when I get it the way I want it.

Any idea how to catch a scene switch being changed? It's an Enerwave 7 button switch and although it hasn't completed the interview process (Version never completes), it works just fine. Shows up in the expert UI but not the HA UI....