Hi!
Just wondering what the benefits of the API is over the customized server.
Out of the box you're able to forward the incoming data with custom server to
ONE target only.
The software cannot determine when it receives this data because the GW1000 sends it at a static interval - limited to 16sec minimal (by default).
At least for forwarding to multiple destinations, there are various software solutions that make one forward several. Like weewx or FOSHKplugin. But you need another computer (Raspi) that runs 24/7 to enable this service.
With API many clients can poll the data whenever they want. Also in parallel and more frequently. Without optional hardware.
However, the data from the connected sensors does not come in faster. So you always get the sensor data of the last transmission of the sensor.
The disadvantage of the API solution is that only the GW1000 is supported.
With a custom server-based software connection, all weather stations that offer this feature can be connected.
So custom server is more generic.
As soon as there are more compatible devices, I am also considering supporting the API/direct connection via CMD_GW1000_LIVEDATA.
Until then, we are well supplied with the custom server.
Regards, Oliver
