I did not notice that the relay status was updated in the browser window based upon the Relay 01 message returned. This would also show up as the Last Change time update. I made some changes to this part.
xapmcsTemp0x will send xAP messages whenever something changes from the Temp08 such as temperature or relay status. xAP Message Viewer is an essential tool to see the xAP message traffic. It is not needed in normal operation, but is a useful tool to understand where issues may exist. The viewer was developed b Edward Pearson and can be downloaded from http://www.erspearson.com/xAP/xFx/viewer_main.htm
Another piece that is required is an xAP hub so that all xAP applications on the same computer will receive all the xAP traffic. There are several of these available. On most of my computers I run one developed in VB6 and runs in the tray much like xapmcsTemp0x. This one can be obtained from the xAP Llibrary on the HS Message Board. Edward also has versions available.
Both xapmcsTemp0x and the xAP Hub need to be started each time the computer is started. I do it with a .vbs script in my windows startup folder. Putting shortcuts the startup folder should also work. Initially when getting the system to work each application can be started manually. At this point both xapmcsTemp0x and one of the xAP hubs should be running on the same computer as well as xAP Message Viewer on any computer on the same LAN. I will assume all on the same for now.
The next step in the integration is to select which of the devices available in xapmcsTemp0x you want to make visible to HS3. This will likely be your Temperature sensors and your relays. Initially select just one of each for testing the process. Use a temperature sensor that tends to change or the temperature of it can be easily changed. You will check the "A"ccept checkbox for your two sensors and then Save the page on xapmcsTemp0x. At the bottom of the page there is a button to send the status of all devices. Click it and you should see an xAP messages in the Viewer for each of the two Accepted devices.
If success at this step then the next step is with mcsXap and HS3. If HS3 is on a different computer then an xAP hub also needs to be running on the one with HS3. I will also assume mcsXap plugin will be on the same computer as HS3.
mcsXap will show all xap messages that it sees. If you click the same button at the bottom of the xapmcsTemp0x page as before followed by viewing the mcsXap browser page from HS3 menu then you should see rows with the two devices. There may be other rows as well for heartbeats or other xAP messages. If you do see them they are not yet visible to HS3. mcsXap firewalls then until mcsXap "A"ccept checkbox is clicked. When you click the "A"ccept checbox then HS3 device will be created. For the relay ON/OFF control buttons will also be visible. Once you see the devices then for a third time click the button to force status to be reported on xapmcsTemp0x. The device status in HS3 on the device management page will reflect the same status that is showing in xapmcsTemp0x browser page. It will be automatically be updated everywhere as the Temp08 provides updates. You can also use HS3 to change the relay. In this case, especially, the command should be visible on the xAP Viewer. If there is a problem at any step of the integration process use xAP Message viewer to determine if the issue is with mcsXap or xapmcsTemp0x.
xapmcsTemp0x will send xAP messages whenever something changes from the Temp08 such as temperature or relay status. xAP Message Viewer is an essential tool to see the xAP message traffic. It is not needed in normal operation, but is a useful tool to understand where issues may exist. The viewer was developed b Edward Pearson and can be downloaded from http://www.erspearson.com/xAP/xFx/viewer_main.htm
Another piece that is required is an xAP hub so that all xAP applications on the same computer will receive all the xAP traffic. There are several of these available. On most of my computers I run one developed in VB6 and runs in the tray much like xapmcsTemp0x. This one can be obtained from the xAP Llibrary on the HS Message Board. Edward also has versions available.
Both xapmcsTemp0x and the xAP Hub need to be started each time the computer is started. I do it with a .vbs script in my windows startup folder. Putting shortcuts the startup folder should also work. Initially when getting the system to work each application can be started manually. At this point both xapmcsTemp0x and one of the xAP hubs should be running on the same computer as well as xAP Message Viewer on any computer on the same LAN. I will assume all on the same for now.
The next step in the integration is to select which of the devices available in xapmcsTemp0x you want to make visible to HS3. This will likely be your Temperature sensors and your relays. Initially select just one of each for testing the process. Use a temperature sensor that tends to change or the temperature of it can be easily changed. You will check the "A"ccept checkbox for your two sensors and then Save the page on xapmcsTemp0x. At the bottom of the page there is a button to send the status of all devices. Click it and you should see an xAP messages in the Viewer for each of the two Accepted devices.
If success at this step then the next step is with mcsXap and HS3. If HS3 is on a different computer then an xAP hub also needs to be running on the one with HS3. I will also assume mcsXap plugin will be on the same computer as HS3.
mcsXap will show all xap messages that it sees. If you click the same button at the bottom of the xapmcsTemp0x page as before followed by viewing the mcsXap browser page from HS3 menu then you should see rows with the two devices. There may be other rows as well for heartbeats or other xAP messages. If you do see them they are not yet visible to HS3. mcsXap firewalls then until mcsXap "A"ccept checkbox is clicked. When you click the "A"ccept checbox then HS3 device will be created. For the relay ON/OFF control buttons will also be visible. Once you see the devices then for a third time click the button to force status to be reported on xapmcsTemp0x. The device status in HS3 on the device management page will reflect the same status that is showing in xapmcsTemp0x browser page. It will be automatically be updated everywhere as the Temp08 provides updates. You can also use HS3 to change the relay. In this case, especially, the command should be visible on the xAP Viewer. If there is a problem at any step of the integration process use xAP Message viewer to determine if the issue is with mcsXap or xapmcsTemp0x.
Comment