I'm wondering if perhaps I've really screwed something up. Back in September I had some issues with my old PMU (https://forums.homeseer.com/forum/li...interval-reset) and decided to buy another unit. However, over the next 48 hours or so, the PMU started working again, so I decided to just hang onto the new unit and wait for it to die again. This weekend the unit was really starting to take a long time to respond to commands, so I thought maybe it was time to finally replace the unit. So I tried.
When I swapped out the unit, the first thing that happened is that HomeSeer couldn't communicate to the new PMU, so I backed up the Insteon.ini and changed the PMU address. I then noticed that the COM port number had changed in the Device Manager from COM4 to COM8, so I made sure to update that as well. That seemed to work, but when I went to Program Replacement/Swapped Interface, it appeared to go through the motions of reprogramming all devices, but at the end it reported that it could not communicate to any of my insteon devices to reprogram them (and the interface was no longer communicating). After stopping and restarting the plugin a few times I was able to get the interface to communicate again, but the same thing happened when I tried the programming again.
I tried uninstalling the COM port and reinstalling it, and switching it back to COM4. I've also tried factory-resetting the new unit. I was successful in manually trying to reprogram 3 or 4 of the Insteon devices from the list of devices that it says are unregistered, but when I try any more, I get "device was not completely reprogrammed". I seem to be losing connection to the new PMU regularly, and it takes several attempts of stopping and restarting the plugin to get it to reconnect.
Finally I've restored the backup copy of the old INI file and swapped back to the old PMU. However, it's not a lot better, and I'm sure some devices now have no idea which PMU they are supposed to connect to. A "Reset and Reprogram Interface" (on the old PMU) fails and causes HomeSeer to lose connection to it, and I'm afraid at this point to try anything else. Any suggestions on what I might do?
When I swapped out the unit, the first thing that happened is that HomeSeer couldn't communicate to the new PMU, so I backed up the Insteon.ini and changed the PMU address. I then noticed that the COM port number had changed in the Device Manager from COM4 to COM8, so I made sure to update that as well. That seemed to work, but when I went to Program Replacement/Swapped Interface, it appeared to go through the motions of reprogramming all devices, but at the end it reported that it could not communicate to any of my insteon devices to reprogram them (and the interface was no longer communicating). After stopping and restarting the plugin a few times I was able to get the interface to communicate again, but the same thing happened when I tried the programming again.
I tried uninstalling the COM port and reinstalling it, and switching it back to COM4. I've also tried factory-resetting the new unit. I was successful in manually trying to reprogram 3 or 4 of the Insteon devices from the list of devices that it says are unregistered, but when I try any more, I get "device was not completely reprogrammed". I seem to be losing connection to the new PMU regularly, and it takes several attempts of stopping and restarting the plugin to get it to reconnect.
Finally I've restored the backup copy of the old INI file and swapped back to the old PMU. However, it's not a lot better, and I'm sure some devices now have no idea which PMU they are supposed to connect to. A "Reset and Reprogram Interface" (on the old PMU) fails and causes HomeSeer to lose connection to it, and I'm afraid at this point to try anything else. Any suggestions on what I might do?
Comment