-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
Ecovacs model no longer supported in HA 2024.12+ #132335
Comments
Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) ecovacs documentation |
Same for DEEBOT N8+ for me |
Same for ECOVACS T30S and ECOVACS T30S COMBO in my case |
See the Backward-incompatible changes in the release notes |
sorry but those models are not old, |
Ecovacs is not providing any public API information. Please blame them to don't publish it. |
while i appreciate that they don't provide API, it was working, and has been without issue for a year. when will my 600€ device will work again? how to get it working? how to activate back on my HA the fallback vaccum? "Now you get a log entry saying your model is not supported and also the attention to improve the expercience with the model by added it to the library." what does this even mean? |
See DeebotUniverse/client.py#612
You paid the 600€ to Ecovacs and not to any code owner of this integration. We are maintaining it in our free time for free. |
It appears that the ECOVACS OZMO T8 is now also no longer working with the integration. It's also been happily working well for many years until this update. |
Can confirm Ecovacs DEEBOT X1 OMNI is also not longer working. Some entities were unreachable. I deleted the integration and re-integrated it, now it can't find any device at all. Edit: |
N8 & N20+ not functioning. :( |
T30s Pro omni don't be reconize too 😭 |
DEEBOT OZMO T8+ also not supported anymore 😢 |
OT8 not supported anymore, any way to help finding a solution? |
Hi, i understand that you have no ability to test for unsupported vacuums, however would it be possible to at least give users the option to enable this fallback vacuum again? This breaks the addon for many users who had no issues at all using this fallback vacuum including me. |
I have the Ecovacs Deebot T9+ and I don´t know how to fix this problem at the moment for my self. Can anyone tell me to fix it? |
A backup of your system is created by default when you update HA, so you can roll back the change quite easily and all will be as before. That's what I've done. If you update HA in the future the problem will recur until the issue is sorted. So best not to. I'm going to write to Ecovacs and suggest they take a role in HA's integration. Being a robotics company I'd have hoped they could see the benefit of working with HA. Maybe others affected by this problem would also contact Ecovacs helpdesk??? In the meantime.... it's in HA's court how they want to support their users. |
I can confirm the Deebot X1 Plus is no longer working. |
The N8 Pro and N8 Pro+ are also not working. |
N10 is no longer working. |
While it is frustrating when things break, there is a pretty useful comment on how to add support for your vacuum model if features previously worked in the integration at DeebotUniverse/client.py#612 (comment) |
It seems that pretty much all models are affected here. And I just don't understand the information about how to help solve the problem. I know that I can of course restore a backup. But I don't think that not doing an HA update is a solution either, especially because you don't know when the Ecovacs problem will be solved. Above all, I still don't understand how these PRs end up in HA, since this is a core integration. I am well aware that Home Assistant is open source software, but I still find this approach of leaving almost all users out in the cold a bit strange. |
Hi all, @edenhaus and the community have been hard at work to add support for Ecovacs models negatively affected by the change in HA 2024.12, and there is currently a pull request that should hopefully be a part of the next HA update: #132467 The update will add support for the following models:
Please be patient while the update rolls out, and remember to be kind to maintainers of this integration. Since Ecovacs does not provide any API information for their vacuum models, it's actually really complex to maintain the HA integration given the number and the diversity of Ecovacs' offerings. |
I'm very confused how my OZMO T8 AIVI stopped being supported. |
@JeandreCoetzer @mclausha1 please follow #132335 (comment), if you your're not able to do this on your own, than please raise an issue to the https://github.com/DeebotUniverse/client.py repo and ask for help to add support for your bot - as you can see in the history of this issue there are a lot of contributers adding support for bots. @eight10man please open an own issue report, when your bot should already be supported, but isn't, than we need to check this, thx 👍 |
@eight10man This is probably a similar case to my PR. In my case, I have a T8+ and although there was already support for that model, it wasn't being picked up because it's 'class' identifier was slightly different (the same models can have a different identifier based on slight variations, regions, etc). Your HA integration will be giving you a log output similar to this. As @mib1185 mentioned, have a look at opening a pull request for your specific class; in your case, this would probably be a case of linking the existing T8 AIVI file to a new file with your class name. Otherwise, posting your class name alongside your vacuum model in the issue you open would probably be most helpful to the devs. |
Ecovacs currently has more than 235 different models. The library contained a forgotten API call to get the product map. With that map, I could add another 24 models in DeebotUniverse/client.py#666, as the model name matched with an already-added model. |
My DEEBOT T30S PRO is not working either. |
Hello, now i am on 2024.12.2, so the deebot N8+ pro should work again, but it don't. I do not understand wich File i have to change. Thx for help |
hello is it possible to integrate the ecovacs t10 turbo thanks for your help |
For those whose robot doesn’t work again: As there are do many models, the developers can’t guess it. |
DEEBOT N8 PRO CARE |
Hello, my DEEBOT T30S combo is not working. |
I created a fork but does anyone have any explanations on the capabilities?
I would like to understand them to know if I can add them to my vacuum cleaner, to avoid as many bugs as possible |
I have the same problem. After upgrading Home Assistant to 2024.12, my Ecovacs T8 can no longer be used. After checking the author's GitHub, I was completely lost. It was almost impossible to manually fix it according to the prompts with my ability. So I ran another previous version of HomeAssistant virtual machine, only running Ecovacs integration, and then used Remote Home Assistant integration to add the vacuum cleaner entity to Home Assistant OS version 12. Although this method is very clumsy and even stupid, it may be the easiest way to continue using Ecovacs vacuum cleaners in the new version of Home Assistant with my ability. |
Deebot N8 Black is also not working. The device class is "7zya6u". Should be functionally the same as N8, which is also already listed. I'll try to figure out how to symlink that on the weekend. |
Can you please poste the steps Here how to syslink?
|
N10 is working now after the latest update. Thanks to everyone who made this possible! |
With HA |
So my N8+ pro ist Not still working. I am really disappointed and do not understand why abtwo year old device is listed out. I ready somethink about a symlink but No Guide how to do this.
|
Hi Here ia a guide for other models to temporary make your bot working. You have to know your device class, and a device class of a compatible bot and adjust symlink command at your need. The 1st file in symlink command is one of the working bot, the other file would be yourdeviceclass.py. Marco |
after doing the fork and moving into the Dev branch, update 2024.12.3 allowed me to recover my T30s Pro under home assistant 😁😁😁😁 |
Hi all, i'm using a deebot 901 , an os 13.2 and core 24.11.3 , and it breaks Yesterday without any changes. I will now test upgrade my HA an check if its working again on my system too. Update: its not working, sure ... my bot is not listed , so my next step should be collecting the needed data and creating the .py file. But i`m really feeling lost to this fork process and all this github things, normally i just reading 😂 can someone assist Device class "ls1ok3" |
Thank you for adding back the Ozmo T8. M |
my suggestion is to take a failover.py from old version, starting renaming this and test. If your bot is not working, perhaps it use a fallback before 2024.12 upgrade. Marco |
Thanks Marco, you mean that i should test it local. I dont find this files/folder (not with file editor or smb share , even not in the backupfile) |
You can find file in github repository for the project Here selecting old version, then you can access to HA console and try this changing filename accordly. Otherwise if you are not sure, open a Issue on project repository here, and wait someone with your bot make a pull request. Marco |
我也遇到了这样的问题。我是今天从2024.10.2升级到了2024.12.3 的HA版本,升级后,所有的ECO功能全部失灵了 |
@afurei, we are an English-speaking community, so please rewrite your comment in English so the community can adequately help with your issue. |
Ecovac Client 9.4.0 doesn't support
|
From here: https://deebot.readthedocs.io/home/models/ |
You are referring the javascript integration, which cannot be used in HA. So to bring support for your bot to HA, you need to check, which commands are missing and add them. Also you need to add the capabilities file of your bot |
The problem
Since update, deebot t9+ IS nonlonger working and log reports device no longer supported
What version of Home Assistant Core has the issue?
2024.12.0
What was the last working version of Home Assistant Core?
2024.11.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Ecovacs
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: