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

Ecovacs model no longer supported in HA 2024.12+ #132335

Open
sleveille4 opened this issue Dec 5, 2024 · 97 comments
Open

Ecovacs model no longer supported in HA 2024.12+ #132335

sleveille4 opened this issue Dec 5, 2024 · 97 comments

Comments

@sleveille4
Copy link

sleveille4 commented Dec 5, 2024

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?

Logger: homeassistant.components.ecovacs.controller
Source: components/ecovacs/controller.py:100
integration: Ecovacs (documentation, issues)
First occurred: December 4, 2024 at 21:40:59 (2 occurrences)
Last logged: 07:50:16

Device "DEEBOT T9+" not supported. Please add support for it to https://github.com/DeebotUniverse/client.py: ...
Device "DEEBOT T9+" not supported. Please add support for it to https://github.com/DeebotUniverse/client.py: ...

Additional information

No response

@sleveille4 sleveille4 changed the title Debout t9+ not supported Debout t9+ no longer supported Dec 5, 2024
@sleveille4 sleveille4 changed the title Debout t9+ no longer supported Ecovacs Deebot t9+ no longer supported Dec 5, 2024
@home-assistant
Copy link

home-assistant bot commented Dec 5, 2024

Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration (ecovacs) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecovacs 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 ecovacs Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


ecovacs documentation
ecovacs source
(message by IssueLinks)

@lu-x
Copy link

lu-x commented Dec 5, 2024

Same for DEEBOT N8+ for me

@zecko8
Copy link

zecko8 commented Dec 5, 2024

Same for ECOVACS T30S and ECOVACS T30S COMBO in my case

@mib1185
Copy link
Contributor

mib1185 commented Dec 5, 2024

See the Backward-incompatible changes in the release notes

@sleveille4
Copy link
Author

sorry but those models are not old,
it's not acceptable that they would stop working when they did previously.
also, the release note does not list no longer working nor working devices, how are we supposed to know?

@edenhaus
Copy link
Contributor

edenhaus commented Dec 5, 2024

Ecovacs is not providing any public API information. Please blame them to don't publish it.
As the fallback vacuum model created more issues especially with newer models, I as code owner decided to remove the fallback. 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.

@sleveille4
Copy link
Author

while i appreciate that they don't provide API,

it was working, and has been without issue for a year.
it is no longer working.
this happen following your change.

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?

@edenhaus
Copy link
Contributor

edenhaus commented Dec 5, 2024

See DeebotUniverse/client.py#612

when will my 600€ device will work again?

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.
Feel free to add your model by yourself or wait until someone else will add if for you. You can also write Ecovacs saying that for the 600€ they should support for your model in HA

@edenhaus edenhaus changed the title Ecovacs Deebot t9+ no longer supported Ecovacs model no longer supported in HA 2024.12+ Dec 5, 2024
@miljw002
Copy link

miljw002 commented Dec 5, 2024

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.

@enter2name
Copy link

enter2name commented Dec 5, 2024

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:
As it seems the device was never in the library. I try to get some time soon and help adding it to the clients.

@Richard-EnglishUK
Copy link

N8 & N20+ not functioning. :(

@elpigeondindo
Copy link

T30s Pro omni don't be reconize too 😭

@Jimtb
Copy link

Jimtb commented Dec 5, 2024

DEEBOT OZMO T8+ also not supported anymore 😢

@Hichiro6
Copy link

Hichiro6 commented Dec 5, 2024

OT8 not supported anymore, any way to help finding a solution?

@drBeam
Copy link

drBeam commented Dec 5, 2024

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.

@compoundbow83
Copy link

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?

@Richard-EnglishUK
Copy link

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 sure the change was made for a good reason, but suspect the size of the consequence was not appreciated. My Deebot is only a couple of months old - a newish model - if mine's affected, I'm guessing most models are.
Hopefully the change can be cancelled for a while to give time for whatever steps are needed.

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.

@treardon17
Copy link

I can confirm the Deebot X1 Plus is no longer working.

@manbeast76
Copy link

The N8 Pro and N8 Pro+ are also not working.

@bazzyo07
Copy link

bazzyo07 commented Dec 6, 2024

N10 is no longer working.

@monik3r
Copy link

monik3r commented Dec 6, 2024

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)

