I've been attracted by the xAP connector for HomeVision as a way to get Flags & Variables greater than 64 into HS... something the HV plugin cannot do. So I do downloaded it from www.ascentium.co.uk/xap/xaphomevision.html and gave it a try (I could not get the one from xapautomation.org to work).
Installation was a snap and after I started HV and then xapHV, I was met with a configuration screen. All straight forward. Viewer on my HS machine started seeing the traffic right away. Cool! Then things got ugly...
The xAP configuration pop-up boxes started comming up for HomeSeer. Click the Raw button, click the check box, and hit Create Devices. Only problem is, you only get one variable, flag, etc. per xAP configuration box. And before I knew it, I had over 500 more waiting! Can these be combined somehow?
So after an hour of clicking and waiting for the next xAP config box (computers are soooo slow), I finally finished and went to look at the result. Hey, I've only got tthe first 64 Flags... no variables and no I/O! A check of the HS Log shows the following:
7/7/2004 8:22:55 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:05 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:17 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:27 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:38 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
... and so on as far as the log will record.
I looked at the device code useage and sure enough, there is a clue as to what went wrong. Flag 35 generated a device at #99 and Flag 36 rolled into a new virtual device prefix at %1. Now things get interesting. Flag 37 created &1, 38 created &1, 39 (1, 40 )1, 41 *1, and so on until Flag 63 created @1 which must be the last virtual code available. Note that devices 2-99 are all unused on these codes. Is this a xAP device creation bug or a HomeSeer bug?
My last observation is that the HS GUI Status field is blank. I would have thought a Flag would show as a 1/0, Off/On, Set,Clear or something. In the Web view, however, they do show up as a On or Off complete with bulb icon.
-----------------
Update:
This morning I noticed the xAPstatus.info output.state 40 log messages above continuing to fill the HS Log. It must have been in an infinite loop. So I restarted HS and that seems to have stopped the log messages. I also noted that after restart, the HS GUI Status field correctly reflects the On/Off Flag state complete with icon. So my last observation is a non-issue.
Installation was a snap and after I started HV and then xapHV, I was met with a configuration screen. All straight forward. Viewer on my HS machine started seeing the traffic right away. Cool! Then things got ugly...
The xAP configuration pop-up boxes started comming up for HomeSeer. Click the Raw button, click the check box, and hit Create Devices. Only problem is, you only get one variable, flag, etc. per xAP configuration box. And before I knew it, I had over 500 more waiting! Can these be combined somehow?
So after an hour of clicking and waiting for the next xAP config box (computers are soooo slow), I finally finished and went to look at the result. Hey, I've only got tthe first 64 Flags... no variables and no I/O! A check of the HS Log shows the following:
7/7/2004 8:22:55 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:05 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:17 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:27 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
7/7/2004 8:23:38 PM~!~xAP Conduit~!~Creating new device scentium.hv-flags.baraboo:flag.64 xAPstatus.info output.state 40
... and so on as far as the log will record.
I looked at the device code useage and sure enough, there is a clue as to what went wrong. Flag 35 generated a device at #99 and Flag 36 rolled into a new virtual device prefix at %1. Now things get interesting. Flag 37 created &1, 38 created &1, 39 (1, 40 )1, 41 *1, and so on until Flag 63 created @1 which must be the last virtual code available. Note that devices 2-99 are all unused on these codes. Is this a xAP device creation bug or a HomeSeer bug?
My last observation is that the HS GUI Status field is blank. I would have thought a Flag would show as a 1/0, Off/On, Set,Clear or something. In the Web view, however, they do show up as a On or Off complete with bulb icon.
-----------------
Update:
This morning I noticed the xAPstatus.info output.state 40 log messages above continuing to fill the HS Log. It must have been in an infinite loop. So I restarted HS and that seems to have stopped the log messages. I also noted that after restart, the HS GUI Status field correctly reflects the On/Off Flag state complete with icon. So my last observation is a non-issue.
Comment