Hi Mark,
Starting Friday my Insteon plug in stopped working. I started getting messages such as
"..Could not contact Interface on COM[]" and then "Interface_TrapError called from SendHex". Here is a log with the example:
Dec-10 7:05:18 PM Insteon Warning! Communications lost. Attempting to restart the port...
Dec-10 7:05:18 PM Insteon Interface_TrapError called from SendHex
Dec-10 7:05:18 PM Insteon The RF PLM has failed to transmit the last 10 commands.
Dec-10 7:04:31 PM Insteon The Insteon device at 1D.85.C7 did not respond. Please check to make sure the address is correct and that the device is powered-up. The device was not registered.
Dec-10 7:03:21 PM Device Control Device: Office Heater to On (100)
Dec-10 7:03:21 PM Event Event Trigger "Office Heater Office Heater Plug On"
Dec-10 7:03:21 PM Insteon Received Office Lights (23.B3.C0) Go ON
Dec-10 7:03:01 PM Insteon Interface successfully restarted.
Dec-10 7:03:01 PM Insteon RF PLM contacted on COM3 with an Insteon address of 41.05.23 and firmware version 9E
Dec-10 7:02:55 PM Insteon Attempting to restart the port and Interface...
Dec-10 7:02:55 PM Insteon ..Could not contact Interface on COM3
I tried a new PLM but no luck. I tried switching PLM cables, no luck. I tried switching Edgeport/1 devices with the working device that supports my alarm system but no luck. Also tried swapping port numbers. I even uploaded new Intel USB drivers onto my HS3 computer but no luck. The only thing that got me back up was to re-load the drivers for the Digi Edgeport/1 USB to Serial device that connects the computer to the PLM. I was about to declare victory but after an hour I started having the problem again.
Might you have any clue what it causing this? Or what I might be able to do to trouble shoot it? I'm using the 2413S and Edgeport/1, Windows 7, your latest Beta and HS3 Standard Edition 3.0.0.368 (Windows). It ran quite well for a long time. Something happened Friday that made this stop working, and it doesn't appear to be affecting other plug-ins, including ones that use the Edgeport/1.
Thanks
Jono
Starting Friday my Insteon plug in stopped working. I started getting messages such as
"..Could not contact Interface on COM[]" and then "Interface_TrapError called from SendHex". Here is a log with the example:
Dec-10 7:05:18 PM Insteon Warning! Communications lost. Attempting to restart the port...
Dec-10 7:05:18 PM Insteon Interface_TrapError called from SendHex
Dec-10 7:05:18 PM Insteon The RF PLM has failed to transmit the last 10 commands.
Dec-10 7:04:31 PM Insteon The Insteon device at 1D.85.C7 did not respond. Please check to make sure the address is correct and that the device is powered-up. The device was not registered.
Dec-10 7:03:21 PM Device Control Device: Office Heater to On (100)
Dec-10 7:03:21 PM Event Event Trigger "Office Heater Office Heater Plug On"
Dec-10 7:03:21 PM Insteon Received Office Lights (23.B3.C0) Go ON
Dec-10 7:03:01 PM Insteon Interface successfully restarted.
Dec-10 7:03:01 PM Insteon RF PLM contacted on COM3 with an Insteon address of 41.05.23 and firmware version 9E
Dec-10 7:02:55 PM Insteon Attempting to restart the port and Interface...
Dec-10 7:02:55 PM Insteon ..Could not contact Interface on COM3
I tried a new PLM but no luck. I tried switching PLM cables, no luck. I tried switching Edgeport/1 devices with the working device that supports my alarm system but no luck. Also tried swapping port numbers. I even uploaded new Intel USB drivers onto my HS3 computer but no luck. The only thing that got me back up was to re-load the drivers for the Digi Edgeport/1 USB to Serial device that connects the computer to the PLM. I was about to declare victory but after an hour I started having the problem again.
Might you have any clue what it causing this? Or what I might be able to do to trouble shoot it? I'm using the 2413S and Edgeport/1, Windows 7, your latest Beta and HS3 Standard Edition 3.0.0.368 (Windows). It ran quite well for a long time. Something happened Friday that made this stop working, and it doesn't appear to be affecting other plug-ins, including ones that use the Edgeport/1.
Thanks
Jono
Comment