mangler

Rabbit and Belias - thank you very much!!! This was a great way to get started. In fact, I spent a little time understanding what you have done and I used the version in this thread mostly as-is. Been testing for a bit, and it seems to work as intended. A couple things I almost missed ... setting the "Leak Startup Program" to auto run at startup; and the fact that you run the Heartbeat Missed programs during startup - BUT DIRECT TO THE "THEN" track. Anyway - Well Done! Thanks again for this. I can see this framework being re-used for other types of alert sensors. This was one of the first "environmental" sensors I have put in - and now I will be adding a hot tub temperature and leak sensor, and probably automation enabled/alarm integrated fire/CO sensors. Thanks again!

Well, I performed a hard reset of the KPL and performed "Restore Device". Voila! The D button works fine. Somewhere in messing around with some scenes and programming over time, it had some kind of problem that was solved by a reset. Thanks for the help folks!

Good suggestion Lee. I don't know why I didn't think of that. Will do when I am home. That, plus a hard reset of the device.

No blink. I will get the chance for a reset tomorrow night. I will let you know. Thanks for keeping the ideas coming. Sent from my iPad using Tapatalk

Yeah - it reads correctly ... ON. But when on it doesn't light when triggered by the button itself ... only when triggered from the scene it is a controller for. Odd. Xathros: I will try that when I get home on Sunday. Thanks!

Stu - the D button is on or off only. No percentage/level. Xathros - I set the KPL to non toggle - and back... No change in behaviour - the light works when the scene is triggered from ISY, but not when triggered from D. I am starting to think I may have a faulty KPL. Is there any way to do a hard reset of this KPL and then I could load it back from the ISY? Sent from my iPad using Tapatalk

I cannot find any programs that reference this key - or even this KPL. I don't have a lot of programs yet - only 15 or so. When I trigger the scene from ISY - the button lights - but when I press the button itself it starts the scene - but the button doesn't light. The other buttons linked to a scene also turn the scene off - but this one won't turn it off (it seems to be stuck in a mode where just button D is an on button only. Not a toggle) All 8 buttons were set to "Toggle" - and I tried resetting them all to "Toggle" again. It didn't help. All the other buttons work fine.

I have an 8 button KPL that has the left buttons assigned to overhead lights or lamps. The right buttons are assigned as controllers for four scenes. Each of the four scenes controls the same 5 lights but have different brightnesses set for "watching TV", "Reading", etc. The scene buttons (right four buttons - B, D, F, H) each are the controller for one of the scenes and they light up when pressed (and the scene fires) or when the scene is tuned on. As expected. EXCEPT ONE! The "D" button fires the scene as expected and ISY reports the button as ON as / when expected, but it won't change from dimly lit to brightly lit. I know it works because it went on when I was messing with LED brightness but it is not driven by the scene. I have tried a bunch including to restore the device, but to no avail. Any thoughts on what I might be missing here?

Thanks, Xathros. Yup - added zwave door locks in the house. Who knows where to next

Thanks Stu, but I understand that. There is an additional folder ... also named Murray Mansion that has a different icon. Nothing in it. It may have had some items in it but I moved them - not sure - maybe zwave items. Thanks for the link on "Auto DR"

Wondering what "Auto DR" is - and also what the folder with a different icon matching the name of my ISY? Both are circled in the attached image.

Thanks guys ... from both replies, this is exactly what I am seeing. I guess I just didn't expect that. I figured when I turned the slave switch on from the ISY - the scene would get fired. Also - it wasn't obvious to me that the scene wasn't getting fired when I turned the load switch on from the ISY because the light comes on. I get it now and understand. Appreciate the quick replies.

I have figured out how to avoid this problem, but would like to understand whats going on. I have a couple of 2477D dimmers that I have wired in where a three way switch was setup. I have only added one of them to the load - the other is just connected for communications. They were each individually added to my ISY994 - the control switch worked fine to control the load - the other did nothing. I connected them both to a scene as controllers. Seemed to work fine (they worked on my previous ISY99i for a couple years. The problem: for some reason the slave stops working, which I think is caused by anytime I try to operate the scene from the slave switch via ISY. The "control" switch works even from the ISY - and the scene works - but if I try to operate the slave from the ISY, it seems to operate independently. As long as I DON'T operate the slave switch from the ISY - all works fine. I am sure there is an explanation that you all know - but I don't yet. Thoughts?

Blueman - not an expert here, but that sounds a lot like the symptoms I was having. Things were great for a long time (couple years 'ish), and then the symptoms you mentioned. Intermittently I would get "could not communicate with ..." errors. After a while of that - the PLM fully cratered. I got a new PLM and it started working again right away. I can't tell you sustained that was - because I also ordered a new ISY with ZWave and such, and have made the jump (needed to add ZWave devices anyway). Working ISY99IRPRO for sale now though comes with brand new PLM!

OK - I tried that, and it didn't help. I have rebooted the new ISY a few times - but had not powered it off. I powered it off for a different reason and now all seems when (after back on of course). It's been intermittent, so we'll see, but it seems to be working fine as shown in my notes (without the 2 seconds added). Good suggestion though - that would have ruled out interference ... or at least the symptoms would likely have changed some. Thanks !!! Mark