@compoundbow83
Copy link

compoundbow83 commented Dec 6, 2024

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.

@mislav
Copy link

mislav commented Dec 6, 2024

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:

  • Deebot N8, N8+, N8 PRo+, N8 PRo+ Black
  • Deebot T10
  • Deebot X1 Omni
  • Deebot N30 Omni
  • Deebot T9 AIVI
  • Deebot OZMO T9 AIVI
  • Deebot Ozmo T8G

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.

@eight10man
Copy link

I'm very confused how my OZMO T8 AIVI stopped being supported.
In the original Deebot 4 Home Assistant integration this robot was one of the original supported ones. And also under "client.py/deebot_client/hardware/deebot" this robot should be supported through x5d34r.py.
Can the robot please be re-added?

@mib1185
Copy link
Contributor

mib1185 commented Dec 11, 2024

@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 👍

@rhys-e2
Copy link

rhys-e2 commented Dec 11, 2024

@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.

@edenhaus
Copy link
Contributor

edenhaus commented Dec 11, 2024

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.
The library currently supports a third of all models

@ostseereiter1
Copy link

My DEEBOT T30S PRO is not working either.

@jan-wern
Copy link

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

@Thunderbird1982
Copy link

hello is it possible to integrate the ecovacs t10 turbo thanks for your help

@katagia
Copy link

katagia commented Dec 12, 2024

For those whose robot doesn’t work again:
Maybe you should post the model id which is meant in the error log?
I would assume that in most cases the solution is to create a symlink with the model id in the name.

As there are do many models, the developers can’t guess it.

@jan-wern
Copy link

For those whose robot doesn’t work again: Maybe you should post the model id which is meant in the error log? I would assume that in most cases the solution is to create a symlink with the model id in the name.

As there are do many models, the developers can’t guess it.

DEEBOT N8 PRO CARE
class': 's1f8g7
UILogicId': 'DT_8SE_G

@zecko8
Copy link

zecko8 commented Dec 12, 2024

Hello, my DEEBOT T30S combo is not working.
Can sameone post a guide to create the symlink for test?
My deebot class is: 9gqyaq

@elpigeondindo
Copy link

I created a fork but does anyone have any explanations on the capabilities?

from deebot_client.capabilities import (
    Capabilities,
    CapabilityClean,
    CapabilityCleanAction,
    CapabilityCustomCommand,
    CapabilityEvent,
    CapabilityExecute,
    CapabilityLifeSpan,
    CapabilityMap,
    CapabilitySet,
    CapabilitySetEnable,
    CapabilitySettings,
    CapabilitySetTypes,
    CapabilityStats,
    DeviceType,
)

from deebot_client.events import (
    AdvancedModeEvent,
    AvailabilityEvent,
    BatteryEvent,
    CachedMapInfoEvent,
    CarpetAutoFanBoostEvent,
    CleanCountEvent,
    CleanLogEvent,
    CleanPreferenceEvent,
    ContinuousCleaningEvent,
    CustomCommandEvent,
    ErrorEvent,
    FanSpeedEvent,
    FanSpeedLevel,
    LifeSpan,
    LifeSpanEvent,
    MajorMapEvent,
    MapChangedEvent,
    MapTraceEvent,
    MultimapStateEvent,
    NetworkInfoEvent,
    PositionsEvent,
    ReportStatsEvent,
    RoomsEvent,
    StateEvent,
    StatsEvent,
    TotalStatsEvent,
    TrueDetectEvent,
    VolumeEvent,
    WaterAmount,
    WaterInfoEvent,
    WorkMode,
    WorkModeEvent,
)

I would like to understand them to know if I can add them to my vacuum cleaner, to avoid as many bugs as possible

@zminde
Copy link

zminde commented Dec 12, 2024

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.

@ponG86
Copy link

ponG86 commented Dec 13, 2024

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.

@jan-wern
Copy link

Can you please poste the steps Here how to syslink?

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.

@bazzyo07
Copy link

Can the N10 be added to the integration please?

N10 is working now after the latest update. Thanks to everyone who made this possible!

@edenhaus
Copy link
Contributor

With HA 2024.12.3, another 34 models were added. More information can be found at https://github.com/DeebotUniverse/client.py/releases/tag/9.4.0

@jan-wern
Copy link

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.

With HA 2024.12.3, another 34 models were added. More information can be found at https://github.com/DeebotUniverse/client.py/releases/tag/9.4.0

@marcolino7
Copy link

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.

With HA 2024.12.3, another 34 models were added. More information can be found at https://github.com/DeebotUniverse/client.py/releases/tag/9.4.0

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.
Please perform a backup o a snapshot of your HA installation, you use these commands at your own risk.
This should get your bot back to life for use, meanwhile you can or create a PR to add your bot to future release or open an Issue Here so someone could take care of your request.

Marco

@elpigeondindo
Copy link

after doing the fork and moving into the Dev branch, update 2024.12.3 allowed me to recover my T30s Pro under home assistant 😁😁😁😁

@TwoB33RS
Copy link

TwoB33RS commented Dec 15, 2024

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"
UILogicId': 'D_900',
'product_category': 'DEEBOT', 'model': 'DN5G',

@msavazzi
Copy link
Contributor

Thank you for adding back the Ozmo T8.
By any chance you think is possible to add the DEEBOT OZMO Slim10 Series (02uwxm) ?

M

@marcolino7
Copy link

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" UILogicId': 'D_900', 'product_category': 'DEEBOT', 'model': 'DN5G',

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

@TwoB33RS
Copy link

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" UILogicId': 'D_900', 'product_category': 'DEEBOT', 'model': 'DN5G',

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)

@marcolino7
Copy link

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" UILogicId': 'D_900', 'product_category': 'DEEBOT', 'model': 'DN5G',

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

@afurei
Copy link

afurei commented Dec 16, 2024

我也遇到了这样的问题。我是今天从2024.10.2升级到了2024.12.3 的HA版本,升级后,所有的ECO功能全部失灵了

@edenhaus
Copy link
Contributor

@afurei, we are an English-speaking community, so please rewrite your comment in English so the community can adequately help with your issue.
thx 👍

@nblasgen
Copy link

nblasgen commented Dec 16, 2024

Ecovac Client 9.4.0 doesn't support 4bdkrs yet (T30S Combo). My ticket in the correct project -- DeebotUniverse/client.py#683

{
  "did": "b10f90fe-7c34-457a-b240-228da84XXXXX",
  "name": "E04A35520F1FPMAXXXXX",
  "class": "4bdkrs",
  "resource": "sJ7G",
  "company": "eco-ng",
  "bindTs": 1719599632965,
  "service": {
    "jmq": "jmq-ngiot-na.dc.ww.ecouser.net",
    "mqs": "api-ngiot.dc-na.ww.ecouser.net"
  },
  "deviceName": "DEEBOT T30S COMBO",
  "icon": "https://portal-ww.ecouser.net/api/pim/file/get/660d039b31620d56505fbb9b",
  "ota": true,
  "UILogicId": "t30combo_ww_h_t30h5",
  "materialNo": "110-2362-0202",
  "pid": "65d44b5a478cc87bfc551ab2",
  "product_category": "DEEBOT",
  "model": "T30_COMBO_INT_BLACK",
  "updateInfo": {
    "needUpdate": false,
    "changeLog": ""
  },
  "nick": null,
  "homeId": "629ac6ff8b5c674d9b6XXXXX",
  "homeSort": 1,
  "status": 1,
  "offmap": true,
  "btName": "ECOVACS-4bdkrs-0419",
  "btMac": "A8:96:09:XX:XX:XX",
  "otaUpgrade": {}
}

@msavazzi
Copy link
Contributor

Thank you for adding back the Ozmo T8. By any chance you think is possible to add the DEEBOT OZMO Slim10 Series (02uwxm) ?

M

From here: https://deebot.readthedocs.io/home/models/
I've seen that the Ozmo Slim is supported but not in HA. Is there a way we can move it? is there any way I can help?

@edenhaus
Copy link
Contributor

Thank you for adding back the Ozmo T8. By any chance you think is possible to add the DEEBOT OZMO Slim10 Series (02uwxm) ?

M

From here: https://deebot.readthedocs.io/home/models/
I've seen that the Ozmo Slim is supported but not in HA. Is there a way we can move it? is there any way I can help?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests