8000 Met.no doesn't load after updating to 2021.4.0 · Issue #48808 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Met.no doesn't load after updating to 2021.4.0 #48808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Salvora opened this issue Apr 8, 2021 · 19 comments · Fixed by #49607
Closed

Met.no doesn't load after updating to 2021.4.0 #48808

Salvora opened this issue Apr 8, 2021 · 19 comments · Fixed by #49607
Assignees
@Danielhiversen
Labels
integration: met

Comments

@Salvora
Copy link
Salvora commented Apr 8, 2021

The problem

After updating the 2021.4.0, met.no doesn't load with the below error.
I have to manually reload the integration, only then it starts working.
My location is set up correctly.
The only thing that comes to my mind is this PR #48741
My location is set up using UI, not yaml. Is it possible that this PR checks for location in the yaml but skips UI? Though, I don't have anything like this in my logs.

What is version of Home Assistant Core has the issue?

core-2021.4.0

What was the last working version of Home Assistant Core?

core-2021.2.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Met.no

Link to integration documentation on our website

https://www.home-assistant.io/integrations/met/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-04-08 06:14:45 ERROR (MainThread) [metno] https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned 
2021-04-08 06:14:45 DEBUG (MainThread) [homeassistant.components.met] Finished fetching met data in 83.126 seconds
@probot-home-assistant
Copy link

met documentation
met source
(message by IssueLinks)

@derwolff
Copy link
derwolff commented Apr 8, 2021
8000

Same here. Manually restart and new configuration doesn't solve the issue. By the way, OpenWeatherMap has the same issue after update.

@serlinGi
Copy link
serlinGi commented Apr 8, 2021

Same here. Manually restart and new configuration doesn't solve the issue. By the way, OpenWeatherMap has the same issue after update.

identical situation for me

@Danielhiversen
Copy link
Member

No errors in the log?

@Salvora
Copy link
Author
Salvora commented Apr 8, 2021

What I previously sent is the only thing I got.

@Danielhiversen
Copy link
Member
8000

Could some of you test this: https://github.com/home-assistant/core/compare/met_lib?expand=1 ?
Some extra logging

@miklosbagi
Copy link
miklosbagi commented Apr 9, 2021 •
edited
Loading 
Logger: metno
Source: /usr/local/lib/python3.8/site-packages/metno/__init__.py:105 
First occurred: 7:35:33 AM (1 occurrences) 
Last logged: 7:35:33 AM

https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned

Affects 2021.4.0 / HAOS and 2021.4.1 / HAOS.

Reloading the integration solves this issue (takes a few minutes though) on HAOS, but comes back after restart.

@Salvora
Copy link
Author
Salvora commented Apr 11, 2021

2021.4.3 still the same.

@Danielhiversen
Copy link
Member

@Salvora Have you tested wth this? https://github.com/home-assistant/core/compare/met_lib?expand=1

@derwolff
Copy link

After update to 2021.4.3 in the afternone the forecast is updated some hours later. The the same occurs with 2021.4.2. Maybe the update timer is broken?
grafik

@Salvora
Copy link
Author
Salvora commented Apr 11, 2021

@Salvora Have you tested wth this? https://github.com/home-assistant/core/compare/met_lib?expand=1

Ehm, I don't get it. How do I test that? It opens a PR?

@Danielhiversen Danielhiversen mentioned this issue Apr 16, 2021
Merged
21 tasks
@serlinGi
Copy link

hi,
my homeassistant.OS is constantly and updated (now I am at core-2021.4.6, supervisor-2021.04.0 with Home Assistant OS 5.13) but the error persists; this morning for greater security I removed the Met.no integration and I reinstalled it but the problem remains the same: when restarting it does not start and the error "Access to https://aa015h6buqvih86i1.api.met.no/ always appears weatherapi / locationforecast / 2.0 / complete returned error 'TimeoutError'; as before, I only resolve with a manual reload.

@Salvora
Copy link
Author
Salvora commented Apr 21, 2021

same here, 2021.4.6 did not fix it.

@Danielhiversen
Copy link
Member

There has not been any attempt to fix the actual issue yet. Just improving the logging.
Could you post the error message with the latest version of HA?

@Salvora
Copy link
Author
Salvora commented Apr 21, 2021

Without any logging:

2021-04-21 09:08:09 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'TimeoutError'

with debug level logging

2021-04-21 14:06:00 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'TimeoutError'
2021-04-21 14:06:00 DEBUG (MainThread) [homeassistant.components.met] Finished fetching met data in 73.545 seconds

@Danielhiversen
Copy link
Member
Danielhiversen commented Apr 21, 2021 •
edited
Loading

Thanks, will fix it in next release of HA.
Edit: The fix will increase the time before timeout. So it might still happen if the met.no server takes a long time to respond.

@brunomgsousa
Copy link

Thanks, will fix it in next release of HA.
Edit: The fix will increase the time before timeout. So it might still happen if the met.no server takes a long time to respond.

Just to inform you that with the same version 2021.4.6, I have the Timeout error in 2 RPI3b+ but not in a RPI4 (yes I have 3 instances, and 3 rpis). Tks.

@Danielhiversen Danielhiversen mentioned this issue Apr 23, 2021
Merged
21 tasks
@Salvora
Copy link
Author
Salvora commented May 6, 2021

It is still the same for me on 2021.5.0.

@derwolff
Copy link
derwolff commented May 6, 2021

Same here, after HASS update or restart it takes several hours until a forecast is showen. Restart at 22:00, valid forecast next day at 6:00 .

@github-actions github-actions bot locked and limited conversation to collaborators Jun 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Danielhiversen Danielhiversen

Labels
integration: met
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update met.no library home-assistant/core
6 participants
@Danielhiversen @Salvora @derwolff @brunomgsousa @serlinGi @miklosbagi
0