home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.07k stars 29.73k forks source link

Met.no not reporting weather data #120835

Open aacentric opened 2 months ago

aacentric commented 2 months ago

The problem

Around 3 days ago the Met.no integration stopped working for me - can't get any locations to report weather, not sure why. When I try the below (un-redacted) API call in my web browser, it returns the folowing:

"Mandatory parameters 'lat', 'lon' missing in call to Metno::WeatherAPI::Controller::Product::try {...}"

Looks like the latitude and longitude aren't being sent with the API request, though it appears to be correctly configured in HA. I've tried creating a new entity with the same, and with different lat/lon coordinates, and it doesn't seem to make a difference. Anyone else experiencing this?

log:

Logger: metno Source: components/met/coordinator.py:79 First occurred: 8:32:21 AM (3 occurrences) Last logged: 8:33:27 AM

Access to https://xxxxxxxxxx.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientResponseError'

What version of Home Assistant Core has the issue?

core-2024.6.4

What was the last working version of Home Assistant Core?

No response

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

Diagnostics information

ERROR (MainThread) [metno] Access to https://xxxxxxxxxxxxxxx.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientResponseError'

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 2 months ago

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

Code owner commands Code owners of `met` 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 met` 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)


met documentation met source (message by IssueLinks)

tweas commented 2 months ago

Getting two similar errors:

Logger: metno Source: components/met/coordinator.py:79 First occurred: 11:06:46 AM (1 occurrences) Last logged: 11:06:46 AM

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

and

Logger: homeassistant.components.met.coordinator Source: helpers/update_coordinator.py:344 integration: Meteorologisk institutt (Met.no) (documentation, issues) First occurred: 11:06:46 AM (1 occurrences) Last logged: 11:06:46 AM

Error fetching met data: Update failed:

NayooZ commented 2 months ago

Also having issues with Met.no

Logger: homeassistant.components.met.coordinator
Source: helpers/update_coordinator.py:344
integration: Meteorologisk institutt (Met.no) (documentation,issues)
First occurred: June 27, 2024 at 5:25:01 AM (1 occurrences)
Last logged: June 27, 2024 at 5:25:01 AM
Error fetching met data: Update failed:
Logger: metno
Source: components/met/coordinator.py:79
First occurred: June 27, 2024 at 5:25:01 AM (1 occurrences)
Last logged: June 27, 2024 at 5:25:01 AM
https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned 503
pgale commented 1 month ago

I've just started seeing the same. Has been working flawlessly for several months and as of 2024.7.2 (ish) I get unreliable updates. Sometimes it works, sometimes I get the error:

Logger: homeassistant.components.met.coordinator
Source: helpers/update_coordinator.py:344
integration: Meteorologisk institutt (Met.no) (documentation, issues)
First occurred: 13 July 2024 at 15:15:17 (4 occurrences)
Last logged: 08:04:47

Error fetching met data: Update failed:
DavidNZ27 commented 1 month ago

Add me to the list of intermittent time outs that recently started happening, though I don't know exactly when as I have only just started noticing the unavailable tile on my dashboard.

Logger: metno
Source: components/met/coordinator.py:79
First occurred: 11 July 2024 at 10:02:31 (25 occurrences)
Last logged: 09:13:54

Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'TimeoutError'
https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned 503
Logger: homeassistant.components.met.coordinator
Source: helpers/update_coordinator.py:344
integration: Meteorologisk institutt (Met.no) ([documentation](https://www.home-assistant.io/integrations/met), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+met%22))
First occurred: 11 July 2024 at 10:02:31 (20 occurrences)
Last logged: 09:13:54

Error fetching met data: Update failed: