JDS for HomeSeer 2.1 BETA

[tman1]

There appears to be a problem with older hardware, Timecommander plus for example. I have to connect at 2400 baud and have always been hit or miss on interface with hs. Here is the log after starting the plug in. Hope this helps.


7/19/2006 11:07:17 PM - Info - Speaker client connected from: 127.0.0.1
7/19/2006 11:07:17 PM - Info - Speaker client connected from: 192.168.0.103
7/19/2006 11:07:18 PM - Info - Speaker host added, Name: myco3200 IP address: 192.168.0.103
7/19/2006 11:07:18 PM - Info - Speaker host added, Name: haserver IP address: 127.0.0.1
7/19/2006 11:07:19 PM - Info - Web Server authorized local login successful from: 127.0.0.1 User: default
7/19/2006 11:07:45 PM - Info - Initializing Plug-in: JDS StarGate on COM port 1
7/19/2006 11:07:45 PM - JDS StarGate - Initializing Global Settings
7/19/2006 11:07:45 PM - Info - Current debug events set:
7/19/2006 11:07:45 PM - JDS StarGate - Stargate plugin version 2.1.0
7/19/2006 11:07:45 PM - JDS StarGate - Attempting contact with JDS hardware
7/19/2006 11:08:05 PM - JDS StarGate - Error in global Init/Comms: Unknown hardware: ###%33ff
7/19/2006 11:08:05 PM - JDS StarGate - Done Initializing Global Settings
7/19/2006 11:08:05 PM - Info - Finished initializing plug-in JDS StarGate

[RJ]

Hello again-

Please see the latest build for a few fixes (Beta 7b). This Error in SGLog has been fixed, and the debug messages have been greatly expanded. If you try this build and are still having trouble with the polling, try enabling "Function Debug" on the config page. WARNING: This will write a large ammount of data to the log. If your system is older, you many not want to enable this message. If you still have trouble with polling, try enabling this feature for about a minute, then send me your log so I can take a look at it.

Thanks!

[Pierre]

I just tried 7b and the errors in the logs are gone, but i cannot trip relays anymore.

A question about polling: Polling was not necessary in the 1.X plugin, as the status changes made outside HS where updated immediatly.
I guess it is the same for ver 2.X so I disabled polling.

I guess that instead of X-10, nothing can be changed, nothing is updated and nothing is logged.

Also I would expect that flags to be on/off from the device page, and not the variables.

[KLS]

I just tried 7b and the errors in the logs are gone, but i cannot trip relays anymore.

A question about polling: Polling was not necessary in the 1.X plugin, as the status changes made outside HS where updated immediatly.
I guess it is the same for ver 2.X so I disabled polling.

I guess that instead of X-10, nothing can be changed, nothing is updated and nothing is logged.

Also I would expect that flags to be on/off from the device page, and not the variables.

Hello Pierre - are you saying that some of your variables are shown as the wrong type? I.E. variables statuses are listed as discrete, On/Off rather than analog as some number?
If so, also, did you import your Stargate device database with an earlier version of the plug-in? Say version 5 or sooner?
What I found is that after the first import of the device database, subsequent imports did NOT update the devices and their types as shown in the HS status screen.
I just MOVED the "sample.db" (Sample database) to a backup location.
Re-started HS, which created a new sample database. Then did the re-import from Stargate and ALL of my devices imported correctly.
It might be worth a try.
Also, can we verify that the import function will correctly update the device database if changes have been made to the Stargate device databases?

[RJ]

Also, can we verify that the import function will correctly update the device database if changes have been made to the Stargate device databases?

Yes. The import fucntion basically mirrors your Stargate Database in HomeSeer. So, if your device was initially imported as "Device 1", if you did a re-import it would stay "Device 1". However, if you change the name in the Stargate Database, or add new devices in the Stargate Database, these changes will appear in HomeSeer.

[Pierre]

Uninstalled HS2, restarted, deleted Homeseer 2 directory, reinstalled HS2 with plugin beta 7, then imported devices.

ON/OFF Controls on status page:
X-10 Yes
Variable Yes
Flags No Should be present, I want to be able to set flags
Relays yes
Analog no
Digital no
Times security yes Should be no

General behaviour:

X-10: OK

Relays can be triggered but if triggered outside:

Variables: changes in variables made outside HS are logged but the status and last change are not updated
security: not logged, not updated, should not have ON/OFF buttons on setup page.
Flags: No ON/OFF button, not loged not updated when triggered outside HS
Digital inputs: Not logged or updated

[RJ]

Uninstalled HS2, restarted, deleted Homeseer 2 directory, reinstalled HS2 with plugin beta 7, then imported devices.

ON/OFF Controls on status page:
X-10 Yes
Variable Yes
Flags No Should be present, I want to be able to set flags
Relays yes
Analog no
Digital no
Times security yes Should be no

