Techman

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.

You should also have a node for light and temperature in addition to Alarm and Wake. The status window in the admin console won't populate until the sensor sends data which could take a while depending on the sensor settings. What controller and firmware version are you running?

In that case I would run link Diagnostics any any devices that are in a scene with the mico dimmer

Is the micro dimmer in a scene with other devices?

The EA link entry can be ignored, it's not indicative of an error. Take a look at this thread Device Links Table Corrupteds - INSTEON Communications Issues - Universal Devices Forum (universal-devices.com)

It might be because the EISY status shows the last command sent to the IOLinc. How are you triggering the IOLinc? When you send an OFF signal to the IOLinc doesn't also trigger the relay?

To compare link tables, right click on a device, click on Diagnostics | Show device links table. After the link table populates, click on Compare. If there any any mismatched links they willl show up after the compare runs. If you have mismatched links then do a restore device which will overwrite the device links with the links stored in your controller It's not unusual for link tables in a device to get corrupted, possibly due to noise on the powerline. Here's an article to troubleshoot random on events. Note: these events will not show up in the log. https://wiki.universal-devices.com/INSTEON_Random_All_On_Events

Create a scene, Put the light and motion sensor in the scene, add the motions sensor as a controller. If you want the light to come on at a lower intensity then you'll need to set the light on level in the scene.

It's possible that one of your device's link tables contains a link to the since removed X10 device. Best way to check is to perform a link table diagnostics / compare on each of your existing devices. If there's a mismatch in a device link table you just have to do a restore device to clean it up.

Zwave requires a seperate backup. I was going to suggest that you do a restore Zwave, but being that you never backed up your zwave there's nothing to restore. When you include your zwave devices, start with the Minoston switch which will act a a zwave repeater for the locks. If you are still unable to include the locks then you may have to move them closer to the ISY to exclude/include them. Adding a zwave repeater between the locks and the ISY should improve the zwave network. If you're still unable to install the locks it may be because S2 security is enabled on your devices. I don't think the 300 series board suported S2 security If you're still having issues with adding the devices try doing a factory reset on the zwave dongle, then an exlude / include on your devices. Once you have all you zwave device installed, do a zwave backup.

In that case the firmware you need is 5.0.16C. The link is in an above post. Did you do a zwave backup prior to any firmware updates? Do you see your zwave devices in the device tree?

What version of the zwave dongle do you have (300 or 500)? What is your current ISY firmware version? Are your Insteon devices and programs all working?

Do you have the 300 or the 500 series zwave dongle? If it's the 300 series then you need the 5.0.16 firmware https://forum.universal-devices.com/topic/27669-5016c-isy994-last-version-to-support-z-wave-300-series/

Were you using the 2448A7 (RF only) USB dongle? Glad you're up and running. You should now have a much more reliable system.

What error are you getting? Not sure what you mean "upgrade the PLM from OTA" There are two PLM models, a Serial and a USB. Did you follow the "replace PLM procedue"? (see attached file) Note: this is for the ISY994 but is basically the same for the Polisy and EISY Replace Modem.pdf

The contacts on the SD card can become oxidized, cleaning the contacts with a soft eraser usually works.

It's best to wait for a response from UD support as I'm not sure what would happen to your programs if you didn't migrate both Insteon and zwave at the same time.

UD support is usually not available on Saturday, but you should hear back from them within the next day. It's best to get your Polisy up and running in order to migrate. What zwave dongle(s) are you using on the Polisy and EISY? Zwave needs to be backed up separately and in addition to Insteon.

I had that happen with one of my motors, the self contained battery failed and I had to replace the entire motor. Glad you were able to exclude it. Is the battery removable or do you have to replace the entire motor.