'device_tracker' from integration tado has a non string unique_id

[tjorim]

The problem

Getting an error after upgrading HA to 2024.5 (only showed up in the full logs).

2024-04-25 14:50:29.919 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'device_tracker' from integration tado has a non string unique_id '5595071', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tado%22

What version of Home Assistant Core has the issue?

core-2024.5.0b0

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

tado

Link to integration documentation on our website

https://rc.home-assistant.io/integrations/tado/

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 @chiefdragon, @erwindouna, mind taking a look at this issue as it has been labeled with an integration (tado) you are listed as a code owner for? Thanks!

Code owner commands

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

---

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

[bdraco]

This one needs a migration to be fixed. It won't cause any functional problems since int is hashable, but it should be fixed eventually.