Techman

What EISY firmware version are you running Are you using the MS1 or MS II Have you tried replacing the battery. If you move the MS closer to the EISY does it then correctly show the status?

It sounds like some of the link tables in your devices may have been corrupted prior to the migration Do a restrore device for the devices in the scenes(s) your're having a problem with. What was your ISY994 firmware version? Was your firmware backup current prior to the migration? Did you uddate the EISY firmware prior to migration?

With the EISY it's either LAN or onboard WiFi, it doesn't support both protocols at the same time.

You can program the sensor to send only an ON command by checking the "on command only" box under the MS options. You'll first need to put the MS into the linking mode

Your then statement should turn on the SCENE not the KPL button

Have the program turn on the scene not the KPL button Not sure \what you mean by "find the P{M link table"

All 3 devices in the scene are going to turn on when any one of them is turned on.

If it doesn't show up in the Topology report then the only other option I can think of would be to factory reset the device and try to add it using the admin console. If it adds, then do a sync in UD Mobile

If all 3 devices are in a scene as controllers, then all 3 will all turn on when one of them is turned on. You'll have to create a 2nd scene with a different keypad button in order for your program to work

Are sure the device isn't somewhere in your device tree, maybe under a different name Under tools, run a topology report to see if it shows up there.

Remove the switches from the scene. Leave the keypad button in the scene Change the THEN statement to: Set Scene ON Change the ELSE statement to: Set Scene OFF

Try reboopting the eisy Do a sync on UD Mobile Is the keybpad still working?

@rskirch The link tables from the scene may still reside in the devices that were in the scene. As @tazman suggested, do a factory reset on the device(s) that were in the scene, then a restore device(s).

It appears that your scene may be corrupted. Try deleting the scene and then recreate it, adding only the devices you want in the scene Let me know if that resolves it.

If you do a restore device. the link tables in the device will be rewritten with the link tables that are stored in the eisy. You can check and/or verify your device link tables using the diagnostic option in the device's right click menu i.e. show device links, after the table populates click on compare. That will compare the links stored in the eisy with the links stored in the device. If there's a link mismatch it will highlighted.

If you're moving to an EISY and If you're unable to exclude the zwave device(s) you can delete them from the ISY then factory reset the device(s) before including them in the EISY

Link for the manuals Door / Window Sensor 6 : Aeotec Help Desk (freshdesk.com)

If you're still getting extra nodes try doing a factory reset on the range extender.

I have a range extender 7 which only installed one node. You can try unistalling and reinstalling to see if the spurious nodes still show up.

It's not unusal to have extraneous nodes, you can ignore them. Create a folder called unused nodes and move the nodes into the folder to get them out of the way.

The node status windows in the Polisy/EISY won't show data until the device's node status changes. Both the sensor 6 and 7 should be completely compatible with the zmatter dongle. Note: check the device suport notes as you may have to change a device paramater.

If it's showing up as v.00 then you should uninstall and reinstall it. When you reinstall the MS, in link management, select "link a sensor", "Motion Sensor II"

Adding to @larryllix suggestion, the serial PLM requires a USB to Serial convertor. It's one more thing that can fail.

Are you leaving your admin console open for an extended period?

You might try moving the sensor closer to the Eisy and then try the update again. If it then still shows 2.16 you could try doing a factory reset on the device and then a firmware update. Being that you've successfully updated one of them you're update process is correct.