Plugin Error

[MarkHargrove]

Yesterday my Insteon plugin stopped working and I'm struggling to figure out what's going on. I kind-of suspect my (relatively new) PLM has failed, but don't know for sure. The symptom is in the log file:

Sep 18 21:04:33 elms-hs3-01 mono[1775]: 09:04:33:9775:[Info]->Plugin Insteon has connected. IP:127.0.0.1:46752
Sep 18 21:04:33 elms-hs3-01 mono[1775]: Connected, waiting to be initialized...
Sep 18 21:04:34 elms-hs3-01 mono[1775]: 09:04:34:1361:[Starting Plug-In]->Initializing plugin Insteon ...
Sep 18 21:04:34 elms-hs3-01 mono[1775]: 09:04:34:2612:[Insteon]->Insteon Support library (Insteon.dll) version: 1.0.7.11
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:6829:[Insteon]->Could not contact Interface on /dev/ttyUSB0
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:7052:[Starting Plug-In]->Plugin Insteon started successfully in 5569 milliseconds
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:7541:[Starting Plug-In]->Insteon loaded in 5912 milliseconds
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:7547:[Plug-In]->Finished initializing plug-in Insteon
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:7816:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:8792:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 18 21:04:39 elms-hs3-01 mono[1775]: 09:04:39:9795:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 18 21:04:40 elms-hs3-01 mono[1775]: 09:04:40:0798:[Insteon]->Port_DataReceived Error: Specified port is not open.
...

This is running on an Ubuntu 16.04 server that is patched current. I'm on HS3 531. I've tried a bunch of usual-suspect types of things (rebooting the server, cycling power on the PLM, etc.), but nothing has improved the situation.

Any thoughts on what might be wrong or what else I might check?

-M.

[mnsandler]

Mark,
A couple of things to try

1. a different usb port, change thje port in plugin, and restart
2. manually factory reset the plm and restart the plugin. if it works, then reprogram the plm from the Config page

[Leeros]

Double-check that the Insteon Hub hasn’t simply been unplugged from power. Take a photo of the underside of your hub. Attach the photo along with proof of purchase to an email that includes your name and address and send to support.

[mnsandler]

Double-check that the Insteon Hub hasn’t simply been unplugged from power. Take a photo of the underside of your hub. Attach the photo along with proof of purchase to an email that includes your name and address and send to support.

the OP has a PLM not a Hub.

[MarkHargrove]

Factory reset/reprogram did the trick.

I switched to a PLM from a Hub to try to get more reliability (and in general, it has been more reliable), but this is kind of worrisome. The PLM has been in service less than six months. How regularly do folks see a PLM get corrupted and require a factory reset?

[mnsandler]

Everyone's mileage will vary. I had a user who would run the reset/reprogram every week (but he had a large installation; over 100 devices and his V1 plm database was almost full)

I have over 100 devices, and never need to reset/program my V2 PLM.

if you want, you can create an event to run the insteon action reset/reprogram on your schedule for maintenance purposes

[MarkHargrove]

I have roughly 70 devices in my home, and the dilemma for me is that a fair number of them (about a dozen) are non-wired (motion sensors, hidden door sensors, etc.) that require a physical trip to the device to reprogram them.

[mnsandler]

the reset and reprogram only touches the PLM database. it doesn't touch the devices themselves. you don't need to reprogram the devices.

[MarkHargrove]

Ah, I was confusing 'reset and program' with 'swap'.

[MarkHargrove]

After only about 24 hours the PLM starting exhibiting exactly the same symptoms as in my original post.

Is it normal for the PLM to get very hot? Not quite so hot that it's going to burn fingers or anything -- but pretty darned hot?

-M.

[MarkHargrove]

What is the cause of this type of error when swapping a new PLM in?

Sep 20 23:14:34 elms-hs3-01 mono[6675]: 11:14:34:9505:[Insteon]->Unknown protocol for device 33
Sep 20 23:14:34 elms-hs3-01 mono[6675]: 11:14:34:9561:[Insteon]->Failed to reprogram device Hall Cans (43.2E.79) Link# 1. Try again or you will need to manually reprogram this device.
Sep 20 23:14:36 elms-hs3-01 mono[6675]: 11:14:36:4522:[Insteon]->Unknown protocol for device 33
Sep 20 23:14:36 elms-hs3-01 mono[6675]: 11:14:36:4576:[Insteon]->Failed to reprogram device Hall Cans (43.2E.79) Link# 2. Try again or you will need to manually reprogram this device.
Sep 20 23:14:38 elms-hs3-01 mono[6675]: 11:14:38:3502:[Insteon]->Unknown protocol for device 33
Sep 20 23:14:38 elms-hs3-01 mono[6675]: 11:14:38:3513:[Insteon]->Failed to reprogram device Hall Cans (43.2E.79) Link# 3. Try again or you will need to manually reprogram this device.
Sep 20 23:14:39 elms-hs3-01 mono[6675]: 11:14:39:7536:[Insteon]->Unknown protocol for device 33
Sep 20 23:14:39 elms-hs3-01 mono[6675]: 11:14:39:7589:[Insteon]->Failed to reprogram device Hall Cans (43.2E.79) Link# 4. Try again or you will need to manually reprogram this device.

A about 10 of my Insteon devices (of several different flavors) give this error during a PLM swap.

[mnsandler]

hot to the touch seems excessive.

The device isn't returning a known value when the plugin asks the device which insteon protocol it supports. you can see the device protocols on the manage device page.

[JimSpy]

Oh, dear. I have something well over 100 physical devices (297 total), and my PLM is over 5 years old. I should maybe create this reset/reprogram event myself. Yes. Yes, I should do that. Very well then....um...."Reset and Reprogram Interface"? That's all? No parameters? Don't need to disable first? I should do this maybe once a week? I should have the event back up the insteon.ini? There is maybe a script or scripting command for this?

[mnsandler]

Oh, dear. I have something well over 100 physical devices (297 total), and my PLM is over 5 years old. I should maybe create this reset/reprogram event myself. Yes. Yes, I should do that. Very well then....um...."Reset and Reprogram Interface"? That's all? No parameters? Don't need to disable first? I should do this maybe once a week? I should have the event back up the insteon.ini? There is maybe a script or scripting command for this?

Jim
"if it ain't broke, don't fix it." I only recommend scheduling this action if your plm has periodic issues. there are also triggers and actions to backup the insteon.ini. please so this.

[MarkHargrove]

My original problem is back. On a restart of the plugin, the initial startup log messages look normal, then a non-ending stream of these messages appears int he log:

Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:3909:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:4911:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:5913:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:6914:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:7914:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:8913:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:02 elms-hs3-01 mono[1780]: 07:44:02:9913:[Insteon]->Port_DataReceived Error: Specified port is not open.
Sep 27 07:44:03 elms-hs3-01 mono[1780]: 07:44:03:0916:[Insteon]->Port_DataReceived Error: Specified port is not open.
...

This is exactly the issue that led me originally to do 'reset/reprogram' and then later buy a new PLM to replace my previous one. These messages are coming from a brand-new PLM that is less than a week old.

I'm pretty baffled about what my next step might be.

-M.