Oakland Jeff

Since I tried starting from scratch with the bedroom switch (deleted it from AC, factory rest it) I am unable to re-link it, so there is nothing for me to try to restore. However, Patti's Room Recessed is still giving me !. Here is the Level 3 Event Viewer during a Restore on Patti's Room Recessed. Wed 11/01/2023 02:46:38 PM : [ 1E 62 F6 1] Preparing Device 'Patti's Room Recesse' for Restore Wed 11/01/2023 02:46:38 PM : [ 1E 62 F6 1] Device 'Patti's Room Recesse' ready for Full Restore Wed 11/01/2023 02:46:38 PM : [All ] Writing 150 bytes to devices Wed 11/01/2023 02:46:38 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:46:38 PM : [INST-ACK ] 02 62 14.BE.B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:46:42 PM : [ Time] 14:46:43 0(0) Wed 11/01/2023 02:46:47 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:46:47 PM : [INST-ACK ] 02 62 14.BE.B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:46:56 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:46:56 PM : [INST-ACK ] 02 62 14.BE.B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:00 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:00 PM : [INST-ACK ] 02 62 14.BF.3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:09 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:09 PM : [INST-ACK ] 02 62 14.BF.3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:12 PM : [ Time] 14:47:13 0(0) Wed 11/01/2023 02:47:18 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:18 PM : [INST-ACK ] 02 62 14.BF.3B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:22 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:22 PM : [INST-ACK ] 02 62 21.D0.FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:32 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:32 PM : [INST-ACK ] 02 62 21.D0.FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:41 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:41 PM : [INST-ACK ] 02 62 21.D0.FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:42 PM : [ Time] 14:47:44 0(0) Wed 11/01/2023 02:47:45 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:45 PM : [INST-ACK ] 02 62 14.D6.91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:47:54 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:47:54 PM : [INST-ACK ] 02 62 14.D6.91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:48:03 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:48:03 PM : [INST-ACK ] 02 62 14.D6.91 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:48:07 PM : [INST-TX-I1 ] 02 62 21 59 44 0F 0D 00 Wed 11/01/2023 02:48:07 PM : [INST-ACK ] 02 62 21.59.44 0F 0D 00 06 (00) Wed 11/01/2023 02:48:12 PM : [ Time] 14:48:14 0(0) Wed 11/01/2023 02:48:16 PM : [INST-TX-I1 ] 02 62 21 59 44 0F 0D 00 Wed 11/01/2023 02:48:16 PM : [INST-ACK ] 02 62 21.59.44 0F 0D 00 06 (00) Wed 11/01/2023 02:48:25 PM : [INST-TX-I1 ] 02 62 21 59 44 0F 0D 00 Wed 11/01/2023 02:48:25 PM : [INST-ACK ] 02 62 21.59.44 0F 0D 00 06 (00) Wed 11/01/2023 02:48:29 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:48:29 PM : [INST-ACK ] 02 62 31.AE.CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:48:38 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:48:38 PM : [INST-ACK ] 02 62 31.AE.CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:48:41 PM : [ Time] 14:48:44 0(0) Wed 11/01/2023 02:48:47 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:48:47 PM : [INST-ACK ] 02 62 31.AE.CD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:48:51 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:48:51 PM : [INST-ACK ] 02 62 31.B6.54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:00 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:49:00 PM : [INST-ACK ] 02 62 31.B6.54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:09 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:49:09 PM : [INST-ACK ] 02 62 31.B6.54 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:11 PM : [ Time] 14:49:14 0(0) Wed 11/01/2023 02:49:14 PM : [INST-TX-I2CS] 02 62 31 B4 65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:49:14 PM : [INST-ACK ] 02 62 31.B4.65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:23 PM : [INST-TX-I2CS] 02 62 31 B4 65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:49:23 PM : [INST-ACK ] 02 62 31.B4.65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:32 PM : [INST-TX-I2CS] 02 62 31 B4 65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/01/2023 02:49:32 PM : [INST-ACK ] 02 62 31.B4.65 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/01/2023 02:49:36 PM : [31 AD B9 1 ] Link 3 : 0FE0 [62011A6830000001] Writing [62011A6830000001] Wed 11/01/2023 02:49:36 PM : [INST-TX-I2CS] 02 62 31 AD B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB Wed 11/01/2023 02:49:36 PM : [INST-ACK ] 02 62 31.AD.B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB 06 (00) Wed 11/01/2023 02:49:41 PM : [ Time] 14:49:44 0(0) Wed 11/01/2023 02:49:45 PM : [INST-TX-I2CS] 02 62 31 AD B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB Wed 11/01/2023 02:49:45 PM : [INST-ACK ] 02 62 31.AD.B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB 06 (00) Wed 11/01/2023 02:49:54 PM : [INST-TX-I2CS] 02 62 31 AD B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB Wed 11/01/2023 02:49:54 PM : [INST-ACK ] 02 62 31.AD.B9 1F 2F 00 00 02 0F E7 08 62 01 1A 68 30 00 00 01 BB 06 (00) Wed 11/01/2023 02:49:58 PM : [31 AD B9 1 ] Link 3 : 0FE0 [62011A6830000001] *Failed Writing [62011A6830000001] Wed 11/01/2023 02:49:58 PM : [INST-TX-I1 ] 02 62 35 73 67 0F 0D 00 Wed 11/01/2023 02:49:58 PM : [INST-ACK ] 02 62 35.73.67 0F 0D 00 06 (00) Wed 11/01/2023 02:50:07 PM : [INST-TX-I1 ] 02 62 35 73 67 0F 0D 00 Wed 11/01/2023 02:50:07 PM : [INST-ACK ] 02 62 35.73.67 0F 0D 00 06 (00) Wed 11/01/2023 02:50:11 PM : [ Time] 14:50:14 0(0) Wed 11/01/2023 02:50:16 PM : [INST-TX-I1 ] 02 62 35 73 67 0F 0D 00 Wed 11/01/2023 02:50:16 PM : [INST-ACK ] 02 62 35.73.67 0F 0D 00 06 (00) Wed 11/01/2023 02:50:20 PM : [INST-TX-I1 ] 02 62 31 AD 1C 0F 0D 00 Wed 11/01/2023 02:50:20 PM : [INST-ACK ] 02 62 31.AD.1C 0F 0D 00 06 (00) Wed 11/01/2023 02:50:29 PM : [INST-TX-I1 ] 02 62 31 AD 1C 0F 0D 00 Wed 11/01/2023 02:50:29 PM : [INST-ACK ] 02 62 31.AD.1C 0F 0D 00 06 (00) Wed 11/01/2023 02:50:38 PM : [INST-TX-I1 ] 02 62 31 AD 1C 0F 0D 00 Wed 11/01/2023 02:50:38 PM : [INST-ACK ] 02 62 31.AD.1C 0F 0D 00 06 (00) Wed 11/01/2023 02:50:41 PM : [ Time] 14:50:44 0(0) This is the link table that the ISY was trying to write to the switch:

