Techman

@Michel Kohanim Any progress on OTA updates?

The ISY Zwave 500 series dongle has an effective range of about 20 feet. If the other switch is working and it's only 5 feet away from the one you're trying to install then it shouldn't be a problem. All line powered Zwave devices also act as repeaters. All you should have to do is put your new swirch into the linking mode, and then open the Zwave menu on the ISY and click on include.

@GregE Are your ISY firmware and UI the same version? Do you have other Zwave devices installed? What is the distance between the Zwave device you're trying to install and your ISY?

For me the power cycle wasn't necessary, just a reboot from the configuration tab.

Updated with no issues. However, I noticed that on the on PG3x "Purchases" tab it shows the beta and the production versions of the Notification Node Server, which I never purchased. Are they required for the UD mobile notifications and automatically included?

@LKO The following is from the UD Wiki. Did you try plugging the ISY into a different port on your router or Switch? Also try power cycling the ISY if you haven't already done that. Error light and Memory light blinking simultaneously: ISY is not able to get on the network. Please ensure: The Network jack on the back of ISY is connected to your router The lights on the Network jack have one steady on and the other one blinking. If not, check cable and connectivity to the router Your router provides DHCP There are no other devices on the network with the same IP address (IP Conflict) If you have configured your ISY to use DHCP, then you will have to search your network for devices that might be in the same DHCP range as your router is providing If you have configured your ISY with a static IP address, and as long as you have a good backup, you can Factory Reset your ISY and then restore a good backup (File | Restore ISY). Once prompted to change the network settings, choose No

You're welcome. There's a few issues with the current version. They should be corrected in the upcoming update

Remove power from your eisy/polisy. After the reboot give it another try. Are you able to log into PG3x via the admin console?

If you click on "run then" in your program does the network resource complete?

Any other commands in your program that could be interfering with the timing?

The correct procedure to replace the PLM is: Remove power from the ISY Remove power from the PLM Remove the cable from the old PLM and plug it into the new PLM (yes all PLMs are now dual band) Plug the new PLM into the power outlet Wait about 15 seconds then power up the ISY After the ISY reboots, click on restore Modem If you have any battery operated devices, then after the restore modem completes, you'll have to put the battery devices into the linking mode, and then do a restore device.. After you complete the above and all is working properly, you should update to the latest firmware, 5.3.4. Be sure to carefully read the release notes before updating.

Probably best to open a support ticket.

In UD Mobile, go into SYSTEMS, click on your ISY and make sure "Use ISY Portal for Remote Connections" is enabled.

Try removing power from the EISY. That seems to work for some issues.

Make sure that DHCP is selected on your new router. Clear your java cache, including checking the box "Installed applications" then download the IoX finder: https://isy.universal-devices.com/start.jnlp Remove power from the ISY and then boot it up. If the ISY doesn't show up in the finder press refresh. Select the cloud option in the finder to access the ISY and delete the old IP address.

It's probably best to submit a support ticket

Try doing an "update packages" on the eisy. Current IoX firmware is 5.6.2, Current PG3 is 3.1.33

Current firmware for the eisy is 5.6.2. Try removing power from the eisy then do a update Packages. It could take a while for the packages to update, give it about 30 minutes. If it still doesn't update then open a support ticket.

It's probably best to submit a support ticket. https://www.universal-devices.com/my-tickets

It's a documented issue, they're working on it. It should be fixed in the next update.

Did you try removing the power cord from the eisy? Are your eisy firmware and UI the same version?

Are you able to access your programs and devices via the admin console?, If so, then power cycle the eisy.

Try removing power from the Polisy for a minute, then try the update. Also verify that your firmware and UI are the same version.

@bmercier I just tried removing power from the EISY and that appears to have corrected the problem. Previously I tried a reboot which didn't resolve the issue. Could it be a cache issue during the update?

I'm still unable to access PG3x, here's the log [admin@eisy ~]$ tail -f /var/polyglot/pg3/logs/pg3-current.log 7/1/2023, 09:06:12 [pg3] info: Verifying node servers are installed on IoX correctly 7/1/2023, 09:06:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection 7/1/2023, 09:06:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.791212ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 7/1/2023, 09:06:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB. 7/1/2023, 09:06:32 [pg3] info: startRefreshToken: Refreshing Portal token 7/1/2023, 09:06:32 [pg3] info: Portal Authentication: Token expires 7/1/2023, 10:06:31 AM 7/1/2023, 09:11:12 [pg3] info: Verifying node servers are installed on IoX correctly 7/1/2023, 09:11:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection 7/1/2023, 09:11:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.789716ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 7/1/2023, 09:11:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB.