dreame.vacuum.r2228o: Can't set Customized Cleaning anymore

stony2k commented 2 years ago

Describe the bug Can't set Customized Cleaning anymore via datapoint switch.dreamebot_l10s_ultra_customized_cleaning. If I switch it in, it switches itself off. If I switch it on in the Mi Home app, Home Assistant doesn't seem to recognize it.

To Reproduce Try to swith the entity switch.dreamebot_l10s_ultra_customized_cleaning

Expected behavior The switch should stay swiched on

Additional Information (please complete the following information)

Model Name: dreame.vacuum.r2228o
Firmware Version: 4.3.3_1121
Home Assistant Version: 2022.10.5
Configuration Type [With or without map support]: with map support
Errors or warnings shown in the HA logs (if applicable): -

Tasshack commented 2 years ago

Can you update the log level to info from your configuration.yaml and share the logs after turning on the Customized Cleaning setting?

logger:
  logs:
    custom_components.dreame_vacuum: info

stony2k commented 2 years ago

I hope I did everything right. Its in German, maybe I should change my system langue first?

A lot of entities seem not to be available anymore, strange.

DreameBot L10s Ultra Customized Cleaning ausgeschaltet ausgelöst durch Dienst switch.turn_off 11:24:51 - Vor 1 Minute - Stony DreameBot L10s Ultra Cleaning Times Primary Bedroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Primary Bedroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Primary Bedroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Cleaning Times Corridor nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Corridor nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Corridor nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Cleaning Times Kitchen nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Kitchen nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Kitchen nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Cleaning Times Living Room nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Living Room nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Living Room nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Cleaning Times Study nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Study nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Study nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Cleaning Times Bathroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity Bathroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level Bathroom nicht mehr verfügbar 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Mop Pad Humidity wechselte zu Feucht 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Suction Level wechselte zu Standard 11:24:51 - Vor 1 Minute DreameBot L10s Ultra Customized Cleaning eingeschaltet ausgelöst durch Dienst switch.turn_on 11:24:50 - Vor 1 Minute - Stony

Tasshack commented 2 years ago

I think i broke something on the latest release. You should see some errors or warnings on the full log, otherwise it is impossible for me to understand reason of the problem.

stony2k commented 2 years ago

Sorry I am new to Home Assistant :)

The log i very huge I tried to pick the right spot. Hope you can make sense of it :)

I worked approximately one week before. Maybe the second last update broke it, but this is more suggested.

Tasshack commented 2 years ago

I can see the transport layer debug logs but there are logs regarding the dreame_vacuum. Did you restart HA after updating the log level from the configuration.yaml?

If your HA is running on linux, you can use this command to filter and list the necessary logs. (You may need to change the log file path) grep -r dreame /home/homeassistant/.homeassistant/home-assistant.log | grep -i dreame

Alternatively, you can share the complete log file directly.

stony2k commented 2 years ago

Yes I restarted HA and saving the file (edited with nano). This is my configuration.yaml (I am using docker):

# Loads default set of integrations. Do not remove.
default_config:

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

logger:
  logs:
    custom_components.dreame_vacuum: info

You command showed me the same log as I have posted, with the same huge amount of entries. So I deleted it (don't know if this was smart). And turned the customized cleaning back on. Now it stays on. But this makes no sense to me.

Should I delete the device i the integration and add it again?

Tasshack commented 2 years ago

Yes, can you try to delete and add the device again to check all entites created as before?

stony2k commented 2 years ago

Good point. How do I delete the device? Disable it or delete the hole integration?

Bildschirmfoto 2022-11-05 um 12 14 49

Edit: Deleted the integration and added the vacuum again (seems to be quicker). Well everything works as intented. I think you can close the issue or do you want to do additional testing? Its very strange that the issue seems to be solved by deleting the log (via ssh).

Tasshack commented 2 years ago

You can delete the device from the integrations page.

delete

Tasshack commented 2 years ago

@stony2k I will close this issue if the problem no longer exists.

stony2k commented 2 years ago

Ok. I can reopen it if the issue occurs again.

Tasshack / dreame-vacuum

dreame.vacuum.r2228o: Can't set Customized Cleaning anymore #32