Insteon devices stuck in config pending after upgrade to 3.5 Insteon Beta to 4.3.8

Newly upgraded to 4.3.8 from 3.4.5 with Insteon Beta binding. After upgrading, installed the 4.3.8 Insteon binding, and most devices began working after taking a while to read device databases, etc.

A few devices stuck in Config pending state, which seemed to be resolved after disabling/enabling the device, and then using the buttons on the device to turn it on then off (I have not tested to see if all these steps are needed).

I have one device I tried to remove, and it stuck in “Removing” state. After an OH restart, it went back to Disabled. Another try at Removing left it stuck in Removing state again; without another restart, clicking Remove again raises a prompt warning that force removing may cause instability, do you really want to proceed. I cancelled…

A note (and I’ll raise a request on Github for this) – most of the Insteon debug messages show the device address as aa.bb.cc, but a few show aabbcc, making it difficult to filter for all messages related to a device.

I’m planning on moving on ahead to 5.1 soonish, so no need from my perspective to fix anything on 4.3.

I’m marking this resolved since the primary issue was solved via the disable/enable/manual button press.

1 Like