mmb

Thanks, I actually didn't try other devices but will if it ever happens again. To resolve the last instance of can not contact UD, I went into the GH app then into Settings/Services/Works with Google then scrolled to the UD module and pressed it. It took me to the portal screen for a login. After logging in the spokens started working again. I do remember having to re-link the UD module on previous occasions. Then logging back in to get spokens working again. I'll pay more attention to the specifics if it happens again.

Thank you, the disconnect results in a can not contact Universal Devices (or similar) on a spoken command. Does losing track of the "agentUserId" necessitate a re-authentication via portal or a re-link of the UD module then an authentication? As noted it doesn't happen often. I assumed it was related to a backend change or an app update.

Maybe @bmercier can help me understand why Google seems to disconnect from time to time which requires either removing the UD link and re-adding or re-authenticating to link up the service? It happens only a couple of times a year with Google but Amazon has been rock solid since I linked it. Just curious, thanks. (sorry if I should have made this a new thread)

I actually had this problem on Saturday out of nowhere -"can't reach UDI" The usual fix of going into Google Home app and linking UD and authenticating fixed it for me.

You can mark the solution and leave it. It will help others and live on…

@DualBandAid I assumed too much. My USB zmatter dongle was the root cause of my initialization forever. Changing the port fixed it.

I had this happen several times and submitted a ticket for the problem. I resolved it before a response. Check to see if the z-wave and zigbee tabs work properly in the AC. Are you using a USB hub? I my case the USB hub was the problem, simply changing the USB port on the hub fixed it. Why it happens, not sure.

I highly doubt the timelines are current if there's anything...

I have zero problems with java and I do my own programming in Python. I also use Home Assistant at another residential location with Insteon and Z-Wave. But I see so many people that having problems with the AC. How many times have you seen Finder doesn't work, where is start.jnlp, delete your java cache after an upgrade, etc. All I'm saying if UD wants to grow adoption of their automation device, the UI needs to be replaced.

I haven't seen any reference to that? @Javi do you have any information and timelines?

I read that too, but I'm not clear how it translates to the PC and Mac.

I've said this before and I say it as a user of other automation systems. The use of Java is cumbersome middleware and is likely a reason the ISY/Polisy/EISY isn't gaining widespread adoption. The UD firmware is far superior and capable than other automation systems I use. I hope there is a plan to replace the UI someday.

@hart2hart I've seen this error message several times before and I reported. Got the same response from UD. It disappears after a period of time in my case so I just ignore it.

UD should clarify, but to me it sounds like Reboot is full OS based and Restart IOX is limited to the IOX service itself. Which makes me wonder what about a UDX service restart?

I think I have an older Polisy (early release) and haven't had any problems. I usually apply updates a week or so after release.

I had the same problem, I just wrote a little program to update the LED based on the status of the device being controlled. There are likely other ways to do it but this is what I did. Bsmt KP D LED Update - [ID 0023][Parent 0001] If Program 'Bsmt HRV On' is True Then Wait 2 seconds Set 'Keypad Bsmt LED D' On Else Wait 2 seconds Set 'Keypad Bsmt LED D' Off

Did you just use the AC Configuration/System/Upgrade Packages or SSH? Thanks!

Huh @vbPhil? Insteon operation is identical on eISY and Polisy. Plus they integrate z-wave (like the ISY) and zigbee for more device options. I'm finding operating range is much better too using the zmatter board - no z-wave repeaters needed. I use my old ISY in my vacation condo. It's all insteon, so a perfect fit.

Congratulations to the team! Read more here. https://www.universal-devices.com/zmatter-usb-zwavep-cert/

There may be another way to get it working but I had to delete the UD service in Google Home and add it again to fix that problem.

Reboot using AC or Reboot by pulling power? Re-power was the only way I fixed it...

@photogeek54 I've seem this as well after a reboot from the AC. The only way to fix it was to pull the power, then it seems to be ok.

We're the same, I just inadvertently grabbed a pic of one of the keys instead of the main key.

Which keypads? Insteon? Z-Wave? My Insteon keypad doesn't have "Backlight", just LED Brightness.

Very slick, exactly what I was looking for, thanks!