core: 2024.1 Upgrade - Weatherflow Tempest Entities Unavailable
The problem
After upgrading to 2024.1 all Weatherflow tempest sensors show unavailable. The device is online and reporting publicly, is routable locally to and from HA, and HA was restarted.
What version of Home Assistant Core has the issue?
core-2024.1.0
What was the last working version of Home Assistant Core?
core-2023.12.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Weatherflow
Link to integration documentation on our website
https://www.home-assistant.io/integrations/weatherflow
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No errors observed in the logs.
Additional information
No response
About this issue
- Original URL
- State: open
- Created 6 months ago
- Comments: 32 (8 by maintainers)
Tonight I thought I would try deleting and re-adding my Tempest station.
After deleting the hub, I can no longer launch the integration. I receive the following error, even after a host reboot.
home-assistant_2024-01-06T06-05-20.257Z.log.zip
I was reading the following bug report: https://github.com/home-assistant/core/issues/101423
And read the new Weatherflow integration uses UDP to communicate with HA. Since my Tempest station sits on an IoT subnet, which is different than the subnet my HA uses, I checked my firewall rules to be sure UDP traffic was permitted. It was.
The above thread also mentions a UDP test one can run on the HA terminal to be sure UDP packets are reaching it from the Tempest. When I tested, I saw no signs of the packets. This led me to believe that the UDP broadcasts from the tempest were not traveling the two subnets.
Since my HA normally uses a wired ethernet connection I added my HA’s (normally disabled) wireless interface to the same IoT subnet as the Tempest. Voila! It works.
So HA and the Tempest must be on the same subnet for the new integration to work. That or you need to setup a UDP Broadcast Relay between the two subnets (I didn’t try this). Why the exact same setup worked in the December ‘23 release but not the January ‘24 one, I have no idea.
An easy way to tell if this is happening to you, try deleting your broken Weatherflow integration and re-adding it. If re-adding the integration fails with a message like “Config flow could not be loaded. Unknown Error” this means HA isn’t seeing the UDP broadcasts from the tempest. Hopefully the error message can be updated to something more meaningful.
I hope this helps.
Just upgraded to 2024.1.3 and still not working.
Removed integration, and now it throws an error attempting to add it back
”Config flow could not be loaded: Unknown error””
@natekspencer I was running 2023.12 before.
Just as another data point, I’m seeing the same error in my HA installation. Same symptoms: none of the WF entities are populating at all since I upgraded to 2024.1.2.
FWIW, I also lost one entity from my Crestron integration. This may or may not be related, but the entity has completely disappeared from HA, but is still showing in the Crestron App, still responds to the Crestron App, and Is still accessible from HomeKit via Homebridge.
LMK if there is any debug you need from me.