So I just started playing with Node-RED to build a custom front-end for my Homeseer3.
I have HS3 running on a Windows machine, and Node-RED currently on my linux desktop. Planning to move it to a RPi when completed.
It is all promising so far and I've made good progress, but was wondering what would be the best way to exchange data between both systems.
So far I'm using the JSON interface (http://HS3/JSON?request=getstatus/ge...icebylabel/etc). It works fine but the JSON payload is WAY bloated. It brings lots of unnecessary information. If I request status of all my 375 devices, the json data is 212kb. To make sure the status of switches and locks is up to date I should poll every few seconds which may be taxing for the machine running HS3. I haven't found a way of getting a JSON with just the status/value fields.
There is also the REST API (http://HS3/HomeSeer_REST_API.aspx?fu...2¶m2=value), which can provide just the value data without any extra content, but only for a single device so I'd have to make lots of separate calls to update the status of all devices on screen. This API also feels slower than the JSON one.
Are those the only/best options to exchange data between these two systems? I've seen mentions of things like MQTT plugins/brokers and not sure how they fit in the scheme of things. So far I have MS3 and Node-RED talking directly, and not sure if other apps/layers inbetween would help or make the system slower/heavier.
how are people handing these issues?
I have HS3 running on a Windows machine, and Node-RED currently on my linux desktop. Planning to move it to a RPi when completed.
It is all promising so far and I've made good progress, but was wondering what would be the best way to exchange data between both systems.
So far I'm using the JSON interface (http://HS3/JSON?request=getstatus/ge...icebylabel/etc). It works fine but the JSON payload is WAY bloated. It brings lots of unnecessary information. If I request status of all my 375 devices, the json data is 212kb. To make sure the status of switches and locks is up to date I should poll every few seconds which may be taxing for the machine running HS3. I haven't found a way of getting a JSON with just the status/value fields.
There is also the REST API (http://HS3/HomeSeer_REST_API.aspx?fu...2¶m2=value), which can provide just the value data without any extra content, but only for a single device so I'd have to make lots of separate calls to update the status of all devices on screen. This API also feels slower than the JSON one.
Are those the only/best options to exchange data between these two systems? I've seen mentions of things like MQTT plugins/brokers and not sure how they fit in the scheme of things. So far I have MS3 and Node-RED talking directly, and not sure if other apps/layers inbetween would help or make the system slower/heavier.
how are people handing these issues?
Comment