David ( @dsj ), For accessing data, there is: REST API. Websocket for structured remote data. UDP for structured local data. Why is there no MQTT transport available to developers?

That is good to know! I will try this.

Thank you. I now have better understanding on how to better use WU and also how I can get MQTT in the meantime, as I already run HomeAssistant on Pi.

Another new user looking for MQTT. All my HA system uses it. Lots of other alternatives but MQTT would be way preferable. Can bridge to your server if that’s an easier option but would prefer it all local.

Yes… if already able to send MQTT to your servers, why not allow us to change that setting on the HUB, so we can keep data completely private, or for me, I would just like the ability to send to a second local MQTT server.

Hi and BIG thanks to you :+1: With the help of your UDP listener I am now able to receive MQTT in my FIBARO Homecenter and finally get weather data without a working internet connection!! In case someone is interested how to receive these messages in Fibaro Homecenter, have a look at here at 10der…

I would like to also ask that we be able to configure the hub to publish the data via a private MQTT broker. With the network being WiFi only, there is too much chance of a flaky WiFi connection causing lost UDP broadcasts. If the hub could be connected to a network cable, it might not be so bad.

Any update on the topic? MQTT would make things a lot easier in terms of local integration with things like Home Assistant. Can we please have this enabled in the hub? I already own a few stations and things are getting more complicated…

Sorry, no update on MQTT. Curious, why do the REST & WS interfaces (with UDP fallback if the network goes down) not work for Home Assistant? Note you can also get forecast and other enhanced data via the remote API (REST & WS) so there is real value in using that as your primary data source.

First of all some of my stations are in remote areas where Internet connection is only a (good) dream. These locations run on solar only and i use home assistant to run the place - all fully offline and localized. Second, i have to maintain a custom integration so i can ingest data from UDP to HA. E…

Thanks for the explanation. It’s true that MQTT (as a higher level protocol) is “easier” to work with than UDP. For the same reason, MQTT adds a lot of overhead to the code running on the Hub. It’s not as simple as “turning it on” unfortunately.

Why no MQTT transport for developers?

Developers

bjarne May 29, 2021, 5:31am 59

Done. There is now a specific post for this integration here: WeatherFlow2MQTT for Home Assistant

Topic		Replies	Views
WeatherFlow2MQTT for Home Assistant Third-Party Integrations tempest	136	17169	October 11, 2025
WeatherFlow UDP listener and MQTT/InfluxDB publisher utility Third-Party Integrations udp , mqtt	74	9964	February 9, 2021
Lower Tempest Bandwidth Capability (either always or at least by API configuration) Feature Requests tempest	27	779	September 8, 2023
Api update intervals Developers	40	3090	September 18, 2018
Will the hub work without Internet? Tempest Owners	42	6069	April 30, 2018

Why no MQTT transport for developers?

Related topics