Hi, I'm a new user and am confused

[Pandora]

Hi,
I'm a new HomeSeer user and am confused. I purchased HomeSeer 3 Pro, and then purchased the Insteon PLM Plug in by Mark Sandler.

I read to install drivers for my PowerLinc 2413U modem and did. The com port for the device is COM4 from device manager. When I enter this device port into the configuration and save, restarting HS3 or rebooting everything doesn't help.

My HomeSeer add on can't seem to communicate with my 2413U. Is this device supported? Did I miss something obvious?


The log sort of follows -

Nov-24 3:09:38 PM Plug-In Finished initializing plug-in Insteon
Nov-24 3:09:38 PM Insteon Could not contact Interface on COM4
Nov-24 3:09:38 PM Insteon Could not contact Interface on COM4
Nov-24 3:09:34 PM Insteon Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
Nov-24 3:09:30 PM Insteon Insteon Support library (Insteon.dll) version: 1.0.5.20
Nov-24 3:09:30 PM Info Plugin Insteon has connected. IP:127.0.0.1:49777
Nov-24 3:09:19 PM Info Plugin Insteon with instance: has disconnected
Nov-24 3:09:19 PM Plug-In Shutting down Plug-In: Insteon

[joegr]

That's the correct PLM. Are you typing it in as "COM4" (uppercase)? I'm still on HS2, but I think HS3 for Windows requires it to be in capitals. Which OS are you using? Are you very certain that it really is COM4? I think that with Windows 8/10, that UAC sometimes causes problems.

[jbbtex]

Do you have any other software running that communicates with the PLM?

[mnsandler]

Hi,
I'm a new HomeSeer user and am confused. I purchased HomeSeer 3 Pro, and then purchased the Insteon PLM Plug in by Mark Sandler.

I read to install drivers for my PowerLinc 2413U modem and did. The com port for the device is COM4 from device manager. When I enter this device port into the configuration and save, restarting HS3 or rebooting everything doesn't help.

My HomeSeer add on can't seem to communicate with my 2413U. Is this device supported? Did I miss something obvious?


The log sort of follows -

Nov-24 3:09:38 PM Plug-In Finished initializing plug-in Insteon
Nov-24 3:09:38 PM Insteon Could not contact Interface on COM4
Nov-24 3:09:38 PM Insteon Could not contact Interface on COM4
Nov-24 3:09:34 PM Insteon Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
Nov-24 3:09:30 PM Insteon Insteon Support library (Insteon.dll) version: 1.0.5.20
Nov-24 3:09:30 PM Info Plugin Insteon has connected. IP:127.0.0.1:49777
Nov-24 3:09:19 PM Info Plugin Insteon with instance: has disconnected
Nov-24 3:09:19 PM Plug-In Shutting down Plug-In: Insteon

are you sure COM4 is correct? with the windows device manager openned to Ports, connect and disconnect the usb cable to the 2413U to see which ports appears/disappears.

[Pandora]

Sorry I was away over the holiday weekend

Hi,
Sorry I was away over the holiday weekend (Thanksgiving). I'm still having issues. COM4 seems to be the correct device.

The serial / USB port from the device manager looks like this (from Windows 10 Home 32 bit) -

[ [ Name] Microsoft-Windows-UserPnp
[ Guid] {96F4A050-7E31-453C-88BE-9634F4E02139}

EventID 20001

Version 0

Level 4

Task 7005

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2015-11-24T20:05:17.594935600Z

EventRecordID 1086

Correlation

- Execution

[ ProcessID] 5368
[ ThreadID] 308

Channel System

Computer Homeseer

- Security

[ UserID] S-1-5-18


- UserData

- InstallDeviceID

DriverName ftdiport.inf_x86_4fc14c634455792e\ftdiport.inf

DriverVersion 2.12.10.0

DriverProvider FTDI

DeviceInstanceID FTDIBUS\VID_0403+PID_6001+A704EP0GA\0000

SetupClass {4D36E978-E325-11CE-BFC1-08002BE10318}

RebootOption false

UpgradeDevice false

IsDriverOEM true

InstallStatus 0x0

DriverDescription USB Serial Port

The Error log from the Insteon plug in looks like this

Insteon Plug-in Error Log Generated 11/30/2015 9:48:31 AM
-----------*Error Message*----------------
Error: Forced error / log generation -- 11/30/2015 9:48:31 AM
--------*Initialization Log*--------------
11/30/2015 9:47:27 AM - Host System: () 3.0.0.208
11/30/2015 9:47:27 AM - Plugin: HSPI_Insteon.DLL - v3.0.5.20
11/30/2015 9:47:27 AM - Insteon Support library (Insteon.dll) version: 1.0.5.20
11/30/2015 9:47:27 AM - RegisterCallback Completed
11/30/2015 9:47:27 AM - Enter InitIO
11/30/2015 9:47:27 AM - Enter InitPlugin
11/30/2015 9:47:27 AM - Global initialization of plug-in required, starting up.
11/30/2015 9:47:27 AM - Initializing Insteon hardware interface...
11/30/2015 9:47:27 AM - In ProcessRawReceiveThread
11/30/2015 9:47:27 AM - Initializing Interface...
11/30/2015 9:47:27 AM - In PLMBuffer_ProcessBufferThread
11/30/2015 9:47:28 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
11/30/2015 9:47:29 AM - ..did not receive a response from the Interface
11/30/2015 9:47:29 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
11/30/2015 9:47:30 AM - ..did not receive a response from the Interface
11/30/2015 9:47:30 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
11/30/2015 9:47:31 AM - ..did not receive a response from the Interface
11/30/2015 9:47:31 AM - Insteon hardware interface initialization failed.
11/30/2015 9:47:31 AM - Enter InitX10
11/30/2015 9:47:31 AM - Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
11/30/2015 9:47:31 AM - Enter InitPlugin
11/30/2015 9:47:31 AM - Global initialization of plug-in required, starting up.
11/30/2015 9:47:31 AM - Initializing Insteon hardware interface...
11/30/2015 9:47:31 AM - Initializing Interface...
11/30/2015 9:47:31 AM - In ProcessRawReceiveThread
11/30/2015 9:47:31 AM - In PLMBuffer_ProcessBufferThread
11/30/2015 9:47:32 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
11/30/2015 9:47:33 AM - ..did not receive a response from the Interface
11/30/2015 9:47:33 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
11/30/2015 9:47:34 AM - ..did not receive a response from the Interface
11/30/2015 9:47:34 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
11/30/2015 9:47:35 AM - ..did not receive a response from the Interface
11/30/2015 9:47:36 AM - Insteon hardware interface initialization failed.
11/30/2015 9:47:36 AM - Exit InitX10
11/30/2015 9:47:36 AM - Could not contact Interface on COM4
11/30/2015 9:47:36 AM - Exit InitIO
11/30/2015 9:48:27 AM - Global initialization of plug-in required, starting up.
11/30/2015 9:48:27 AM - Initializing Insteon hardware interface...
11/30/2015 9:48:27 AM - Initializing Interface...
11/30/2015 9:48:27 AM - In ProcessRawReceiveThread
11/30/2015 9:48:27 AM - In PLMBuffer_ProcessBufferThread
11/30/2015 9:48:28 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
11/30/2015 9:48:29 AM - ..did not receive a response from the Interface
11/30/2015 9:48:29 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
11/30/2015 9:48:30 AM - ..did not receive a response from the Interface
11/30/2015 9:48:30 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
11/30/2015 9:48:31 AM - ..did not receive a response from the Interface
11/30/2015 9:48:31 AM - Insteon hardware interface initialization failed.
11/30/2015 9:48:31 AM - Exit InitX10
11/30/2015 9:48:31 AM - Could not contact Interface on COM4
11/30/2015 9:48:31 AM - Scheduled polling enabled.
11/30/2015 9:48:31 AM - ***:Forced error / log generation

-----------*Pre-Error Log*----------------
11/30/2015 9:47:36 AM - Could not contact Interface on COM4
11/30/2015 9:48:27 AM - Submit Changes Selected
11/30/2015 9:48:27 AM - Enter InitX10
11/30/2015 9:48:27 AM - Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
11/30/2015 9:48:27 AM - Enter InitPlugin
--------*End Pre-Error Log*--------------
--------*Start C:\Program Files\HomeSeer HS3\Config\Insteon.ini*--------------
[Config]
MaxHops=2
NumRetries=5
WaitTimeout=3
DetailedLog=1
UseLocation2=0
DoCleanups=1
DisablePolling=0
SortDeviceLinks=0
PortType=USB
DisableRestart=True
InterfacePort=COM4
X10Enabled=1

--------*End C:\Program Files\HomeSeer HS3\Config\Insteon.ini*--------------

I am unable to talk to my device and am uncertain what to do. Any help is greatly appreciated.

[mnsandler]

please do a factory reset on the plm. see the plm manual for instructions

[Pandora]

Thank you Mark, it now works

Mark,
Thank you very much. My device now works.

If you don't mind another question ...

I'm migrating from X10 to Insteon. I have several older X10 controllers installed in ceiling fans, but forgot their X10 codes. Is there a way to search for devices? I had an older X10 controller which was connected to a PC but ran when the PC was off, from Smarthome. I has a configuration file, but I can't find a way to read it. My device codes are in that file and I misplaced the installation CD.

[mnsandler]

Mark,
Thank you very much. My device now works.

If you don't mind another question ...

I'm migrating from X10 to Insteon. I have several older X10 controllers installed in ceiling fans, but forgot their X10 codes. Is there a way to search for devices? I had an older X10 controller which was connected to a PC but ran when the PC was off, from Smarthome. I has a configuration file, but I can't find a way to read it. My device codes are in that file and I misplaced the installation CD.

glad you got the plm working.

the plugin will not scan for x10 addresses. if you remember the house code, finding the unit code shouldn't be too much trouble. Create an insteon x10 device from the hs3 add dev page, use the Insteon tab to 'Save as Insteon X10'. then just sequence through the unit codes and try and control the remote device.

[Pandora]

Thank you so very much

Thank you very much. You have provided wonderful support. Will your plug in work with a Raspberry Pi 2 and HS3 for the Raspberry Pi 2? If so, you may have yet another sale.

[mnsandler]

I don't have any experience with the Pi 2.

if it runs a typically hspi_xxx.exe plugin file, then there should be no problems

if it requires an hspi_xxx.dll then it won't work