Last Beta Call - Let's get a release out

[Oman]

Last Update 2/3/2007

There was a Keypadlinc button control problem reported that has been fixed. It is possible that this same bug was causing some remote link tables to be corrupted in Keypadlincs causing erratic behavior after some time in the keypads. This build resolves the issue. This build will also check for the presence of the remote device support script before requesting that HomeSeer try to run it; avoiding a warning message at startup. In-linelinc relay support has also been fixed. I'm releasing this build to the updater immediately although sometimes it takes a while to get posted).

Jon


It's been a while, and there have been fewer and fewer bug reports coming in... especially now that the SDM seems to have stabilized. I'm posting version 0.0.4.1 which I hope will be the final beta (I've said that before but things keep cropping up). This version does have a fairly major change incorporated that needs to be mentioned. The group devices are now status/value pair devices rather than lighting devices. This means that groups can now support a bit more functionality. Insteon didn't give us group dimming to a preset level but they did give us ramp start/stop and dim up/down by one step. These have now been implemeneted in the group devices. Your group device addresses won't change *but the device types will*. This means you will need to visit any events that use or set groups and edit them to use the proper group commands or triggers.

The other change is that there is now an API for basic support of non lighting Insteon devices. Scripts can be written that can control and interact with Insteon devices with support from the Insteon plug-in. Of course you can still talk directly to the SDM and go around the Insteon plug-in but the API eliminates some of the frustrating details of getting reliable Insteon communications working. Using the API makes the plug-in aware of the additional traffic and avoids what otherwise ends up as collisions when two applications use the SDM to talk to the PLC.

I have included a very rough script for supporting the SimpleHomeNet irrigation controller and IO controller (EZRain and EZIO). It only controls the EZIO outputs at this time but input support is a few lines of code away. I have not been able to get one to test with yet. The script file is in the ZIP file and should be placed in the HomeSeer scripts directory if you have one of these devices. For those of you familiar with .NET scripting I think you will find the add-on scripts pretty easy to understand.

I'm putting the update ZIP file here first, and if there are no major issues it will go to the updater Monday. Please post any issues here.


Jon




Version 0.0.2.16 is now available. Has fixes for some custom keypadlinc button name issues and support for VALUE_SET translation (Maestro uses VALUE_SET to control lights). Also added a warning if an older version of the SDM is being used. SDM 122.278 or newer is required.

Version 0.0.2.15 (Release Candidate 2) is now available here, and I have sent it out to be included in the updater.

This version has several bug fixes, mainly dealing with large databases. The plug-in will support up to 256 devices and 253 groups (the number of groups available decreases by at least 6 with each KeypadLinc in the system). Each device can have a maximum of 255 links supported, but most devices will only hold a much smaller number based on the available memory within a the device.

A problem where manually entered or edited device Insteon addresses could cause the plug-in to fail to recognize valid device assoications has also been fixed.

No changes to the database (INI) file or to the user interface have been made since version 0.0.2.13.

This version is a release candidate. Please report any problems as soon as possible (with a log of course). I plan on officially releasing this plug-in next week barring any significant issues coming up that can't be resolved by then.

To update (from at least the last version in the updater): Just shut-down HomeSeer and unzip the files into your HomeSeer 2 directory, then re-start HomeSeer.

Thanks
Jon

[chamoun]

A couple of issues:

1. Mannually adding a new Keypad generated the "Record #9 is past the high water mark error". The log is attached at the end of this message. Communication reliability is 100% and the device programmed fine.

2. I changed the names for all the buttons on my Keypads to (On,A,B,C,D,Off) from (On/Load, Button A, Button B, Button C, Button D, Load/Off). After Doing so the plugin stopped displaying the Device names next to the button name in status, events etc. Therefore for a particular location it was impossible to tell the Keypads apart. I deleted all the Keypads and started over and now the default button names for any newly added Keypad is (On, A, B, C, D, Off) and the device name is still ommitted from status, events etc. The only way around this issue is to type in manually the device name and button name for each button on a Keypad. Please advise.

Thanks.


11/7/2006 5:27:47 AM - Startup -
11/7/2006 5:27:47 AM - Startup - ************************************************************ ********************
11/7/2006 5:27:47 AM - Startup - HomeSeer version 2.1.104.0 Starting Now (Release Build)
11/7/2006 5:27:47 AM - Startup - ************************************************************ ********************
11/7/2006 5:27:47 AM - Startup -
11/7/2006 5:27:48 AM - Startup - Loading Settings
11/7/2006 5:27:48 AM - Startup - Settings Loaded.
11/7/2006 5:27:48 AM - Startup - Loading configuration file ...
11/7/2006 5:27:48 AM - Info - Loading device types file...
11/7/2006 5:27:48 AM - Database - Opening up HomeSeer database C:\Program Files\HomeSeer 2\config\sample.mdb
11/7/2006 5:27:49 AM - Info - Loading Devices...
11/7/2006 5:27:49 AM - Load Config - 20 total devices loaded.
11/7/2006 5:27:49 AM - Load Config - Checking device type settings for all devices...
11/7/2006 5:27:49 AM - Load Config - Finished checking device type settings.
11/7/2006 5:27:49 AM - Load Config - Loading Events...
11/7/2006 5:27:49 AM - Load Config - 5 total events loaded.
11/7/2006 5:27:49 AM - Info - Loading TV Timers...
11/7/2006 5:27:49 AM - Database - HomeSeer configuration database C:\Program Files\HomeSeer 2\config\sample.mdb has been closed.
11/7/2006 5:27:49 AM - Info - HomeSeer version is: 2.1.104.0
11/7/2006 5:27:50 AM - Startup - Checking for available plug-ins
11/7/2006 5:27:50 AM - Info - Found plug-in: Insteon, version: 0.0.2.15
11/7/2006 5:27:50 AM - Startup - Restoring device status
11/7/2006 5:27:50 AM - Startup - Initializing Plug-Ins
11/7/2006 5:27:50 AM - Info - Initializing X10 Plug-in: Insteon On COM Port 1
11/7/2006 5:27:50 AM - Info - Initializing Plug-in: Insteon
11/7/2006 5:27:50 AM - Insteon - Plugin: HSPI_Insteon.DLL - BETA VERSION 0.0.2.15
11/7/2006 5:27:50 AM - Insteon - RegisterCallback Completed
11/7/2006 5:27:50 AM - Insteon - Connecting to SmartHome Device Manager (SDM) component...
11/7/2006 5:27:51 AM - Insteon - Connected to SDM component, Checking Insteon interface connection...
11/7/2006 5:28:01 AM - Insteon - Insteon interface found containing firmware version 2.13 (Version 2 Revision 13)
11/7/2006 5:28:01 AM - Insteon - Insteon interface Address: 06.6A.69
11/7/2006 5:28:01 AM - Insteon - X10 Interface Initializing...
11/7/2006 5:28:01 AM - Info - Finished initializing X10 interface Insteon
11/7/2006 5:28:01 AM - Info - Finished initializing infrared interface
11/7/2006 5:28:01 AM - Info - Initializing Plug-in: Insteon
11/7/2006 5:28:01 AM - Insteon - IO/Insteon Interface Initializing...
11/7/2006 5:28:01 AM - Insteon - (Re)Loading 9 Insteon device information tables...
11/7/2006 5:28:01 AM - Insteon - (Re)Loading 0 Insteon group information tables...
11/7/2006 5:28:01 AM - Info - Finished initializing plug-in Insteon
11/7/2006 5:28:02 AM - Info - Local IP address is: 192.168.1.98/24
11/7/2006 5:28:02 AM - Info - Web server remote access is disabled. It can only be accessed from this computer
11/7/2006 5:28:02 AM - Info - Web Server started on localhost, port 80
11/7/2006 5:28:02 AM - Warning - Port number 80 in use, trying 81
11/7/2006 5:28:02 AM - Info - Web Server started on localhost, port 81
11/7/2006 5:28:02 AM - Startup - Initializing text to speech
11/7/2006 5:28:02 AM - Info - Listening for remote speaker connections on port 8742
11/7/2006 5:28:02 AM - Startup - Start remoting
11/7/2006 5:28:02 AM - Startup - Start event processing
11/7/2006 5:28:02 AM - Info - This version of HomeSeer is registered.
11/7/2006 5:28:02 AM - Startup - Scripting is OK
11/7/2006 5:28:02 AM - Info - Finished initializing scripting
11/7/2006 5:28:02 AM - Startup - Starting scheduler
11/7/2006 5:28:02 AM - Startup - Start up complete.
11/7/2006 5:28:04 AM - Info - Web Server authorized local login successful from: 127.0.0.1 User: default
11/7/2006 5:30:06 AM - Insteon - Found unused link # 13 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - Found unused link # 14 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - Found unused link # 15 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - Found unused link # 16 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - Found unused link # 17 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - Found unused link # 18 in our address space, assigning for use.
11/7/2006 5:30:06 AM - Insteon - (Re)Loading 10 Insteon device information tables...
11/7/2006 5:30:06 AM - Insteon - (Re)Loading 0 Insteon group information tables...
11/7/2006 5:30:06 AM - Database Item - Saving Device On
11/7/2006 5:30:06 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 1...
11/7/2006 5:30:06 AM - Database Item - Saving Device A
11/7/2006 5:30:06 AM - Database Item - Saving Device B
11/7/2006 5:30:06 AM - Database Item - Saving Device C
11/7/2006 5:30:06 AM - Database Item - Saving Device D
11/7/2006 5:30:06 AM - Database Item - Saving Device Off
11/7/2006 5:30:15 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 2...
11/7/2006 5:30:22 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 3...
11/7/2006 5:30:30 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 4...
11/7/2006 5:30:37 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 5...
11/7/2006 5:30:44 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 6...
11/7/2006 5:30:53 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 7...
11/7/2006 5:30:54 AM - Insteon - Record #7 is empty, skipping to next record
11/7/2006 5:30:54 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 8...
11/7/2006 5:31:02 AM - Insteon - Reading remote link database record for device ID 06.1C.5F record # 9...
11/7/2006 5:31:03 AM - Insteon - Record #9 is past the high water mark, ending link table query for ID 06.1C.5F

[Oman]

#1 is not an error, it is a debug statement. The high water mark indicates the last record used, so there is no point reading past it.

#2) Was there an error when you changed the name? Is there an error when you restart the plug-in? I need a log file that is generated upon an error, or the manual log generate option in order to tell what is wrong.

Jon

[chamoun]

Jon:

Thank you for explaining #1.

#2) This happened while I was using 0.0.2.13 and I do not recall if it created an error message. I recall some write errors in the past but everything continued to work fine. I have shutdown and restarted the system many times with no errors. The attached log is typical. It seems that something got altered and moving to 0.0.2.15 did not help. I can send you my INI file as an attachement if that is helpful. I can also rename my INI and start fresh to see if I can reproduce the problem.

Let me know.

[Oman]

There were some problems with .13 and the device channel naming code. Those should be fixed in .15. If you delete that one device and re-add it you should be good. If something does not work the way you expect then use the manual log generation right after you see the unexpected behavior and post the log. It will contain everything I need to track the problem down. If you restart HomeSeer the info will be lost.

Jon

Jon:

Thank you for explaining #1.

#2) This happened while I was using 0.0.2.13 and I do not recall if it created an error message. I recall some write errors in the past but everything continued to work fine. I have shutdown and restarted the system many times with no errors. The attached log is typical. It seems that something got altered and moving to 0.0.2.15 did not help. I can send you my INI file as an attachement if that is helpful. I can also rename my INI and start fresh to see if I can reproduce the problem.

Let me know.

[chamoun]

So if you do not change the key names you are not getting the device and key name? If you leave the default you should get

"Device Name - Key Name"

If you override the key name then you will not get the device name added. This was by request.


Jon


I added a new device manually this AM using .15 and the behavior was consistent. The default names for the Keypad are still (On,A,B,C,D,Off) and the name of the device never appears next to each key in the various sections (events, status etc..) unless I manually include it in the name of each key. No errors were generated.

[chamoun]

Go to your device edit screen and look at the highest device number you currently have (say 15 for example).

Now shut down HS and edit the Insteon.ini file.

Delete all device section entries that are > 15.

Try to add a new keypadlinc and see if it behaves properly.

If so then the problem is the old INI entries are not getting reset upon adding a new device.

Jon


The problem is my default appears to be set to the edited names (On,A,B,C,D,Off) and therefore I am no longer able to get "Device Name - Key Name" for newly added Keypads. I have deleted all Keypads and started over but that did not change the outcome. Somehow the default got modified permanently.

Thoughts?

[chamoun]

I deleted all devices beyond my last device in the INI file and that did not help. I had to go back and delete all my Keypads and then delete the devices beyond my last device in the INI file for the default naming to start working properly again. Hopefully that gives you a better idea of what is going on. I am worried now about hand editing keynames on keypads because of the risk of having to start all over. Let me know how to best handle this situation.

Thanks.

[Oman]

I think I have it all fixed. If you PM me an email address that I can send an attachement to I'll drop you a build to make sure all the issues you are seeing are taken care of.

Thanks
Jon

I deleted all devices beyond my last device in the INI file and that did not help. I had to go back and delete all my Keypads and then delete the devices beyond my last device in the INI file for the default naming to start working properly again. Hopefully that gives you a better idea of what is going on. I am worried now about hand editing keynames on keypads because of the risk of having to start all over. Let me know how to best handle this situation.

Thanks.

[chamoun]

Jon:

I just looked at the problem again and here is what I found. Changing the button names on all Keypad devices no does not appear to mess up the default naming for new additions (fixed from .13 to .15?). Having said that once you change the names on any device you can no longer restore the default naming convention. If you type Button A and hit save no error message is generated but the old name reappears. A restore defaults button may be the easiest solution for those who to recover the automatic naming for Keypad buttons. Deleting the Channel names from the INI file restores the default names.

Did you send me a build? No ruch, just cheking to make sure it was not lost in cyberspace.

Thanks.

[Oman]

The ability to change the names was a new addition to the code base, and I have found several problems there. I am assuming not too many people are changing the default names at this point because I would think more people would have found these issues.

Jon

Jon:

I just looked at the problem again and here is what I found. Changing the button names on all Keypad devices no does not appear to mess up the default naming for new additions (fixed from .13 to .15?). Having said that once you change the names on any device you can no longer restore the default naming convention. If you type Button A and hit save no error message is generated but the old name reappears. A restore defaults button may be the easiest solution for those who to recover the automatic naming for Keypad buttons. Deleting the Channel names from the INI file restores the default names.

Did you send me a build? No ruch, just cheking to make sure it was not lost in cyberspace.

Thanks.

[Majkman]

A couple of fixes

Please excuse me, as this is my first post here, and I am a new Homeseer user (2 weeks), But have been using x10 automation for over 25 years. Homeseer will be my 8th different automation controller.


Currently running 2.1.143.0 with Insteon 0.0.2.15 so the software is up to date, i think.

Minor issue 1:
in the log it shows 11/10/2006 11:44:41 AM - Info - Initializing X10 Plug-in: Insteon On COM Port 1

But the Insteon device is a USB device, not on Com1 (same issue on the install of the interface screen)

Minor issue 2:
Insteon device type 'In-LineLinc relay' 2475S is showing up on the status screen as
Insteon Unknown Device Type 0210 Unknown

Minor issue 3:
Noticed that on the status screen, SOMETIMES after running scripts to activate X10 Lamp modules, at 100 percent, it would appear on the status screen at 10 percent.

Minor issue 4:
Templinc- you have a box to indicate templinc II, how do i determine if its a templinc or a templinc II. The templinc has been disconnected for now,as i try to de-haunt the house (see major issue 1 below).

Major issue 1:
X-10 devices seem haunted, they turn off whenever. When I played with the Insteon Device polling, and turned that off, it seemed to make it less haunted.

Major issue 2:
From the Testerlinc i am showing a lot of BBK and BSC, bad block and bad start code. Only when the PowerLinc 2414U is connected. Any Ideas? The house is clean, showing no noise on the testerlinc. Lots of filters are used.

Major issue 3:
I had to unplug the one boosterlink (V3) to be able to install the insteon devices.
Any Ideas?

I am thinking of hooking back up the 1132CU to use only for the X10 devices as the x10 signal appears to be stronger from it, any problems with running the 1132CU as the X10 device controller and the 2414U as the Insteon controller. Must I plug them into different AC circuits? or can they co exist on the same AC circuit?

I have added the current log, from the most current startup below.

<TABLE cellSpacing=2 cellPadding=0 width="100%" border=0><TBODY><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Settings Loaded.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType1 align=left colSpan=3>Startup </TD><TD class=LOGEntry1 align=left colSpan=8>Loading configuration file ...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Loading device types file...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType1 align=left colSpan=3>Database </TD><TD class=LOGEntry1 align=left colSpan=8>Opening up HomeSeer database C:\Program Files\HomeSeer 2\config\sample.mdb</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Loading Devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType1 align=left colSpan=3>Load Config </TD><TD class=LOGEntry1 align=left colSpan=8>75 total devices loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:39 AM </TD><TD class=LOGType0 align=left colSpan=3>Load Config </TD><TD class=LOGEntry0 align=left colSpan=8>Checking device type settings for all devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Load Config </TD><TD class=LOGEntry1 align=left colSpan=8>Finished checking device type settings.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Load Config </TD><TD class=LOGEntry0 align=left colSpan=8>Loading Events...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Load Config </TD><TD class=LOGEntry1 align=left colSpan=8>28 total events loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Loading TV Timers...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Database </TD><TD class=LOGEntry1 align=left colSpan=8>HomeSeer configuration database C:\Program Files\HomeSeer 2\config\sample.mdb has been closed.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>HomeSeer version is: 2.1.143.0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Initializing phone interface...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Warning </TD><TD class=LOGEntry0 align=left colSpan=8>No addressbook.xml file exists, creating default</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Warning </TD><TD class=LOGEntry1 align=left colSpan=8>No mailboxes.xml file exists, creating default</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Checking for available plug-ins</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Found plug-in: Insteon, version: 0.0.2.15</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Found plug-in: SmartHome PowerLinc USB, version: 1.0.0.7</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Found plug-in: SmartLinc Templinc, version: 2.0.0.1</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:40 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Found plug-in: Media Player, version: 2.0.0.12</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Startup </TD><TD class=LOGEntry1 align=left colSpan=8>Restoring device status</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Initializing Plug-Ins</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Initializing X10 Plug-in: Insteon On COM Port 1</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Initializing Plug-in: Insteon</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Host System: HomeSeer 2.1.143.0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Plugin: HSPI_Insteon.DLL - BETA VERSION 0.0.2.15</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>RegisterCallback Completed</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Enter InitX10</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Enter InitPlugin</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Global initialization of plug-in required, starting up.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:41 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Connecting to SmartHome Device Manager (SDM) component...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:42 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Connected to SDM component, Checking Insteon interface connection...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>IsResponding returned: 'DM=active,1.01.122.278,11/10/2006 11:44:51 AM,responded,07.8A.EF,2.13'</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Insteon interface found containing firmware version 2.13 (Version 2 Revision 13)</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Insteon interface Address: 07.8A.EF</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>In TransmitMessageThread</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>X10 Interface Initializing...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Exit InitPlugin</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Exit InitX10</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Finished initializing X10 interface Insteon</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Finished initializing infrared interface </TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Initializing Plug-in: Insteon</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Enter InitIO</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Enter InitPlugin</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Global initialization already completed.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>IO/Insteon Interface Initializing...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>In CreateDevices</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>(Re)Loading 20 Insteon device information tables...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Warning: An unknown Insteon device of type 0210 was added to the system.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>(Re)Loading 0 Insteon group information tables...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>[HCM] There are existing 'DeviceBaseCode' class HomeSeer devices currently using the previously allocated base house code of: '\'.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>24 Matching HS device records were found and updated for the Insteon device database.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>[HCM] There are existing 'GroupBaseCode' class HomeSeer devices currently using the previously allocated base house code of: '['.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>1 Matching HS device records were found and updated for the Insteon group database.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Exit CreateDevices</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Insteon </TD><TD class=LOGEntry0 align=left colSpan=8>Exit InitPlugin</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Insteon </TD><TD class=LOGEntry1 align=left colSpan=8>Exit InitIO</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Finished initializing plug-in Insteon</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Local IP address is: 192.168.1.108/24</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Web Server started on port 81</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:52 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Web Server authorized local login successful from: 127.0.0.1 User: gary</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:53 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Creating ASP.NET application host...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>ASP.NET application host created</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Initializing text to speech</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Listening for remote speaker connections on port 8742</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Start remoting</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType1 align=left colSpan=3>Startup </TD><TD class=LOGEntry1 align=left colSpan=8>Start event processing</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>This version of HomeSeer is registered.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType1 align=left colSpan=3>Startup </TD><TD class=LOGEntry1 align=left colSpan=8>Scripting is OK</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Finished initializing scripting</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:44:54 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Powerfail Recovery will take place in 100 seconds.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:45:03 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Speaker client connected from: 127.0.0.1</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:45:03 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Speaker host added, Name: garyp IP address: 127.0.0.1</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Synchronizing events from 11/9/2006 11:46:00 PM until now</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Synchronizing Events: Waiting for event actions to process...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Synchronization complete, updating devices</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Device update complete</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType0 align=left colSpan=3>Startup </TD><TD class=LOGEntry0 align=left colSpan=8>Starting scheduler</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:46:34 AM </TD><TD class=LOGType1 align=left colSpan=3>Startup </TD><TD class=LOGEntry1 align=left colSpan=8>Start up complete.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>11/10/2006 11:48:13 AM </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Event Trigger "WeatherWarnings"</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>11/10/2006 11:48:13 AM </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Running script in background: Weather Warnings.txt</TD></TR></TBODY></TABLE>





Thanks for any assistance,
Gary Morgan

[Oman]

1) This is a legacy HomeSeer issue, not from the plug-in. It just assumes that we need a com port.
2) The plug-in has to know about a device to use it. That device isn't on the published road map that I have. I'll have to see if I can find it's description and add it.
3) I have not seen that one. See #5
4) I think you are talking about an X10 device here, so the plug-in doesn't manage it.
5) The 2414 interfaces don't do X10 well. I would highly recommend that you use a different interface for X10. Some 2414s seem to send out a very poor X10 signal, and even when they send out a good signal the X10 is slow and extended commands are not supported.
6) There is a known incompatibility between a number of the "Boosterlink" devices and Insteon. See SmartHome support about this.
7) Yes, you can have the 2414 and another X10 interface on the same circuit.

