Announcement

**Michael McSharry** · October 20, 2003, 08:53 PM

I believe I found reason the com port is not recognized. I suspect those with a problem with it are using the ocelot as the homeseer X10 interface. I'm not so I overlooked this when testing. If a problem still exists then I will add some debug info to help understand why.

I also added a new method PlayIREx after seeing Jim Doolittle's desire for it. Everything was already in the plugin to handle it so it was not a biggie.

I do not have a SECU16IR so I was not able to test to confirm that I got the IR Zone processing done correctly with the PlayIREx command. Someone else with the SECU16IR will need to confirm.

PlayIREx is a generalize Play IR method that will accept either a specific IR location or a mnemonic that is defined in the IR config of homeseer.

bStatus = PlayIREx (Location as Variant)

The returned value bStatus is 0 if Location is not a recognized value and 1 if recognized.

The input parameter Location is a variant. If it is a number then it is treated as the specific IR location. In this mode the PlayIREx and PlayIR methods are equivalent.

Location can also be a string of the form “Device Label” with a space use to separate the Device and the IR label. The Device and Label values are those defined from the Homeseer GUI View/IRConfig and contained in the file \Config\irlbl.cfg.

If the specified IR label is associated with a SECU16-IR zone then the PlayIREx method will command the remote unit. If it is associated with the ocelot/leopard then it will be a local IR command. The zone definitions used are those contained in \Config\irzone.cfg. If a zone is not defined, or defined as either 0 or 17 then the command will be a local IR command to the ocelot/leopard.

Examples:
Set cpuxa = hs.GetPlugins(“ADIOcelot”)
cpuxa.PlayIREx “TV On”
Status = cpuxa.PlayIREx(56)

**Michael McSharry** · October 25, 2003, 05:47 PM

System map synchronization has been added to the plugin. While I cannot provide source for the plugin, the system map processing is isolated to a single module and it is posted for reference. A vbs file was also added to rename the updated IR files. The zip file is stored with a file structure and can be unzipped from the homeseer root directory.

A little reoganization of the setup form was done, but most of the change is related to the CMAX support.

**Jim Doolittle** · October 27, 2003, 05:03 AM

Very nice. I just got my Ocelot up and running again, ADIOcelot plugin was released, and TouchPad plugin was released. This should all work together nicely.

The ability to start/stop CMAX without stopping/starting HomeSeer is a big time saver.

Thanks,

Jim Doolittle

**Michael McSharry** · October 29, 2003, 05:54 PM

Replaced by powerline interface and was able to track down the X10 receive problem. All should be 100% now with the plugin. I'll leave it here for awhile and if everyone is happy then move it to the updater.

**Jim Doolittle** · November 8, 2003, 06:45 AM

So far I have no major problems with ADIOOcelot. It works very good. I did receive an "Define HSIR Permission denied" error when trying to use System Map for device and IR label naming.

Would it be possible to add an option to the System Map <-> HomeSeer naming function that would only include devices with names that differ from default plugin device names? This would be easier to maintain than determining which of the device codes need to be checked in the Variables To/From HomeSeer Devices section.

For example, if that option were available and selected, then all device names starting with "Variable #" for Ocelot devices or "Input #" for Secu16/Secu16I devices would be ignored and correspondingly unchecked in the Variables To/From HomeSeer Devices section. Hopefully, user would not rename and still include that portion of original name.

If this sounds reasonable and doesn't create a lot of work on your part, I will test as soon as it is available. Meanwhile, I have to do some IR troubleshooting.

Jim Doolittle

**Michael McSharry** · November 8, 2003, 10:27 AM

I think I understand what you are asking, but I do not see the relationship between the request and the System Map Synchronization function.

When a Variable or IO point is unchecked on the plugin's grid then the homeseer device is deleted. There is no longer anything for the Synchronize function to look at on the homeseer side. I can see where it is possible to add a button that will "auto populate" the grid based upon current homeseer device definitions. This button would only come into play one time after someone originally used the ocelot plugin and is now using the ADIOcelot one.

Lets explore what really should be done to make the plugin intuitive for the user in this area.

I can see the the DefinedHSIR error message. Dont know what happened yet, but I'll run it down.

**Jim Doolittle** · November 8, 2003, 10:49 AM

Yes, what I am asking is not directly related to the System Map synchronization. Just a logical extension of the process.

If it were used without System Map being involved, then I am not sure how it should work once a user first uses it. Maybe if the user names it, then it would not be deleted/re-created by the plugin. The user would need to deal with it unless the plugin were uninstalled and all devices go bye-bye.

Right now, the ability to see the device name by hovering over the checkbox in the Variables To/From HomeSeer Devices section works great for accomplishing the same result. So, consider this request a very low priority.

Jim Doolittle

