LuBlueLu SL60D Start Cleaning/Pause are misbehaving #2334
Comments
reef-actor
changed the title
make-all
added
device improvement
|
It isn't clear what needs to be done here. |
|
If there is any diagnostics/logs that might contain clues I can have a dig through them. I had assumed this vacuum didn't support this, but on a whim I tried localtuya and was able to start cleaning (ironically this was the only function that worked out of the box with that integration). I am trying to understand what that code is doing differently but I don't regularly deal with python so it will take a bit of effort to understand how it maps DPs. |
|
It is more the tuya developer portal info for the device that will help. ie, the QueryThingsDataModel cloud API call result. That will show what names Tuya has given to the dps, and maybe include Chinese language descriptions that explain a bit more how they are used. The commit you highlight just makes those two dps optional, as previous reports showed they weren't always reported by the device. The power dp has a default of off added, because if the power is missing HA makes the whole entity unavailable and you cannot use it. What you are saying sounds familiar, so probably one of the other vacuums has already been changed to deal with this same issue. |
QueryThingsDataModel resultFrom the API: In the YAML I'm not 100% on how to interpret this, but that looks suspect? |
|
Yes, when the dps are labelled switch_go and pause, they cannot be mapped directly to power and activate like that. |
make-all
added a commit
that referenced
this issue
Sep 28, 2024
Rather than power and activate, these dps are listed in iot.tuya.com as switch_go and pause. This appears to be the same as Kabum 700 v2023 vacuums, so use the same pattern. Issue #2334
make-all
added a commit
that referenced
this issue
Sep 28, 2024
Additional dps from iot.tuya.com info for the device. Some dps were listed as attributes, made available as entities so they can be controlled. Others are new. Any new ones marked as optional so as not to increase requirements for detection. Issue #2334
make-all
added
awaiting confirmation
|
I added support getting maps for this vacuum (from the cloud) to the tuya_cloud_map_extractor and think it would be cool if it could be done locally. DP 16 looks promising, but my concern is the disruption on this codebase caused by bringing all the parsing and decompressing functions over here. |
|
It may be worth adding the compression and decoding to the camera platform within tuya_local. |
make-all
removed
awaiting confirmation
|
I appreciate your work here. It is ✨sometimes✨ working now. Update: It seems that it is just necessary to keep trying Start until it works. Sometimes it works on the first attempt, sometimes it takes quite a few attempts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the vacuum is docked (status: sleep), the▶️ button does not start cleaning. It does change the value of the Activate attribute to true. The ⏸️ button will reset Activate to false.
I have not found a way to start cleaning using Tuya Local.
Starting cleaning using the app, I see the following attribute changes:
Power: false -> true
Command: return_to_base -> smart
The "Activate" attribute stays false.
When cleaning has been started, the▶️ button will change the vacuum to "status: paused".
When the vacuum is "status: paused", the ⏸️ button will resume cleaning.
Expected behavior▶️ button will start or resume cleaning.
The
The ⏸️ button will pause cleaning or returning to dock.
Device diagnostics
The text was updated successfully, but these errors were encountered: