Various warnings and error with ZAMG

[011V32]

The problem

I got the following warnings and error:

Logger: homeassistant.bootstrap Source: bootstrap.py:507 First occurred: 4. Juli 2023 um 21:22:14 (1 occurrences) Last logged: 4. Juli 2023 um 21:22:14

Waiting on integrations to complete setup: zamg

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 4. Juli 2023 um 21:22:36 (1 occurrences) Last logged: 4. Juli 2023 um 21:22:36

Config entry 'MY_LOCATION' for zamg integration not ready yet; Retrying in background

Logger: homeassistant.helpers.entity Source: helpers/entity.py:850 First occurred: 4. Juli 2023 um 21:35:13 (1 occurrences) Last logged: 4. Juli 2023 um 21:35:13

Updating state for sensor.my_location_wind_speed (<class 'homeassistant.components.zamg.sensor.ZamgSensor'>) took 0.536 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+zamg%22

Logger: homeassistant.helpers.frame Source: helpers/frame.py:124 First occurred: 05:06:04 (1 occurrences) Last logged: 05:06:04

Detected integration that closes the Home Assistant aiohttp session. Please report issue for zamg using this method at homeassistant/components/zamg/coordinator.py, line 44: device = await self.zamg.update()

Logger: homeassistant.components.zamg Source: helpers/update_coordinator.py:229 Integration: Zentralanstalt für Meteorologie und Geodynamik (ZAMG) (documentation, issues) First occurred: 4. Juli 2023 um 21:46:13 (9 occurrences) Last logged: 07:43:23

Timeout fetching zamg data

What version of Home Assistant Core has the issue?

core-2023.6.3

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

ZAMG

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `zamg` 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 zamg` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[ldoench]

I also had various outages in the last two days. Maybe their datahub-api is not responding?

[killer0071234]

Hi,

It seems that zamg (or newly Geosphere) has some outage.

Currently it's working again.

BR

[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.