New "Official" Weatherflow Ingegration

Feature Requests
1

Thank you very much for this integration.

There is a problem when you are running under Docker without “host” networking. The integration only searches direct network connections (in this case the Docker network) and can’t find the Weatherflow hub - it throws and error and the configuration fails. It would be really nice if, instead, it asked for the IP address or hostname of the hub to finish the configuration.

For now I’ve fixed it on my install by forcing HA to appear directly on the local LAN, but for security reasons this is not ideal.

Also - any plans to do an integration for Weatherflow Forecast data? With all the changes in how forecast is handled the “unofficial” mqtt integration needs a good deal of work.

2

How do you connect to anything without a network?

In the YouTube release party they did mention that the Weatherflow integration will receive more features in a future update. What features?

Not sure, they did not say.

1 Like
3

Network is super simple!

You do have a network, but it is a “private” network local to the docker host (provided by Docker networking). For HTTPS access there is an instance of Traefik on the same host to proxy the traffic. HA can get to anything if it knows the IP address - Docker networking takes care of the NAT & routing. But HA itself is reasonably secure.

This does break most HA discovery, but as a personal preference I find discovery to be generally more trouble than help. And I don’t mind hand-typing addresses (and managing static DHCP settings so that they don’t change).

My ask isn’t that you change anything about how the Integration discovers the Weatherflow hub. Just that when it can’t find one instead of just a hard error you ask for the required information that it didn’t find (i.e., the Hub address or whatever is needed).

4

I’ve moved this to feature requests then. Don’t forget to vote for your own request.

5

My impression (as the developer of the WeatherFlow UDP station driver for WeeWX) is that the new integration also listens for UDP broadcasts on the local IP subnet. These packets cannot cross router/subnet boundaries. Prompting for the IP address or hostname of the Hub is pointless, since it does not accept direct connections…just emits UDP broadcasts every time that it receives a sensor reading.

WeatherFlow offers a few different cloud-based API options that are more suitable to HA deployments that cannot receive the UDP broadcasts, and adding support for those is a feature request that can actually be implemented…

6

Using HA in docker without host networking is not supported.

7

My HA Core is running in host mode, but I get the following error:
image

image

I previously had the HACS integration running successfully, then migrated to the new/official one. Upon first install, it seemed to load, then I noticed that HA was reporting all entities as unavailable, so I removed the integration to reinstall, and now this is all I get. I’m running the latest HA Core 2023.10.3.

Any help is appreciated. Thanks!

8

I figured it out.
After some research, I discovered that the updated weatherflow uses UDP to communicate and my tempest was on my IoT network and therefore not routable to communicate. After moving the weather station to the same LAN as my Home Assistant, it connected immediately.

1 Like
9

I’m having a problem with the New WeatherFlow integration not reporting the precipitation. the precipitation on 2 stations are showing “unavailable”. Sensors are showing correctly just no data.
Thanks MikeyM