Roborock: 'utf-8' codec can't decode byte 0xe9 in position 0: invalid continuation byte

[jlatvala]

The problem

This was written into log while my Roborock Qrevo Curv was mopping.

[Roborock Qrevo Curv] 'utf-8' codec can't decode byte 0xe9 in position 0: invalid continuation byte Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py", line 464, in on_message_received if endpoint.decode().startswith(self._endpoint): ~~~~~~~~~~~~~~~^^ UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 0: invalid continuation byte

What version of Home Assistant Core has the issue?

core-2025.4.4

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

Roborock

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

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

---

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

[misosoup7]

I also see this error:

Logger: roborock.version_1_apis.roborock_mqtt_client_v1
Source: /usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py:484
First occurred: 12:01:23 AM (7 occurrences)
Last logged: 12:26:17 AM

[Living Area Vacuum] 'utf-8' codec can't decode byte 0xe6 in position 0: invalid continuation byte
[Living Area Vacuum] 'utf-8' codec can't decode byte 0xc8 in position 2: invalid continuation byte
[Living Area Vacuum] 'utf-8' codec can't decode bytes in position 0-1: invalid continuation byte
[Living Area Vacuum] 'utf-8' codec can't decode byte 0xa3 in position 0: invalid start byte
[Living Area Vacuum] 'utf-8' codec can't decode byte 0xc1 in position 2: invalid start byte
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py", line 464, in on_message_received
    if endpoint.decode().startswith(self._endpoint):
       ~~~~~~~~~~~~~~~^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 0: invalid start byte

I wonder if it's also the reason the map for my curv doesn't load where as my Qrevo and Qrevo S shows up fine.

[Melantrix]

I also have this error:

Logger: roborock.version_1_apis.roborock_mqtt_client_v1
Source: /usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py:484
First occurred: 05:25:43 (1 occurrence)
Last logged: 05:25:43

[Vacuum] 'utf-8' codec can't decode byte 0xbf in position 3: invalid start byte
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py", line 464, in on_message_received
    if endpoint.decode().startswith(self._endpoint):
       ~~~~~~~~~~~~~~~^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbf in position 3: invalid start byte

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.