You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have 3 X10 vacuums and running latest HAOS (Core 2024.8.2, Supervisor 2024.08.0, OS 13.1, Frontend 20240809.0) and HACS (
Integration version 2.0.0, Frontend version 20240814080035), plugin version is also the latest (v2.0.0b16) downloaded directly using HACS. The services running fine until I click reset button (any reset, e.g., reset main brush, reset mop etc). Once it is clicked, the UI shows all entities in unavailable status until I reconfigure devices. Map seems still fine.
To Reproduce
Create a new dashboard for vacuums, each vacuum as a view in my scenario.
In the layout, I used grids and stacks to make the page until satisfactory. One of the stacks I put counter statistics and reset buttons as entities (sorry for not putting it in a better way as a newbie in making dashboards). See attached screenshots (sensitive information blurred out) as my layout.
When necessary, click "PRESS" in the one of the entities of resetting counter.
All entities became unavailable. I tried multiple times on different entities, as far as I tested, the behaviors were the same.
To resolve this, a reconfigure is necessary - I tried to wait for a couple of hours, without letting the vacuum run again, it didn't recover.
Once the reconfigure is done, the counter is indeed reset, I can see the counter recovers to 100% in both HA and Dreame app.
I also created a button group of all resetting entities, and it worked once (I accidentally clicked it in the lovelace dashboard, didn't know how to make it confirmable) and all worked fine without making any entities unavailable. I haven't tried again though.
Expected behavior
I would expect the respective counter is reset and UI shows 100% left, not affecting other procedures.
Screenshots
Additional Information
Model Name: dreame.vacuum.r2235
Firmware Version: 4.3.9_1551
Home Assistant Version: latest
Configuration Type: With map support, tried both normal and low-res map settings.
Errors or warnings shown in the HA logs (if applicable): Didn't see any in HA core / supervisor / host logs. - possibly not finding in the correct place.
Incase it's necessary, here is the code for the layout
Note: the code is generated using visual editor
This is not just because of resetting a consumable but also happens if you try to change any setting after your internet connection lost for a short period of time.
I know this bug for a long time but I haven't had time to fix it yet.
Thanks for your reply. I didn't see if any internet interruption occurred, both LAN and WAN. And I couldn't find a stable way to reproduce this issue except resetting consumable - I tried to change some settings once but it gone through correctly.
Luckily it seems able to recover when the next time the robot starts the cleaning progress - I have a schedule starts like 3.30 am every other night and I see it recoverred at exactly 3.30am this night without reconfiguring the device. So it seems less critical but just inconvinence. Any idea which source code file should I look at to fix the issue? I may able to try to fix. Thanks.
Describe the bug
I have 3 X10 vacuums and running latest HAOS (Core 2024.8.2, Supervisor 2024.08.0, OS 13.1, Frontend 20240809.0) and HACS (
Integration version 2.0.0, Frontend version 20240814080035), plugin version is also the latest (v2.0.0b16) downloaded directly using HACS. The services running fine until I click reset button (any reset, e.g., reset main brush, reset mop etc). Once it is clicked, the UI shows all entities in unavailable status until I reconfigure devices. Map seems still fine.
To Reproduce
Expected behavior
I would expect the respective counter is reset and UI shows 100% left, not affecting other procedures.
Screenshots
Additional Information
Incase it's necessary, here is the code for the layout
Note: the code is generated using visual editor
The text was updated successfully, but these errors were encountered: