Techman

The battery operated remote can only be added to a scene as a controller. In the admin console you'll notice that's there's no relationship associated to the "is responder to". This is by design. If you list a device that is capable of being both a controller and a responder, then the associations would show up.

What format is your firmware file in? UDI OTA supports .gbl and .otz

The IoX Launcher supports Java 8. It may not support OpenJava (OpenJDK) You can try clearing your java cache and downloading the IoX Launcher again https://isy.universal-devices.com/start.jnlp

First you need to clear your java cache, be sure to check all 3 boxes then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp The downloaded launcher will place an icon on your desktop.

Correct. It can only be a controller. It is unable to "respond".

You could create two scenes, one with and one without the device, then have a program call up the scene based on the time. The battery operated devices will need to be put into the linking mode to update their link tables

After the update did you clear your java cache and download the IoX Launcher?

Updated eisy to 5.7.1. All looks good. No issues

@TMcCarthy Is the green led on the PLM lit, if not then its power supply failed. 10 years is quite old for a PLM. The older PLMs has issues with capacitors failing. In the long run you're better off with a USB PLM as there's less to fail.

@ShawnW Check to see if there were any additional nodes that were installed during the migration that are showing ON/OFF. I just took a look at my Zwave devices, and some are showing the ON/OFF status. Try a Zwave Synchronize by right clicking on one of the devices then click on synchronize.

Try clearing your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp Let me know if that resolved your issue.

When you clear your java cache be sure to check all 3 boxes You should download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

@rlebel It's working as designed. The time will automatically adjust for DST or not based on your location.

What are you using for a motion sensor. Is it battery or A/C powered. What do you mean by it "won't handle all situations", can you elaborate.

@jdlugosh The information you're looking for is towards the bottom of this manual. 2334-2222 Keypad Dimmer manual.pdf

@KHouse Take a look at this document, the ISY Cookbook, It has a lot of insights into programming. It may take a while for the site to load, you can then save the pdf file for future reference. universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf

Your program will only run if the time is exactly 9:00 pm and the light is switched on at exactly that time. Change the first line to Basement Lights STATUS IS ON

Some Z-wave devices tend to install nodes that aren't applicable to UD Controllers. I created a folder and moved those unused nodes into the folder to get them out of the way. When you migrated to the Zmatter dongle the Zwave prefix changes from ZW to ZY.

I think the controller is able to buffer the commands, however i usually put a second or two wait time in between commands to allow a little breathing room.

Probably best to submit a support ticket. I've never come across the "check log" entry and it's not in the list of error codes.

I think the problem is that you have several conditions in your "Dusk Sensed" program so the next run time is not a hard number. Try deleting the first two conditions leaving only the Sunset condition and see if the next run time is then correct.

My programs ran at the correct time. It appears that the UI sunrise / sunset display is incorrect.

To factory reset the Z-wave dongle: In the admin console, click on Z-wave | Advanced | Factory reset Z-wave dongle

There's no option to make that change. Maybe in a future firmware update.

@Chris Jahn After the switch to PST my eisy sunrise and sunset display times are also off by an hour. My firmware is 5.7.0_5