core Shelly Integration no longer working correctly

The problem

I used 18x Shelly Plus 1PM gen2 and 2x Shelly Plug gen3

With version 2025.4 i can see everything. Energy, Input, Current, Power, etc.

With Version 2025.5.1 it's not working anymore: The error is: "This entity is no longer being provided by the shelly integration. If the entity is no longer in use, delete it in settings."

My 18x Shelly Plus 1PM gen2 and my 2x Shelly Plugs are up to date with version 1.6.1

What version of Home Assistant Core has the issue?

2025.5.1

What was the last working version of Home Assistant Core?

2025.4

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

home-assistant_shelly_2025-05-12T22-27-27.111Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Maybe this could help, but there no morte Errors or Warnings.

2025-05-13 00:20:44.209 ERROR (SyncWorker_5) [homeassistant.loader] Error parsing manifest.json file at /usr/src/homeassistant/homeassistant/components/sensor/manifest.json: unexpected character: line 1 column 1 (char 0)
2025-05-13 00:20:44.402 ERROR (SyncWorker_4) [homeassistant.loader] Error parsing manifest.json file at /usr/src/homeassistant/homeassistant/components/sensor/manifest.json: unexpected character: line 1 column 1 (char 0)
2025-05-13 00:20:44.413 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Integration 'sensor' not found.
2025-05-13 00:20:51.964 ERROR (SyncWorker_7) [homeassistant.loader] Error parsing manifest.json file at /usr/src/homeassistant/homeassistant/components/sensor/manifest.json: unexpected character: line 1 column 1 (char 0)
2025-05-13 00:20:51.965 ERROR (MainThread) [homeassistant.setup] Setup failed for 'sensor': Integration not found.

Additional information

No response

May 12 '25 22:05 ThomasFischer2024

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

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

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

May 12 '25 22:05 home-assistant[bot]

Looks like you have some file system corruption. Try rebuilding your container and checking your storage media for errors

May 12 '25 23:05 bdraco

The problem has been solved.

The storage was fine, with no errors. 😊

The issue was with how I launched the Home Assistant Docker container.

First, I stopped the old container using docker stop homeassistant. Second, I removed the container with docker rm homeassistant, and finally, I deleted the old image using docker rmi homeassistant/home-assistant:2025.4.

However, instead of running Docker with the correct image tag homeassistant/home-assistant:2025.5.1, I accidentally used homeassistant/home-assistant:2025.5.

Strangely, Home Assistant still reported the version as 2025.5.1. 😑

Anyway, everything is working fine now. 😊

Sorry for opening a bug report on this!

May 13 '25 04:05 ThomasFischer2024