MarkJames Posted December 29, 2023 Posted December 29, 2023 I bought my eISY last year to upgrade my 994. I replaced my 2413s with a 2413u, ported everything over and for the last few months all has been well. Recently my eISY has lost connection to the 2413u. In diagnostics it says 'not connected' I did a hard reset on the PLM, power cycled the eISY and made sure the cable was plugged in properly but no luck. This sounds like a PLM failure, right? Or is there something else for me to try?
Techman Posted December 29, 2023 Posted December 29, 2023 Is the green led on the PLM lit? What's the 4 digit date code on the PLM. What's the firmware version of the PLM? Have you tried replacing the USB cable
MarkJames Posted December 29, 2023 Author Posted December 29, 2023 Thanks for the quick reply Green LED is on. The reset procedure went as expected Revision 2.6 1223 I don't have another cable like that to try so no - I'm stuck in that regard
Techman Posted December 29, 2023 Posted December 29, 2023 The PLM is the current version, it's rare for that to fail so soon. Try unplugging it for a few minutes. If that doesn't help then try a different USB port on the EISY and/or a new USB cable 1
MarkJames Posted December 29, 2023 Author Posted December 29, 2023 Thanks, I'll try and post back either way
paulbates Posted December 29, 2023 Posted December 29, 2023 9 hours ago, Techman said: The PLM is the current version, it's rare for that to fail so soon. Try unplugging it for a few minutes. If that doesn't help then try a different USB port on the EISY and/or a new USB cable I recently set up a new eisy on a new 2413u and had the same problem. It took several eisy power off / on cycles, including a longer off (~30 secs) for it to work.. and since then its been fine.
Solution MarkJames Posted December 29, 2023 Author Solution Posted December 29, 2023 So it's embarrassing to admit this but it was my own fault. I was changing some entries on the configuration page the other day and I must have accidentally unclicked 'enable insteon support'. Re-enabled and now working. I must have touched my touchscreen or something sigh. Thanks for the help, though.
Recommended Posts