DennisC

When was the last time you updated? This should have been fixed in v5.7.0. Check your version of firmware and be sure to download a new start.jnlp after upgrading and to clear your Java cache before running the new start.jnlp. Also, see this post:

One possibly good reason to upgrade to an eisy is the ability to incorporate node servers in to your automation. These include weather, device from different manufacturers, alarm systems, enhanced time/date programing, and a whole lot more.

The document below may help you. While the document I linked below was written for ISY994, all of the excellent examples would work the same. https://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf

As @larryllixindicated, only a state variable will trigger a program. It doesn't matter if it is an ISY994, Polisy, or eisy, variables work the same across all platforms. From the wiki on variables https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:Program_Variables: Integer Variables A signed integer (32 bit) Arithmetic operations available in Actions Comparison operations available in conditions Initialized at startup Changes to the value do not cause an event to be sent State Variables Identical to an Integer variable except that changes to the value do cause an event to be sent, causing programs to run

Here are a few things you can try before opening a support ticket with UD. Restart the admin console after trying each one. To find nodes ZWave devices should have: Right+click on one of the Schlage nodes, select "X-Ray", a window will open Do "DH Command Classes" GO Do the same for "Device/Channel Database Object" If you are missing nodes then: Zwave - Synchronize - Update with Interview - restart admin console and Zwave - Synchronize - Update (no Interview) and restarted the admin console.

I believe moving from Z-stick to ZMatter is done through a ZWave migration, not a backup. I don't recall seeing the option of doing a ZWave migration on eisy. However, maybe I don't see it because I am not running a Z-stick on eisy. Might be best to confirm with UD via a support ticket.

Polisy can do everything eisy can for home automation as of now, only eisy is faster. There is also the benefit of being able to access eisy to use as a stripdown computer with it's own monitor. Don't now if that is important to you. UD has committed to supporting Polisy for several more years.

Sounds like you should be asking your questions on the developers Discord channel.

Not sure what you mean: "between hub and controllers" ?

After saving a UD Mobile backup, either email it to yourself or copy it manually to your computer or other backup device. I use an app to automatically backup import files (photos, UD Mobile backup, etc) from my phone to my NAS unit every night.

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.