Jon

Please excuse me, as this is my first post here, and I am a new Homeseer user (2 weeks), But have been using x10 automation for over 25 years. Homeseer will be my 8th different automation controller.


Currently running 2.1.143.0 with Insteon 0.0.2.15 so the software is up to date, i think.

Minor issue 1:
in the log it shows 11/10/2006 11:44:41 AM - Info - Initializing X10 Plug-in: Insteon On COM Port 1

But the Insteon device is a USB device, not on Com1 (same issue on the install of the interface screen)

Minor issue 2:
Insteon device type 'In-LineLinc relay' 2475S is showing up on the status screen as
Insteon Unknown Device Type 0210 Unknown

Minor issue 3:
Noticed that on the status screen, SOMETIMES after running scripts to activate X10 Lamp modules, at 100 percent, it would appear on the status screen at 10 percent.

Minor issue 4:
Templinc- you have a box to indicate templinc II, how do i determine if its a templinc or a templinc II. The templinc has been disconnected for now,as i try to de-haunt the house (see major issue 1 below).

Major issue 1:
X-10 devices seem haunted, they turn off whenever. When I played with the Insteon Device polling, and turned that off, it seemed to make it less haunted.

Major issue 2:
From the Testerlinc i am showing a lot of BBK and BSC, bad block and bad start code. Only when the PowerLinc 2414U is connected. Any Ideas? The house is clean, showing no noise on the testerlinc. Lots of filters are used.

