DennisC

From the UD migration document: The original implementation on Eisy / Polisy can use generic Z-Wave controllers such as the Zooz stick, or, it can use the ZMatter Z-Wave controller (either board or USB dongle). The ZMatter Z-Wave implementation can only use the ZMatter Z-Wave controller (either board or USB dongle).

Backing up Zwave is from the top level Zwave menu. This needs to be done before backing up eisy.

For your issue, go through the list of steps here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Finder_does_not_find_ISY

For the ISY994, the last firmware was 5.3.4 if you are not using Zwave or you are using Zwave and have the 500 board. Try upgrading to the last stable version and after upgrade is completed, power cycle the unit.

Are you sure you don't have a conflict with another program? Try a search using the front door and the light to make sure. Once that is ruled out, try rewriting your program to list the sunrise/sunset trigger first and enclose it in ( ) by clicking the brackets on the right and moving them in to position. Doing this will insure that condition is met first. Having the light status is off will mean that the if condition will re-evaluate as false as soon as the light turns on. I don't think that is what you want. I would remove that and use a variable to monitor when the light is already on.

I'm not clear if you tried restore device from the menu you see by right clicking on a device? You can also try plugging the PLM in to a different outlet on a different circuit. Have you plugged in anything different recently? Maybe some LED lights or something with a transformer? If so , it might be causing interference with the Insteon signal. Make sure the PLM is not plugged in to a surge suppressor power strip or a UPS.

If you are getting the not found message, you need to completely clear your Java cache (all 3 boxes) and then download a new start.jnlp. After running the new start.jnlp you will have a new IoX Launcher on your desktop. That should stop the message. If you still have red, try the restore device I mentioned earlier.

Try right clicking on one device and select restore device. Did that correct the problem for that device?

Was this repaired PLM just installed or has it been working? Try right clicking a device that is not working and select restore device.

Did you follow all of the migration instructions from the wiki? To start, check Tools from the main menu and make sure your PLM is connected and it shows x amount of links.

Do you have any Zigbee devices? If not, is Zigbee support checked? You should probably flag @Javifor specific help.

If you have a portal subscription, you sign in to the portal and obtain the URL from their that you add to the admin console.

I'm not in front of the admin console, but under Tools in the top menu check the number of links for the PLM. If none, the PLM is bad. If you just installed the PLM, make sure you plug it in 30 seconds before your ISY device.

Use the portal IP address and login using your portal credentials. The IoXauncher is used by selecting add a d then entering the IP address of your portal device, which you can find on the portal. Once logged in to the admin console, go to File Backup. You can also find your portal IP from UD Mobile,Settings - System.

Also, to prevent possible issues, download a new start.jnlp. Don't attempt to run a previously downloaded copy.

Typically, after an update of firmware and PG3, you need to reboot to complete the process. Then when you sign in to PG3 you will see a notice at the bottom of the screen that PG3 needs to be restarted. Try rebooting again and see if that clears up your issue.

Besides what @Geddysuggests, it might be necessary to delete your "state" files. Look in the wiki if you need directions.

If I double-tap the Launcher. I get the message “Not Found” twice, once apparently for each of two networks. But, after acknowledging each message, the addresses for each network appear. When a LAN address js selected the Admin Console appears for the LAN. All appears well at that point. You can correct this issue by clearing your Java cache being sure to check all 3 boxes. Next you need to download a new start.jnlp and run it. This will download and place a new IoX Launcher on your desktop. You mention in your post you deleted files, but you need to do it again and download new start.jnlp. The link is in wiki.

There were issues with the discovery process and UD made improvements in how IoX Launcher discovers eisy/Polisy. Which is why a new start.jnlp needed to be downloaded.

It wasn't supposed to stop that from happening, since it is a normal condition. There were issues with the discovery process and UD made improvements in how IoX Launcher discovers eisy/Polisy. If it finds the device by local host and IP address, they will both be listed and both will work. Since this is normal, it shouldn't be of concern.

The fix is in the start.jnlp file. It needs version numbers that are stored there and allows IoX Launcher to match the version of firmware.

@kalman8, when you go to clear your Java cache, are you checking all 3 boxes? You need to download a new copy of start.jnlp, not run a previously downloaded copy. Are downloading a new start.jnlp?

@Geddyis correct about this issue impacting several people last week. The fix is too clear your Java cache, making sure to check all 3 boxes, then download a new start.jnlp from UD's website. The link to start.jnlp is in the wiki. After running start.jnlp a new IoX Launcher will be added to your desktop. This should clear up your issue.

Doesn't really matter, if you want to use node server and/or native notification support in UD Mobile, you will need to upgrade to eisy. You can not install v5 6.2 firmware on an ISY 994.

ISY 994 can not upgrade past v5.3.4 or 5.0.16c, depending on if you are using Zwave and which board you have.