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
After updating Homeassistant to Core 12.5 (I tried from 12.0 upwards the last weeks), my Deebot is not working any logner.
I followed the discussions about the update from 12.0 on and I would kindly ask if somebode can configure the DEEBOT X2S BLACK (3u90zu) into the Ecovacs solution.
Now, after updating to Homeassistant Core 12.5 I got my Deebot running by using the workaround (#632 (comment)), but I think this should not be the solution for forever.
On which deebot device (vacuum) you have the issue?
DEEBOT X2S BLACK (3u90zu)
Which version of the deebot-client are you using?
9.4.0 (I hope this is right, searched a longer time and found it in Ecovacs AddIn Diagnostics)
Country
CN
Continent
NA
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Checks
The problem
After updating Homeassistant to Core 12.5 (I tried from 12.0 upwards the last weeks), my Deebot is not working any logner.
I followed the discussions about the update from 12.0 on and I would kindly ask if somebode can configure the DEEBOT X2S BLACK (3u90zu) into the Ecovacs solution.
I am sorry, but I do not know how to add my device type to the library (https://github.com/DeebotUniverse/client.py).
Now, after updating to Homeassistant Core 12.5 I got my Deebot running by using the workaround (#632 (comment)), but I think this should not be the solution for forever.
On which deebot device (vacuum) you have the issue?
DEEBOT X2S BLACK (3u90zu)
Which version of the deebot-client are you using?
9.4.0 (I hope this is right, searched a longer time and found it in Ecovacs AddIn Diagnostics)
Country
CN
Continent
NA
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: