mcsMQTT 5.19.1.0 has been submitted to HST so should be available soon through the Update channel. It is also available at http://mcsSprinklers.com/HSPI_mcsMQTT_5_19_1_0.zip for HS4 and http://mcsSprinklers.com/mcsMQTT_5_19_1_0.zip for HS3. The updater override process can be used to install the zip file. One description of it is at first post of https://forums.homeseer.com/forum/hs...es-to-influxdb
There is much change from the prior release 5.17.3.2. It has a combination of usability improvements and new features that have been primary a result of user feedback.
While there has been no 'breaking' change since 5.17.3.2 there has been a change of the feature added in 5.18.0.0 that allows a user to poll data from a URL. The pseudo-topic has been changed from JSON/ to URL/ in 5.19.1.0. This was done because additional protocols have been added beyond the HTTP GET protocol that was introduced in 5.18.0.0. Now a user can select from GET, POST, UDP, WebHook/WebSocket and generic TCP listener. This allows a user to interact with a device (or web site) that supports some type of API. Internally mcsMQTT views data as JSON. If the provider sends it in XML or HTTP querystring formats then mcsMQTT will convert it automatically to JSON so it looks to the user the same as if it came via MQTT. Depending upon the protocol it is command/response or listen. Hooks have been added for oAuth2, but have not yet been enabled with this release. What has been added are Expression functions to generate TCP/HTTP headers for Basic Authorization and MD5 Hash that use Base64 encoding.
YoLink devices have been added since 5.17.0.0. These devices fit the nice for sensors and actuators that are located a distance from the HS install. They use LoRa protocol between the device and its base station to achieve the long range. Conceptually a range of miles can be achieved with LoRa, but my experience in a wooded environment is that 500-1000 ft is what one should expect to provide reliable operation. YoLink uses 928 MHz so if you have line-of-sight without obstruction the effective distance should be much better. Unfortunately, YoLink only provides API for integration with their cloud server so its application should most likely be "nice to have" and not "mission critical".
The GW1000 interface was also added for Ecowitt and Ambient products. Thank jim@beersman.com for all the engineering associated with this addition. I was only the coding monkey on this effort to integrate with mcsMQTT based upon the code that he had already developed. (p.s. Jim was also very active in the YoLink integration) The GW1000 is a RF to WiFi gateway for a set of good-value sensors from Ecowitt and Ambient. They provide the gateway for 915Mhz, 868Mhz and 433Mhz sensors. The frequency is dependent upon location of use so be careful if you use this device that your sensors are compatible. The separation by region is an attempt to minimize the interference in the free ISM band. RF is good for distance, but receivers get confused when two widgets transmit at the same frequency at the same time.
The Updater release notes and the change log at https://forums.homeseer.com/forum/li...mcsmqtt-plugin detail other advances of mcsMQTT.
There is much change from the prior release 5.17.3.2. It has a combination of usability improvements and new features that have been primary a result of user feedback.
While there has been no 'breaking' change since 5.17.3.2 there has been a change of the feature added in 5.18.0.0 that allows a user to poll data from a URL. The pseudo-topic has been changed from JSON/ to URL/ in 5.19.1.0. This was done because additional protocols have been added beyond the HTTP GET protocol that was introduced in 5.18.0.0. Now a user can select from GET, POST, UDP, WebHook/WebSocket and generic TCP listener. This allows a user to interact with a device (or web site) that supports some type of API. Internally mcsMQTT views data as JSON. If the provider sends it in XML or HTTP querystring formats then mcsMQTT will convert it automatically to JSON so it looks to the user the same as if it came via MQTT. Depending upon the protocol it is command/response or listen. Hooks have been added for oAuth2, but have not yet been enabled with this release. What has been added are Expression functions to generate TCP/HTTP headers for Basic Authorization and MD5 Hash that use Base64 encoding.
YoLink devices have been added since 5.17.0.0. These devices fit the nice for sensors and actuators that are located a distance from the HS install. They use LoRa protocol between the device and its base station to achieve the long range. Conceptually a range of miles can be achieved with LoRa, but my experience in a wooded environment is that 500-1000 ft is what one should expect to provide reliable operation. YoLink uses 928 MHz so if you have line-of-sight without obstruction the effective distance should be much better. Unfortunately, YoLink only provides API for integration with their cloud server so its application should most likely be "nice to have" and not "mission critical".
The GW1000 interface was also added for Ecowitt and Ambient products. Thank jim@beersman.com for all the engineering associated with this addition. I was only the coding monkey on this effort to integrate with mcsMQTT based upon the code that he had already developed. (p.s. Jim was also very active in the YoLink integration) The GW1000 is a RF to WiFi gateway for a set of good-value sensors from Ecowitt and Ambient. They provide the gateway for 915Mhz, 868Mhz and 433Mhz sensors. The frequency is dependent upon location of use so be careful if you use this device that your sensors are compatible. The separation by region is an attempt to minimize the interference in the free ISM band. RF is good for distance, but receivers get confused when two widgets transmit at the same frequency at the same time.
The Updater release notes and the change log at https://forums.homeseer.com/forum/li...mcsmqtt-plugin detail other advances of mcsMQTT.
Comment