core: NWS fails after .105 upgrade

First Home Assistant release with the issue: 0.105.1

Last working Home Assistant release: 0.104.3

Operating Environment: HASSIO on RPi

Integration/platform: /integrations/nws/

Description of problem: My NWS settings and card worked perfectly in .104. Upgraded to .105 today and the NWS entity became unavailable. Reboots and restarts made no difference. The NWS entity disappeared completely from everything including logs.

Problem-relevant configuration.yaml entries (email redacted) `# Weather from NWS weather:

  • platform: nws api_key: MYEMAIL@SERVER.COM station: KCRW`

Traceback (most recent call last): Update of weather.kcrw is taking over 10 seconds Error updating observation from station KCRW: 502, message=‘Bad Gateway’, url='https://api.weather.gov/stations/KCRW/observations/ Error updating forecast from station KCRW: 502, message=‘Bad Gateway’, url='https://api.weather.gov/gridpoints/RLX/62,66/forecast Error updating observation from station KCRW: 502, message=‘Bad Gateway’, url='https://api.weather.gov/stations/KCRW/observations

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 18 (9 by maintainers)

Most upvoted comments

I’m hoping that all the issues here were either caused by 1) the NWS API server being down or 2) the change to using strings in the NWS API data.

Any issue that was occurring a week ago @mostlychris might be a separate issue (although I would suspect it is probably due to that specific station/forecast office having issues temporarily), so feel free to raise another issue if this continues to occur.

I fixed the observation error, but now that the forecast end point is back up, the same thing happens there. The forecast values are now strings. This will have to be another fix. Hopefully done soon (not today though).

File “/usr/src/homeassistant/homeassistant/util/temperature.py”, line 21, in celsius_to_fahrenheit return celsius * 1.8 + 32.0 TypeError: can’t multiply sequence by non-int of type ‘float’

I was able to reproduce this error. It seems in addition to the flakiness of the server, NWS has suddenly decided to provide all observation data as strings rather than float or integers.

@Rocketman69 it is not approved and not included in 105. Do you guys have any errors in your home-assistant.log file?