OK, some more details... About half of my switches are in permanent "needs to be written" state starting yesterday afternoon. Two switches started giving me the red "!" also at that time. Immediately prior to that, I could communicate and write to all these switches. The master bedroom switch is the one that started giving me the red "!". It seems to be the worst off, and it's most important, so I thought I'd try to resolve it first. I also JUST replaced this switch less than 2 months ago, and it worked fine until yesterday afternoon. What caused this yesterday afternoon? Beats me. I was trying to recover from a bad migration that happened 4 months ago. I restored a back up from several months prior to that in hopes of trying to resolve the bad/stale links to a previous PLM (serial, from my ISY) that others had helped me identify as the problem. So I did the restore, and all the switches were working! Yay, I thought. But I noticed that almost all of device link tables did not match the eISY tables, so I was doing Device Restores on each device, one at a time. Somewhere along the line, about half the switches became "needs writing" green, and a couple switches gave me the red "!".

No joy. None of those suggestions resulted in any observable difference at all

Still trying to recover from a problematic migration from isy to eisy. About half of my switches are in permanent need of needing updates written. I do the write, progress bar finishes without incident, and the switch still shows the green icon. FINE, I'll just delete the switch from AC, factory reset the switch, and start fresh. NOPE! This is what I get when I now try to link the switch: Prior to factory resetting and deleting the switch, this is what I got when I tried to read its link table from AC: Any insight or advice is more than welcome! Thanks, Jeff

Thanks for all of your kind advice (even though I posted in the wrong place) !! ♥️

Hmmm, my paid Kasa Nodeserver is staying Disconnected. And in the Admin Console, I see my 3 lights but their pages have not been populated with any data. Rather new to the eISY and Polyglot, so please forgive the "newbie" question, but what should I try? BTW, may or may not be relevant, but along with all the other updates I just did, I had to restore a new PLM with a 3 month old backup (due to link table corruption). Thank you in advance! Jeff

I did one final verification. I deleted the switch, reset and relinked it. As you predicted, it now has a well-formed E2 link and it is now triggering programs as desired. I'm hoping that the folks at UD can work some magic on a backup file or something so I don't have to manually delete and re-link and reconfigure everything. Anyway, here is my happy-place new link table for the switch I was testing with.

OK, ticket it is. After a quick spot check, I don't think any of my devices have that E2 link to control the PLM. Thank you so much!!!

IndyMike, thanks so much for sticking with this one. So, not all my devices have that null link where my PLM should be. For example, the switch that I used for my test... its link table seems fine in this regard. Attached are both the link table and the program. When I tap the physical switch on, the program doesn't get triggered. Given this info, any other ideas before I submit a ticket?

So I'm not having any luck getting controls to trigger programs. Here's a dead simple one that's not working. It was created fresh after I went through each device and scene, restoring every device (and appreciating the smaller resulting link tables) and testing scenes, and editing them if necessary (by removing devices and replacing them if the Scene Test indicated they "failed"). My link tables should be pretty clean. After all that, all my migrated programs were not working, so I tried to create a new simple test one... seen below. It doesn't get triggered. I'm pretty confident coms is not the culprit, as I can perform any operation I want on that switch from the AC.

