vbPhil

I did the upgrade packages and it's still showing 3.1.31. Also tried a browser refresh and a reboot but it's still showing the previous revision number. I only have the Notification node server installed and it was still spitting out notifications so I guess it's still working. BTW... I'm on Polisy.

That announcement doesn't provide much guidance for deciding which to use, PG3 or PG3x and why are there 2? Seems like you'd only want one series to maintain going forward.

This upgrade announcement states "PG3x v3.1.29 for eisy and Polisy". I'm on PG3 3.1.21 for Polisy. Now I'm confused about what PG3x is for. I thought it came out for EISY only? Is there some info on this somewhere?

Yes I concur. Still evaluating router specs before pulling the trigger.

Installing a new router and I wanted certain devices, like smart controllers, to keep the same IP from the old router to the new so I thought of using static IP addresses.

Not perfect but doable.

I've always had my ISY set to Automatic DHCP and never paid much attention to the Network Settings on the AC Configuration tab. I notice now that it's set for DHCP and greyed out so I can't change it. How do I change the network settings on my Polisy IoX? I want it static at a fixed IP address.

Works for me. Also, I get 5 beeps in succession, not 4 as always stated.

I'm running Polisy 5.6.0 and PG3 should have been current. After completing the Upgrade Packages from the AC I did a restart on PG3. Now when I try to launch the PG3 browser interface I'm getting a "ERR_CONNECTION_REFUSED" in the browser window. I've tried doing a full reboot from the AC but it didn't help. Any ideas on what to do next?

UDI has indicated a while back that they are working on the i3 Paddle but consider it a minor issue. I don't agree that not be able to operate a dimmer in dimmer mode is minor but..... which is why I'm using it with Home Assistant instead.

Does IoX 5.6 support the Insteon i3 Paddle dimmer mode? The previous versions did not allow the Paddle to operate in dimmer mode only on/off. Therefore, I moved mine over to my Home Assistant Insteon PLM network where it does run in dimmer mode.

I knew how to do the factory restore but didn't read anywhere that it actually cleared out the links database in the PLM. But now, we've heard it from the horse's mouth, Steve Lee, who's probably the foremost expert on Insteon.

I asked Insteon and here's their answer:

Good idea. Assuming original factory settings would have an empty link database this from the 2413U quick Start Guide should do the trick.

I'm going to replace my Polisy's old serial PLM with a brand-new USB version. The ISY Cookbook procedure is pretty straightforward on how to do this in the section, 5.2.1.7 Restore Modem (PLM), so hopefully there's no gotchas. I was wondering if the memory on the new PLM is erased before it's restored to my network so that there won't be any orphaned links hanging around? That would also apply to reusing the old PLM someday but yet it's full of links. Does all that get cleared away somehow?

Good point. Just wondering, is there such a thing as "ISY" anymore that is still supported?

I read in the release email that one of the changes was; "ISY to IoX". Just wondered why I still see "ISY" everywhere?

Here's a custom email that I use. Every line comes thru in the email on its own line. The custom email has text selected.

Just to confirm. Can you wake up the device from the AC using the Keep Awake button? I've never been sure of that or actually found it to work. I've always had to wake up the device manually by pulling the cover. My intuition isn't good for the z-wave controls in the AC.

Funny, I was aware of those settings, and it didn't occur to me, I should be running with the defaults. Anyway, The AC is now showing readings and it's been about 1 hour. I doubt any of the readings have change all that much because they're in pretty stable environments. Home assistant is still showing Unknown so that's a separate troubleshoot. I still would like to know what the "as designed" process is for IoX. After a reboot will it wait for the device to send data again or display the last known value? Does the AC always show the last reading, and then you wouldn't know that the device quit sending.

So, I have several ZSE44 TEMPERATURE | HUMIDITY XS SENSORS and their readings had an Unknown status in Home Assistant after having worked for many months. I checked the IoX Admin Console and it was showing values. Poked around some and couldn't find anything obviously wrong so I re-booted IoX from the AC Reboot button and restarted Home Assistant. It's been an hour later and still no values shown in the AC. I've gotten kind of numb dealing with all the z-wave issues from the z-matter upgrade that I never know if it's a normal z-wave operation or a real issue. I can't imagine that all of the sensors have quit working, so I have some questions. When does IoX update the displayed readings from a z-wave battery device? If a z-wave battery device fails, will IoX indicate somewhere that's it's offline or something? What are some good troubleshooting steps for this issue? Home Assistant question: What would explain HA showing Unknown for the sensor when it was working earlier?

I noticed that when you submit a support ticket, the drop-down list for firmware version on the form has been showing 5.6.0 for a while now. Could be for some other product, but I'm just saying.

For Polisy, 5.5.9. Just installed a new i3 Paddle wall switch and configured it manually with the set button as a dimmer. However, IoX only sees it as an on/off switch so none of the usual dimmer controls are available in IoX like the on-level and ramping. Is this normal behavior for the current i3 support in 5.5.9 or do I need to do something additional to make IoX see it as a dimmer? I tried searching the forums on i3, but nothing is coming up, so I apologize if this topic has already been covered.

My ticket was responded to by @Michel Kohanimthis morning to say that it will be fixed in the next update.

I put in a Service Ticket. Could I be the only one in Albuquerque with this issue?