home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.

Home Page:https://www.home-assistant.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No entity for vacuum robot error state

zunixnuz opened this issue · comments

The problem

There is no diagnose or status entity which is showing the vacuum error state.

What version of Home Assistant Core has the issue?

2022.5.5

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Hey there @rytilahti, @syssi, @starkillerOG, @bieniu, 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!
(message by CodeOwnersMention)


xiaomi_miio documentation
xiaomi_miio source
(message by IssueLinks)

vacuum.roborock_s6 does change to the status of error.

The problem seems to be two entities have the same name "Roborock S6". This confuses both the automation yaml writer and history. "State vacuum.roborock_S6 becomes error" as a trigger does work if the device tracker entity is renamed.

So I change the name of device_tracker.roborock_S6 to avoid this conflict.

It would be nice to know the type of error, if available in the API

The type of the error is available (as a code as well as as a human-readable string), but they are not currently exposed. I think this must wait until the underlying library (python-miio) gets a better way to expose sensors to homeassistant.

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.