Persistent 17TRACK repair notifications "17Track package sensors are being deprecated" won't go away.

[stnvsb]

The problem

I get 2 repair notifications for the 17Track integration. After an upgrade of the integraties this started. I cannot get rid of them. I have tried everything: rebooting, removing the integration, re-adding the integration,.. The notification "17Track package sensors are being deprecated" doesn't make sense because I don't use package sensors for 17track integration..

Here are some screenshots:

What version of Home Assistant Core has the issue?

core-2024.9.2

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

17TRACK

Link to integration documentation on our website

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

Diagnostics information

home-assistant_seventeentrack_2024-09-18T12-25-42.827Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

File "/usr/src/homeassistant/homeassistant/components/repairs/issue_handler.py", line 76, in async_create_flow
    flow = await platform.async_create_fix_flow(self.hass, issue_id, issue.data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/seventeentrack/repairs.py", line 47, in async_create_fix_flow
    assert entry
           ^^^^^
AssertionError

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

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

---

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

[shaiu]

@stnvsb did you try to click Submit after clicking on the repair?

[stnvsb]

@shaiu after clicking on the repair I'dont get a "Submit" I always get the error message: "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" with an "OK" button. But pressing the OK button doesn't do anything..

[rodrigoscna]

I'm getting the same error. I also removed the integration and now I'm getting the "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" error message as well.

[Hellchampion]

I'm getting the same error. I also removed the integration and now I'm getting the "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" error message as well. Reinstall i get the same error.