ronv42
November 26, 2022, 12:19pm
9
There are multiple drivers here on Hubitat, one that makes a API call to the cloud services, another that uses the websocket interface, and then a couple that uses the local UDP broadcast to to WeeWx and then WeeWx pushes the updates to Hubitat
The API Driver:
This driver polls the WeatherFlow API for information that your weather station or another has provided. The WeatherFlow API driver is REQUIRED and is the parent device (if both are used), and the WeatherSensorChild is OPTIONAL and is a child device driver. Now available within the Hubitat Package Manager (HPM).
REQUIRED: WeatherFlow API driver to poll the WeatherFlow API.
OPTIONAL: WeatherSensorChild driver is optional overall but required for child devices to work if you want to use the Enab…
The WebSocket
The WeeWx:
Hello,
I've released a package that provides a direct (local) data connection between WeeWX and Hubitat. The direct connection allows for efficient real-time access to data from your weather station, with no internet connection required.
Depending upon your weather station hardware, the Hubitat will provide access to over 20 attributes from your station:
temperature
humidity
windSpeed
windDirection
windGustSpeed
windGustDirection
apptemp
heatindex
humidex
windchill
rain
rainRate
hourRain
day…
I was up late last night cleaning up local access to the MQTT driver of a WeeWx implementation that is hosting my WeatherFlow Tempest weather station. It's very basic, has some error handling to reconnect to MQTT if the connection is dropped. Also just for better understanding there are 3 json payload types that WeeWx puts on the weather/loop topic:
1 Minute Observations
3 Second wind and rain
5 Minute WeeWx archive observation
To keep updates to a minimum I filter for the 1 minute observati…