Thanks Techman. I understood IndyMike's explanation to cover only the 22's, and accounting for those 3 lines being gone after the restore, I expected to see 7 lines left, but there were only 4. In the end I don't care. If everything works with fewer links, all the better. And that seems to be the case. I've restored every device in my setup, and tested every scene. About 70% of the scenes had at least one failed device, so I deleted the failing ones from the scenes, then replaced them again and reconfigured all their on levels and ramp rates, and now all my scenes are working as expected. Phew! HOWEVER... My sensors are still not triggering my programs. I've tried the same trick... changing the sensor in the program to something else, saving, then putting it back to what it should be, and saving. But this trick didn't work for the programs. Since sensors not triggering the programs is the only remaining issue I know of, I'm going to close this thread as resolved and just work on that other thread. Thanks for all the help!

I didn't notice that! Thanks for the info. That still leaves a mystery consolidation from 6 to 4 links after the restore though.

Yes, it is now!

HA, OK, I just discovered that if any of my devices in the scene are set to Default, the test returns a failure for them. So my updated scene, with both switches set to an Insteon command, succeeds! I had previously left the slave switch as Default before, since it wasn't caring any load and was just coming along for the ride. I thought doing so would reduce traffic, but maybe it's best practice to control them as part of a scene too?

The switch above is part of a simple 3-way circuit and a motion sensor. I restored both switches and the sensor. All 3 shed about half their links after the restore, as above. They are part of programs that manage auto-off, but as per instructions I disabled all the programs before testing the scene. The test still failed.

So I'm noticing something very strange and potentially very cool... Before restore, the Device and the ISY have identical link tables with 12 or 13 links, but after restore, they are still identical, but they only have 3 or 4 links! This blows my mind since I thought the ISY was the source of truth, and how/why would a restore to the device from the source of truth affect the source of truth? Clearly, my assumptions were wrong. Please tell me this is some cool clean-up function of Restore and not a symptom of failed comms!! Here is an example of a short one. some of the links that were Identical but not Ignore are gone. 10 down to 4!

Boy, did I speak too soon about being done with Migrate Madness! As I'm unraveling all the things that are broken after the migration, including ALL of my scenes and ALL of my program's inability to be triggered by control changes, I'm hoping that there is a magic bullet utility that will clean up all the links that seem to be broken? I really don't want to have to recreate every single scene and every single program one at a time. Please, pitch me some salvation here. Any and all ideas are welcome. Yes, I have backups of previously working configurations on the old ISY before migration to the current... That's what I used that landed me in this spot though. Should I try restoring a current backup from the new eisy? Is there code to vet the config file as it imports and correct anything wonky? All of my 50 scenes, except for the ones that I've been working on and have recreated already, look like this pic when I Scene Test. I also noticed that in the Network list of all my devices, if I do All On's and All Off's, the only devices that correctly respond are the ones that I've been modifying by hand. Everything else just stubbornly sits there in its current state. The thing is, as with this example, the device IDs match the physical hardware, so I don't know where the disconnect is.

Oof, OK thanks, I'll give it a try next weekend... THIS weekend's project already spilled well into Monday and today. LOL! I'll reply with results later. Thanks again!

And that's what I did... delete them, factory reset them, and start from scratch. Everything is working perfectly. The new ISY Links table has only 17 entries in it.

Yes, both of my problem new KPLs are replacements for failed devices. I did a Replace With operation after the new KPL was installed, and restored each device too. This left them in a perma 1011 state, and unable to read the device link table. Here is what eisy thinks the link table should be. No idea how to tell if this is corrupt or not. I may just try to delete it and re-link it anyway.

This is the result of me trying to do a Show Device Links Table for one of troublesome KPLs. I should note that the Failed dialog appeared only about halfway through generating the coms in the Event Viewer.

Hmmmmm... Identical, but still not triggering "control is switched on" in the IF of my programs like they used to before migrating...

So most of my motion sensors are the 2420Ms, and they fast flash when they are having comm problems. They are ALL fast flashing when they detect motion. When I watch the event viewer and I manually trigger the sensor by tapping the set button, the event viewer just sits there, silent, blank. To compare, I got my remoteLinc working, and I see 15 lines of events instantly when I tap a button on it. So while motion is not triggering events, the AC successfully writes updates when I do so on the Motions when they are in linking mode, according to the event viewer. So what's happening here? Why doesn't PLM/eisy see motion triggers, but they can communicate with the motion otherwise?

Techman, thanks, great insight! Those two programs both referenced a 2-wire dimmer that hadn't changed in forever, but for whatever reason its record was corrupted during the migration so the lines to beep it, turn it on, and turn it off were replaced by comments that said that node ###### was missing or something like that and that the desired action could not be taken. I restored those lines and the program now works, but none of the sensors are triggering the programs. I'm just bench testing by executing the Thens & Elses by hand.