ZAMG integration name outdated

[MattWestb]

The problem

The name is GeoSphere Austria from 01.01.2023. Info https://www.zamg.ac.at/cms/de/aktuell/news/zamg-und-gba-werden-zu-geosphere-austria.

First need the docks being updated and later also the name in the integration.

What version of Home Assistant Core has the issue?

core-2023.1.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

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 Change the title of 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)}}

[killer0071234]

Thanks for your information. Did you also know if there is a change on the api? To change the integration name i think we need to follow a specific procedure. The only hint what i found is that renaming-pages.

[MattWestb]

The naming of the integration must being inline with HA guidelines and can taking some time but i wondering if its possible only doing renaming in HA GUI with new logo and doing the underlying changes later. I think best is asking some of the leader team hot to do it right.

I have not looking only that most of the weekend they looks have doing maintenance until after 10 in the morning with long time with not replay and the rest with frozen data but looks working now.

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