This is a continuation of the thread started in the General Discussion area https://forums.homeseer.com/forum/ho...plugin-for-hs3 to discuss the mcsMQTT implementation of the integration.
At this point with version 6.1.0.0 of HS4 plugin, a full, albeit initial implementation. The delta files from the version 6 mcsMQTT plugin available from the HS4 Updater is at http://mcsSprinklers.com/MCSMQTTHS4_6100.zip. Unzip all files into the \bin\mcsMQTT subfolder of HS. The HS version will not show a change, but the MQTT Page, General tab, top header will show the version of the .dll that is being run. There is one .html file and it should be placed in \html\mcsMQTT subfolder.
The setup interface is on the Local Page, HVAC Tab of mcsMQTT plugin. This tab was previously labeled Intesis/Daikin, but has been renamed to handle a third type of local HVAC/Thermostat integration. The new label is in Local.html, but it only cosmetic.
When the plugin starts it will do a SSDP request to find Venstar thermostats on the network. Those found will be used to populate the Local Page, HVAC Tab, Venstar Table. The discovery can also be done using the button on the Local Page, HVAC tab. If none are found then it is still possible to manually enter the IP on this table. The other entry that is need on the this page's setup is the polling rate to refresh the status of information from the thermostat. It defaults to 0 (disabled). Reasonable values such as 60000 or every minute or larger should be used.
mcsMQTT will poll four endpoints of each thermostat. Data returned from /info, /sensors and /alerts will result in the Association Table of the MQTT Page, Association Tab showing the decoded data. It will also result in a HS Device being created for each Thermostat and the Features setup for each property advertised. The /runtimes will also be polled, but no HS Features created automatically. If one desires to see any of the runtimes in HS then use the "a" column checkbox from the Association table of the MQTT Page.
Controls are setup for the Features that can be controlled. When commanded via HS Devices page, Event Action or Script the request will be delivered to the Venstar thermostat. It will first be checked for compliance on heat and cool setpoints and delta constraint for these. HS Log will reflect out of bounds requests. The last received cool and/or heat setpoints will be used to satisfy the requirement that these always be provided in a request along with the other property that is being commanded.
Alerts are itemized and shown as either Active or Inactive. Sensors are shown with temperature measurement and humidity measurement if available. If the humidity reported is not zero and additional humidity properties are available such as setpoint then they will be included as HS Features.
I have not yet updated mcsMQTT.pdf or the HS3 plugin. I would prefer to get some feedback on the HS4 implementation before taking this step to minimize rework.
At this point with version 6.1.0.0 of HS4 plugin, a full, albeit initial implementation. The delta files from the version 6 mcsMQTT plugin available from the HS4 Updater is at http://mcsSprinklers.com/MCSMQTTHS4_6100.zip. Unzip all files into the \bin\mcsMQTT subfolder of HS. The HS version will not show a change, but the MQTT Page, General tab, top header will show the version of the .dll that is being run. There is one .html file and it should be placed in \html\mcsMQTT subfolder.
The setup interface is on the Local Page, HVAC Tab of mcsMQTT plugin. This tab was previously labeled Intesis/Daikin, but has been renamed to handle a third type of local HVAC/Thermostat integration. The new label is in Local.html, but it only cosmetic.
When the plugin starts it will do a SSDP request to find Venstar thermostats on the network. Those found will be used to populate the Local Page, HVAC Tab, Venstar Table. The discovery can also be done using the button on the Local Page, HVAC tab. If none are found then it is still possible to manually enter the IP on this table. The other entry that is need on the this page's setup is the polling rate to refresh the status of information from the thermostat. It defaults to 0 (disabled). Reasonable values such as 60000 or every minute or larger should be used.
mcsMQTT will poll four endpoints of each thermostat. Data returned from /info, /sensors and /alerts will result in the Association Table of the MQTT Page, Association Tab showing the decoded data. It will also result in a HS Device being created for each Thermostat and the Features setup for each property advertised. The /runtimes will also be polled, but no HS Features created automatically. If one desires to see any of the runtimes in HS then use the "a" column checkbox from the Association table of the MQTT Page.
Controls are setup for the Features that can be controlled. When commanded via HS Devices page, Event Action or Script the request will be delivered to the Venstar thermostat. It will first be checked for compliance on heat and cool setpoints and delta constraint for these. HS Log will reflect out of bounds requests. The last received cool and/or heat setpoints will be used to satisfy the requirement that these always be provided in a request along with the other property that is being commanded.
Alerts are itemized and shown as either Active or Inactive. Sensors are shown with temperature measurement and humidity measurement if available. If the humidity reported is not zero and additional humidity properties are available such as setpoint then they will be included as HS Features.
I have not yet updated mcsMQTT.pdf or the HS3 plugin. I would prefer to get some feedback on the HS4 implementation before taking this step to minimize rework.
Attached Files
Comment