GDACS Unable to Change to a New Lattitude and Longitude

[liquidbear99]

The problem

I moved out of the state and am trying to set GDACS to set to a new location. After deleting and reinstalling the integration, GDACS does not recognize a new location. The old location still persists. This problem occurs when using the GUI or .yaml to configure the location manually. The sensor name and its values do not change to match the new latitude and longitude.

What version of Home Assistant Core has the issue?

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

GDACS

Link to integration documentation on our website

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

Diagnostics information

There is no avility to doenload diagnostics for this integration

Example YAML snippet

gdacs:
  categories:
    - Drought
    - Earthquake
  radius: 1000
  latitude: -41.2
  longitude: 174.7

Then change it to any random location

gdacs:
  categories:
    - Drought
    - Earthquake
  radius: 1000
  latitude: -30.2
  longitude: 17.7

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `gdacs` 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 gdacs` 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)}}

---

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

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