carealtor

@IndyMike Thanks for the workaround and the link. Are you of the opinion that a new IOLinc has fixed this issue? I still think there is more to this problem. The State for this Entity in Home Assistant is ALWAYS correct, even when the Admin Console shows it wrong.

1. Yes 2. I think NC, but not sure how that is relevant?

I just tested this extensively with another/spare IOLinc that I have in my stash. Exactly the same incorrect behavior.

I believe this to be an issue with eisy as I did not have this issue with Polisy. I have an IOLinc 2450 that I use the sensor side to tell me if a garage door is open or closed. I do not use the relay side for anything. If I operate the garage door, and thus cycle the sensor, the Admin Console will show the status correctly. BUT, if I run a Query, the status will always come back reversed to the actual status. In the options for this IOLinc, I have selected Trigger Reverse. This is part of puzzle if anyone is trying to replicate this. With Trigger Reverse unchecked the inconsistency does not occur. What is also interesting is that Home Assistant is always showing the correct status. So, HA will correctly show the door position, while at the same moment in time (after a Query), the Admin Console will show it incorrectly. My guess is this is some kind of glitch with the Query of an IOLinc where it is not taking into account the Trigger Reverse option? This would normally not be much of an issue as I don't make it a habit of doing a Query on this IOLinc (or any other device for that matter). But I do need to occasionally reboot IoX, which Queries all devices.

So, it sounds like there would be no difference in my case because I only have Insteon and no Zwave.

Surprised that nobody knows the answer to this.

What is the difference, if any, between "Restore Backup" and "Migrate from PG3 backup"? I just moved from Polisy to eisy and the instructions I was following (the wiki) said to use the migrate button and I mistakenly used the restore. Should I do anything to resolve this misstep? I have everything working again, so there doesn't seem to be any lasting issues from this that I can tell.

Ah. Obviously I never tried it.

"Repeat 0 times" ?

Couple months ago I had something similar. Someone suggested logging out and back in to PG3. Worked for me. As has already been suggested, reinstalling all plugins often works.

I'm in the same boat that a couple of Plugins refuse to start. HueEmulator and Ecobee.

Thanks Goose. This should work fine.

Tagging @Goose66

Is it possible to have a Plugin Node be the Controller of a Scene? Maybe it's a case by case basis? I have Bond Bridge Pro (and installed Plugin) to control a SmartWings shade. I created a Scene with a KPL button and the shade's Node. I was not offered the option to set the shade's Node as a Controller of the Scene, just as a Responder. The KPL button works fine to control the shade, but if I use the Bond Bridge App to control the shade, the KPL Status does not update to reflect the current position of the shade, even though the shade's Node does update.

Maybe this helps someone... If you want to control your SmartWings shades through the Bond Bridge, the Device to use is the "Dooya Bi-directional". (I don't want to take credit for figuring this out. I had inquired about this on the Bond Forum a couple of months ago and someone recently figured this out and posted the solution.)

Can you be a bit less cryptic? ☺️ Are you suggesting that there is a problem with my network/internet? Everything else in the house seems to be humming away fine.

My turn for problems. Yesterday noticed that automations had stopped running. I started the Administrative Console and it opened up blank and did not ask for login. So I rebooted Polisy by unplugging, waiting, and plugging back in. I started the AC again, was able to log in, and things looked good. Scheduled automations caught up and everything. Later in the evening I noticed things still weren't quite right. I traced it to some, but not all, Plugins were not working. The ones that are not working are HueEmulator, Bond, Ecobee, and ST-Sonos. If I hit Restart, I get a message in a red box for each them that says "Plugin Restart: No valid license" I also find it notable that when I click on Purchases, it says "Total Purchases: 0".

Thank you! That did it. The Bond Plug-In instructions say it's under "Settings".

I've seen the instructions about adding the hostname and token custom parameters before trying to Discover, but I still can't get it to work. I have a message: "Unable to authenticate with the Bond bridge at hostname 192.168.1.73 using the supplied token. Please check the corresponding 'token' parameter value in the Custom Configuration Parameters and try Discover command again." I couldn't find anything in the Bond app Settings about a "local access token", but I did find something called "Account Code" that is 16 digit hexdecimal, so I've been trying that, but it doesn't seem to be the right thing as it doesn't work.

Well, I just checked my original power adapter that came with the Polisy and it's 1 amp. It appears the original and the adapter I bought on Amazon are EXACTLY the same adapters. No argument from me that a 2 amp might be better for longevity.

Oops. Never thought to look at amps. I was zeroed in on 12V and the right size barrel connector.

Oh man, so happy I found this thread. I was in a panic yesterday morning. Thanks to Amazon, $7, and same day delivery, I was back up and running by dinner time. Amazon power supply for Polisy

I apologize for my naivete, but I'm not sure what you are saying. Are saying the currently available ZMatter board does or doesn't work with Polisy?

I still have a Polisy and want to get some SmartWings shades. (I plan to get an eisy some day.) When ordering the SmartWings shades, I assume I want the Z-Wave Plus motor option? Since I currently have no Z-Wave, I know I will need a module for the Polisy. Does the current ZMatter board work with Polisy? (Sorry for this question that I'm sure everyone but me knows the answer, but I haven't been paying a lot of attention to all this new development for awhile.)

The dream would be to be able to use HueEmulator with my Brilliant Home Control panels. I've had discussion with Jimbo in the past, but now it has been awhile and wanted to see if anything has changed that might make this a possibility. As I understand the issue (and I could be way off because I don't claim to understand these things) is that a real Hue bridge runs on port 80 and thus that is the only port that Brilliant looks at. It is also my understanding that ISY also runs on port 80 and that cannot be changed. Thus, HueEmulator cannot run on port 80. If Brilliant would change the way it works to look at the port that HueEmulator is using, it would probably work. But Brilliant is not going to do this. I have tried and they see no reason to make the change since real Hue runs on port 80. My workaround had been to use the Emulated Hue integration in Home Assistant, but now that is not working either. Talking with Brilliant support at length, I was able to learn this information: "One thing that did change with the Hue integration recently was we switched the discovery of Hue to use MDNS instead of UPnP (Hue will be deprecating UPnP). It may be possible the virtual hub mentioned (Home Assistant Emulated Hue) doesn't implement MDNS properly so we cannot find it on our end after switching the discovery method." I have no idea what this means, but it seems to be why the Home Assistant Emulated Hue integration used to work, but now it doesn't. Another thing I have run across that I have not seen before is this tidbit from the Home Assistant Emulated Hue integration readme: "This virtual bridge runs at HTTP port 80 and HTTPS port 443 on your local network. These ports can not be changed as the HUE infrastructure requires them to be at these defaults." Does this mean that HueEmulator could be made to work on port 443? Probably wishful thinking.