Removal of working Deebot N10 support after update

[slartibartfast11]

The problem

My Deebot N10 was working perfectly until the 2024.12.0 update, even though it was apparently using the "generic vacuum" driver. Now, the integration reports the vacuum to be unsupported.

What version of Home Assistant Core has the issue?

core-2024.12.0

What was the last working version of Home Assistant Core?

No response

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

Logger: homeassistant.components.ecovacs.controller
Source: components/ecovacs/controller.py:100
integration: Ecovacs (documentation, issues)
First occurred: 09:20:50 (3 occurrences)
Last logged: 09:28:14

Device "DEEBOT N10" not supported. Please add support for it to https://github.com/DeebotUniverse/client.py: {'did': 'f5172d90-6717-4189-ba4b-e35a7118442f', 'name': 'E24P17524E00YM7Y0003', 'class': 'm1wkuw', 'resource': 'gaIh', 'company': 'eco-ng', 'bindTs': 1698056694757, 'service': {'jmq': 'jmq-ngiot-na.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-na.ww.ecouser.net'}, 'deviceName': 'DEEBOT N10', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/63e1e022d775e750ca44246b', 'ota': True, 'UILogicId': 't8_ww_n_nobel', 'materialNo': '110-2241-0201', 'pid': '635b46fc7fe5cb6124de84da', 'product_category': 'DEEBOT', 'model': 'NOBEL_INT', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': 'Singularity', 'homeId': 'XXX', 'homeSort': 1, 'status': 1, 'offmap': True, 'otaUpgrade': {}}

Logger: deebot_client.api_client
Source: components/ecovacs/controller.py:81
First occurred: 09:20:50 (3 occurrences)
Last logged: 09:28:14

Device class "m1wkuw" not recognized. Please add support for it: {'did': '[REMOVED]', 'name': 'E24P17524E00YM7Y0003', 'class': 'm1wkuw', 'resource': 'gaIh', 'company': 'eco-ng', 'bindTs': 1698056694757, 'service': {'jmq': 'jmq-ngiot-na.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-na.ww.ecouser.net'}, 'deviceName': 'DEEBOT N10', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/63e1e022d775e750ca44246b', 'ota': True, 'UILogicId': 't8_ww_n_nobel', 'materialNo': '110-2241-0201', 'pid': '635b46fc7fe5cb6124de84da', 'product_category': 'DEEBOT', 'model': 'NOBEL_INT', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': 'Singularity', 'homeId': 'XXX', 'homeSort': 1, 'status': 1, 'offmap': True, 'otaUpgrade': {}}

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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)}}

[edenhaus]

See DeebotUniverse/client.py#612

[slartibartfast11]

The umwv6z.py N10 Plus driver for my similar N10 model appears work fine in my limited testing so far.

[Mod74]

The umwv6z.py N10 Plus driver for my similar N10 model appears work fine in my limited testing so far.

I have an N10 that's stopped. Is using the umwv6z.py N10 Plus driver a change I can make? I'm not sure any files that need editing would be.