Roborock Integration Retrying setup: name error

[mesut3000]

The problem

Trying for hours but still getting 'Retrying setup: name' error message. My homeassistant is also rebooting if i do not disable integration. Deleted and added many times, nothing changed.

What version of Home Assistant Core has the issue?

core-2023.5.0b1

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

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

Link to integration documentation on our website

No response

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

[RubenKelevra]

HA gets unresponsive and will eventually reboot. But not sure if that's related to roborock.

However, I can confirm your observation about the setup issue:

#92142 (comment)

[Lash-L]

Hi @mesut3000 just wanted to repeat this here as I stated it in your last issue as well - the issue stems with the incorrect information for dock for your device.

It will be fixed in b2.

As far as the freezing up, I believe that was a secondary problem with the sockets that the library was using and the sockets were for some reason immune tot he async timeout - the issue only happened when the enum bug occurred, that is why I didn't not originally notice it. I was able to recreate the issue and it should also be fixed as we repaired how the local connection works. I would recommend removing the integration until b2 is out

[home-assistant]

Hey there @humbertogontijo, 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.

_{^{(message by CodeOwnersMention)}}

---

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

[tinkerberlin]

Also got this problem. Is this also on the roadmap for b2? (same as #92142)
I've got a S6 MaxV.
Thanks!

2023-04-28 09:17:04.707 WARNING (MainThread) [roborock.cloud_api] Roborock mqtt client disconnected (rc: 0)
2023-04-28 09:17:04.741 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Unexpected error fetching roborock data: name
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/components/roborock/coordinator.py", line 77, in _async_update_data
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/components/roborock/coordinator.py", line 67, in _update_device_prop
    device_prop = await self.api.get_prop(device_info.device.duid)
  File "/usr/local/lib/python3.10/site-packages/roborock/api.py", line 289, in get_prop
    dock_summary = await self.get_dock_summary(device_id, status.dock_type)
  File "/usr/local/lib/python3.10/site-packages/roborock/api.py", line 251, in get_dock_summary
    if RoborockDockTypeCode.name != "RoborockDockTypeCode":
  File "/usr/local/lib/python3.10/enum.py", line 437, in __getattr__
    raise AttributeError(name) from None
AttributeError: name
2023-04-28 09:17:04.748 WARNING (MainThread) [homeassistant.config_entries] Config entry 'xxx@gmail.com' for roborock integration not ready yet: name; Retrying in background
2023-04-28 09:17:10.362 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds

[notice] A new release of pip is available: 23.1 -> 23.1.2
[notice] To update, run: pip install --upgrade pip
2023-04-28 09:17:14.821 WARNING (MainThread) [roborock.cloud_api] Roborock mqtt client disconnected (rc: 0)
2023-04-28 09:17:14.868 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Unexpected error fetching roborock data: name
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/components/roborock/coordinator.py", line 77, in _async_update_data
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/components/roborock/coordinator.py", line 67, in _update_device_prop
    device_prop = await self.api.get_prop(device_info.device.duid)
  File "/usr/local/lib/python3.10/site-packages/roborock/api.py", line 289, in get_prop
    dock_summary = await self.get_dock_summary(device_id, status.dock_type)
  File "/usr/local/lib/python3.10/site-packages/roborock/api.py", line 251, in get_dock_summary
    if RoborockDockTypeCode.name != "RoborockDockTypeCode":
  File "/usr/local/lib/python3.10/enum.py", line 437, in __getattr__
    raise AttributeError(name) from None
AttributeError: name
2023-04-28 09:17:14.870 WARNING (MainThread) [homeassistant.config_entries] Config entry 'xxx@gmail.com' for roborock integration not ready yet: name; Retrying in background
2023-04-28 09:17:17.581 WARNING (SyncWorker_11) [custom_components.xiaomi_cloud_map_extractor.camera] Got exception while fetching the state: Unable to discover the device 192.168.0.143

[Lash-L]

Yes @tinkerberlin see #92142

[tinkerberlin]

Thanks @Lash-L ! Yup, had seen that in #92142 it was mentioned that that issue was being fixed in b2. I just wasn't 100% sure that that also applied to this issue. Thanks for the quick reply and for the great work! :-)

[Lash-L]

@tinkerberlin @mesut3000 please try with the latest beta (b2) and report back

[RubenKelevra]

b2 works for me :)

[tinkerberlin]

hi @Lash-L. Yes b2 works for me. Showing one device (correct) with 3 entities.

[mesut3000]

@tinkerberlin @mesut3000 please try with the latest beta (b2) and report back

Yeah, it is working now, issue solved.