**Michael McSharry** · November 8, 2003, 11:58 AM

The update for the Permission error is posted. I also received a permission error when trying to copy the backup in the .vbs script so I changed it to time-stamp the backups. That avoids the problem as well as retaining a history. This is a safer approach rather than a single file backup.

I'll leave device name recognition alone at this time and keep the V1.3.3 update posted for awhile before moving it to the Updater.

**sbessel** · November 9, 2003, 02:11 PM

Help:
I am running ver 1.3.2 and I am unable to toggle a relay on my SEC16 unit through scripting.

Using the GUI I can toggle on/off without any problems.
I attempt the following lines in scripting and nothng happens, not even an error. HomeSeer will read back the correct status.
<pre class="ip-ubbcode-code-pre">
hs.SetDeviceStatus "]16",2
hs.waitsecs 1
msgbox hs.devicestatus("]16")
hs.SetDeviceStatus "]16",3
hs.waitsecs 1
msgbox hs.devicestatus("]16")
</pre>

I then attempted to use this method:
<pre class="ip-ubbcode-code-pre">
Set cpuxa = hs.GetPlugins(“ADIOcelot”)
cpuxa.setpoint 1,16,1
</pre>
and I get the following error:
<pre class="ip-ubbcode-code-pre">
11/9/2003 1:04:33 PM~!~Error~!~Script error in file: DoorBell.txt: 1032:Invalid character in line 1
</pre>

Ideas? fixes?

thanks...

**jabrans** · November 9, 2003, 03:58 PM

I have installed ADIOcelot 1.3.3. I've added it as an interface. I have removed the Applied Digital Ocelot as an interface. I have selected ADIOcelot as my infared interface in View --> Options. I did not select a com port. When I set a com port there it seemed to interfere with the ADIOcelot plug-in communicating with the Ocelot. Here's my questions:
1. Do I have it configured properly when using ADIOcelot 1.3.3?
2. In this config how do I learn IR commands and how do I relabel them? When I was using the Applied Digital Ocelot plug-in I did it from IR Config under View but now that is blank.

Thanks, Jabran

**Michael McSharry** · November 9, 2003, 05:04 PM

sbessel,
I'm not clear on the nature of the problem. Is the correct status displayed in messages boxes when the hs devicevalue methods are used? Do the message boxes even appear?

The cpuxa object was defined in homeseer in versions before beta 130 or so. In the later betas it is defined by homeseer only when their ocelot plugin is used. If you have an earlier version of hs, then you cannot use the cpuxa object name, but should be able to use just about any other (e.g. cpuxa2). While using the plugin methods directly such as setpoint, they do not provide any more functionality than using the deviceValue of the homeseer object. Either can be used, but I find it easier to manage only one object (hs) rather than dealing with two.

The points defined for the SECUs are numbered from 0 to 15, while the homeseer devices are numbered from 1 to 16. When using setpoint you need to backoff the point number by 1. 16 is out of range.

I also noticed that your posting used the smart quotes for the ADIOcelot definition. This just may be the posting, but in actual script only the standard quote (") should be used.

jabrans,
After you deselect the original ocelot plugin I think you need to restart homeseer to free-up the port. Then you are able to select if for the ADIOcelot.

The View / IRConfig is the homeseer interface to IR learning and device labeling. It is independent of the IR interface selected. It should show up one the com port is established so the plugin will have success at initialization.

**sbessel** · November 9, 2003, 05:57 PM

<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by Michael McSharry:
sbessel,
<snip>
The points defined for the SECUs are numbered from 0 to 15, while the homeseer devices are numbered from 1 to 16. When using setpoint you need to backoff the point number by 1. 16 is out of range.

I also noticed that your posting used the smart quotes for the ADIOcelot definition. This just may be the posting, but in actual script only the standard quote (") should be used.
<snip><HR></BLOCKQUOTE>

These two fixed it... I can now use the cpuxa reference, I guess I copied and pasted the set statement and it contained the 'strange' quotes.

Although I am still puzzled why <pre class="ip-ubbcode-code-pre">hs.SetDeviceStatus "]16",2</pre> doesn't work.

Thanks for the help...

**jabrans** · November 9, 2003, 06:06 PM

I see what I was doing wrong. In the IR section of Interfaces I didn't have the com port selected. I thought I only selected it in the ADIOcelot plug-in setup but it has to be selected in both places.
Thanks, Jabran

**Rupp** · November 9, 2003, 06:48 PM

Is there any documentation? Is this the hspi_ocelot.exe that communicates with my Ocelot? I installed mine over 2 years ago and haven't done any upgrading and was wondering if it was finally time to upgrade?

-Rupp
Isn't Disney World a people trap operated by a mouse?

Announcement

ADI Ocelot Plugin Updates

ADI Ocelot Plugin Updates

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment