xAP for Xlobby

by **siliconmelt** on Fri Feb 25, 2005 3:42 pm

It's running about 85 messages/minute

by **siliconmelt** on Fri Feb 25, 2005 4:25 pm

PM isn't working

mailto:siliconmelt@comcast.net

by **ptrinchi** on Fri Feb 25, 2005 9:11 pm

You can download it at http://www.france.xlobby.com/plugins/xAP-Xlobby/
(don't forget to make a backup of the old files)

If you don't speak French ask me and I will explain you how it works :lol:

Be careful, this version use 2 XML (events and actions) that give the plug descriptions of dynamic outgoing and incoming messages.

ACTIONS.XML is used for describe outgoing messages. With this XML you can add every xAP actions (existing and coming) to XL

EVENTS.XML is used to explain what kind of messages XL must listen to. This file is not full exploited yet :oops:

I have also add a new variable, try for example :
plugin>xAP-Xlobby>imagetext>garage.barlight

Good tests :wink:

----- French Team Member -----

by **siliconmelt** on Mon Feb 28, 2005 2:17 pm

plugin>xAP-Xlobby>imagetext>garage.barlight
it gives me the 0 - 100 state of the devices. I like this option
My question is this:
Is there anyway to make the 0 - 100 png files generic instead device specific?
100 png files for each device, plus an ON,OFF,UNkown png for each device doesn't make any sense to me. Just guesing for my setup, I would end up with 1,000s of png files.

As for my prior problem, I am trying to set up xap-xlobby to query HS when it loads. I am begining to wonder is maybe the HS pluggin is the culprit to alot of my problems.

In the xap-Xlobby configuration, does the (mi4.homeseer.*.* ) need to be changed to - in my case (mi4.homeseer.main154.*) ?

by **ptrinchi** on Mon Feb 28, 2005 5:20 pm

Is there anyway to make the 0 - 100 png files generic instead device specific?

Yes, it's a good idea. If the png does'nt exist the plug could load a generic png file (without the device name) perhaps in the next version :wink:

As for my prior problem, I am trying to set up xap-xlobby to query HS when it loads. I am begining to wonder is maybe the HS pluggin is the culprit to alot of my problems.

I'm glad to see that the xAP-Xlobby plug-in work well.

In the xap-Xlobby configuration, does the (mi4.homeseer.*.* ) need to be changed to - in my case (mi4.homeseer.main154.*) ?

The plug will answer more quickly if you change the destination address to mi4.homeseer.main154.*

by **siliconmelt** on Mon Feb 28, 2005 5:42 pm

I'm not having much luck in setting up a working query to HS from the plugin.
What is the correct way? Can you give me an example of what steps I need to take to get a query and a command toggle to work?

by **ptrinchi** on Mon Feb 28, 2005 7:06 pm

no problem,

First be sure that your HS address is correct (in the config panel of xap-xlobby plug-in)
Then, be sure that the command is correct in XML file (Two days ago I have seen some problem in my action.xml, download the new one on the French forum) You should have something like this :

<?xml version="1.0" encoding="UTF-8" ?>
<xAP>

<event>
<name>Basic Control</name>
<class>xAPBSC.cmd</class>
<adress>*Xlobby*</adress>
<Desc>bsc 1.3</Desc>
<body>output.state
{
id=*
state=[On,Off,Toggle]
}
</body>
</event>

<event>
<name>Basic Query</name>
<class>xAPBSC.Query</class>
<adress>*Xlobby*</adress>
<Desc>bsc 1.3</Desc>
<body>
request
{
[]
}
</body>
</event>

<event>
<name>HomeSeer Command</name>
<class>homeseer.command</class>
<adress>Master</adress>
<Desc>HS Cmd</Desc>
<body>
homeseer.command
{
command=[Speak,TriggerEvent,TriggerScript]
data1=*Xlobby*
data2=
data3=
data4=
}
</body>
</event>
</xAP>

Create an event and assign the plugin command toggle with for example Garage.BarLight :wink:

Create a second command in the same event (plugin command query) with the same parameter.

You can use the test button, not the test button under the parameter but the test button under the events tree.

Then go to your xAP hub and try to find the two messages, open it to see if all is correct.
- the target must be the address you enter followed by :Garage.BarLight
For the command message
- the class must be xAPBSC.cmd
- the bloc name must be output.state
- and 2 ligne id=* and state=Toggle
For the query message
- the class must be xAPBSC.Query
- the bloc name must be request
- and no line in it

If so all is correct and the HS plugin must execute and respond :lol:

by **siliconmelt** on Mon Feb 28, 2005 7:22 pm

Set it up as per you directions, I get the following xap messages, but HS does nothing.

xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.event
source=PTrinchi.Xlobby.main154
target=mi4.homeseer.main154.*:Garage.BarLight
}
output.state
{
id=*
state=Toggle
}
xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.Query
source=PTrinchi.Xlobby.main154
target=mi4.homeseer.main154.*:Garage.BarLight
}
request
{
}

