upstatemike Posted December 5, 2015 Share Posted December 5, 2015 I have a pair of simple programs I use to control the lights in my front hall and this has worked great for years but now suddenly they won't time out and shut off. The programs are very simple where the first one turns the light on when motion is detected: If Status '1stMid / FrontHall:Sensor' is Off Then Set Scene '1stMid / Scene:FHallMotion' On Else -No Actions- And the second one waits for the timeout period and shuts the light off unless I have turned on a keypad button that I use to lock the lights on: If Status '1stMid / FrontHall:Sensor' is Off And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- Suddenly the off command never executes and I can't figure out why. I verified that all of the links are right in each device and the communications is good because the status is accurate in the admin console. I have two different locations with the exact same problem but I also have several locations using the same program with wireless motion sensors instead of IOLincs and they are still working fine. I did just update to 4.3.26 but I haven't seen any report of a bug that would account for this behavior so I'm not just blaming the firmware. I also tried connecting the motion sensors to Elk zones instead of IOLincs to trigger the programs but I got the exact same issue... the lights go on but never go off. Sometimes I can shut the lights off from the admin console and the programs will cycle correctly exactly one time on and off but the second time the motion is triggered they just stay on. Can anybody see a problem in the programs or something else obvious that I'm just overlooking? Link to comment
larryllix Posted December 5, 2015 Share Posted December 5, 2015 What devices are in your scene? Is your KPL D button in Toggle mode? Is the first line in your first program contain a typo that should read 'On'? Do you have your MS units with Off enabled? Link to comment
Teken Posted December 5, 2015 Share Posted December 5, 2015 The OP's problem seems very similar to what I am seeing this very moment in my home. This problem seems to have started about the same time I upgraded to 4.4.1 Beta firmware. The strange thing is activating the direct node turns the *foyer* light on-off with out issue. Using the scene again has no issue completing this task. Going directly to any linked switch in the home has no problem either. Its when the MS turns the light on it doesn't turn the load off yet (some) of the linked devices turn off. As a next step after doing all the device restores, air gap, hard reset and restore, etc. I replaced the MS with a brand new unit and it (almost) behaves the same way. Everything was rock solid a month ago and nothing new has been introduced besides replacing a few single band devices to dual band switch linc dimmers. As an aside in the 4.4.1 thread I noted that I can not create a new scene that controls a device WTF? Link to comment
upstatemike Posted December 5, 2015 Author Share Posted December 5, 2015 What devices are in your scene? Two dimmer switches. Is your KPL D button in Toggle mode? No Is the first line in your first program contain a typo that should read 'On'? The motions sensors are normally closed contacts so they cause the IOLincs to send Off when activated and On when they reset. The reversed logic has never been an issue. Do you have your MS units with Off enabled? Not using wireless motion snsors in these locations - they are alarm motion sensors connected to IOLincs (also tried using Elk Zones). The places where I am using wireless motion sensors the OFF is not set and they work fine using programs with the same logic. No reason IOLincs should suddenly act different but they are. Link to comment
larryllix Posted December 5, 2015 Share Posted December 5, 2015 I see nothing wrong with your programs then Teken may have something as this just stated when you upgraded to v4.4.1. I am at v5.0.2 and not willing to step backward again so I can't test this or experience this properly. You could try v5.0.2 and gain much but lose the font scaling. Link to comment
upstatemike Posted December 5, 2015 Author Share Posted December 5, 2015 Solved it. Your point about wireless motion sensors only sending on helped me find the problem. Since alarm motion sensors will transition back to off or secure before the wait statement completes the second program was switching to False before the off command for the lights was executed. Switching the trigger on the second program solved it: If Status '1stMid / FrontHall:Sensor' is ON And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- (motion on/off logic is still reversed when using IOLincs) It also works fine now with Elk inputs: If Elk Zone 'Front Hall Mot' is Violated Then Set Scene '1stMid / Scene:FHallMotion' On Else -No Actions- If Elk Zone 'Front Hall Mot' is Normal And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- I don't know why it worked before but I probably had it right and then changed it at some point. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.