Roborock - Segment / Room names are not correct

[ambiman]

The problem

I've named my rooms in the Roborock app correctly (like living room, kitchen etc.) but in HA the segments are simply named as "Room 16", "Room 17" etc. - so the mapping to the actual areas is quite difficult :-)

What version of Home Assistant Core has the issue?

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

Output of action roborock.get_maps:

vacuum.mo:
maps:
- flag: 0
name: CDG-EG
rooms:
"16": Room 16
"17": Room 17
"18": Room 18
"19": Room 19
"20": Room 20

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@ambiman Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20roborock%22%20
_{^{(message by IssueContext)}}

---

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

[allenporter]

(1) Hello can you please attach diagnostics information for the device?
https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics

(2) Would you be able to enable debug logging and capture debug logs when the integration is reloaded? https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

This may help is catch if information is present anywhere.

[ambiman]

Dear Allen,

for sure, please see attachments.

In the debug log this one looks promising.
But the credentials most be valid otherwise the other telemetry data won't load at all, or?

2026-05-03 19:54:06.355 INFO (MainThread) [roborock.web_api] Get Home Id failed with the following context: {'msg': 'invalid token', 'data': None, 'code': 2010}
2026-05-03 19:54:06.355 DEBUG (MainThread) [roborock.devices.traits.v1.rooms] Failed to fetch rooms from web API
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/roborock/devices/traits/v1/rooms.py", line 116, in _refresh_rooms
    return await self._web_api.get_rooms()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/roborock/web_api.py", line 757, in get_rooms
    return await self._web_api.get_rooms(self._user_data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/roborock/web_api.py", line 540, in get_rooms
    home_id = await self._get_home_id(user_data)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/roborock/web_api.py", line 454, in _get_home_id
    raise RoborockInvalidCredentials(
        f"Invalid credentials ({home_id_response.get('msg')}) - check your login and try again."
    )
roborock.exceptions.RoborockInvalidCredentials: Invalid credentials (invalid token) - check your login and try again.

home-assistant_roborock_2026-05-03T17-54-09.789Z.log

config_entry-roborock-01JD799GY52J10WFAYQNV1GYW5.json

Thanks for your support and all the best,

ambiman

[allenporter]

OK that explains it. It refreshes rooms names in the background, but does not prevent the device from working when those fail. As a result, when the credentials need to be refreshed it won't load the room names.
So.. we'd need to force this to reauth in home assistant (disabling the integration temporarily )for it to refresh them. This needs some work to resolve. i don't have a good suggestion for a workaround in the short term.

[gjohansson-ST]

Not sure if it's exactly same issue but the result is the same so somehow maybe it's the same problem.

If I use my partners account, I get the proper names if the rooms
If I use my account (secondary) I get the same result as the issue reports.

Somehow I suspect only the main (owner) account may get this info?
I don't think I can rename room etc either on my account (while it does seem like I can divide rooms etc 🤷‍♂️

[Lash-L]

Not sure if it's exactly same issue but the result is the same so somehow maybe it's the same problem.

If I use my partners account, I get the proper names if the rooms
If I use my account (secondary) I get the same result as the issue reports.

Somehow I suspect only the main (owner) account may get this info?
I don't think I can rename room etc either on my account (while it does seem like I can divide rooms etc 🤷‍♂️

I have seen other people having a very similar issues with shared accounts - we should run an experiment with one shared account and one original account and compare the three different ways of getting rooms. My guess is vacs that give more information via mqtt may work, but those that don't where we have to rely on the web api home data call may not. But a shared account can see room names in the app so it must be possible, we just have to figure out what we need to do.

[Lash-L]

Not sure if it's exactly same issue but the result is the same so somehow maybe it's the same problem.
If I use my partners account, I get the proper names if the rooms
If I use my account (secondary) I get the same result as the issue reports.
Somehow I suspect only the main (owner) account may get this info?
I don't think I can rename room etc either on my account (while it does seem like I can divide rooms etc 🤷‍♂️

I have seen other people having a very similar issues with shared accounts - we should run an experiment with one shared account and one original account and compare the three different ways of getting rooms. My guess is vacs that give more information via mqtt may work, but those that don't where we have to rely on the web api home data call may not. But a shared account can see room names in the app so it must be possible, we just have to figure out what we need to do.

Ding ding ding.

There is a different endpoint for shared device rooms that we are not currently using. Implementing that should fix a lot of users problems. Not this issue though.