I just restarted HA and tried to install the Dreame integration via HACS again. Same error, and there is no log entry in the System log.
If there some HACS specific logging I can check?
I just restarted HA and tried to install the Dreame integration via HACS again. Same error, and there is no log entry in the System log.
If there some HACS specific logging I can check?
Thanks a lot man! Itâs alive!!
ok, I think I solved this. I used the âDownloadâ button in the bottom right instead of the âAdd IntegrationâŚâ button inside the help text. This works and brings up the dialog to select the different versions.
v2.0.0b11 has been released with some fixes and new features.
switch.streaming_voice_prompt
: For disabling the voice alerts when live streaming.sensor.cleaning_progress
: Current cleaning task progress in percent.sensor.drying_progress
: Drying progress in percent.button.start_recleaning
: Start second cleaning. (When CleanGenius detects that a room has not been cleaned enough)select.custom_mopping_route
: For controlling the Mopping Effect feature. (thanks to @kimagure)Hello. I have a DreameBot S10 Plus (R2246) that I have added and created a vacuum card. with vacuum platform as tasshack/dreame-vacuum. I tried starting the vacuum but I am getting this error⌠could you please kindly advise?
This error originated from a custom integration.
Logger: custom_components.dreame_vacuum.dreame.device
Source: custom_components/dreame_vacuum/dreame/device.py:2745
Integration: Dreame Vacuum (documentation, issues)
First occurred: 10:49:22 PM (2 occurrences)
Last logged: 10:52:01 PMSend action failed START (None): {âaiidâ: 1, âcodeâ: -1, âdidâ: â2.1â, âsiidâ: 2}
I have another R2210 and⌠seems like there are not issues for that one when using the same platform. many thanks!
I am on beta version (as R2210 only supported in beta)
It is probably because of Region Locking
from firmware.
You can confirm this by;
Nation Matched
vacuum attribute.thank you. yes i have trouble accessing it on the app due to region lock!
i checked, nation is mismatched,
i bought it from china and canât access on the app. i was hoping i could control via this. any way to resolve it?
Edit: i searched the topic again and found that you say there is no way to bypass it⌠arghâŚ
Surely there might be other solutions out there but this integration cannot be used for that purpose.
thank you.
how about this error?
This error originated from a custom integration.
Logger: custom_components.dreame_vacuum
Source: helpers/update_coordinator.py:406
Integration: Dreame Vacuum (documentation, issues)
First occurred: 9:38:13 PM (1 occurrences)
Last logged: 9:38:13 PM
Error requesting dreame_vacuum data: Unable to discover the device over cloud
This error originated from a custom integration.
Logger: custom_components.dreame_vacuum.dreame.protocol
Source: custom_components/dreame_vacuum/dreame/protocol.py:1040
Integration: Dreame Vacuum (documentation, issues)
First occurred: 9:37:23 PM (7 occurrences)
Last logged: 9:46:41 PM
Error while executing request: https://api.io.mi.com/app/v2/home/rpc/639156562 HTTPSConnectionPool(host=âapi.io.mi.comâ, port=443): Read timed out. (read timeout=5)
There are too many reason for this error but basically your server cannot reach to the device over cloud.
may i please know why is there no support for L10 Ultra
It is supported on Beta.
This might not be the right thread for this, but I didnât really find a better one.
In my home network, I create separate VLANs with separate subnets for devices that should be blocked from the internet and for cloud devices that should be allowed to talk to the internet, Home Assistant, and nothing else.
The cross-subnet communication problem essentially means that I need to place the vacuum (a Dreame L10 Ultra) on my main untagged VLAN. I have a Unifi router that allows me to define per-device rules, which is a little trickier than having it under the umbrella of the separate VLAN.
Does anyone have any experience with this integration blocking the vacuum from the rest of their network, and preferably the cloud? If so, what is your preferred method for accomplishing this and what are the tradeoffs?
Is there a way to change the custom cleaning settings for cleaning mode by room?
I set it to sweep only and it started cleaning the mop pads of my L10s ultra as the current customized cleaning in the Mi home app has sweep and mop for the dining hall and kitchen.
We do not mop these rooms every day and switching to the mihome app to change the cleaning mode for a specific room is not ideal.
Even a room set to sweep only in mihome app will start cleaning the mop pads and attempt to mop.
What is the entity for âSensors must be cleanedâ notification? I would like to use it as a trigger in an automation.
Try the Beta.
Using state trigger, selecting my vacuum entity, I only have âsensor dirty leftâ and âsensor dirty time leftâ attributes available
You cannot use state trigger for that purpose thatâs why I have posted the documentation link for events.