by **ptrinchi** on Mon Feb 28, 2005 7:28 pm

Your actions.xml file is corrupt

The class of your message must be xAPBSC.cmd and not xAPBSC.event

You must modify your actions file, the first line with class tag (<class>) You certainly have this : <class>xAPBSC.event</class> and this line is wrong.
You must have :
<class>xAPBSC.cmd</class>

Make the change and it would work

by **siliconmelt** on Mon Feb 28, 2005 7:31 pm

I just caught that. I noticed the <name>Basic Control</name>
<class>xAPBSC.cmd</class> was wrong so I changed it and got it to work(sort of).
Now when I click the button it toggles the device but only for a second, then it goes right back to it's previous state.

by **ptrinchi** on Mon Feb 28, 2005 7:40 pm

Are you sure that they're no other messages that makes problem.

You must have only 2 messages, one with xapbsc.cmd class and an other with xapbsc.query.

Also, be sure that HS have no event that will turn the device to it original state.

by **siliconmelt** on Mon Feb 28, 2005 8:12 pm

this is sent out:

xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.cmd
source=PTrinchi.Xlobby.main154
target=mi4.homeseer.main154.*:Garage.BarLight
}
output.state
{
id=*
state=Toggle
}
xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.Query
source=PTrinchi.Xlobby.main154
target=mi4.homeseer.main154.*:Garage.BarLight
}
request
{
}

I clicked the button 2 times and got this in HS log:
2/28/2005 3:05:01 PM~!~Event Trigger~!~Status change trigger (Bar Lights on):Garage Bar Light O5 On
2/28/2005 3:05:01 PM~!~Info~!~Exec command: Garage Bar Light ON dim: 0 extra: 0
2/28/2005 3:05:04 PM~!~Event Trigger~!~Status change trigger (Bar Lights off):Garage Bar Light O5 Off
2/28/2005 3:05:04 PM~!~Info~!~Exec command: Garage Bar Light OFF dim: 0 extra: 0
2/28/2005 3:07:35 PM~!~Event Trigger~!~Status change trigger (Bar Lights on):Garage Bar Light O5 On
2/28/2005 3:07:35 PM~!~Info~!~Exec command: Garage Bar Light ON dim: 0 extra: 0
2/28/2005 3:07:38 PM~!~Event Trigger~!~Status change trigger (Bar Lights off):Garage Bar Light O5 Off
2/28/2005 3:07:38 PM~!~Info~!~Exec command: Garage Bar Light OFF dim:

I have no other events assigned to this device.
I setup another device and it works fine, so I will look deeper into this barlight and see why it will not stay on.

The Query is working beautifully

by **ptrinchi** on Mon Feb 28, 2005 9:40 pm

I setup another device and it works fine, so I will look deeper into this barlight and see why it will not stay on.

The Query is working beautifully

I'm happy for you. See you soon (for the next realease)

PS : If you have other ideas about what the plug can do let me know :wink:

by **Hiller** on Tue Mar 01, 2005 9:52 pm

ptrinchi,

If you could interface with the xAP X10-Connector that would be great! I don't own HS and since xAP can do it all for free I'm going that route.

by **ptrinchi** on Wed Mar 02, 2005 12:59 pm

Ok, I will try :wink: