Weatherflow API seems to have broken the integration #81

robchandhok · 2023-08-28T20:27:32Z

See also #80 I think.

Home Assistant 2023.8.4
Supervisor 2023.08.3
Operating System 10.5
Frontend 20230802.1 - latest

I just stopped being able to read my Tempest. When you reload, the log reports:

2023-08-28 12:49:19.004 WARNING (MainThread) [homeassistant.config_entries] Config entry 'TheView' for weatherflow integration not ready yet: Error while retreiving forecast data: Error occured processing forecast data. Error message: 'sea_level_pressure'; Retrying in background

I turned on debugging and see this pattern:

2023-08-28 12:50:38.459 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.218 seconds (success: True)
2023-08-28 12:50:38.878 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.419 seconds (success: False)
2023-08-28 12:51:59.649 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.195 seconds (success: True)
2023-08-28 12:52:00.141 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.492 seconds (success: False)

My guess is that something changed in the API return values?

I am quite puzzled. My parents instance of HA (not up to 2023.8.4) still works with their tempest.

I have tried:

deleting and re-adding the integration
redownloading via HACS
making a new access token and using it
accessing the API via their URLs and my token, and that worked

The text was updated successfully, but these errors were encountered:

eelcovb · 2023-08-28T20:29:51Z

I have exactly the same versions / issue:

in my log:

2023-08-28 16:27:52.329 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.102 seconds (success: True)
2023-08-28 16:27:52.642 DEBUG (MainThread) [custom_components.weatherflow] Finished fetching weatherflow data in 0.313 seconds (success: False)
2023-08-28 16:27:52.642 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Orlando-TerraceNET' for weatherflow integration not ready yet: Error while retreiving forecast data: Error occured processing forecast data. Error message: 'sea_level_pressure'; Retrying in background

Tried the exact same things, rebooted everything multiple times.

jeremyhamm · 2023-08-28T21:44:44Z

My integration is also broken with WeatherFlow

Logs:
Logger: homeassistant.config_entries
Source: config_entries.py:430
First occurred: 2:51:24 PM (1 occurrences)
Last logged: 2:51:24 PM

Config entry '******' for weatherflow integration not ready yet: Error while retreiving forecast data: Error occured processing forecast data. Error message: 'sea_level_pressure'; Retrying in background

jeremyhamm · 2023-08-28T22:50:56Z

@robchandhok Any idea what version of HA your Parents are running. I reverted to an older backup (2023.8.3) and it was still broken.

jgosnell56 · 2023-08-28T23:10:57Z

I am on 2023.8.4 of HA and seeing this same error. HA log shows:
2023-08-28 16:42:50.552 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Stratford' for weatherflow integration not ready yet: Error while retreiving forecast data: Error occured processing forecast data. Error message: 'sea_level_pressure'; Retrying in background

API from my weather station still reports sea_level_pressure so not quite sure why we are suddenly seeing this error. Excerpt from the API webpage of my weather station:
{ "elevation": 189.06375122070312, "is_public": true, "latitude": xxxxx, "longitude": xxxxx, "obs": [ { "air_density": 1.15988, "air_temperature": 23.8, "barometric_pressure": 988.7, "brightness": 5308, "delta_t": 0.5, "dew_point": 23.1, "feels_like": 23.8, "heat_index": 23.8, "lightning_strike_count": 1, "lightning_strike_count_last_1hr": 178, "lightning_strike_count_last_3hr": 223, "lightning_strike_last_distance": 10, "lightning_strike_last_epoch": 1693264013, "precip": 0.807931, "precip_accum_last_1hr": 14.031167, "precip_accum_local_day": 19.700306, "precip_accum_local_day_final": 20.045038, "precip_accum_local_yesterday": 0, "precip_accum_local_yesterday_final": 0, "precip_analysis_type_yesterday": 0, "precip_minutes_local_day": 90, "precip_minutes_local_yesterday": 0, "precip_minutes_local_yesterday_final": 0, "pressure_trend": "rising", "relative_humidity": 96, "sea_level_pressure": 1011.4, "solar_radiation": 44, "station_pressure": 988.7, "timestamp": 1693264013, "uv": 0.47, "wet_bulb_globe_temperature": 23.7, "wet_bulb_temperature": 23.3, "wind_avg": 0.2, "wind_chill": 23.8, "wind_direction": 332, "wind_gust": 0.7, "wind_lull": 0 }

jeremyhamm · 2023-08-28T23:18:21Z

@jgosnell56 Not sure if it matters to you but you may want to hide your exact location.

ragd011 · 2023-08-29T00:50:05Z

I can confirm same issue started earlier today. As luck would have it, we lost power at 3:40 ET and when it came back, this integration is no longer working. Completely updated system.

Logger: homeassistant.config_entries
Source: config_entries.py:1290
First occurred: 8:39:58 PM (1 occurrences)
Last logged: 8:39:58 PM

Config entry 'The House' for weatherflow integration not ready yet: Error while retreiving forecast data: Error occured processing forecast data. Error message: 'sea_level_pressure'; Retrying in background

Mine started work today 8/29 at 10am without doing anything???

eelcovb · 2023-08-29T00:54:03Z

I had exactly the same power outage "luck".. Checked my whole setup 6 times, changed the DB, threw away existing sensor data, just to find a fix..

gitBrave-hub · 2023-08-29T02:09:54Z

it is broken for me too, as described above by robchandhok

idaband · 2023-08-29T02:18:43Z

well time to dig into this code....uggg fun times LOL. I already commented out some stuff...with no luck.

idaband · 2023-08-29T02:29:53Z

well time to dig into this code....uggg fun times LOL. I already commented out some stuff...with no luck.

so looking at the straight up forcast api data that comes back... i don't see an issue with that json.... which means...something is getting messed up as its reads the data back is my guess, which could be the python library maybe?

  "current_conditions": {
    "air_density": 1.2,
    "air_temperature": 13,
    "brightness": 0,
    "conditions": "Clear",
    "delta_t": 1,
    "dew_point": 12,
    "feels_like": 13,
    "icon": "clear-night",
    "is_precip_local_day_rain_check": true,
    "is_precip_local_yesterday_rain_check": true,
    "lightning_strike_count_last_1hr": 0,
    "lightning_strike_count_last_3hr": 0,
    "lightning_strike_last_distance": 41,
    "lightning_strike_last_distance_msg": "39 - 43 km",
    "lightning_strike_last_epoch": 1692936462,
    "precip_accum_local_day": 0,
    "precip_accum_local_yesterday": 0,
    "precip_minutes_local_day": 0,
    "precip_minutes_local_yesterday": 0,
    "pressure_trend": "rising",
    "relative_humidity": 93,
    "sea_level_pressure": 1016.6,
    "solar_radiation": 0,
    "station_pressure": 983,
    "time": 1693275901,
    "uv": 0,
    "wet_bulb_globe_temperature": 16,
    "wet_bulb_temperature": 12,
    "wind_avg": 0,
    "wind_direction": 0,
    "wind_direction_cardinal": "N",
    "wind_gust": 0
  },

robchandhok · 2023-08-29T02:30:41Z

@robchandhok Any idea what version of HA your Parents are running. I reverted to an older backup (2023.8.3) and it was still broken.

2023.8.3

I am now convinced it's a bug in the config/init flow. So restart breaks it. Running instances are fine. Can't see it though.

robchandhok · 2023-08-29T03:29:58Z

Annnnnndddd….. it’s back working. There still might be an opportunity to catch this at init (defensive programming) but I don’t hav3 an example to test against. Hopefully working for others.

ZeddicPrime · 2023-08-29T03:35:46Z

Just reloaded the plugin and it's still broken for me.

robchandhok · 2023-08-29T04:17:30Z

Hmmm. Race condition?

Yomegaman · 2023-08-29T05:19:11Z

My Weatherflow died today too. I've tried deleting & reinstalling (HA Supervisor) but get these error lines;

ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-7' coro=<WeatherFlowMqtt._update_forecast() done, defined at /usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/weatherflow_mqtt.py:755> exception=KeyError('sea_level_pressure')>
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/weatherflow_mqtt.py", line 760, in _update_forecast
if any(forecast := await self.forecast.update_forecast()):
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/forecast.py", line 187, in update_forecast
row["sea_level_pressure"]
KeyError: 'sea_level_pressure'

Then it sets up all my sensors with lines like this;
INFO:weatherflow2mqtt.weatherflow_mqtt:Setting up Tempest sensor: Status

Finally giving these errors;
Traceback (most recent call last):
File "/usr/local/bin/weatherflow2mqtt", line 33, in
sys.exit(load_entry_point('weatherflow2mqtt==3.1.6', 'console_scripts', 'weatherflow2mqtt')())
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/main.py", line 10, in main
File "/usr/local/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/weatherflow_mqtt.py", line 859, in main
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/weatherflow_mqtt.py", line 232, in run_time_based_updates
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/weatherflow_mqtt.py", line 760, in _update_forecast
File "/usr/local/lib/python3.10/site-packages/weatherflow2mqtt-3.1.6-py3.10.egg/weatherflow2mqtt/forecast.py", line 187, in update_forecast
KeyError: 'sea_level_pressure'

This has worked great for about a year - until today.

PLEASE HELP

UpDryTwist · 2023-08-29T13:00:56Z

I also started encountering this after a Home Assistant restart yesterday (using the cloud-based integration, not the local MQTT integration). Like the others, if I call the API myself, it appears to return well-formed JSON, with the appropriate "sea_level_pressure" key. I can't see any difference between that key and surrounding keys. I walked through the code (inspection, not debugger), and couldn't see anything anomalous in the code -- nothing that indicates why "sea_level_pressure" would hiccough and not any other value (if, say, it was indeed a race condition, I wouldn't expect us all to have the exact same experience). I think someone's going to have to look at this in a debugger (or with a lot of debugging statements turned on) to catch it. (If no one has a chance to do so, I may have some time this coming weekend, but certainly not before then.)

One hypothesis: different JSON is returned for some reason when we're all invoking it in the browser than when it's being invoked from within Home Assistant (although this doesn't really make sense, as it seems to happen both for folks using the cloud-based API and the local MQTT-based API). First thing to do, I think, would be to see if it reproduces when just calling https://github.com/briis/pyweatherflowrest from a command-line harness. Just a thought.

idaband · 2023-08-29T13:33:44Z

I haven't checked weatherflow community forum yet either... They might have info of changes Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: UpDryTwist ***@***.***> Sent: Tuesday, August 29, 2023 9:01:09 AM To: briis/hass-weatherflow ***@***.***> Cc: Green Eggs and Code ***@***.***>; Comment ***@***.***> Subject: Re: [briis/hass-weatherflow] Weatherflow API seems to have broken the integration (Issue #81) I also started encountering this after a Home Assistant restart yesterday (using the cloud-based integration, not the local MQTT integration). Like the others, if I call the API myself, it appears to return well-formed JSON, with the appropriate "sea_level_pressure" key. I can't see any difference between that key and surrounding keys. I walked through the code (inspection, not debugger), and couldn't see anything anomalous in the code -- nothing that indicates why "sea_level_pressure" would hiccough and not any other value (if, say, it was indeed a race condition, I wouldn't expect us all to have the exact same experience). I think someone's going to have to look at this in a debugger (or with a lot of debugging statements turned on) to catch it. (If no one has a chance to do so, I may have some time this coming weekend, but certainly not before then.) One hypothesis: different JSON is returned for some reason when we're all invoking it in the browser than when it's being invoked from within Home Assistant (although this doesn't really make sense, as it seems to happen both for folks using the cloud-based API and the local MQTT-based API). First thing to do, I think, would be to see if it reproduces when just calling https://github.com/briis/pyweatherflowrest from a command-line harness. Just a thought. — Reply to this email directly, view it on GitHub<#81 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADRHLMD7KOW7ZFUQ7I54FPLXXXRZLANCNFSM6AAAAAA4B52ZAQ>. You are receiving this because you commented.Message ID: ***@***.***>

robchandhok · 2023-08-29T15:30:43Z

Agree with @UpDryTwist . It's starting to look like the forecast API call is the culprit, it would be nice to still succeed with the station data in the face of that error (regardless of this specific error many of us are experiencing). I'm not a good enough python programmer to make that change tho. Just needs a wrap in an error catch.

JtwoA · 2023-08-29T17:02:14Z

@briis - any feedback?

briis · 2023-08-29T18:04:05Z

I have been away for a long time, so I did not monitor this for a while. I will have a look at it ASAP.

id628 · 2023-08-29T18:04:38Z

FYI, this might help. The other Home Assistant integration is having the same issue:
briis/hass-weatherflow2mqtt#234

A stated workaround there is:

Until there is a fix, a workaround is to remove STATION_ID and STATION_TOKEN from the config page for the weatherflow2mqtt add-on (this prevents the add-on from trying to get the forecast)

(I have not verified that this helps, since I'm running this one...)

(EDIT: I didn't realize both projects are by the same author! Cool!!!)

eelcovb · 2023-08-29T19:03:08Z

Haven't looked into it thoroughly, but my 2 cents:

Looking at a piece of forecast code, I noticed 'weather_daily' and 'weather_hourly' are used as keys:

`_WEATHER_DAILY = "weather_daily"
_WEATHER_HOURLY = "weather_hourly"

_LOGGER = logging.getLogger(name)

WEATHER_TYPES: tuple[WeatherEntityDescription, ...] = (
WeatherEntityDescription(
key=_WEATHER_DAILY,
name="Day based Forecast",
),
WeatherEntityDescription(
key=_WEATHER_HOURLY,
name="Hourly based Forecast",
),
)`

However, on checking the API response, the forecast keys used seem to be 'daily' and 'hourly' (https://apidocs.tempestwx.com/reference/get_better-forecast). Again, only took a quick look, will try to look into it and test hopefully later today. We have a hurricane coming up, and it'd be great to get everything recorded in HA.

Cheers

JtwoA · 2023-08-29T20:00:16Z

We have a hurricane coming up, and it'd be great to get everything recorded in HA.
@eelcovb
Where are you in the path? Lowcountry of SC here.

eelcovb · 2023-08-29T20:34:31Z

We have a hurricane coming up, and it'd be great to get everything recorded in HA.
@eelcovb
Where are you in the path? Lowcountry of SC here.

Orlando, FL no direct exposure, but probably some tornado's. Stay safe!

eelcovb · 2023-08-29T22:04:49Z

Haven't looked into it thoroughly, but my 2 cents:

Looking at a piece of forecast code, I noticed 'weather_daily' and 'weather_hourly' are used as keys:

`_WEATHER_DAILY = "weather_daily" _WEATHER_HOURLY = "weather_hourly"

_LOGGER = logging.getLogger(name)

WEATHER_TYPES: tuple[WeatherEntityDescription, ...] = ( WeatherEntityDescription( key=_WEATHER_DAILY, name="Day based Forecast", ), WeatherEntityDescription( key=_WEATHER_HOURLY, name="Hourly based Forecast", ), )`

However, on checking the API response, the forecast keys used seem to be 'daily' and 'hourly' (https://apidocs.tempestwx.com/reference/get_better-forecast). Again, only took a quick look, will try to look into it and test hopefully later today. We have a hurricane coming up, and it'd be great to get everything recorded in HA.

Cheers

Checked it, not the issue.

ldeffenb · 2023-08-29T22:27:45Z

East coast of Florida and my HA-integrated Tempest has also gone offline. Talk about (bad) timing!

UpDryTwist · 2023-08-29T22:56:44Z

OK, thought I wouldn't have time until this weekend, but it was bugging me (and it's driving me nuts looking at my dashboard with errors on it!), so I pulled it up in the debugger. @briis if you didn't already figure this out, the problem is that the hourly forecast no longer includes sea_level_pressure (I wonder if there was just a firmware push?). I'll confirm a fix and put up a pull request this evening.

For others on this thread, after I confirm, I'll let you know how you might patch until Bjarne has a chance to cut a release.

EDIT: Yup. Confirmed the fix. Will put up the pull request later, but for you hurricane trackers, below are general guidelines for how you can fix this in your installation. WARNING: There are many ways to run Home Assistant. I cannot speak for your own instance (nor, unfortunately, do I have the bandwidth today to troubleshoot other instances). You need to be reasonably technical to apply this patch; you need to understand the mechanics of your Home Assistance instance; and you need to be comfortable patching Python. You could break things!

The error occurs in pyweatherflowrest/api.py. The Weatherflow API has changed (firmware update?) in the last day or two to no longer return sea_level_pressure and uv in the hourly forecasts. This results in a KeyError exception in api.py
I have patched this by providing a more resilient way of reading the hourly forecast values (as maybe this was a defect on the Weatherflow side, and they'll be restored). You can find this fix in my fork at: https://github.com/UpDryTwist/pyweatherflowrest/blob/main/pyweatherflowrest/api.py
This patch adds logging (so that future changes here will be easier to diagnose). By default, my end version will error out, unless you edit the file to set a value (IGNORE_FETCH_ERRORS = True). This is a bit clunky, but I think that @briis is better-positioned to figure out a cleaner way to support a parameter in the two different implementations that call this.
You can find a version with this already set to True for you (so you don't need to edit) here: https://github.com/UpDryTwist/pyweatherflowrest/blob/b167b56b914bd24db155787928e05a7edf452773/pyweatherflowrest/api.py

Here are the steps I took to patch my version:

Go to the link above for the file (confirm that IGNORE_FETCH_ERRORS = True at the top). Click "Raw" and grab the URL.
Here's where your instructions may vary. You need to find where pyweatherflowrest is installed for your Home Assistant instance. There could be lots of places, which will vary by how you run, which OS you're using, etc., so I can't answer this for you. For me, I run in a container. So I opened a bash shell in my container and went to /usr/local/lib/python3.11/site-packages/pyweatherflowrest.
From there, I renamed the old file (mv api.py api.py-save)
Then I downloaded the patched file (wget <>)
. . . and restarted Home Assistant.

Voila:

UpDryTwist · 2023-08-30T00:12:09Z

OK, @briis , the PR is there. Thanks, BTW, for this fantastic implementation! You can see how freaked out we all get when it's not working!

briis/pyweatherflowrest#3

idaband · 2023-08-30T02:31:27Z

I can confirm the change works. I was able to make the change inside HA. I'm using the OS version.

robchandhok · 2023-08-30T20:44:09Z

Again my apologies for not really being a python guy, but if I could suggest (a) package a release with IGNORE_FETCH_ERRORS set to true by default, and (b) when debugging is on, log the IP address of the server (if that's possible).

I pointed the Weatherflow support folks at this ticket as well, as the intermittent behavior points to a disparity between the load balanced instances of the server.

UpDryTwist · 2023-08-30T20:47:34Z

@ldeffenb - yes, the logging will have the offender (first one found) and (if DEBUG enabled) the overall array returned. @robchandhok - good idea, and really my fault for having left it as False (I was erring on the side of no silent failures, but should have erred on the side of make it work). I'll try to get to it tonight with a PR for @briis to see tomorrow. In the meantime, folks can use the same patching instructions from my note above, which should work as-is still (WARNING, that's from theory, not because I tried it against the latest release!).

UpDryTwist · 2023-08-30T22:12:37Z

@robchandhok - did the Weatherflow folks happen to mention the type of load balancing they're doing? If they're doing DNS round-robin, then it'll be useful to get the IP address returned by DNS for any given user. But if they have a bunch of servers behind a load balancer . . . then the IP of the actual server will be opaque to us. And I'm loathe to add in a bunch of extra code to fetch the IP if it won't be meaningful . . .

robchandhok · 2023-08-30T22:36:56Z

@robchandhok - did the Weatherflow folks happen to mention the type of load balancing they're doing? If they're doing DNS round-robin, then it'll be useful to get the IP address returned by DNS for any given user. But if they have a bunch of servers behind a load balancer . . . then the IP of the actual server will be opaque to us. And I'm loathe to add in a bunch of extra code to fetch the IP if it won't be meaningful . . .

@UpDryTwist They haven't replied yet, but you are correct it's behind ELB on AWS. Not worth the time, I agree. Best to just enable the robust handling of missing keys.

rwolfe5420 · 2023-08-31T01:44:42Z

Mine is also broken with the same sea level error. Not sure how to resolve the issue. So I have disabled for the time being.

Logger: pyweatherflowrest.api
Source: custom_components/weatherflow/init.py:121
Integration: WeatherFlow Weather (documentation, issues)
First occurred: 9:39:37 pm (3 occurrences)
Last logged: 9:39:37 pm

The key sea_level_pressure is missing from the following array (DEBUG logging only), causing an error. It is likely that the Weatherflow API has changed unexpectedly. pyweatherflowrest on Github.
{'air_temperature': 13.0, 'conditions': 'Clear', 'feels_like': 13.0, 'icon': 'clear-night', 'local_day': 30, 'local_hour': 22, 'precip': 0, 'precip_icon': 'chance-rain', 'precip_probability': 0, 'precip_type': 'rain', 'relative_humidity': 79, 'time': 1693447200, 'wind_avg': 3.0, 'wind_direction': 30, 'wind_direction_cardinal': 'NNE', 'wind_gust': 4.0}
You can set the value IGNORE_FETCH_ERRORS in pyweatherflowrest/api.py to ignore this error.

yegorh · 2023-08-31T02:26:41Z

Hey guys, I updated to .15 this morning, but it didn’t fix the issue. However, I just checked and it’s working fine now.

JtwoA · 2023-08-31T03:19:10Z

I updated and neither of my two stations was working. Now one is/one isn't.

janick · 2023-08-31T03:52:25Z

What is the easiest way to break out of the shell container and edit HA files/update files directly?

briis · 2023-08-31T04:14:11Z

I have now done some more testing - and as many of you noticed, it is the Sea Level Pressure for the Hourly Forecast that is causing the problems.
I tried different Station ID's and with some of them (mine f.ex.) I get a value for sea level pressure, but for others I don't. I am not sure why, I have to get in touch with the WeatherFlow team to understand that.
In the meantime, we could work around this by setting a 0 value for sea level pressure if it does not exist?

janick · 2023-08-31T04:21:03Z

How would HA react to a NAN value?

UpDryTwist · 2023-08-31T04:30:46Z

@briis - I just added PR that defaults the variable I'd set to turn on/off ignoring errors in the hourly data to True (i.e., it will now just semi-silently ignore errors in the Weatherflow data). I changed the logging so that it logs at level WARNING at least once, but then shifts to DEBUG logging to not spam the logs.

If you have a way to let the user set this variable (through a config setting when configuring the component), that'd be even better - but this should work for now for the vast majority of users.

UpDryTwist · 2023-08-31T04:36:36Z

Just to summarize for everyone the situation:

Weatherflow is having some trouble with their API. We are speculating that they have multiple servers behind a load balancer, and that only some of the servers are poisoned. So you will see inconsistent results depending on which server gets handed to you by the load balancer. For the poisoned servers, neither "sea_level_pressure" nor "uv" is returned for the hourly forecasts, which breaks the Home Assistant integration.
Yesterday, I put in a patch that allowed the code to ignore errors (currently, only in the hourly forecasts; it could easily be extended to all the data reads). HOWEVER, I defaulted the condition to NOT ignore the errors, with a "todo" to add some way to set it to ignore (other than by editing the file). I did this on the misguided principle that errors shouldn't be silently ignored (e.g., for people using the component to record data, so they wouldn't have bad data recorded without a signal). Of course, this was a mistake, as most folks would rather it just collected bad data and worked otherwise ;).
@briis cut a release with my PR this morning. But of course, it was set to NOT ignore the errors, so it didn't fix things for people
I just submitted a PR that changes the default. So by default it will now ignore errors in the hourly data.
When briis gets a chance to accept the PR and cut 1.0.16, that should start working consistently for everyone.

briis · 2023-08-31T04:43:47Z

Thank you @UpDryTwist for this summary.

I am right now working on making it possible to toggle the IGNORE_FETCH_ERRORS from the Config Menu in the Integration. But the default will now be changed to True instead of False, so that you should get data, no matter if a single item is not present. Hopefully this can be released later today (It is early morning here in Denmark)

briis · 2023-08-31T05:31:00Z

1.0.16 is now published, which hopefully fixes this for everybody.
I will get in touch with the WeatherFlow team to see if they can give an explanation to why some stations do not have the Sea Level Pressure in the Forecast.

I will keep this open for a while until I am sure this now works for all.

psmith3 · 2023-08-31T06:18:05Z

1.0.16 is now published, which hopefully fixes this for everybody. I will get in touch with the WeatherFlow team to see if they can give an explanation to why some stations do not have the Sea Level Pressure in the Forecast.

I will keep this open for a while until I am sure this now works for all.

Fixed. Thanks for this!

deadrubberboy · 2023-08-31T10:50:18Z

We have a hurricane coming up, and it'd be great to get everything recorded in HA.
@eelcovb
Where are you in the path? Lowcountry of SC here.

Orlando, FL no direct exposure, but probably some tornado's. Stay safe!

Orlando here too! Also my Tempest having same issue as others.

robchandhok · 2023-08-31T11:29:30Z

1.0.16 is now published, which hopefully fixes this for everybody.

I will get in touch with the WeatherFlow team to see if they can give an explanation to why some stations do not have the Sea Level Pressure in the Forecast.

I will keep this open for a while until I am sure this now works for all.

Confirmed fixed for me, thank you @briis !

JtwoA · 2023-08-31T12:19:00Z

HUZZAH! Both units reporting in successfully - many thanks for hitting this hard, @briis - much appreciated!

rwolfe5420 · 2023-08-31T12:37:27Z

Thank You for this, mine is working as well this morning. Get Outlook for iOS From: Bjarne Riis ***@***.***>Sent: Thursday, August 31, 2023 1:31 AMTo: briis/hass-weatherflow ***@***.***>Cc: rwolfe5420 ***@***.***>; Comment ***@***.***>Subject: Re: [briis/hass-weatherflow] Weatherflow API seems to have broken the integration (Issue #81) 1.0.16 is now published, which hopefully fixes this for everybody. I will get in touch with the WeatherFlow team to see if they can give an explanation to why some stations do not have the Sea Level Pressure in the Forecast. I will keep this open for a while until I am sure this now works for all. —Reply to this email directly, view it on GitHub, or unsubscribeYou are receiving this because you commented.Message ID: ***@***.***>

jeremyhamm · 2023-08-31T13:22:01Z

1.0.16 resolved the issue for me. Thanks for everyones hard work in fixing this.

janick · 2023-08-31T13:28:22Z

Working now.

if they can give an explanation to why some stations do not have the Sea Level Pressure in the Forecast.

Maybe because my station is at 800ft altitude? :-)

deadrubberboy · 2023-08-31T15:09:23Z

1.0.16 resolved the issue for me. Thanks for everyones hard work in fixing this.

Same. All working again. Thank you!

dennyChandler · 2023-08-31T15:48:34Z

Confirmed working here as well, thank you all for your efforts in fixing this!

chheiss · 2023-08-31T15:56:05Z

Confirmed as working, thanks for all the effort!

PYehl73 · 2023-08-31T16:18:27Z

I updated all my files - getting some data but many entities are showing not available? Weather Station not giving air temp anymore?? lol

robchandhok · 2023-08-31T17:15:23Z

I updated all my files - getting some data but many entities are showing not available? Weather Station not giving air temp anymore?? lol

Did you update to the .16 release or patch by hand? I'm getting air temp just fine on the actual release.

PYehl73 · 2023-08-31T20:13:21Z

I updated the files manually. What steps do I need to do for actual release? (sorry newbie to HA)

Update - never mind I figured it out... rebooting now.

Nope after restarting - even deleted old one and put in my station ID / token again - only 45 sensors now.

I updated all my files - getting some data but many entities are showing not available? Weather Station not giving air temp anymore?? lol

Did you update to the .16 release or patch by hand? I'm getting air temp just fine on the actual release.

Yomegaman · 2023-09-01T03:49:39Z

Your fixes have everything working perfectly for me again. (Supervisor version)

Thank you ALL so much!

briis · 2023-09-01T05:24:55Z

I will close this now as the particular issue has been solved.
If anyone still have issues please create a new issue with data from the logs.

UpDryTwist mentioned this issue Aug 29, 2023

Anyone else getting Unknowns? #80

Closed

briis closed this as completed Sep 1, 2023

Weatherflow API seems to have broken the integration #81

Weatherflow API seems to have broken the integration #81

Comments

robchandhok commented Aug 28, 2023

eelcovb commented Aug 28, 2023

jeremyhamm commented Aug 28, 2023 • edited Loading

jeremyhamm commented Aug 28, 2023

jgosnell56 commented Aug 28, 2023 • edited Loading

jeremyhamm commented Aug 28, 2023

ragd011 commented Aug 29, 2023 • edited Loading

eelcovb commented Aug 29, 2023

gitBrave-hub commented Aug 29, 2023

idaband commented Aug 29, 2023

idaband commented Aug 29, 2023

robchandhok commented Aug 29, 2023

robchandhok commented Aug 29, 2023

ZeddicPrime commented Aug 29, 2023

robchandhok commented Aug 29, 2023

Yomegaman commented Aug 29, 2023

UpDryTwist commented Aug 29, 2023

idaband commented Aug 29, 2023 via email

robchandhok commented Aug 29, 2023

JtwoA commented Aug 29, 2023

briis commented Aug 29, 2023

id628 commented Aug 29, 2023 • edited Loading

eelcovb commented Aug 29, 2023

JtwoA commented Aug 29, 2023 • edited Loading

eelcovb commented Aug 29, 2023

eelcovb commented Aug 29, 2023

ldeffenb commented Aug 29, 2023

UpDryTwist commented Aug 29, 2023 • edited Loading

UpDryTwist commented Aug 30, 2023 • edited Loading

idaband commented Aug 30, 2023

robchandhok commented Aug 30, 2023

UpDryTwist commented Aug 30, 2023

UpDryTwist commented Aug 30, 2023

robchandhok commented Aug 30, 2023

rwolfe5420 commented Aug 31, 2023

yegorh commented Aug 31, 2023

JtwoA commented Aug 31, 2023

janick commented Aug 31, 2023

briis commented Aug 31, 2023

janick commented Aug 31, 2023

UpDryTwist commented Aug 31, 2023

UpDryTwist commented Aug 31, 2023

briis commented Aug 31, 2023

briis commented Aug 31, 2023

psmith3 commented Aug 31, 2023

deadrubberboy commented Aug 31, 2023

robchandhok commented Aug 31, 2023

JtwoA commented Aug 31, 2023

rwolfe5420 commented Aug 31, 2023 via email

jeremyhamm commented Aug 31, 2023

janick commented Aug 31, 2023 • edited Loading

deadrubberboy commented Aug 31, 2023

dennyChandler commented Aug 31, 2023

chheiss commented Aug 31, 2023

PYehl73 commented Aug 31, 2023

robchandhok commented Aug 31, 2023

PYehl73 commented Aug 31, 2023 • edited Loading

Yomegaman commented Sep 1, 2023

briis commented Sep 1, 2023

jeremyhamm commented Aug 28, 2023 •

edited

Loading

jgosnell56 commented Aug 28, 2023 •

edited

Loading

ragd011 commented Aug 29, 2023 •

edited

Loading

id628 commented Aug 29, 2023 •

edited

Loading

JtwoA commented Aug 29, 2023 •

edited

Loading

UpDryTwist commented Aug 29, 2023 •

edited

Loading

UpDryTwist commented Aug 30, 2023 •

edited

Loading

janick commented Aug 31, 2023 •

edited

Loading

PYehl73 commented Aug 31, 2023 •

edited

Loading