DennisC

Yes, it is out. Look for the release announcement and follow the directions.

You highlighted the error log that indicates to check your IoX IP address. Did you verify the IP address in PG3?

Does upgrading to the latest version of PG3x correct the issue, v3.2.2?

There is one more thing you can try and if that doesn't work definitely open a support ticket. Go to Configuration tab and uncheck Zwave support and then reboot. After Polisy has completely restarted go and enable Zwave support and reboot again.

That is not what I am saying. ZWave addresses use to start with ZW and after migration, they will begin with ZY. Therefore, all programs and/or notifications will require their address to be updated. Some type of intervention might be required, like resaving all programs and updating addresses as mentioned above. I sent you the current link for migration because I wanted you to read through it and make sure you followed all of the directions to the letter. Did you follow the directions exactly and if so, what specific differences are you seeing? Can you explain in more detail? What are you seeing in admin console? Can you query the devices? If devices are not showing status, go to the top level menu and select ZWave - Synchronize - New & Deleted with Interview. Before doing that, if you have battery devices, click the battery icon in the top level menu to turn off battery devices. By the way, the instructions include: " If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration." If your migration didn't work, you can back out and try again. Important, go to Configuration tab and make sure ZWave support is checked.

You need to read through the document attached linked below and follow all of the directions. When migrating from Zooz to UD ZMatter dongle, the Zwave address will change and will require manual intervention. All necessary instructions are here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Be sure you followed the specific instructions for migrating ZWave: If you are migrating your Z-Wave network Leave your current Z-Wave board / dongle connected Go to configuration tab in Admin Console and select "Migrate to ZMatter Z-Wave" Choose the option that allows you to create a "migration" backup (first option) You will see a series of popup windows providing information and asking simple questions Once you have your "migration" backup you are ready to migrate A migration backup is different than a regular backup. When a migration backup is restored it also migrates your Z-Wave network Post Migration If you migrated your Z-Wave Network If you have any Z-Wave nodes with a type of (Placeholder) it means the device has not been migrated yet. In most cases they are battery powered devices that were not awake during migration To migrate one of these devices, wake it up (see user manual for the device) and then do the following right+click on a placeholder node for the device, select Z-Wave | Synchronize | Update with Interview When it completes do the same for the next device

Polyglot v2 is no longer supported. I suspect it won't be long before the associated store will no longer be available. In addition, ISY994 is also no longer supported. You might want to consider an upgrade to eisy and PG3x.

I would suggest you shutdown gracefully and then pull the plug for a couple of minutes before plugging power back in.

I would suggest you start by powering down, waiting a bit and power up again. After about 30 minutes, check your Zwave device. If there is no status, try a query. Also, make sure Zwave is enabled on the Configuration tab of admin console.

I completed the upgrade and it fixed the version number issue. After about 5 minutes of uptime, I checked the node server in the admin console and it was showing disconnected. I had to restart the Elk node server and no all seems fine. Thank you.

After updating PG3x to v3.2.1 and reinstalling all of the node servers, I noticed there was an update to Elk v3.8.0. After doing the upgrade, I noticed the version # on the Elk node server page was v0.0.0. I re-did the upgrade with the same result. I tried to sop and restart the node server with no change.

Start by power cycling your eisy/Polisy. What protocol does the lock use?

@Jimbo.Automates I had this happen to me awhile back with Weatherflow. It turned out there was an old nls file, EN_US.TXT, left over that interfered with proper display of the values. I was told to locate and delete the file, then to restart IoX. Maybe?

Most common reason is a reboot of ISY is required.

Not sure about that, it has been working all week until late yesterday morning.

I sent the requested backup file. However, I am starting to believe this has something to do with Android security certificate. If I lease the premises or turn WIFI off, the camera image appears.

If you still have an issue after trying all of the above, then work through this list: 1. Java applications are blocked by your security settings Close all your browsers Go to System Preferences | Java to get to Java Control Panel Click on Delete Files and make sure you check Applications Click on the Settings Button Make sure Keep temporary files on my computer is checked Click on the Security tab on the top Click on Restore Security Prompts and then click on Restore All button on the ensuing dialog Click on the Edit Site List Click on the Add button Enter https://isy.universal-devices.com followed by hitting the Return key on the keyboard. Accept the warning Click on the OK button 2. Resource cannot be downloaded (admin.jnlp) 99.9% of the cases, this is due to the installation of the following software: Relevant Knowledge Qustodio 3. admin.jnlp does not start the Admin Console If Java is indeed installed, the reason is that .jnlp file association is broken (it has to point to javaws.exe). Search for javaws.exe in the computer. Right mouse click and select "Open with" and point to "javaws.exe" to fix the .jnlp file association. Cannot find Valid Java Home This issue usually happens on Windows and when you have had multiple versions of Java installed especially the older version. What you need to do: Clear your java cache Uninstall all versions of Java using the Control Panel | Add/Remove Programs Delete these directories (if they exist): C:\Program Files\Java C:\Program Files\Oracle C:\Program Files(x86)\Java C:\Program Files(x86)\Oracle C:\Program Files (x86)\Common Files\Java C:\Program Files (x86)\Common Files\Oracle Delete the following directories (if the exist): Open file explorer and click in the tree to reach c:\users\<username>\AppData\ Search for "java" (note: other windows settings and preferences for your user determine where "Java" folders get created. (generally they appear under "sun" and "oracle" folders.) Open Search or click "Windows/Start" button: In the search box, type Environment and choose Edit the System environment Variables Click Environment Variables Under User variables for <username> Click on the Path | Edit and then delete all occurrences of Java and Oracle If you see JAVA_PATH, click on it and then click the Delete button Under System variables Click on the Path | Edit and then delete all occurrences of Java and Oracle If you see JAVA_PATH, click on it and then click the Delete button Click the OK button (3 times to get out of "System Properties") Reboot your computer Reinstall Java 64bit version If you were running the 32bit (x86) version of Java you might need these additional steps after reinstalling Java 64bit version: Open Search or click "Windows/Start" button: In the search box, type Environment and choose Edit the System environment Variables Click Environment Variables Under "System variables" Click "New..." For "Variable name:" type JAVA_HOME (ALL CAPS) For "Variable value:" enter the directory for your new Java install Example: C:\Program Files\Java\jre-#.# [NOTE: #'s will be current version just installed] You can click "Browse Directory.." to find the directory or type or paste it in the entry field. Click OK Find "PATH" (still under System Variables) Click "Edit..." Click "New" Enter: %JAVA_HOME%\bin Pay attention to CAPS Click "OK" (total of 3 times to exit "System Properties" Reboot your computer To confirm Java is on the system start Command Prompt or PowerShell and type java -version. You should get a result similar to: java version "1.8.0_371" Java(TM) SE Runtime Environment (build 1.8.0_371-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode) IoX Launcher should be able to launch correctly every time now. If you still have issues please file a support ticket. Windows should update these entries as Java updates, but should you have issues you might need to update the JAVA_HOME directory above.

I understand this. Correct, the system that was updated to v5.6.4 stopped working. The system at another location running v5.6.3 still works. Favorites and Home respond the same way, neither will display the camera feeds. Yes Done prior to posting my problem here. If you feel this issue has nothing to do with the upgrade, I will look in to other causes

Samsung Galaxy S20+ Since it worked just before I upgraded and it's still working on my other system running v5.6.3, I thought they were connected.

@Javi Upgrade to v5.6.4 0n Polisy appears to have broken my ability to view cameras that were previously added to UD Mobile v1.1.23. I was able to connect to the same cameras this morning running v5.6.3. I checked the Play Store, but there doesn't appear to be any updates available. When attempting to view a camera, the display continually cycles through: Loading, Buffering, Stopped, and then the display freezes and you can not back out of the page. Sometimes, the app then crashes, sometimes it continues and repeats the same cycle. I can still view cameras on an eisy running v5.6.3.

I would wait for @Jimbo.Automatesto confirm, but I would suggest reinstalling the node server in the same slot. It sounds like to me the node server didn't install correctly.

At this point, try reinstalling the node server in PG3(x). Go to Purchases, select the node server, and then reinstall in same slot.

Install Dev Packages is used to install packages required to develop node servers.

Is it possible the node address is listed incorrectly on that screen? Try opening a browser and entering (replace the "x's with your local IP address): https://xxx.xxx.x.xxx:8443/rest/nodes/ Click through the warnings and enter your login information when requested. Then look for the node address.

Go to the admin console of eisy/Polisy, configuration tab, reboot. It is no longer possible to just restart PG3(x).