Core: Roborock Vacuum has no entities

[MatthiasF999]

The problem

After adding a Roborock S5 Max to the Xiaomi Miio Integration, the device is added, but it has no entities.
The log then contains a message xiaomi_miio: Error on device update!

Environment

• Home Assistant Core release with the issue: 0.111.4
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core): HassOS 4.10
• Integration causing this issue: Alarm control panel
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/alarm_control_panel

Traceback/Error logs

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 319, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/xiaomi_miio/alarm_control_panel.py", line 124, in async_update
    state = await self.hass.async_add_executor_job(self._gateway.alarm.status)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/miio/gateway.py", line 176, in status
    return self._device.send("get_arming").pop()
AttributeError: 'str' object has no attribute 'pop'

Additional information

[probot-home-assistant[bot]]

Hey there @rytilahti, @syssi, mind taking a look at this issue as its been labeled with an integration (xiaomi_miio) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[rytilahti]

All platforms besides the alarm panel need to be initialized using the manual configuration. Ping @starkillerOG unsupported devices should be ignored from the automatic integration?

[starkillerOG]

@MatthiasF999 did the Roborock S5 Max show up as an discovered integration?
It schould not show up because everything schould have been filtered out that does not start with "lumi-gateway" for the zeroconf model.

If you set up the integration manually using the + icon, in that case @rytilahti is right, only the gateway part of the miio integration supports config flow, all other integrations like the vacuum cleaners schould be integrated using YAML config.

[MatthiasF999]

I set it up manually using the + icon.
After removing the integration and adding the device to the configuration.yaml it works as expected.

The documentation is confusing, as the link in the dialog on how to get the access token points to https://www.home-assistant.io/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token, which describes how to setup a vacuum.

[starkillerOG]

Yes the documentation is kind of a mess at the moment.
At some point I will try to clean it up and try to structure it better.

[stale[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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.