Config entry '192.168.1.8' from integration sma has an invalid unique_id '3010653335'

[kgooris]

The problem

the error logs show, I should create a bug report :) - however integration seems to work fine.

What version of Home Assistant Core has the issue?

core-2024.10.1

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

SMA Solar Inverter 3KW

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-10-11 21:55:04.848 ERROR (MainThread) [homeassistant.config_entries] Config entry '192.168.1.8' from integration sma has an invalid unique_id '3010653335', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+sma%22

Additional information

No response

[home-assistant]

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

Code owner commands

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

---

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

[rklomp]

duplicate #127428

[joostlek]

@rklomp this error is raised at load time before the migration is run, so after you've fixed it, people will still see the error in the log for the first time

[kgooris]

for whatever reason I'm now also having 2 SMA devices. One 'correct one' has no entities, and then another one, that got added is having all the entitities....
any ideas? Is it related to this bug?

[Robbe-B]

for whatever reason I'm now also having 2 SMA devices. One 'correct one' has no entities, and then another one, that got added is having all the entitities.... any ideas? Is it related to this bug?

Same, I have 2 SMA devices now

[RealCommerzpunk]

Same here, and the not working one is the one that I used in all my Variables and Dashboards.

How can I fix that, to switch the devices and make just one appear and working?

[RealCommerzpunk]

Hello,
are there still investigations to solve this issue? Because I can not monitor my sunny boy and solar production since this bug.

Here some pictures to show the issue for better understanding:

2 devices, but only one working:

New one:

Old one:

The easiest way would be, to just use the new device, but what's strange, I can't! When ever I try to use it, it just somehow links to the old one:

[RealCommerzpunk]

I can't understand why, but its working again now. It's still 2 devices, but one, in my memory the old one, has no more sensors. But the new one, (again, as I remember) has all the values. And what's stranger: All my variables and dashboards are working again now. Maybe it's just the latest update to 2024.11.0 that did the magic?

[Robbe-B]

I can't understand why, but its working again now. It's still 2 devices, but one, in my memory the old one, has no more sensors. But the new one, (again, as I remember) has all the values. And what's stranger: All my variables and dashboards are working again now. Maybe it's just the latest update to 2024.11.0 that did the magic?

I have something similar

[nemihome]

This has much more effect than decribed here for me. I see the two devices after the upgrade. Furthermore due to this the old device has another ID than the new one and all sensors which are created based on the old device lose history data. Which means I can't upgrade Home Assistant without losing all history data. And no that is not fixed by latest updates because I upgraded to 2024.12.4 and still run into this problem.

Directly after upgrade after first start the sensors based on the SMA sensors did work but after first restart they don't work anymore and have no history.

[Robbe-B]

This has much more effect than decribed here for me. I see the two devices after the upgrade. Furthermore due to this the old device has another ID than the new one and all sensors which are created based on the old device lose history data. Which means I can't upgrade Home Assistant without losing all history data. And no that is not fixed by latest updates because I upgraded to 2024.12.4 and still run into this problem.

Directly after upgrade after first start the sensors based on the SMA sensors did work but after first restart they don't work anymore and have no history.

Same