oberkc

I apologize for the misinformation. Queries are generally available for Insteon and zwave, but I guess some of the other nodes don't have it. I should have been more careful in my response.

In answer to your original question...yes, "query" is one of the choice in a program action.

If you have positively confirmed that there are no programs or scenes that causes this, then my temptation would be to restore the two (switch and panel) devices.

I had a time very near after migration (it turns out that this was coincidentally) to EISY that some of my zwave devices quit responding or responded quite slowly. In my case, there were a select few devices that were constantly a problem, while other zwave devices continued to operate just fine, if a little slowly. The cause of all this was a failed device that, I assume, was part of the signal path for some others. Until that point, I had not noticed or had not needed to use the "Capture Log" feature of the zwave tab. It was this log that revealed the failed signal path. If you have not tried it, I suggest doing so. Start the log, attempt to trigger some of your troublesome zwave devices, stop the log, then see if it reveals a problem.

YoLink sensors work well for me, as well. I agree with @dwengrovitz that the battery life is really good. But, you must be willing to put in the (little) extra effort for the node server and hub. Furthermore, unless you go with the higher-end hub, you will be cloud dependent.

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.