Hi Steve, well done on getting this out - it's going to be great
I have a problem though although others seem to have got this to work but for me the variables that comprise the HomeSeer device address arent't being added to the target address..
xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.cmd
source=Hiller.XLobby.Lightning
target=mi4.homeseer.Lightning.*:
}
output.state.1
{
id=*
state=On
level=100/100
}
You'll note that after the : in the target address is blank whereas its should show hall.light as was entered in the variables field.
Also - just a couple of comments - I wonder if you could (for the time being) wildcard the target instance of HomeSeer - ie the 'Lightning' bit above in the target address in my example - this is because my HomeSeer application is not on the same machine as XLobby (xAP works transparently across the network it doesn't matter where the various applications sit)
... and just as a thought I would steer away from the ABCD UID digits as it is quite a common 'favourite' choice - choose some really obscure number for here. BTW I have registered Hiller as an official xAP developer ID for you
... you may find sending level as a % is a more natural and universal way to set levels although /100 obviously achieves the same thing.
I was also thinking that if you make the target address a variable too ie the mi4.homeseer.*.* then you would be able to send BSC messages to anything including for example directly to the xAP X10 connector - the BSC13 version that is in beta. Then people could use this for X10 without having to own HomeSeer even - and it would work with any xAP BSC capable conduit.
The response times of xAP are super fast - you should see no appreciable delays introduced by xAP as it's is Ethernet speed UDP - X10 is slow to react because of the way it works but when you connect to a speedy device like say C-Bus lighting or a relay I/O board it's effectively instant.
Kevin