mbking

I’m having the same issue. It seemed to start around IoX version 5.5.4 or 5.5.5, but I’m not totally certain of the specific version. I had to disconnect the garage relay because it opened my garage door in the middle of the night. Status is not updated and the log doesn’t show any activity related to those devices that turn on by themselves. I’m running IoX on Polisy. Could a failing PLM cause this? Mine is reaching the typical failure time frame for failure.

I prefer being notified that an update(s) is available and letting me plan a time to actually execute the update. I like to monitor the update process so I can report any unusual beeps or messages I might get during the update. And most importantly, I want to create a backup of IoX, PG3, and UD Mobile before doing the update. I think it's reasonable to expect users to be at the current version when reporting issues unless the issue occurred during the actual update. Most companies will ask you if you are on the current version when you call for help. UDI should be able to expect the same thing from us. With so many systems making up the whole now, I don't do interim updates anymore. I wait for a notice under the assumption that all the necessary pieces will be updated and will work together. I would like the notice to come in the form of an email or other automated notification instead of waiting to read about it on the forum, AC, or UD Mobile.

Successful upgrade from IoX 5.5.6 to IoX 5.5.9 on Polisy. Also upgraded PG3 3.1.17 to 3.1.18. Upgrade was initiated from the AC. The only thing different this time was the absence of the 5 beeps at the end of the update. I followed the basic instructions listed with the upgrade except for power cycling Polisy. Mine is not easy to get to at the moment. If you reboot from the AC, is it necessary to also power cycle Polisy?

I’m using iOS version 1.0.20. I do get the Force Update option, but wanted to wait until it was determined to be a bug so I could test the solution.

@Javi, I was going to use UD Mobile to update IoX from 5.5.6 to 5.5.7, but 5.5.6 is showing as Up to Date. When my system was at 5.5.4, UD Mobile showed 5.5.6 available. I chose to use the AC to do that update. But this time, I was going to use UD Mobile and 5.5.7 isn't available yet. Is that a bug or is IoX 5.5.7 really just for eisy. I'm using Polisy. Anyone else seeing this?

For others who might be thinking of updating to IoX 5.5.6, I upgraded successfully from IoX 5.4.4 and PG3 3.1.16 on Polisy. I'm using the Z-Matter board. I used the Upgrade Packages button in the Admin Console. Once I received the 4+ beeps from Polisy, I waited about 5 minutes for IoX to restart (this can take around 4 or 4 minutes on my system). I then used the Reboot button for Polisy in the Admin Console to restart Polisy. Everything came back online including PG3 which in the past required a separate reboot to get the versions displaying properly in the main screen. I rebooted it for good measure and so far so good. Next time I'll try the firmware update from UD Mobile(iOS).

Until we're able to update the Ambient Weather NS with a restart, there is another method you can use to update the NS. I had to do this with the ELK node server and just completed it with this node server and it worked fine. 1) Go to the Node Server store and select the AmbientWeather button. 2) The next screen with show the latest version. On the Perpetual line, select the Install button. 3) On the form displayed, look for "AmbientWeather is already installed in slot (your slot number)" and select the "Reinstall here?" button. 4) The latest version will be installed and the NS restarted. Configuration info is preserved. Worked for me. All the data looks good.

Launching the Admin Console via the Cloud is working now.

I updated successfully from IoX 5.5.2 to 5.5.3, but the Admin Console only launches from the LAN selection in IoX Launcher. The Cloud version does not launch. I cleared Java cache and downloaded the latest start.jnlp file. Other than the Cloud issue, all seems normal with Insteon and Z-Wave devices. I'll continue to test. @Chris Jahn, I've seen this before in previous updates.

This issue is fixed in UD Mobile iOS version 1.0.3. @Javi, thanks!

Hello @Javi, Yes, I had this same device on the Zooz module and it worked fine. I'm not an expert with Z-Wave and I only have this dimmer device and a range extender, but this device was given the ID of ZW-003 on the Zooz dongle and it has the ZY-003 ID on the ZMatter board. Not sure how those ID's are determined except for the sequence number. Note: The recent onboarding changes seem to have improved overall performance of UD Mobile. It wasn't bad before, but just seems a little more responsive which is nice.

@Javi, When I try to create a widget for a Z-Wave dimmer I added using Polisy with the ZMatter board, I'm getting errors when syncing and creating the widget. All the errors seem to be related to the Node Def ID. Here are the errors when running Sync: The first time I tried to add the widget, I got an error related to the Node Def ID when adding the device to the Display Node. It added, but Display status had no values to pick, so adding the widget failed. I did another Sync, same errors as shown above, but this time I could add the Display Status value and the widget was created. But when I try to add a User Mapped Value, I get "Could not get node def ID". When I try to control the device via the widget, I get the following error:

@Michel Kohanim, It does now and is working fine. I had originally placed it near Polisy as I had had to do with the Zooz dongle to get it to add to the Z-Wave network. But doing that now, IoX never sees it. May be related to signal strength. Once I moved it to its final location, it connected normally. So other than not being able to see the Aeotec Range Extender 7 in the tree, everything is working as expected. My Update Package worked normally as well. Thanks for your help.

@Bumbershoot, Thanks for the quick reply. Good to know I have the right version. I rebooted Polisy as well just after resetting the Z-Wave dongle for good measure. Adding the extender seemed to work fine, but it never sees the dimmer. I'll move the extender to its proper location and then try to add the dimmer where it will be.

@Bumbershoot, I'm not seeing my Aeotec Range Extender 7 either. It did appear to add it, but it's not in the tree. This time is asked me for the key. But I tried to add a dimmer, and Polisy never sees it. Did the IoX version number change after the update. Mine still says 5.5.0?

I've waited about an hour since starting the upgrade from the Admin Console and Polisy is still at 5.4.5. In fact, it never seems to go into upgrade mode. The left most LED stays solid green and the other lights are blank. In previous upgrades, Polisy emits some beeps right after pressing the Upgrade button and the left most LED goes blank while the right 2 LED's blink. That isn't happening this time. Prior to running this update, I was on IoX 5.4.5 having updated to get the latest PG3 software recently. I checked my OS version and it is 13.1-p4. I think I was pretty much up to date before starting the upgrade. IoX and PG3 are running normally; I just don't seem to be able to get the update to start. I'm assuming an hour is long enough to wait for the upgrade to start and finish. Is that a good assumption? Is anyone else experiencing what I'm seeing?

@gviliunas, Did your IoP update to 5.5.0? I tried Update Packages and nothing happened. I'm still at 5.4.5. No beeps or blinking lights on Polisy.

@Michel Kohanim, Just attempted to upgrade from 5.4.5 to 5.5.0 and the upgrade does not start. The Admin Console closed as usual, but there were none of the customary beeps from Polisy at the beginning of updates and the left most LED is green and steady. I'm able to log back into the Admin Console and the version is still 5.4.5.

I installed the new ZMatter board in my Polisy Pro this afternoon and my system is up and running as before the installation. I have a Zooz Stick and it is still functional; communicating with a couple of Z-Wave devices. I'm fully operational while I wait for the migration and upgrade tools to activate the new board. As others have noted; it was easier to install the antenna leads to the board before installing the board in Polisy. It takes some pressure to snap them in place and this was easier to do without the board being installed.

@bpwwer, I finally had another NS ready for update and it updated normally. Whatever is going on, it must be unique to the Ambient Weather NS. Once I restart the Ambient Weather NS, the "new version" message goes away. But when I return the next day to PG3, it's there again. Just an observation. Maybe there's a clue there.

@bpwwer, I had a notice for the Ambient Weather NS to update to 2.0.7. I'm on 2.0.6. After restarting the NS, the version remains 2.0.6(at least according to the NS info). I've tried this several times with the same results. The PG3 log for that event is attached. I'm running PG3 3.1.15. Can't say if this is limited to this NS. Ambient Weather Update(25Nov22).rtf

@Michel Kohanim, since using IoX Launcher, I too could not launch the Admin Console via the Cloud. But just a few minutes ago, I tried it again and it worked. Maybe it was the website issues. Java Console did not show any errors. Mark

I tried adding this URL, but nothing was added. Now, that URL is how my Polisy is setup in Launcher, so maybe nothing was added because it's already there. Admin Console Cloud doesn't work for me, Admin Console LAN does. Note: I deleted and reinstalled using Start.jnlp Mark

@asbril, I have the same issue with Launcher; I can access Polisy through the LAN connection but selecting Cloud does nothing. There was a change to launcher recently; it is now called IoX Launcher. I suppose this is in preparation for the launch of eisy. There's been no official word on IoX Launcher though. There may be more back end work required before Cloud works again. Also, if I save my launcher configuration and look at it with a text editor, it's junk, no configuration data. The Reboot ISY menu selection was removed in the recent PG3 3.1.14 update. Looks like the Admin Console is the preferred location to reboot ISY.

I'm curious the see what others who updated PG3 are seeing with IoX Launcher. (PG3 updated to 3.1.14 normally) I'm on macOS Ventura 13.0. Launching IoX Launcher, my Polisy is detected automatically. I can load the Admin Console using Admin Console (LAN), but selecting Admin Console (Cloud) does nothing. This used to work. I'm also able to launch PG3 via IoX Launcher. I selected Save to save my configuration, but when I look at the file with a text editor, I see this (was expecting to see Polisy info):