November 1Nov 1 I migrated from an ISY994i with both Insteon and Z-Wave devices that all worked fine in the 994i, to an EISY after saving the Z-Wave and ISY backups and loading them into the EISY. Some of the Insteon switches work, but most don't. In one case there are two identical switches side by side on the same power line, one works, the other shows a node error. I have a mixture of different types of Insteon devices and there seems to be no pattern in which work and which don't. The Z-wave devices seem to work on the EISY although I've only played with a few.I'm using a the same serial PLM I used on the 994i and can go back from the EISY to the 994i with everything plugged in exactly the same way in both, reload the same backup file into the 994i I used on the EISY and everything works perfectly, Insteon and Z-Wave. Returning to the EISY setup, it behaves the same. Some Insteon devices work, most don't. I've tried doing multiple Query and Write Changes to the devices with no improvement.All the packages are shown as the current versions. I tried upgrading to the Beta version 1.4.8 and it's mostly the same although one switch that didn't work in 1.4.6 now works in 1.4.8. Most Insteon devices still don't work. I'm using an Ethernet connection for both the 994i and EISY.This is from the About page.UUID00:21:b9:f2:72:43OS Version14.4-RELEASE-p6Node.jsv24.16.0Memory20%1.5 GB / 7.7 GBStorage5%4.2 GB / 91.0 GB Edited November 1Nov 1 by RDoc
November 2Nov 2 Try removing power from both the PLM and the eisy. Wait about 30 seconds then power up the PLM. Wait 30 seconds then power up the eisy.Let me know if that fixed your issue Edited November 2Nov 2 by Techman
November 3Nov 3 Author Techman: I tried that an there's no change. I also listed the PLM links and the links to the failed node devices are in the PLM list. I also tried manually switching the light on and when I did a query on the switch in the eisy-ui it correctly showed the switch as on. However, when I tried turning it off in the eisy-ui I got the same note failure and it didn't turn off. It seems to be connected and can be queried but the EISY can't control it.
November 3Nov 3 Try doing a restore device on one of the failed devices to see if that corrects the issue
Monday at 04:24 AM3 days Author Thanks for the replies. I tried that early on with no change. I'm getting a new USB PLM to see if that makes any difference.
Monday at 01:41 PM2 days @RDoc , can you run a query on one of your problem devices with the event viewer to to level 3 (and post it). I can remember others having similar issues with the EISY showing node errors where no problems existed. I'm thinking you are having the same issue (no actual communication error exists).I would NOT advise upgrading to a new PLM at this point. Doing so will require writing the new PLM address to all of your devices and will needlessly complicate things. If your old PLM works with the ISY994, it should work with the EiSY.
Tuesday at 10:34 PM1 day Author Unfortunately the log looks like there is an error. events-2026-11-10T22-32-21.csv
Tuesday at 10:57 PM1 day @RDoc , your query did NOT return an error -Your device responded correctly to the query with 2 Hops remaining (good communication).The ERR 0 notation is the EISY indicating that there is no error (or that it is clearing a previous error).Regardless, what you posted shows the device communicating normally. If you see an ERR 1 in the event viewer, that is typically a timeout error. [INST-TX-I1 ] 02 62 20 AB 28 0F 19 00 [INST-ACK ] 02 62 20.AB.28 0F 19 00 06 LTSREQ (LIGHT) [INST-SRX ] 02 50 20.AB.28 52.63.4C 2B 00 FF (FF) [Std-Direct Ack] 20.AB.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 [20 AB 28 1 ] ERR 0
Tuesday at 11:41 PM1 day Author I finally got these devices to work, although I'm not sure exactly how. It seems to be a combination of Restore Device rapidly followed by Write Changes, or something like that. Apparently the communication link was there but for some reason both ends weren't communicating over it. Some variation of a deadly embrace?If it were me, I'd put some effort into figuring out how the com link gets hung like that.Thanks everyone for the suggestions and encouragement.
Create an account or sign in to comment