David
Here\'s one way - add this as a script function in a HS event
&hs.plugin(\"pjcComfort2\").Transmit(\"X!P1005\")
The line above sends X10 P16 On - using standard Comfort RS232 as outlined in the document above.
You could try Colley\'s forum on homeseer.com - but be warned - I tried to ask a question - my first in the forum - and I was shown the middle finger and told to \'get lost\' as he \'was too busy\' - Homeseer.com were not interested in pushing this. Strangely, not too busy to add major CBUS support in the latest build.
And I PAID for the plugin.
Thanks for that. However the only thing that I can script is an on command. However it took me about two days to get that far! I wish I put up the query in this forum.
I really want to go beyond that but without knowledge of scripting and no examples to follow its virtually impossible. I would like to know things like; turn on P16 to 50%, How to make the chime work, etc. If there were some basic examples somewhere I am sure I would start to pick it up.
I share your concern regarding support though what can you expect for a few quid, frankly I\'d be happy to pay for it. But as with a lot of the HS software its written by enthusiasts and when they lose their enthusiasm..... Trying to get the best out of ã4k\'s worth of home control with a ã15 plug-in is hardly ideal.
Cheers
David
There\'s another way. With the Sonos plugin, I set a counter to a value, and then let Comfort do the rest. In Comfigurator, you tell it to fire off a response when a counter changes.
Set a counter that you want to trigger, and put all your X10 commands and other functions in there, rather than letting homeseer control it. For example, the HS Sonos plugin send this type of command when a Zone starts playing :
&hs.plugin(\"pjcComfort2\").Transmit(\"C!C901\")
So when the Lounge Zone starts playing, HS detects this via the Sonos plugin, and tells Comfort to set Counter 201 (C9 in Hex) to a value of 1. Comfort now knows that lounge has started playing, and sends the IR commands to the Amp for the lounge, etc. HS is a conduit only for settings some flags and all the logic is in Comfort
As for HS doing commands, refer to this -
https://www.cytech.biz/Downloads/Files/163/rs232.pdf
Search for X!P1005 which is the command I posted above - this shows you examples of what to send as an RS232 command.
Thanks, very much, really appreciate that \"real\" advice. I might even try to get my Sonos kit integrated..
At least if you get any X10 queries, and you use the counter method, you can just pop here for x10 support.
Shout if you want any help with Sonos. or drop me a PM and we can talk over email.
Interesting to read the comment about lack of support from HS/Rod Colley - I had quick responses but that was a year or more ago - probably when the enthusiasm was still there!
I had forgotten about the \"Transmit\" command as pointed out in the thread. Note that there is also a \"TransmitX10\" command in HS which doesn\'t need hex codes as in the Transmit(\"X!P1005\") command. I don\'t use these so am not sure whether you can set dim levels via these commands.
Note also that there are various other commands which you may find useful, specifically \"ControlOutput\" for your question on how to control outputs.
If you can\'t make Transmit or TransmitX10 work, then you\'ll probably have to use counters. Are you aware of the PDF that comes with the plug-in? It should be in C:\\Program Files\\Homeseer2\\Docs. This explains how to map counters to Comfort and all the plug-in commands.
For your example of activating the chime, one way of doing this with counters is ....
Create a response, say \"DoChime\" containing the following:
Siren Chime
Then select a counter in Comfigurator (say Counter1), and set the Response column to \"DoChime\". Now, whenever the counter gets set (to any value), \"DoChime\" will be triggered and the chime will be activated.
In HS, set up a script, say \"TriggerChime\" as follows:
Sub Main
hs.PlugIn(\"pjcComfort2\").Transmit_SetCounters \"Counter1,1\"
End Sub
Now, when you run \"TriggerChime\" in HS, the counter gets set and Comfort runs the \"DoChime\" response.
You could obviously get much more elaborate, possibly for your X10 commands, by setting the counter in HS to different values denoting different dim levels, and then the Comfort response, say \"DoLightOn\" could resemble the following:
If Counter Counter1 = 1 Then
X10 A1 On
End If
If Counter Counter1 = 2 Then
X10 A1 Dim
End If
Hope this helps.
Thanks for that response, its really useful and although may appear basic, the plug-in assumes reasonable knowledge, or as they say a little bit of knowledge can be dangerous, that maybe where I am at.
I have lots of questions but if you could answer a couple that would be great.
Do I understand correctly that the process of setting up the counters in Comfigurator is as simply as selecting a spare counter, using the drop down ment for the action you are trying to achieve, upload to Comfort? You don\'t have to set up references/responses, etc in Comfigurator?
Then in Homeseer Create the Counter (I have\'nt yet read up on that)? What do I want to do if I am adding new counters, do I simple just increase the number of counters and hit create? i.e I don\'t need to re-read the CCL file?
Thanks, your real scripts are a massive help, as I can then work from something known.
Cheers, Dave.
Yes, on the Comfort side just use a spare counter.
The PDF referred to previously should give some help in setting up the counters, but I did struggle when I first did this - the doc isn\'t written too well, in my opinion (just my opinion, I don\'t wish to start another off-topic argument
).
In my opinion (again!) the counter HS/Comfort mapping isn\'t too robust (but it\'s a small price to pay - I\'m still impressed by the plug-in - and HS and Comfort!). Also, I haven\'t upgraded my HS or Plug-in for some time so don\'t know if there is a later version available.
Every time I wanted to change something during initial development/experimenting, I ran into some problems with the counter mapping - I can\'t quite remember the details and it may simply be that I don\'t understand the mapping methodology - I normally only learn enough about a product to be able to do what I need to do!
I found that if you use the Comfort default counter names, and you then changed a counter name in Comfort and then re-run the plug-in setup (i.e., re-read the CCL), you\'d lose the mapping or portions of it (or something to that effect). So what I eventually did was to rename all the counters in Comfort to non-default names (Counter_001 to Counter_254) and to create ALL the counters in HS just once. Then, if I subsequently changed a counter name in Comfort to make it more intuitive, like \"cChime\" (the leading \"c\" being my way of identifying counters easily), I could then simply change the name in the plug-in setup and also change the name of the HS device - a couple of extra steps but has been well worth it. OK, so you end up having lots of unused counters displayed in HS Devices, but I simply hide the ones that I\'m not interested in seeing. (Maybe there are other negatives to my method, but it works for me!)
Good luck!
Leon
Isnt TransmitX10 in HS referring to direct X10 control of a CM12 - and not the comfort plugin ?
I typically use: eg.
hs.Plugin(\"pjcComfort2\"). TransmitX10 \"A\",01,05,00
I don\'t use the CM12 so can only assume that it speaks directly to the plug-in through Comfort.