Major issue 3:
I had to unplug the one boosterlink (V3) to be able to install the insteon devices.
Any Ideas?

I am thinking of hooking back up the 1132CU to use only for the X10 devices as the x10 signal appears to be stronger from it, any problems with running the 1132CU as the X10 device controller and the 2414U as the Insteon controller. Must I plug them into different AC circuits? or can they co exist on the same AC circuit?

I have added the current log, from the most current startup below.

[Majkman]

Both Smarthome 2414u, and 1132cu

I have installed both interfaces now, the insteon commands go thru the 2414u, as do the x10 commands. Both interfaces are enabled, with the insteon and the x10 on two different interfaces inside of HS.

Do I need to delete the X10 devices that were created when i only had the 2414u connected, (are the x10 devices bound to the interface they were created on)?

Another way to ask the same question: do I need to delete, and re-define the x10 devices to use the 1132cu interface? or does HS automatically see that the old interface is disabled and use the new interface?

[Oman]

X10 devices are generic. They will use whatever X10 interface is active. Usually HomeSeer only allows one. Just disable X10 on the 2414 side and that should be it.

PS: I just updated the .16 build in the sticky thread to add an additional error message if the SDM is too old. Some of the old ones work and some don't, so I just warn if I think it is too old. I did not update the version number.

Jon

I have installed both interfaces now, the insteon commands go thru the 2414u, as do the x10 commands. Both interfaces are enabled, with the insteon and the x10 on two different interfaces inside of HS.

Do I need to delete the X10 devices that were created when i only had the 2414u connected, (are the x10 devices bound to the interface they were created on)?

Another way to ask the same question: do I need to delete, and re-define the x10 devices to use the 1132cu interface? or does HS automatically see that the old interface is disabled and use the new interface?