oberkc

I am glad it is working for you. Not being a user of HA, I was not certain what happens in HA when one turns on an Insteon virtual switch that is already on, or off when already so. I was also suspecting problems in keeping things in sync when garage doors are operated by means other than the virtual switch, or whether that is even an issue. I know, also, that Alexa is easily confused when you have multiple devices with similar words in the name, such as garage, and that it might be helpful to remove the genie skill from Alexa to avoid some of that confusion. Hopefully those concerns were unfounded or that you found good ways to handle them.

While I don't use HA, I understand that it integrates well with the ISY (or whatever term you want to use). Given this, and given that you can open the door from HA, would it not be simple enough to create a virtual switch (or, possibly two virtual switches)..add the virtual switch(es) to HA, and to Alexa...trigger programs from HA based on the state of the virtual switch...and create a couple of routines in Alexa: when I say "Open Garage Door" Turn on a virtual switch when I say "close garage door" Turn off a virtual switch (or turn on a second virtual switch) There are certainly a few details to be worked out, but this seems like a promising start to a concept using virtual switches. On the other hand, it would also surprise me if you could not do this directly with an Alexa routine and bypass the virtual switch intermediary. Can one not trigger an HA action from an Alexa routine?

I don't know what garage door integration you use, but I find it unlikely that any Insteon device (real or virtual) would allow you to bypass the PIN requirement required by Alexa. Can Home assistant control the door without a PIN?

This thread is in the "Hue" forum. I am not sure how much of a difference that will make, but it certainly does not help. My perception is that things at Honeywell have changed, rendering the Honeywell Home plugin non-functional. I also understand that the plugin is no longer supported by whoever does such things. Regarding the HomeKit code, is it possible that this code is on a sticker somewhere on the thermostat? (The few HomeKit devices I have paired had such stickers and the instructions that came with them had the code printed somewhere.).

I recall than, when I did the migration, I required no extraordinary steps. The wiki instructions worked for me. https://wiki.universal-devices.com/ISY_Portal_Migrate_configurations_to_a_new_ISY

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.