Announcement

Collapse
No announcement yet.

Plugin Error

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

  • #16
    Mark,

    do you have a 2413S or 2413U? if you have a 2413S, are you using a 3rd party usb-serial adapter? have you tried different usb ports on your server?

    these errors used to be more common with older usb PLMs. electrical noise on the powerline could cause the plm to disconnect on the usb. unplugging the usb cable and reconnecting was the only solution. I wonder if you are still suffering from something like this. One solution is to put a usb hub between the pc and plm. you can search this forum for 'usb disconnect' to find other discussion.
    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


    • #17
      It's a 2413U, and unplugging and replugging doesn't help. Even a reboot the underlying server doesn't help. I'll try putting a hub in the middle -- that's a reasonable suggestion.

      I'm also trying to move HS3 to a new server (to an RPI model 4), but I'm running into licensing issues.

      Comment


      • #18
        After moving the 2413U to a new outlet AND isolating it from server with a USB 2.0 hub AND rebooting the server, there is no change in the situation.

        I did a factory reset of the PLM and started over again. After the reset, the plugin is able to contact the PLM without issue. I used the 'Update Interface Database' function on the plugin management page which said it was programming the links and updated as it processed about 200 links, then said reprogramming was successful. I restarted the plugin again -- and the problem immediately reappeared. This is the start-up log for the plugin after the reset/reprogram.

        Code:
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: Plugin: Insteon Instance:  starting...
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: Connecting to server at 127.0.0.1...
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: 10:42:12:8638:[Info]->Plugin Insteon has connected. IP:127.0.0.1:38306
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: Connected, waiting to be initialized...
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: 10:42:12:8716:[Starting Plug-In]->Initializing plugin Insteon ...
        Sep 28 10:42:12 elms-hs3-01 mono[1780]: 10:42:12:9862:[Insteon]->Insteon Support library (Insteon.dll) version: 1.0.7.11
        Sep 28 10:42:14 elms-hs3-01 mono[1780]: 10:42:14:8121:[Insteon]->Could not contact Interface on /dev/ttyUSB0
        Sep 28 10:42:14 elms-hs3-01 mono[1780]: 10:42:14:8339:[Starting Plug-In]->Plugin Insteon started successfully in 1962 milliseconds
        Sep 28 10:42:14 elms-hs3-01 mono[1780]: 10:42:14:9071:[Insteon]->Port_DataReceived Error: Specified port is not open.
        Sep 28 10:42:14 elms-hs3-01 mono[1780]: 10:42:14:9203:[Starting Plug-In]->Insteon loaded in 2205 milliseconds
        Sep 28 10:42:14 elms-hs3-01 mono[1780]: 10:42:14:9211:[Plug-In]->Finished initializing plug-in Insteon
        Sep 28 10:42:15 elms-hs3-01 mono[1780]: 10:42:15:0033:[Insteon]->Port_DataReceived Error: Specified port is not open.
        Sep 28 10:42:15 elms-hs3-01 mono[1780]: 10:42:15:1032:[Insteon]->Port_DataReceived Error: Specified port is not open.
        Sep 28 10:42:15 elms-hs3-01 mono[1780]: 10:42:15:2035:[Insteon]->Port_DataReceived Error: Specified port is not open.
        Sep 28 10:42:15 elms-hs3-01 mono[1780]: 10:42:15:3036:[Insteon]->Port_DataReceived Error: Specified port is not open.
        Sep 28 10:42:15 elms-hs3-01 mono[1780]: 10:42:15:4037:[Insteon]->Port_DataReceived Error: Specified port is not open.
        One other note, maybe relevant, maybe not: after replacing my previous PLM with this new one, ALL device control, whether direct or through events, started seriously lagging, requiring anywhere from 2-5 seconds to turn a device or group on/off. The system has never behaved like throughout the many years I've been running Insteon.


        Any additional suggestions?



        -M.

        Comment


        • #19
          have you noticed if the plm led is flashing a lot? this would indicate a lot of traffic/noise which may be the culprit.

          what about plugging in the plm to a different outlet on a different circuit using an extension cord?

          is there another usb port on the hs server you can try?
          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


          • #20
            I do not see any particular flashing on the PLM LED -- it's illuminated as a solid green. If it's supposed to be OFF most of the time -- well, then I've got a serious problem with traffic/noise. :-)

            I did, as part of this last set of changes, move it to a different AC circuit.

            Yes, I have moved it to a different USB port. My server, an i5-based Intel NUC, is running Ubuntu 16.04 with latest patches. It dynamically creates the USB device as I move between ports so the port name stays /dev/ttyUSB0 irrespective of the port it's plugged into.

            -M.

            Comment


            • #21
              The only recent changes to my setup was the addition of three 2992-222 range extenders to try to help with connectivity to some of the rooms that are pretty far away from the PLM. Those don't appear to need any setup. If the status lights on those are depicting traffic then I do see a pretty fair amount of traffic. Not crazy, but constant -- about what you'd see on a port status light on an Ethernet switch.

              I have, btw, tried unplugging all of the range extenders to see if they were actually contributing to the problem. Whether they are plugged in or not doesn't change the problem at all.

              -M.

              Comment


              • #22
                Can you try cutting other circuits and see if the problem goes away. I’m not sure a steady stream of flashing is normal. I think the flashing is Tx only . But I can’t find any doc to confirm that.
                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


                • #23
                  It will take quite a while to isolate a noisy dimmer or sensor, but I'll give that a try.

                  Meanwhile, there is something I'm not quite understanding in the log at plugin startup:

                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: Plugin: Insteon Instance: starting...
                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: Connecting to server at 127.0.0.1...
                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: 04:21:55:2986:[Info]->Plugin Insteon has connected. IP:127.0.0.1:44944
                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: Connected, waiting to be initialized...
                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: 04:21:55:4780:[Starting Plug-In]->Initializing plugin Insteon ...
                  Sep 28 16:21:55 elms-hs3-01 mono[1796]: 04:21:55:6008:[Insteon]->Insteon Support library (Insteon.dll) version: 1.0.7.11
                  Sep 28 16:21:59 elms-hs3-01 mono[1796]: 04:21:59:2237:[Insteon]->RF PLM contacted on /dev/ttyUSB0 with an Insteon address of 4C.16.F8 and firmware version 9E
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:2277:[Insteon]->Could not set the Interface configuration. Init failed.
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:2505:[Starting Plug-In]->Plugin Insteon started successfully in 4772 milliseconds
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:2735:[Starting Plug-In]->Insteon loaded in 5113 milliseconds
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:2738:[Plug-In]->Finished initializing plug-in Insteon
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:3198:[Insteon]->Port_DataReceived Error: Specified port is not open.
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:4188:[Insteon]->Port_DataReceived Error: Specified port is not open.
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:5190:[Insteon]->Port_DataReceived Error: Specified port is not open.
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:6192:[Insteon]->Port_DataReceived Error: Specified port is not open.
                  Sep 28 16:22:00 elms-hs3-01 mono[1796]: 04:22:00:7192:[Insteon]->Port_DataReceived Error: Specified port is not open.

                  Those last two lines in bold font suggest that in fact the port is opened and that an initial communication is happening with the PLM. What happens (in the code) just after that?

                  -M.

                  Comment


                  • #24
                    I've now moved my entire HS3 installation to new hardware, and then removed and reinstalled the Insteon plugin. I moved the PLM to a completely different part of the house. I still had the exact same problem on startup.

                    One thing of potential note, though, was that when I (finally!) enabled detailed logging for the plugin, I saw a continuous stream of these:

                    Code:
                    Sep 28 18:06:16 hs3-01 mono[805]: 06:06:16:4877:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:16 hs3-01 mono[805]: 06:06:16:8879:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:17 hs3-01 mono[805]: 06:06:17:3867:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 41 11 01 Debouncing repeat.
                    Sep 28 18:06:17 hs3-01 mono[805]: 06:06:17:4871:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4A 11 01 Debouncing repeat.
                    Sep 28 18:06:17 hs3-01 mono[805]: 06:06:17:8866:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4B 11 01 Debouncing repeat.
                    Sep 28 18:06:18 hs3-01 mono[805]: 06:06:18:2866:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:18 hs3-01 mono[805]: 06:06:18:7878:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 45 11 01 Debouncing repeat.
                    Sep 28 18:06:18 hs3-01 mono[805]: 06:06:18:9866:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4A 11 01 Debouncing repeat.
                    Sep 28 18:06:19 hs3-01 mono[805]: 06:06:19:2866:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:19 hs3-01 mono[805]: 06:06:19:6879:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:20 hs3-01 mono[805]: 06:06:20:1880:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4F 11 01 Debouncing repeat.
                    Sep 28 18:06:20 hs3-01 mono[805]: 06:06:20:5879:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 45 11 01 Debouncing repeat.
                    Sep 28 18:06:20 hs3-01 mono[805]: 06:06:20:7880:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 4A 11 01 Debouncing repeat.
                    Sep 28 18:06:21 hs3-01 mono[805]: 06:06:21:1881:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 41 11 01 Debouncing repeat.
                    Sep 28 18:06:21 hs3-01 mono[805]: 06:06:21:3869:[Insteon]->Received STX 0x50 (Raw Insteon Rec):1D 47 28 4C 15 C4 46 11 01 Debouncing repeat.
                    Because of my recent cleanup activities I recognized that address as a dimmer switch that I was having issues with -- it was connected to an event but not responding to the event firing. I pulled the tab on the dimmer to remove power...and everything suddenly started working again.

                    So, lesson-learned for me: turn detailed logging on sooner. Doing that earlier in my troubelshooting process would have saved me many, many hours.

                    UPDATE: I replaced the dimmer switch (I always keep a couple of spares on hand, given the relatively high failure rate of these critters) and now all is good.

                    -M

                    Comment


                    • #25
                      Well glad you figured it out.
                      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

                      Working...
                      X