ss42

Thanks Techman and Andy for the suggestions, I had tried both before, and again just now, with these results: Trying the rt-clk Restore Device on the devices that dont work gives the "would you like to proceed" modal, I respond OK, and nothing happens. There is still an exclamation mark in the device tree view. And still no device control for those devices. On the full PLM reset, I did the Restore Modem (PLM), and I see the "system busy" progress for what looks like way too short of a time. I can see briefly "reset PLM", but no comfort that link tables are being downloaded. This is a new USB PLM I bought to go with eisy - I was paranoid that either or both of the serial U413S I used with my isy994 were defective in some way. ... I didn't do the "power up the PLM with the reset button depressed" dance, is that possibly why Restore PLM doesn't seem to be working? I've attached my event log for the actions described above just now. I suppose I could nuke the devices and start over, but some of the devices are in hard to reach places that are difficult to get into reset mode. Thanks so much in advance for any next step suggestions. ISY-Events-Log.v5.8.4__Sat 2024.09.21 09.14.21 AM.txt

Just got a new eisy device and USB Insteon PLM to replace our trusty isy994. The switchover was as easy as the docs said. The desktop and mobile apps working fine. Even the integration with Alexa - just worked. Nice! With one hitch: About a third of the Insteon devices show up in the apps - but they do not respond to any command. Apologies if this is covered elsewhere in the doc: But how can I fix these devices which apparently got confused in the update? I would like to avoid the brute-force of removing them all and adding them back in. I tried and failed with several permutations of the link learning, but maybe I got it wrong? The brute-force (that works) is to remove the device, synchronize, and them add the device address-model-name tuple back in as if it were new. Hoping there is trick to kick eisy (which already knows the device address-model-name) to find a new link that works. This behavior is not intermittent in any way: The Insteon devices that function work reliably. The Insteon devices that do not, never do. Any pointers appreciated.