2024.1 Upgrade - Weatherflow Tempest Entities Unavailable

[mtwhitley]

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

[home-assistant[bot]]

Hey there @natekspencer, @jeeftor, mind taking a look at this issue as it has been labeled with an integration (weatherflow) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `weatherflow` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign weatherflow` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

weatherflow documentation weatherflow source _{^{(message by IssueLinks)}}

[jeeftor]

I'm still on 2023.11 ... @natekspencer - you able to take a look?

[natekspencer]

Mine is still working with the upgrade to 2024.1. There also weren't any notable updates in this release that should have caused issues. @mtwhitley has your sensor entered a power saving mode by chance? This could cause it to not have sent all the necessary information to HA on restart and may take some time before all sensors show up. Additionally, please enable debugging to see if there are any errors or logs to help with troubleshooting.

[miwhitle]

Thanks for helping me out. The Tempest is up and running, queryable via my home server and posting to WeatherUnderground, CWOP, and PWSWeather.com. I rebooted the station just now to see if that helped. Same result.

I've had no issues up till the upgrade. Strange. I enabled debugging, and took a look at the System > Logs but didn't see much related to Weatherflow. I'm attaching the log here in case that helps. Let me know if I should be looking for the debug logs in a different location since I don't do that regularly.

Thanks again. home-assistant_2024-01-04T20-38-25.893Z.log.zip

[jeeftor]

I see the errors ... we probably need the backing lib debugging turned on as well:

Template<template=({{((float(states('sensor.weatherflow_air_temperature')) * 9/5) + 32 | round(2))}}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1974, in forgiving_float
    return float(value)
           ^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 567, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2305, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/jinja2/environment.py", line 1301, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.11/site-packages/jinja2/sandbox.py", line 393, in call
    return __context.call(__obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1977, in forgiving_float
    raise_no_default("float", value)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1625, in raise_no_default
    raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{((float(states('sensor.weatherflow_air_temperature')) * 9/5) + 32 | round(2))}}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 693, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 569, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{((float(states('sensor.weatherflow_air_temperature')) * 9/5) + 32 | round(2))}}' but no default was specified
2024-01-04 02:08:37.931 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{((float(states('sensor.weatherflow_air_temperature')) * 9/5) + 32 | round(2))}}' but no default was specified') while processing template 'Template<template=({{((float(states('sensor.weatherflow_air_temperature')) * 9/5) + 32 | round(2))}}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.weatherflow_temp'
2024-01-04 02:08:37.936 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states.sensor.printables.attributes["downloadCount"] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 567, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)

(Do you know how to turn on debugging manually in config.yaml)

logger:
  default: info
  logs:
    pyweatherflowudp: debug

[natekspencer]

I see the errors ... we probably need the backing lib debugging turned on as well:

These errors aren't part of the integration, but rather for a template sensor. Enabling debug logging automatically enables the pyweatherflowudp logs as well. HA isn't seeing any traffic from the device however it seems.

[jeeftor]

what platform are you running on we can do the netcat test to see if there is UDP traffic at all?

[mtwhitley]

I’m running on a HA Yellow. Still need me to enable debug in the yaml?

[craigwitter]

It definitely seems slower at creating the sensors then previously, I also note that I'm missing data for a few that were previously there > Feels Like, Wind Direction Average, Wind Gust, Wind lull, and Wind Speed average. Log is below:

2024-01-05 12:14:05.739 DEBUG (MainThread) [pyweatherflowudp.client] Started listening 2024-01-05 12:14:06.587 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855762,"rssi":-60,"timestamp":1704474844,"reset_flags":"BOR,PIN,POR","seq":584982,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:14:06.587 DEBUG (MainThread) [homeassistant.components.weatherflow] Found a device: Hub 2024-01-05 12:14:06.587 DEBUG (MainThread) [homeassistant.components.weatherflow] Adding sensors for Hub 2024-01-05 12:14:16.590 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855772,"rssi":-61,"timestamp":1704474854,"reset_flags":"BOR,PIN,POR","seq":584983,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:14:26.591 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855782,"rssi":-60,"timestamp":1704474864,"reset_flags":"BOR,PIN,POR","seq":584984,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:14:36.593 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855792,"rssi":-60,"timestamp":1704474874,"reset_flags":"BOR,PIN,POR","seq":584985,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:14:46.597 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855802,"rssi":-61,"timestamp":1704474884,"reset_flags":"BOR,PIN,POR","seq":584986,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:14:56.596 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855812,"rssi":-61,"timestamp":1704474894,"reset_flags":"BOR,PIN,POR","seq":584987,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:06.600 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855822,"rssi":-62,"timestamp":1704474904,"reset_flags":"BOR,PIN,POR","seq":584988,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:16.601 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855832,"rssi":-61,"timestamp":1704474914,"reset_flags":"BOR,PIN,POR","seq":584989,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:26.608 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855842,"rssi":-62,"timestamp":1704474924,"reset_flags":"BOR,PIN,POR","seq":584990,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:36.605 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855852,"rssi":-61,"timestamp":1704474934,"reset_flags":"BOR,PIN,POR","seq":584991,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:46.608 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855862,"rssi":-62,"timestamp":1704474944,"reset_flags":"BOR,PIN,POR","seq":584992,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:15:56.608 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855872,"rssi":-61,"timestamp":1704474954,"reset_flags":"BOR,PIN,POR","seq":584993,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:06.609 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855882,"rssi":-62,"timestamp":1704474964,"reset_flags":"BOR,PIN,POR","seq":584994,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:16.670 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855892,"rssi":-63,"timestamp":1704474974,"reset_flags":"BOR,PIN,POR","seq":584995,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:26.620 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855902,"rssi":-61,"timestamp":1704474984,"reset_flags":"BOR,PIN,POR","seq":584996,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:36.617 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855912,"rssi":-61,"timestamp":1704474994,"reset_flags":"BOR,PIN,POR","seq":584997,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:46.618 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855922,"rssi":-61,"timestamp":1704475004,"reset_flags":"BOR,PIN,POR","seq":584998,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:16:56.644 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855932,"rssi":-61,"timestamp":1704475014,"reset_flags":"BOR,PIN,POR","seq":584999,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:06.639 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855942,"rssi":-60,"timestamp":1704475024,"reset_flags":"BOR,PIN,POR","seq":585000,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:16.631 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855952,"rssi":-60,"timestamp":1704475034,"reset_flags":"BOR,PIN,POR","seq":585001,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:26.633 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855962,"rssi":-61,"timestamp":1704475044,"reset_flags":"BOR,PIN,POR","seq":585002,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:33.349 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"ST-00007277","type":"device_status","hub_sn":"HB-00018767","timestamp":1704475051,"uptime":79970428,"voltage":2.360,"firmware_revision":156,"rssi":-76,"hub_rssi":-71,"sensor_status":8192,"debug":0}' 2024-01-05 12:17:33.349 DEBUG (MainThread) [homeassistant.components.weatherflow] Found a device: Tempest 2024-01-05 12:17:33.462 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"ST-00007277","type":"obs_st","hub_sn":"HB-00018767","obs":[[1704475051,null,null,null,null,300,999.90,-1.44,80.42,18903,0.51,158,0.000000,0,0,0,2.360,1]],"firmware_revision":156}' 2024-01-05 12:17:33.463 DEBUG (MainThread) [homeassistant.components.weatherflow] Adding sensors for Tempest 2024-01-05 12:17:35.319 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"ST-00007277","type":"rapid_wind","hub_sn":"HB-00018767","ob":[1704475053,0.76,153]}' 2024-01-05 12:17:36.631 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855972,"rssi":-61,"timestamp":1704475054,"reset_flags":"BOR,PIN,POR","seq":585003,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:46.633 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855982,"rssi":-62,"timestamp":1704475064,"reset_flags":"BOR,PIN,POR","seq":585004,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:17:56.635 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5855992,"rssi":-63,"timestamp":1704475074,"reset_flags":"BOR,PIN,POR","seq":585005,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:06.642 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856002,"rssi":-60,"timestamp":1704475084,"reset_flags":"BOR,PIN,POR","seq":585006,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:16.643 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856012,"rssi":-62,"timestamp":1704475094,"reset_flags":"BOR,PIN,POR","seq":585007,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:26.643 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856022,"rssi":-61,"timestamp":1704475104,"reset_flags":"BOR,PIN,POR","seq":585008,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:36.646 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856032,"rssi":-60,"timestamp":1704475114,"reset_flags":"BOR,PIN,POR","seq":585009,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:46.656 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856042,"rssi":-62,"timestamp":1704475124,"reset_flags":"BOR,PIN,POR","seq":585010,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:18:56.648 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856052,"rssi":-61,"timestamp":1704475134,"reset_flags":"BOR,PIN,POR","seq":585011,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:06.650 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856062,"rssi":-60,"timestamp":1704475144,"reset_flags":"BOR,PIN,POR","seq":585012,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:16.656 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856072,"rssi":-61,"timestamp":1704475154,"reset_flags":"BOR,PIN,POR","seq":585013,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:26.656 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856082,"rssi":-60,"timestamp":1704475164,"reset_flags":"BOR,PIN,POR","seq":585014,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:36.656 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856092,"rssi":-63,"timestamp":1704475174,"reset_flags":"BOR,PIN,POR","seq":585015,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:46.668 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856102,"rssi":-62,"timestamp":1704475184,"reset_flags":"BOR,PIN,POR","seq":585016,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:19:56.660 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856112,"rssi":-60,"timestamp":1704475194,"reset_flags":"BOR,PIN,POR","seq":585017,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:06.667 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856122,"rssi":-63,"timestamp":1704475204,"reset_flags":"BOR,PIN,POR","seq":585018,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:16.664 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856132,"rssi":-60,"timestamp":1704475214,"reset_flags":"BOR,PIN,POR","seq":585019,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:26.669 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856142,"rssi":-61,"timestamp":1704475224,"reset_flags":"BOR,PIN,POR","seq":585020,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:36.667 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856152,"rssi":-61,"timestamp":1704475234,"reset_flags":"BOR,PIN,POR","seq":585021,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:46.736 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856162,"rssi":-60,"timestamp":1704475244,"reset_flags":"BOR,PIN,POR","seq":585022,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}' 2024-01-05 12:20:56.681 DEBUG (MainThread) [pyweatherflowudp.client] Received message from 192.168.2.178:50222 - b'{"serial_number":"HB-00018767","type":"hub_status","firmware_revision":"171","uptime":5856172,"rssi":-60,"timestamp":1704475254,"reset_flags":"BOR,PIN,POR","seq":585023,"fs":[1,0,15675411,524288],"radio_stats":[22,1,0,3,31263],"mqtt_stats":[296,717]}'

[natekspencer]

@craigwitter your Tempest is in power mode 2 which explains why it takes longer to initialize some of the sensors since they don't report near as frequently. Once it gets an update from your device, those will populate.

[craigwitter]

Thanks for the quick response!

On Fri, Jan 5, 2024, 12:46 PM Nathan Spencer @.***> wrote:

@craigwitter https://github.com/craigwitter your Tempest is in power mode 2 https://help.weatherflow.com/hc/en-us/articles/360048877194-Solar-Power-Rechargeable-Battery which explains why it takes longer to initialize some of the sensors since they don't report near as frequently. Once it gets an update from your device, those will populate.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/107070#issuecomment-1879043918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDNYG6BC7YOURZ3J7NGGSLYNA36VAVCNFSM6AAAAABBMSOUQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGA2DGOJRHA . You are receiving this because you were mentioned.Message ID: @.***>

[miwhitle]

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

[kmichels]

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.

[paulmona]

I am also seeing this same behavior. Just upgraded to 2024.1.2 and broke my Weatherflow Tempest. All sensors show Unavailable. No other changes.

[natekspencer]

@kmichels / @paulmona, were you previously on 2023.12 releases? Or had you upgraded to 2024.1.0/1 before and all was working then?

[paulmona]

@natekspencer I was running 2023.12 before.

[Darkcitadel]

I am having the same issue. It started when I upgraded the OS to the latest version. I was on 2024.1.0 I believe it was. I upgrade to 2024.1.2 and that did not fix the issue.

I did notice that before I did the OS upgrade that the integration would stop updating but then would start up again hours later. So like the wind speed would get stuck at 5.1mph for a few hours and then would start updating again some time later.

Interesting, while typing this up it got an updated and is not showing data, but it took a good 5+ minutes.

[kmichels]

@kmichels / @paulmona, were you previously on 2023.12 releases? Or had you upgraded to 2024.1.0/1 before and all was working then?

It was working on 2024.1.1 for me

[kmichels]

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””

[mtnbiker717]

Also having the same issue. My integration has not updated values since December 26th, 2023.

[jeeftor]

Well I’ll take a look when I’m back in town and see if I can duplicate the issues Sent from my iPhoneOn Jan 14, 2024, at 5:53 PM, mtnbiker717 @.***> wrote: Also having the same issue. My integration has not updated values since December 26th, 2023.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mtnbiker717]

Well I’ll take a look when I’m back in town and see if I can duplicate the issues Sent from my iPhoneOn Jan 14, 2024, at 5:53 PM, mtnbiker717 @.> wrote: Also having the same issue. My integration has not updated values since December 26th, 2023. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

I ended up changing my WiFi network and I can pull the values. However, I now have 3 devices in the integration. The device that is the name of my device still has no values. One of the other two devices has no values either. The other one is names what appears to be the original device name, has all the values. Hope that helps.

[paoloGH]

Same issue here.... Core 2024.1.5 Supervisor 2023.12.1 Operating System 11.4

[cmittlesteadt]

Same here. Core 2024.1.5 Supervisor 2023.12.1 OS 11.4

[dotMorten]

Mine became unavailable January 13, which sounds like around when I updated HA

[mtwhitley]

@jeeftor @natekspencer Any updates that you can share?

[rhursig]

Same issue here. Station is correctly reporting to internet and local network. I have an AIR/SKY setup, so there are 4 devices in my integration/setup: the hub device, the AIR device, the SKY device, and the "AIR & SKY" device that I've been using in all of my automations and dashboards. The individual AIR device and SKY device seem unaffected and are being updated with sensor data just fine, but the "AIR & SKY" device has "unavailable" sensors across the board. The usual power cycling of equipment and full rebooting of Home Assistant has been performed.

Integration was working until upgrade of the core to 2024.1.6 yesterday. • Core 2024.1.6 • Supervisor 2023.12.1 • Operating System 11.4

Debug Log

EDIT: Reverting to 2023.12.3 did not correct the problem (this was not a reversion from backup so could point to some persistent issue after an initial failure independent of the core).

[rhursig]

Same issue here. Station is correctly reporting to internet and local network. I have an AIR/SKY setup, so there are 4 devices in my integration/setup: the hub device, the AIR device, the SKY device, and the "AIR & SKY" device that I've been using in all of my automations and dashboards. The individual AIR device and SKY device seem unaffected and are being updated with sensor data just fine, but the "AIR & SKY" device has "unavailable" sensors across the board. The usual power cycling of equipment and full rebooting of Home Assistant has been performed.

Integration was working until upgrade of the core to 2024.1.6 yesterday. • Core 2024.1.6 • Supervisor 2023.12.1 • Operating System 11.4

Debug Log

EDIT: Reverting to 2023.12.3 did not correct the problem (this was not a reversion from backup so could point to some persistent issue after an initial failure independent of the core). Well I feel silly, but it looks like the previous set of entities for the combined AIR + SKY sensor were deprecated, leaving a different subset of sensors and sensor names than the predecessor. I got rid of the HACS Weatherflow (UDP) integration long ago, so I probably missed some communication on recent updates. I was able to reclaim most of my previous sensors, by renaming to match (preserving history and front-end content) and creating a few template sensors. Maybe this comment will help others in this sameboat.

[mtwhitley]

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.

[Aipoc76]

Not sure if this offers any help, but Uptime and Signal Strength entities were disabled by default. I enabled them for the Station, and everything all entities then became unresponsive / unavailable. Tried restarting, no change. Disabled them, and everything went back to normal (working as intended).

[dotMorten]

@Aipoc76 how did you enable these? I looked everywhere in the app and home assistant but don't see any settings like this.

[Aipoc76]

@Aipoc76 how did you enable these? I looked everywhere in the app and home assistant but don't see any settings like this.

Settings > Devices & Services > Weatherflow

Click the 2 Devices.

Then select the one that says HUB

Under Diagnostics will be 2 Entities not shown.

Click 1, then click on the cog (settings) and enable it..

Then do the same for the other device.

[cftechwiz]

Same issue after updating... I deleted and tried to re-add the integration to the HUB and I get this:

Unable to discover Tempest WeatherFlow devices. Click submit to try again.

UDP Discovery Error. - These are on the same network which have has no changes

[jeeftor]

Can you try the cloud / forecast tempest integration? See if that one works at least?

[cftechwiz]

Can you try the cloud / forecast tempest integration? See if that one works at least?

That one works fine...

[JevVan]

I too am experiencing the same problem with my integration. I also have multiple vlans with the Home Assistant instance on a separate vlan from the tempest. Have you figured out what/if any ports need to be broadcast for it to work?

[jeeftor]

Honestly I use the cloud stuff personally. You need udp traffic to flow correctly to ha.

https://weatherflow.github.io/Tempest/api/udp/v171/

Here's the udp docs.

[jeeftor]

But also don't vlan- so I have both running side by side.

[mtwhitley]

I too am experiencing the same problem with my integration. I also have multiple vlans with the Home Assistant instance on a separate vlan from the tempest. Have you figured out what/if any ports need to be broadcast for it to work?

See my last post above, (if you missed it). Simply permitting traffic to flow between subnets will not suffice, you’ll likely need a broadcast relay that sits between subnets to retransmit packets to your HA subnet. This is not a common setup since subnets are designed to isolate broadcast traffic among other things.

I’d recommend trying to add a secondary HA network interface on your WF vlan if at all possible.

[kjsanders86]

Same here with latest update. Will the integration be updated...fixed?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.