oberkc

Yes, I can reach it with the resideo app. But, now that you mention it, I am unsure whether I assigned a static IP address for the thermonstat. I will have to look into this.

After over a year working, my Honeywell plugging gives me this error. I have restarted the plugin several times and rebooted the EISY. Is anyone getting this error? Is anyone else's still working? Is anyone still using this?

I could not remember for certain, but I was thinking that matter-over-wifi could be directly added. It was only the matter-over-thread that I thought required another platform. Having said that, I don't even remember whether I have tried.

Is your dedicated Outlook on a separate circuit? I understand that the PLM is not on the surge suppressor, but the mere presence of surge suppressors and UPS can make it hard for insteon devices to communicate of whether the insteon devices are powered by the UPS or surge Suppressors.

Not at all. I am saying that this was different from my experience and that I have no explanation based upon my understanding and perceptions of how things work with our home automation system.

"Surge Protector" and :battery backup!!!??? Is this on a filterlinc? Those things have been a problem for me...enough that I put all mine on a filterlinc. And...you don't actually have to "move" things. Get an extension cord into which you can plug the PLM without much moving it. Take the other end of the extension cord into another outlet on a different circuit.

I believed this part, it was where the admin drop down boxes quit working that was so different from my experience:

I wonder if these six devices are simply experiencing communication problems during the restore process. How easy would it be to try moving the PLM to a different electrical outlet on a different circuit (a long extension cord can be useful)?

I am curious how you have done this? Have you unplugged the EISY or by a different method?

No. I don't believe that the load can be "on" and the backlight to be off.

I had a zwave device fail, impacting the response of many other zwave devices. Unlike you, I did NOT experience the impact to IoX or to the dongle. Mine continued to appear to operate normally. While I have come to understand why a single device failure would affect zwave communications, it makes no sense in my head that it would affect the EISY and admin console operation in the ways you describe. Still, I am glad you got it working again.

@hart2hart 's solution should work in your particular situation. If, for some reason, you cannot change the variable to an "integer" type, then allow me to expand upon @Techman 's suggestion to try a second program: if IF status Device_X is off AND status Device_Y is off AND status Device_Z is off then run a second program (if path) Second program (disabled): if variable Poll_Running =1 then do something

I think I would figure out why this is happening, rather than trying to create a bandaid program to correct the first error. I assume that you now have a program somewhere that is turning it on and now a program trying to turn it off. It sounds as if the first program is winning.

I have no experience or knowledge to supect that this is true, but maybe it is my turn to have a good day

I believe the solution from @dbwarner5 is the simplest (thus most elegant) solution. The program will be triggered upon chage of status of ANY of the six switches and evaluated based upon the entire program logic. Problem solved.