search

jjvdgeer / weatherflow-udp

WeatherFlow Personal Weather Station driver for weewx, via UDP broadcast packets
GNU General Public License v3.0
12 stars 2 forks source link

Feature request - REST only #3

Open Klarstein opened 2 years ago

Klarstein commented 2 years ago

Would it be easy to implement a REST-only mode? Since it’s already in there as a fallback it might not be too hard.

It could then be activated with the rest_enabled option. (False, Fallback, Always)

jjvdgeer commented 1 year ago

Sorry for not coming back to you earlier. It seems I'm not notified of activity in the issues of this project. Need to look into why that is...

Anyway, regarding your request, can you tell me a bit background why this feature would be useful?

Klarstein commented 1 year ago

Not a problem at all! The use case would be for people who like to use WeeWX but still want to profit from the processing Weatherflow does on the data.

MrPeteH commented 1 year ago

Interestingly, Weatherflow recommends avoiding the direct UDP interface except as a backup or off-grid solution. In the developer intro to their API's they say (emphasis mine):

Can I access data from the hardware locally? To ensure access to the best data, all third-party applications and integrations should use the remote interfaces (REST & Websockets) as their primary source for data, even if they are running on the same network as the local Tempest device. There is also a local UDP interface available for those applications that require completely off-grid applications, but this should only be used as a backup to the remote interfaces.

This driver doesn't make use of the Websocket API at this point... and that API only updates once a minute. Interesting alternatives!

I have not yet seen a document explaining what "processing" Weatherflow does to the raw data.

I'm certainly going to be interested in the near future: I collected enough data to submit a rainfall calibration request to them. Haven't done it yet. Have assumed they change the raw data reported from the device. If not, if it only changes what is seen from REST+Websocket, then I'll be wanting this as an alternative myself. More later...