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

Missing RoborockMopModeS8ProUltra code: 302 #96707

Closed
Gloomyeye opened this issue Jul 16, 2023 · 6 comments · Fixed by #96877
Closed

Missing RoborockMopModeS8ProUltra code: 302 #96707

Gloomyeye opened this issue Jul 16, 2023 · 6 comments · Fixed by #96877

Comments

@Gloomyeye
Copy link

The problem

Hello,

my Roborock S8 creates a warning in the log. I don't know when the code will be created.

What version of Home Assistant Core has the issue?

core-2023.7.2

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

roborock

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: roborock.code_mappings
Source: runner.py:179 
First occurred: 14:48:10 (285 occurrences) 
Last logged: 17:10:11

Missing RoborockMopModeS8ProUltra code: 302 - defaulting to 300

Additional information

No response

@home-assistant
Copy link

Hey there @humbertogontijo, @Lash-L, mind taking a look at this issue as it has been labeled with an integration (roborock) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roborock 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 roborock Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


roborock documentation
roborock source
(message by IssueLinks)

@Lash-L
Copy link
Contributor

Lash-L commented Jul 16, 2023

What were your mop settings in the app when this happened?

What are all your potential mop modes

@Gloomyeye
Copy link
Author

I created an individual cleaning plan for my rooms. I selected the following settings in the app:
Vac & Mop: "Saugleistung Normal" and "Wischintensität Mittel" for one area, the second area Vac & Mop "Saugleistung normal", "Wischintensität Intensiv".

@Gloomyeye
Copy link
Author

This are the individual settings of the roborock app:
IMG_9415

These are the general settings:
IMG_9412

IMG_9413

IMG_9414

Background:
Modell: roborock.vaccum.a70
Firmware: 02.16.72

@Lash-L
Copy link
Contributor

Lash-L commented Jul 16, 2023

And when you are on those various settings which are causing you to have that issue?

Can you look here: humbertogontijo/homeassistant-roborock#261

And see how your s8 compares to the other s8 data commented

@Gloomyeye
Copy link
Author

Regarding this: humbertogontijo/homeassistant-roborock#261 (comment)
The setting "custom" is missing here:

Home Assistant Roborock App
null Fast
standard Standard
deep Deep
deep_plus Deep+
custom custom

My Home Assistant mop select shows that:

Bildschirmfoto 2023-07-17 um 10 50 40

The debugging gets the following response:
2023-07-17 10:51:07.105 DEBUG (MainThread) [roborock.cloud_api] id=14467 Response from get_status: {'msg_ver': 2, 'msg_seq': 184, 'state': 8, 'battery': 100, 'clean_time': 1593, 'clean_area': 25245000, 'error_code': 0, 'map_present': 1, 'in_cleaning': 0, 'in_returning': 0, 'in_fresh_state': 1, 'lab_status': 3, 'water_box_status': 1, 'fan_power': 106, 'dnd_enabled': 0, 'map_status': 3, 'is_locating': 0, 'lock_status': 0, 'water_box_mode': 204, 'water_box_carriage_status': 1, 'mop_forbidden_enable': 1, 'adbumper_status': [0, 0, 0], 'water_shortage_status': 0, 'dock_type': 0, 'dust_collection_status': 0, 'auto_dust_collection': 1, 'mop_mode': 302, 'debug_mode': 0, 'dock_error_status': 0, 'unsave_map_reason': 0, 'unsave_map_flag': 1}

@github-actions github-actions bot locked and limited conversation to collaborators Aug 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants