HS2 Insteon Plug-In Version 2.0.0.4 Release

[mnsandler]

See the following thread for all the changes and enhancements
http://forums.homeseer.com/showthread.php?t=158453

Fixes:
- Ramp rate and on level Settings for device type 0120 (2.0.0.2)
- bug fixes (foreign country dates in insteon.ini)

To Install:

The plugin is now in three pieces, you must install all three pieces otherwise you will get an error when you start homeseer.

1. Backup your current hs database and insteon.ini
2. Shutdown HS
3. Copy all the DLLs to the homeseer folder, start HS

For new users only:
4. copy the insteon.lf to the homeseer\config (this will provide a 30-day trial license)
5. Enable the plugin on the hs setup/interface page
6. Visit the plugin config page, and enter the necessary Port information (either COMx, or Hub IP info)
7. Restart HS

[kuntakintay]

Is this for HS2 or HS3?

[mnsandler]

Is this for HS2 or HS3?

HS2. I updated the title. thanks

PS. From here on out... v2.x will always be for HS2, and v3.x will always be for HS3.

[scotthpdx]

Help Please with installation and migration from 1.0

Hey ya'll

I am moving from the free version 1.0 to the 2.0 version. I had to purchase the newer USB interface, installed the drivers for it and I think it is on COM10.

I had trouble getting the Insteon to come up with Interface OK in the Interfaces screen, but rebooted and messed around. Now I have the Insteon HSPI_INSTEON.dll 2.0.0.0 in there. I am on a 3 day trial. I think that the clock started when I started the upgrade a month ago. So I guess I have 3 days to try to get this working....

I click on the Yellow Config and I see Calling ConfigIO for Insteon and nothing... There is noting in the pink area on the screen like the old interface had where I could change the Insteon stuff, or add devices. I assume that will be in the Config area that I cannot get to come up.

Anyway... SYSTEM DOWN.... Help....

Scott

Log File when booting...

11/12/2013 6:56:32 PM - Info - HomeSeer version is: 2.1.104.0
11/12/2013 6:56:32 PM - Startup - Checking for available plug-ins
11/12/2013 6:56:32 PM - Info - Found plug-in: X10 CM11A/CM12U, version: 1.0.2.0
11/12/2013 6:56:32 PM - Info - Found plug-in: DSC PANEL, version: 1.0.0.20
11/12/2013 6:56:32 PM - Info - Found plug-in: Insteon, version: 2.0.0.0
11/12/2013 6:56:32 PM - Info - Found plug-in: MLHSPlugin, version: 2.0.0.40
11/12/2013 6:56:32 PM - Info - Found plug-in: Touchpad, version: 2.0.0.21
11/12/2013 6:56:32 PM - Startup - Restoring device status
11/12/2013 6:56:32 PM - Startup - Initializing Plug-Ins
11/12/2013 6:56:32 PM - Info - Finished initializing X10 interface
11/12/2013 6:56:32 PM - Info - Finished initializing infrared interface
11/12/2013 6:56:32 PM - Warning - Interface Insteon is running as a trial, 3 days remaining.
11/12/2013 6:56:32 PM - Info - Initializing Plug-in: Insteon
11/12/2013 6:56:32 PM - Error - Initializing interface: Insteon->Object reference not set to an instance of an object.
11/12/2013 6:56:32 PM - Info - Finished initializing plug-in Insteon
11/12/2013 6:56:32 PM - Info - Initializing Plug-in: Touchpad
11/12/2013 6:56:32 PM - COM Plugin - Calling InitIO
11/12/2013 6:56:32 PM - COM Plugin Info - Touchpad Initializing...
11/12/2013 6:56:32 PM - Touchpad - Touchpad 2.0.21 starting.
11/12/2013 6:56:32 PM - Startup - Touchpad is configured for HomeSeer 2.0
11/12/2013 6:56:32 PM - Touchpad - Touchpad Configuration completed.

OK, Messing around some more and now I am worse off.. I did find a post that said to add in a line that says Error - Initializing interface: Insteon->Object reference not set to an instance of an object.

See below...

Now when I start HS I get a red line

11/12/2013 7:26:44 PM - Info - Found plug-in: X10 CM11A/CM12U, version: 1.0.2.0
11/12/2013 7:26:44 PM - Info - Found plug-in: DSC PANEL, version: 1.0.0.20
11/12/2013 7:26:44 PM - Info - Found plug-in: Insteon, version: 2.0.0.0
11/12/2013 7:26:44 PM - Info - Found plug-in: MLHSPlugin, version: 2.0.0.40
11/12/2013 7:26:44 PM - Info - Found plug-in: Touchpad, version: 2.0.0.21
11/12/2013 7:26:45 PM - Startup - Restoring device status
11/12/2013 7:26:45 PM - Startup - Initializing Plug-Ins
11/12/2013 7:26:45 PM - Info - Finished initializing X10 interface
11/12/2013 7:26:45 PM - Info - Finished initializing infrared interface
11/12/2013 7:26:45 PM - Warning - Interface Insteon is running as a trial, 3 days remaining.
11/12/2013 7:26:45 PM - Info - Initializing Plug-in: Insteon
11/12/2013 7:26:45 PM - Error - Initializing interface: Insteon->Object reference not set to an instance of an object.
11/12/2013 7:26:45 PM - Info - Finished initializing plug-in Insteon

[mnsandler]

Scott,
Sorry for the troubles, I tried to make this error proof but sometimes HS doesn't want to cooperate. so try the following

add the following line to the [config] section of the insteon.ini and restart HS
InterfacePort=COM10

Another idea is to add InterfaceType=USB to the [config] section and restart. this will use the FTDI DLL driver instead of the microsoft Serial port driver.

Also, I've seen other users have problems with COM10. you might delete some of the unused COM ports from the registry so you can get the port number below 10. I think FTDI has a utility for doing this.

please report back

[scotthpdx]

[mnsandler]

Scott
We can fix this today. I can't extend the trial that's a hst issue.

The config page is where the com port is defined. I no longer use the hs setup page for this. N/A is ok but the plugin io must be enabled.

Did you update the insteon.dll during the upgrade? What is the version of this file?

Put in [config]
interfaceport=COM2

And restart

We might be able to do a remote session this evening

[mnsandler]

try the following link if the config btn isn't working. this will take you to the plugin config page.

/insteon_config

[JHughes]

Thank You

Updated to the new version using the updater. Went very smoothly.
Thank you for your continued work on this.

[mnsandler]

Updated to the new version using the updater. Went very smoothly.
Thank you for your continued work on this.

Thanks for the feedback. I was worried that there was a problem with the package I posted...guess its working.

[scotthpdx]

insteon_config

try the following link if the config btn isn't working. this will take you to the plugin config page.

/insteon_config

I tried that in the immediate windows and I got an error. It said:

11/14/2013 11:19:48 AM Info Control Panel Immediate Script: &/insteon_config
11/14/2013 11:19:48 AM Error Running script, init error: Expected statement

[scotthpdx]

Scott
We can fix this today. I can't extend the trial that's a hst issue.

The config page is where the com port is defined. I no longer use the hs setup page for this. N/A is ok but the plugin io must be enabled.

Did you update the insteon.dll during the upgrade? What is the version of this file?

Put in [config]
interfaceport=COM2

And restart

We might be able to do a remote session this evening

My version is 2.0.0.0

[mnsandler]

I tried that in the immediate windows and I got an error. It said:

11/14/2013 11:19:48 AM Info Control Panel Immediate Script: &/insteon_config
11/14/2013 11:19:48 AM Error Running script, init error: Expected statement

/insteon_config is the plugin webpage so it needs to go in the browser address; its not a command to run

something like

http://192.168.1.10:81/insteon_config

replace the id address and port number with your setup

[IanIreland]

Following on from 1.9 :-)

In the previous thread I was having problems with the plugin stopping responding.
I may (fingers crossed) have found the problem.
I noticed one of my INSTEON units failing to respond. In the log this preceded the plugin failing to respond, not always immediately!
The INSTEON unit is a DIN rail switch. In the same cabinet was an X10 booster I had installed when having some X10 problems. I have resolved the X10 problems but had not removed the booster.
I took this out, the INSTEON now responds every time and the plugin hasn't failed since!
Let's see how long I go.....

[mnsandler]

In the previous thread I was having problems with the plugin stopping responding.
I may (fingers crossed) have found the problem.
I noticed one of my INSTEON units failing to respond. In the log this preceded the plugin failing to respond, not always immediately!
The INSTEON unit is a DIN rail switch. In the same cabinet was an X10 booster I had installed when having some X10 problems. I have resolved the X10 problems but had not removed the booster.
I took this out, the INSTEON now responds every time and the plugin hasn't failed since!
Let's see how long I go.....

Glad you found the issue, but a non-responsive device shouldn't hang the plugin as long as the plm is responding to the plugin requests.

that said a non-responsive device will slow things down depending on your retry count and timeout settings on the config page.

thanks for reporting back.