Whether I click on the “Add WeatherFlow to my” button or follow the directions for manual installation, I wind up getting the error message “failed to set up”.
When I click on Add Integration, I can select “WeatherFlow Weather”, which does not seem like the right thing because it has a red box (but there is no other option). I enter my station ID and my Personal API Token (which I refreshed by deleting the old one and creating a new one). I get a popup that declares “Success” and it says that it “created configuration” for my station. I click Finish. The entry on the Integrations page says WeatherFlow Weather “failed to set up”. Any idea what I am doing wrong?
I am running 2025.2.5 core, 2025.02.4 supervisor, 14.2 operating system, and 20250221.0 frontend.
Are you using the old/deprecated HACS version that connects to the WeatherFlow web API over the Internet, or the one with the same exact name that’s now included in HA and gets its data via broadcast UDP on the local IP subnet?
There is a new version of the old/deprecated HACS version titled “WeatherFlow Forecast” by the same person who wrote the deprecated version, and it does everything that the old version did plus retrieve forecast info:
http://homeassistant.hvtraffic.com:8123/hacs/repository/692701325
I just replaced the deprecated version on my HA deployment (that refused to load for a few months now) a minute ago with this new one, and will be going through the new sensor names and updating my automations accordingly…
I start at this page. There is a button labeled “Add WeatherFlow to my” which links to this page. It initiates a process that is exactly the same as what happens if I click the Add Integration button in Settings/Integrations. If there is some other version that I am supposed to install, how do I find it?
I think I figured out the problem. I had something installed in HACS. It must have been the deprecated version you referred to. After I removed it, I used the Add Integration button to start over. The installation succeeded. I can now see values for sensors in the tempest device.
1 Like
The old HACS version that worked over the web came first, and then HA added a built-in integration that grabs local UDP broadcast packets with the same exact integration package name (hence the confusion).
The HACS author deprecated that version because of the name conflict, and launched the new and improved “WeatherFlow Forecast” integration in HACS.
If you want local-only stuff and your WF Hub is on the same IP subnet as HA to receive the UDP broadcasts, the included HA integration is the choice. If you also want cloud observation data correction like rain check and WF’s forecast data, then the new HACS integration is a better option.
Up until last night, I had the old deprecated HACS cloud version installed. It hasn’t loaded without erroring out in months. Your post drove me to grab the new HACS cloud version, since thunderstorm season is approaching and one of my key automations needs to know when lightning is nearby.
I should throw in a disclaimer that I developed/published the WeeWX WeatherFlow-UDP station driver and have it running locally on another Raspberry Pi, which is why I am not concerned with local HA access to the station data and using the HACS cloud integration instead…
1 Like
Thank you for this very clear explanation. I do not need to know about lightning strikes, so I will stick with the local-only version, but if my situation changes I am glad to know how to proceed.
1 Like
Is anyone else having this issue still as well? I’m having trouble reconfiguring mine. I’ve had to completely delete the integration and start over, and now I’m getting the following error: “Error
Config flow could not be loaded: Unknown error”
I can’t find anything related to this in the logs either. Any help?
Which version, the old HACS/cloud, the new HACS/cloud, or the UDP/local integration that’s now included in HA?
Note that WeatherFlow did a big server-side update a week or so ago that messed up cloud integrations for several days. They also disabled a generic developer API auth token that some people were using instead of creating their own, which broke some other WF third-party station apps and integrations that used the cloud interface…
1 Like
I had been using the UDP local integration since it came out in November 2023. But, I realized what my issue was… I had been testing my Unifi firewall rules trying to move the Weatherflow hub to my IoT network, and forgot to move it back to the main LAN as my HA server after testing still didn’t work 
Switched back to my main LAN and worked perfectly fine
1 Like