Techman

Click on Help | About and verify that your firmware and UI are the same version. Try rebooting your EISY/Polisy

Create a 2nd program and move everything in your THEN statement to the THEN statement in the second program. In the first program have the THEN statement call the THEN statement in the 2nd program. The 2nd program will complete even if the door is closed.

@agoltz Clear your java cache, including all installed applications, and then download the IoX Finder from here: https://isy.universal-devices.com/start.jnlp

@agoltz When you change a PLM you'll always need to manually wake up battery operated devices in order to write the new PLM address into the device.

What is your EISY and UI firmware versions? Did you clear your java cache, including all installed applications, and then download the IoX Finder from here: https://isy.universal-devices.com/start.jnlp

Have you tried rebooting your eisy/polisy?

@TheA2Z Take a look at the attached screenshot. You should first try resetting the eisy network by clicking the front button 4 times

You now need to update the eisy to the current firmware. Click on "update packages" in the configuration tab. It could take a while for the update to complete. This will update your firmware to 5.6.2 After the update you'll need to clear the java cache and then download the IoX Launcher again

Are you on a PC or MAC? Clear your java cache including checking the box "all installed applications", then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp Let me know if that resolved the issue.

Are your firmware and UI the same version? Try removing power from the eisy for about 30 seconds.

The PG3x update is working, I'm now on 3.1.29.

Tried to update the EISY from 3.1.28 to 3.1.29. Seems I'm stuck on 3.1.28. I tried several times using both the update packages and a single button push on the eisy, with reboots, to no avail.

The antennas are color coded, there should have been instructions that came with the Zmatter board that detailed the antenna placement. The red banded antenna is Zigbee/Zmatter

The ESY has four 3.0 USB ports so there's really no need for a splitter.

The Zmatter enclosure has a standard USB connector. You can locate it outside of your cabinet using an USB cable which connects to the USB port on the EISY.

You might have a corrupted link table in the device, try doing a restore device

After a reboot the device status will default to blank until a device status change takes place. If you want an immediate status update on all your device(s) do a query or query all

If I recall there are other options above or below the Migrate option, but I don't remember what they were. Once you click the correct option that menu will go away and your zwave will be fully operational.

No issues with the EISY. Update went smoothly.

@mmb If your ISY has the 500 series zwave board and your Polisy has the zmatter board then zwave will migrate without having to do any exclude/include functions. On the other hand if your ISY has the 300 series zwave then you'll have to manually exclude/include each zwave device

Restore device - re-writes the link table stored in the controller to the device. This is useful if the link table in the device is mismatched / corrupted.

Did you do a compare to see if the ISY and Device link tables match? Trying a restore device on the keypad and the Switchlinc as it's possible that the link tables got corrupted.

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.