Techman

INSTEON Random All On Events Random All On events are related to INSTEON commands being sent to the PLM from ISY and, on the other hand, one (or more) INSTEON devices sending events to the PLM at the same time and thus causing packet collision. RF/dual band devices increase the likelihood of this event since they send two packets for each signal. The combination of the following technique will dramatically reduce the likelihood of All On events: You don't have any programs that use Control for a device and then send a Scene command to a scene which includes the same physical device. So different buttons from the same KPL are considered one device Don't Use a Control for a device which is already a Controller for some Scene and then have the program send other INSTEON commands to other devices/scenes. This basically causes two or more events arrive at the PLM at the same time In addition, motion sensors with low battery, sometimes go crazy and start sending sequences of on/off every second or so. As such: Check Tools | Log for sequences of motion sensor on/off every few seconds and in succession If you do have those, change the motion sensor battery NOTE: All on events won't appear in the ISY log because they didn't originate from the ISY. Powerline noise and/or a defective device can also contribute to an on event.

It's possible that your firmware and UI aren't the same version. Clear your java cache, including checking the box all installed applications, then download the IoX installer.

@Illusion Glad to hear you're back in business. The extra nodes can be ignored. Not sure why they're created, but that seems to be the case with most zwave devices. It might be a compatibility component of the switch being used by various controllers. I put the unused nodes into a separate folder to get them out of the way.

Anytime you add, delete or change a Zwave device you should do a Zwave backup which backs up the data on your Zwave dongle.

@vmastros Are your firmware and UI the same version? Can you post a copy of your program Also, run a diagnostics on the switch. Right click on the device, click on show device links table, after the window fully populates, click on compare at the bottom of the window. Does it then show any mismatched links?

Clear your java cache, including all installed applications, then install the IoX Launcher. https://isy.universal-devices.com/start.jnlp Did that resolve your problem? start.jnlp

Unplug everything from the outlet, then plug a lamp into the top outlet. Can you control the lamp from the Keypad?

You should submit a support ticket https://www.universal-devices.com/my-tickets

Try removing power for a few minutes, then power it up and let it reboot.

@JRC Try removing power from the eisy, then rebooting. Have you tried a different ethernet cable between the eisy and your switch?

@rxjock Were you able to resolve your issues, if so how?

You can rebuild the link table in the device by right clicking on the device then click on "restore device." SwitchLinc LED will blink red to indicate noise on the powerline. Have you added any new electronics lately. Is your PLM isolated from other electronics? Here's some trouble shooting tips INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com)

The red leds usually indicate a communications problem. Run a diagnostics | show link tables on one of the switches that is flashing red. After the link table populates, click on compare (on the bottom of the link table display. Do you have any mismatched links? Do you have any error indicators on the left side of you links in the device tree, either red exclamation points or green symbols?

@rxjock So, is everything working now? Do you still have red leds? If you query one of your devices do you get any errors?

@rxjock It sounds like your PLM has failed. Try removing power from the PLM and the ISY. Wait a few minutes, then power up the PLM, wait about 30 seconds then power up the ISY. Are you then able to access the ISY from the admin console, if so, click on TOOLS | DIAGNOSTICS | PLM INFO / STATUS. Does the PLM show as connected?

@Sparks Press the button on the front of the eisy once. That will update the eisy and pg3x. Wait about 10 minutes then log into the admin console and click on reboot in the configuration tab.

The ISY doesn't have an internal PLM, it uses the 2413S PLM which is connected to the ISY via the cable that was included with the ISY. The eisy doesn't have built-in Zwave, you would need the external Zmatter card and enclosure sold by UD. ZMatter USB: Z-Wave+ & Matter Module for eisy (Beta) - Universal Devices (universal-devices.com) The migration process is dependent upon your current hardware and firmware, i.e. do you currently have zwave, what is your current ISY firmware? When you get ready to migrate there are detailed migration instructions available.

HTTPS is more secure than HTTP because it uses encryption to protect information as it is being sent between clients and servers. If you were to use the cloud access rather than local, https provides better security

You could try uninstalling it, factory resetting it, and then reinstalling. What is the hardware device you installed, make and model?

Do you have the 300 or 500 series Zwave board in your ISY? Is your ISY firmware and UI the same version? Did you wake up the leak detectors before you tried Synchronize?

@vmastros Take a look at this wiki article regarding communication issues. https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

@geddy I stand corrected. The node names, which had a prefix of ZW didn't change, but if I look at the actual node it changed to ZY

When I migrated from the ISY to the EISY all my Zwave nodes maintained their ZW prefix in the eisy except for a few nodes that didn't exist in the ISY but appeared in the eisy, such as "Scene Responder"

Are you still on a Polisy? What are your firmware and UI versions If a Z-wave node is blank or unresponsive, right click on the node, click on Z-wave | Synchronize | Update with interview. All the active Z-wave nodes should have migrated as ZW nodes. The ZY nodes either need to be updated, or are nodes that aren't being used, in which case you can create a folder called unused nodes,and move the unused nodes into it.

@dex Did your previous system have a Z-wave dongle installed?