General behaviour:

X-10: OK

Relays can be triggered but if triggered outside:

Variables: changes in variables made outside HS are logged but the status and last change are not updated
security: not logged, not updated, should not have ON/OFF buttons on setup page.
Flags: No ON/OFF button, not loged not updated when triggered outside HS
Digital inputs: Not logged or updated

Pierre-

Great findings on a lot of issues. I fixed the button problems on the status page, due to old values in the plugin it was hiding the buttons or flags. The buttons for timers, timelabels, and security have all been removed.

The error in "HandleEvent" is a bit trickier, and is probably the reason you are not seeing values being updated as a result of polling! I am going to post a new build (8) right now that includes much more logging on the HandleEvent function. I knew the polling code was OK, and I think this is where the culprit is!

Thanks for the feedback!

[Lance]

Double Stargate listings on Homeseer status page

RJ<O</O

<O</O

I have an issue with double Stargate listings of inputs, relays, flags, analog and variables on the HomeSeer status page. The X10 and security listing are ok. (Listed once)<O</O



Is there any way to clear the stargate devices from the Homeseer status page so I can try a fresh Stargate DBF file import? <O</O

<O</O
Lance

[ajackson123]

Lance,

Have you tried deleting all Stargate-related devices and then doing a fresh import? That's been my workaround.

Correction: just noticed your question like I should have. Check off all Stargate devices on the status page, then down at the bottom of the page there's a drop-down box wherein you can choose "delete." That's how you get rid of them. Then do the import.

[Lance]

Thanks Andy

Andy

Thank you, that fixed the problem. I'm new to Homeseer and I never noticed the pull down menu.

thanks again

Lance

[ajackson123]

Device codes for Stargate devices

RJ,

Noticed that with the new plugin the device codes have changed to numerical values (e.g. digital inputs, flags, security are all two or three digit device codes). Is it safe to assume it will stay that way? Before I go through the arduous task of rewriting all my 1.7 scripts I thought I should check it out - or (as I've often wondered) can I just bypass referencing them with the device codes by using the old "DeviceByName" means? (or whatever is akin to that in .Net)?

Thanks,
Andy

[RJ]

Andy-

This is one of those anomalies in HomeSeer with assigning device codes. If possible, I would update to the latest plugin, Delete the "JDS.ini" file in your HomeSeer "config" folder, and re-import from scratch. I don't think there is any harm in having numbers as device codes, as they are just another ASCII value, but it bothered me while testing.

As far as getting devices, you can do a few things. "rval = hs.GetDeviceRef("A1")", followed by "dv = hs.GetDeviceByRef(rval)", will return the device object for the device at A1 into dv. You could also do "hs.GetDeviceRefByName("My Device")", to get the device reference. All the scripting functions are we documented in the Help file, and these are only two of the ways to implement this.

Whatever you do, stay away from hs.GetDevice and the device index. We have moved away from this in HomeSeer 2, and it is simply safer to use the Device referenece number instead.

[ajackson123]

Thanks much!

[RJ]

Hello All,

This thread has been pretty quiet lately, so I just posted a new build. It looks like if the activity here has died down, we are going to give this plugin the stamp of approval and put it into the updater as beta.

If you still have outstanding issues, please post them in this thread!

[tman1]

There appears to be a problem with older hardware, Timecommander plus for example. I have to connect at 2400 baud and have always been hit or miss on interface with hs. Here is the log after starting the plug in. Hope this helps.


7/19/2006 11:07:17 PM - Info - Speaker client connected from: 127.0.0.1
7/19/2006 11:07:17 PM - Info - Speaker client connected from: 192.168.0.103
7/19/2006 11:07:18 PM - Info - Speaker host added, Name: myco3200 IP address: 192.168.0.103
7/19/2006 11:07:18 PM - Info - Speaker host added, Name: haserver IP address: 127.0.0.1
7/19/2006 11:07:19 PM - Info - Web Server authorized local login successful from: 127.0.0.1 User: default
7/19/2006 11:07:45 PM - Info - Initializing Plug-in: JDS StarGate on COM port 1
7/19/2006 11:07:45 PM - JDS StarGate - Initializing Global Settings
7/19/2006 11:07:45 PM - Info - Current debug events set:
7/19/2006 11:07:45 PM - JDS StarGate - Stargate plugin version 2.1.0
7/19/2006 11:07:45 PM - JDS StarGate - Attempting contact with JDS hardware
7/19/2006 11:08:05 PM - JDS StarGate - Error in global Init/Comms: Unknown hardware: ###%33ff
7/19/2006 11:08:05 PM - JDS StarGate - Done Initializing Global Settings
7/19/2006 11:08:05 PM - Info - Finished initializing plug-in JDS StarGate

uh hello!!