home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.11k stars 29.79k forks source link

Roborock/Xiaomi E251 Unknown model #122798

Open somerockenguy opened 1 month ago

somerockenguy commented 1 month ago

The problem

Unfortunately unsure of what version this last worked on but my E2 / E251 no longer seems to work with the Xiaomi Miio integration which it once worked with. When adding the entity I get the error "Failed setup, will retry"

I have deleted and recreated my Android Mi Home account, re-added the vacuum, and rebooted HA. The vacuum still functions as expected with the Mi Home app. This vacuum is not compatible with the roborock app.

What version of Home Assistant Core has the issue?

core-2024.7.1

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

Xiaomi Miio

Link to integration documentation on our website

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

Diagnostics information

2024-07-29 13:47:04.331 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] Initializing with host 192.168.0.156 (token ceeba...) 2024-07-29 13:47:04.333 DEBUG (SyncWorker_43) [miio.click_common] Unknown model, trying autodetection. None None 2024-07-29 13:47:09.338 DEBUG (SyncWorker_43) [miio.miioprotocol] Unable to discover a device at address 192.168.0.156 2024-07-29 13:47:09.338 DEBUG (SyncWorker_43) [homeassistant.components.xiaomi_miio] Unable to fetch timers, this may happen on some devices: Unable to discover the device 192.168.0.156 2024-07-29 13:47:09.338 DEBUG (SyncWorker_43) [miio.click_common] Unknown model, trying autodetection. None None 2024-07-29 13:47:14.333 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] Finished fetching Robot vacuum data in 10.001 seconds (success: False) 2024-07-29 13:47:14.344 DEBUG (SyncWorker_43) [miio.miioprotocol] Unable to discover a device at address 192.168.0.156

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

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

Code owner commands Code owners of `xiaomi_miio` 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 xiaomi_miio` 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)


xiaomi_miio documentation xiaomi_miio source (message by IssueLinks)

rytilahti commented 3 weeks ago

Hi @somerockenguy!

Looks like the device doesn't respond to discovery packets at all. You could try to install python-miio and use its miiocli to see if the discovery is working at all with your device. You could try miiocli roborockvacuum --ip <host> --token <token> --model <model> status to see if skipping the model detection allows controlling the device.

You can use miiocli cloud to find the model and the token for the device.