Reolink chime given bogus name when Home Hub added to Home Assistant

[jezzaaa]

The problem

I have a chime and a battery doorbell. I purchased a Home Hub so that I could integrate them with Home Assistant. I added the hub using the integration, and everything seems OK. Brilliant integration, thankyou!!!

However, the name given to the chime device is made up of 3 characters, two of which are non-ASCII. It appears to be 2 bytes of unicode and the "3": �ݷ3 [\u{FFFD}\u{777}3] The chime's name is I think "Reolink Chime" or just "Chime" so that's what I expected as the name of the newly discovered device.

What version of Home Assistant Core has the issue?

core-2024.11.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

reolink

Link to integration documentation on our website

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

Diagnostics information

config_entry-reolink-01JD4AZ82CP1JSAVVKX05XD0KC.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Refer image:

It's easy enough for me to rename the device, but I shouldn't need to.

Related entities also have the same name, followed by "LED" or "Volume". The entity IDs use "chime":

[home-assistant[bot]]

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

Code owner commands

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

---

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

[jezzaaa]

Another possibly useful fact is that after renaming to "Chime" and then removing and re-adding the Home Hub, the chime was given the exact same bogus name. This suggests that it's unlikely the result of a mis-directed pointer or some memory corruption, but rather a deterministic anomaly.

[starkillerOG]

@jezzaaa could you enable debug logging of the reolink integration, reload the integration, wait 3 minutes, disable debug logging and post the resulting log.txt file here?

https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

I probably have a way of fixing this, but I would need to see what the Hub is sending back to the HTTP request.