Announcement

Collapse
No announcement yet.

Failure replacing PMU

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Failure replacing PMU

    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?

    #2
    you need to run the "replace/swap interface" (on the config page) routine with the new PLM installed. you will enter the OLD PLM insteon id when prompted.

    this will update all the device links with the new PLM insteon id
    Mark

    HS3 Pro 3.0.0.534
    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

    Comment


      #3
      That’s exactly what I did, three times, in all three cases it went through the routine (even having me put the non-PLC devices in linking mode) but when it finished it said it couldn’t communicate to any of them. When I went to check the status of the plug-in, it had lost communications with the PLM, likely during the reprogramming of the links. I was looking for an option to do it in steps (reprogram the PLM first to ensure that works, then reprogram all of the other devices to communicate to it), but there doesn’t appear to be an option to do that. It was only after I was unable to get the new PLM to work that I swapped back to the old one, hoping I could at least get the system to work temporarily while I figured out why the new one wouldn’t set up properly.

      Comment


        #4
        if the plugin can find the plm when it starts, but is having troubles sending and receiving command, then it sounds like there is something (a device) on the insteon network causing a communication problem.

        one way to test this is run the 'program device for homeseer' on one device (a switchlinc). if this is successful, you should be able to control that device form the hs ui and get status back if the device is controlled physically.

        Mark

        HS3 Pro 3.0.0.534
        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
        Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

        Comment


          #5
          I tried that as well. I was able to program 3 or so devices that way, and I got them to program successfully. It didn’t clear out the old programming, though, or at least it didn’t reprogram any of the groups it belonged to. Looking at the device list showed a bunch of “unregistered groups”. When I swapped back to the old PMU the groups were still properly registered to that (old) PMU.

          Comment


            #6
            the routine will delete links; it just creates what it needs. you can delete the old ones.

            as for the groups you can reprogram them from the Groups page.
            Mark

            HS3 Pro 3.0.0.534
            Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
            Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
            Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

            Comment


              #7
              Okay, I just swapped out the interface to the new one again. HomeSeer connected to it and gave me the message that it was a different interface than the system had configured before, so I ran the replace/swap interface routine. The same thing happened as last time; it appears to reprogram the device and then tries to reconnect all the devices, but it fails to connect to any of them, and then when the routine finishes HomeSeer can no longer connect to the PLM. It took about five attempts to stop and restart the plugin for it to reconnect.

              I then attempted to "Program Device for Homeseer". It said it was successful, but I wasn't able to control it through the HomeSeer interface, and again it appears that HomeSeer has lost connection to the PLM. I just waited a minute or two, and I got the "OK" on the interface list again. Sending a second command appeared to work, but then it lost communications again and I got an unknown state on the device.

              Comment


                #8
                Looking at the log I am getting a lot of "Warning! Communications lost. Attempting to restart the port...Attempting to restart the port and Interface... " messages. Sometimes it reconnects, sometimes it doesn't. What's happening now is that I'm trying to reprogram a device close by so I can see it work, but I'm losing connection to the PLM before it can even finish programming.

                Comment


                  #9
                  In trying to reprogram one particular switch, I hear the interface chirp once, but the response chirp generally takes somewhere between 5 and 10 seconds to come back (if it does at all, which seems to be about 80% of the time). However, the "Program Device for Homeseer" times out before this happens, so it doesn't try to finish programming the links, and about 30% of the time the link dies and HomeSeer has to restart it.

                  Comment


                    #10
                    none of this is going to work until you resolve the comm issue. something is interfering with normal operation

                    Mark

                    HS3 Pro 3.0.0.534
                    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                    Comment


                      #11
                      Is there something in one of the logs that might help diagnose where the problem might be?

                      Comment


                        #12
                        enable detailed logging within the plugin, and see if there are messages from devices you don't recognize.

                        there are several threads in the forum about hunting down noisy devices.
                        Mark

                        HS3 Pro 3.0.0.534
                        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                        Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                        Comment


                          #13
                          Here are three attempts to access the dining room light. The first attempt to turn it on eventually worked, but still set the device to an unknown state within HomeSeer. The second try, which attempted to turn the light off, successfully turned off the light and set the appropriate status. The third attempt, to turn it back on, never worked at all.

                          Dec-28 3:45:47 PM Insteon Setting value for device 24.A5.AF:1. Old Value:0, New Value: -1
                          Dec-28 3:45:47 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:45:47 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:47 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:45:47 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:47 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:45:47 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:46 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:46 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:45:46 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:46 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:45:46 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:46 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:45:46 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:46 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:46 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:45:46 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:45 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:45:45 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:45 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:45:45 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:45 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:45 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:45:45 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:45 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:45:45 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:44 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:45:44 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:45:44 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:44 PM Insteon Did not receive a response from Dining room Dining room light (24.A5.AF). Try #1 failed.
                          Dec-28 3:45:41 PM Insteon ..Got RF PLM Response 02 62 24 A5 AF 0A 11 80 06
                          Dec-28 3:45:41 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:41 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
                          Dec-28 3:45:41 PM Device Control Device: Main Dining room Dining room light to On (100) by/from: CAPI Control Handler


                          Dec-28 3:45:05 PM Insteon Setting status and value for device 24.A5.AF:1. Old status:-1 Old Value:-1, New Status:3 New Value:0
                          Dec-28 3:45:05 PM Insteon Received a Direct ACK from Dining room Dining room light (24.A5.AF): 24 A5 AF 53 BF DA 2A 13 00
                          Dec-28 3:45:05 PM Insteon Received STX 0x50 (Raw Insteon Rec):24 A5 AF 53 BF DA 2A 13 00
                          Dec-28 3:45:02 PM Insteon ..Got RF PLM Response 02 62 24 A5 AF 0A 13 00 06
                          Dec-28 3:45:02 PM Insteon Sending command 02 62 24 A5 AF 0A 13 00 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:45:02 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
                          Dec-28 3:45:02 PM Device Control Device: Main Dining room Dining room light to Off (0) by/from: CAPI Control Handler


                          Dec-28 3:44:10 PM Insteon Received a Direct ACK from Dining room Dining room light (24.A5.AF): 24 A5 AF 53 BF DA 2A 11 80
                          Dec-28 3:44:10 PM Insteon Received STX 0x50 (Raw Insteon Rec):24 A5 AF 53 BF DA 2A 11 80
                          Dec-28 3:43:44 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:43:44 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:44 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:43:44 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:43 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:43:43 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:43 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:43:43 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:43:43 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:43 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:43:43 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:43 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:43:43 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:42 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:43:42 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:43:42 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:42 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:43:42 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:42 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:43:42 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:42 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:43:42 PM Insteon **Internal transmit attempt failed for CMD: 00 00 00 24 A5 AF 0A 11 80
                          Dec-28 3:43:42 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:41 PM Insteon ..Retry #2 required. Pausing 300ms for RF PLM to clear...
                          Dec-28 3:43:41 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:41 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
                          Dec-28 3:43:41 PM Insteon ..Got NAK from the RF PLM for command
                          Dec-28 3:43:41 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:43:41 PM Insteon Did not receive a response from Dining room Dining room light (24.A5.AF). Try #1 failed.
                          Dec-28 3:43:38 PM Insteon ..Got RF PLM Response 02 62 24 A5 AF 0A 11 80 06
                          Dec-28 3:43:38 PM Insteon Sending command 02 62 24 A5 AF 0A 11 80 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          Dec-28 3:43:38 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
                          Dec-28 3:43:38 PM Device Control Device: Main Dining room Dining room light to On (100) by/from: CAPI Control Handler

                          Comment


                            #14
                            I spoke slightly too soon: at 3:48:00, the light finally went on.

                            Comment


                              #15
                              So far I'm not seeing any Insteon activity that I don't initiate, except my 2844-222 motion sensors (which are on USB power) sending periodic updates, such as:
                              Dec-28 3:58:51 PM Insteon Received STX 0x50 (Raw Insteon Rec):4A 63 26 CC 77 0B CF 0C 80 Debouncing repeat.
                              Dec-28 3:58:51 PM Insteon Setting value for device 4A.63.26:21. Old Value:176, New Value: 119
                              Dec-28 3:58:51 PM Insteon Setting value for device 4A.63.26:4. Old Value:100, New Value: 0
                              Dec-28 3:58:51 PM Insteon Setting value for device 4A.63.26:4. Old Value:0, New Value: 100
                              Dec-28 3:58:51 PM Insteon ProcessInsteonTrigger Parameters: DeviceID=4A.63.26, Command=0C, Command2=80, Group=11
                              Dec-28 3:58:51 PM Insteon Device Stairs Top motion sensor (4A.63.26) sent a heartbeat: Battery=Good, Temp=67.6, Light=119
                              Dec-28 3:58:51 PM Insteon Received STX 0x50 (Raw Insteon Rec):4A 63 26 CC 77 0B CF 0C 80

                              Comment

                              Working...
                              X