Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xiaomi Miio: vacuum: sensors "mop attached" & "water box attached" are always OFF (Roborock S5) #77291

Closed
ildar170975 opened this issue Aug 24, 2022 · 15 comments

Comments

@ildar170975
Copy link

ildar170975 commented Aug 24, 2022

The problem

Using Roborock S5 robot vacuum with Xiaomi Miio.
Recently I realized that these sensors are always OFF:

  • mop attached
  • water box attached

Some time ago (at least - on December 2021) at least "water_box_attached" was changing "ON <-> OFF" dependingly on an actual state.

Strange that these sensors were created by the integration when I recently re-added the vacuum - but are NOT changing.

What version of Home Assistant Core has the issue?

2022.8.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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

@probot-home-assistant
Copy link

xiaomi_miio documentation
xiaomi_miio source
(message by IssueLinks)

@probot-home-assistant
Copy link

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)

@dewi-ny-je
Copy link

I'm not aware of the S5 actually having a sensor for the presence of the mop or water tank.
I also disassembled it yesterday for other reasons and I haven't seen any sensor which could detect it.

@rytilahti
Copy link
Member

How does the status response from the device look like? If it contains water_box_carriage_status that is set to 0, that's where it comes from and detecting the availability of the sensor would require checking for the model prior reporting that status.

@ildar170975
Copy link
Author

ildar170975 commented Sep 14, 2022

I'm not aware of the S5 actually having a sensor for the presence of the mop or water tank.

It will be very strange if this sensor is absent.
I tested this vacuum on December 21, repeat - "at least "water_box_attached" was changing "ON <-> OFF" dependingly on an actual state".
Then I got the same vacuum a month ago for some maintainment and realized that the sensor is not changing.

I also disassembled it yesterday for other reasons and I haven't seen any sensor which could detect it.

If this is for sure - then probably I forgot something...
May be I added this sensor & automation "detach the waterbox after completion" and then only WAS GOING to test it.

@dewi-ny-je
Copy link

I also wonder: the water box has no magnets and if you remove the bottom cover you see no circuit boards nearby, so I'm not sure how the change can be detected.
https://dontvacuum.me/teardowns/roborock.vacuum.s5/
The closest circuit board is on the top side of the housing so not even capacitive sensing would work!

I would say that before going further with this ticket, you should check with a different vacuum of the same series (s5x) and verify again with and without tank, with and without water.

@dewi-ny-je
Copy link

dewi-ny-je commented Sep 14, 2022

If I remember correctly, it was also stated in reviews that the Xiaomi app has no idea about the presence of the box, so you have to manually set it to "delicate/mopping" mode.
Some later models like s6 s7 (not sure which ones) have sensors for the purpose, hence the sensor provided by miio.

From my point of view... The bug is that the water sensor is provided also for s5x, while it shouldn't!

@rytilahti can the sensor be removed only for s5x?

@ildar170975
Copy link
Author

you should check with a different vacuum of the same series (s5x) and verify again with and without tank, with and without water.

Cannot check it unfortunately, there is only one vacuum nearby.
As for "with and without water" - no, there is no any sensors for a water presence for sure.
OMG, I was sure that this sensor was changing...

The bug is that the water sensor is provided also for s5x, while it shouldn't!

Then yes, probably the sensor should be removed.

it was also stated in reviews that the Xiaomi app has no idea about the presence of the box, so you have to manually set it to "delicate/mopping" mode.

I only have seen "enabling Carpet mode".

@rytilahti
Copy link
Member

From my point of view... The bug is that the water sensor is provided also for s5x, while it shouldn't!

@rytilahti can the sensor be removed only for s5x?

I have been working on moving the logic about available sensors towards the upstream lib (rytilahti/python-miio#1495), which should make implementing this fairly straightforward.

@bachoo786
Copy link

Hey guys I am having issues with integrating my Xiaomi Roborock S7 to HA. It used to work all well until the recent update to 2022.9.

It is not available on HA and I get this error message:

Logger: homeassistant.config_entries
Source: config_entries.py:388
First occurred: 13:26:21 (1 occurrences)
Last logged: 13:26:21

Config entry 'Roborock S7' for xiaomi_miio integration not ready yet; Retrying in background

Is there any work around this or any solutions?

Thanks.

@ildar170975
Copy link
Author

. It used to work all well until the recent update to 2022.9.

Your issue seems to be not related to the discussed topic.
You should create a separate issue for S7.

@WRoss7
Copy link

WRoss7 commented Nov 3, 2022

On the S5 i can still see the two sensors always off

@issue-triage-workflows
Copy link

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.

@WRoss7
Copy link

WRoss7 commented Feb 2, 2023

Persistent in 2023.2.0

@github-actions github-actions bot removed the stale label Feb 2, 2023
@issue-triage-workflows
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants