Techman

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.

@kzboray You should probably send an email to Insteon support as they may not closely monitor their forum. Some of the firmware mentioned in your posts has since been updated. There's no way to for the end user to retroactively flash the older firmware. The only option would be to replace the device. support@insteon.com

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

If the motion sensor status changes to off before the 30 seconds in the THEN clause completes then the ELSE clause would run and the scene wouldn't turn off. Try also putting the "SET (light scene) off" in the ELSE statement.

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?

I'm not 100% sure, but it appears to be an issue with the PLM not the ISY. I just took a look at the Insteon forum and didn't see any reference to an all on Home - Insteon Discussion Community

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.

The PLM firmware cannot be updated by the end user. From the UDI Wiki: 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

You can put both MS in a scene as controllers along with your lights. When either sensor activates the scene will turn on the lights.

You can't query a battery operated device because the device goes into a sleep mode to preserve battery life and doesn't see the query.