mmb

@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!

@Javi, I’ve noticed in UD Mobile that variables don’t always display their values. Is there a way to force an update of all the variables? I find it to be a very handy to see all the values rather tapping each variable individually. Thanks!

I was told years ago -170001 is an informational message. So I just ignore them. It would be nice if there was a log debug setting to turn warnings off and errors on as needed. Log formatting needs work too.

I have an older Polisy but up-to-date OS/IOX and mine is showing correctly.

I'm impressed the ISY could run that many programs. Must be challenging to manage.

How long did you leave the sensor when eisy reached Reading? Chris says it should take about 10 minutes.

@Chris Jahn that would be helpful, thanks!

@DesertRat I went through exactly this with my Zen17, it uploads the fragments properly but gets stuck on the Reading and never seems to finish. I just killed the window and with Chris Jahn's help I was able to confirm that it had indeed completed successfully. Chris tested the same Zen17 and had the same result - stuck on Reading. Techman shows how to confirm the version. I believe Chris says to do a Synchronize and Update with interview before checking version.

Thanks @Chris Jahn, why wouldn't IOX capture these changes as part of the update process? Like close the loop...

@peterathans try moving the gbl file to the Desktop or Documents folder.

@Chris Jahn passed along how to confirm z-wave firmware version information for a device. right+click | X-Ray | DH Command Classes and look for the Version command class (134) and you will see the application/library/etc. versions for the device In this case version 1.30.

Thanks Chris, this has been quite a learning experience, but that's a good thing. 👍

@Chris Jahn the process started with Sending 8400 fragments then followed with the Reading message where it’s been for the last several hours. Fyi the Zen17 was on the initial firmware release and there’s been 5 or 6 updates since. 1.03 -> 1.30