#ecovacs support broken

5 messages · Page 1 of 1 (latest)

young bear
#

My ecovacs t9+ integration was working just fine, but with 2024.12 it no longer is. WTF guys! I understand the need to drop non-working integrations but why break the stuff that was working???? Is there a work-around? No word in the docs.

2024-12-05 15:30:16.801 WARNING (MainThread) [deebot_client.api_client] Device class "um2ywg" not recognized. Please add support for it: {'did': '[REMOVED]', 'name': 'E09G00724C09HKEW0291', 'class': 'um2ywg', 'resource': 'KjsJ', 'company': 'eco-ng', 'bindTs': 1717142168835, 'service': {'jmq': 'jmq-ngiot-eu.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-eu.ww.ecouser.net'}, 'deviceName': 'DEEBOT T9+', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/608b997e17c95b0008ff221f', 'ota': True, 'UILogicId': 'T9_PRO_G', 'materialNo': '110-2010-1102', 'pid': '608b9981fc527c00087fddf1', 'product_category': 'DEEBOT', 'model': 'T9_PLUS_ECO_INT', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': 'bobik', 'homeId': '626dd46d63a68e33483881e3', 'homeSort': 1, 'status': 1, 'offmap': True, 'otaUpgrade': {}}

2024-12-05 15:30:16.804 WARNING (MainThread) [homeassistant.components.ecovacs.controller] Device "DEEBOT T9+" not supported. Please add support for it to https://github.com/DeebotUniverse/client.py: {'did': '7200c027-78fa-44d7-a692-9cbb4268b847', 'name': 'E09G00724C09HKEW0291', 'class': 'um2ywg', 'resource': 'KjsJ', 'company': 'eco-ng', 'bindTs': 1717142168835, 'service': {'jmq': 'jmq-ngiot-eu.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-eu.ww.ecouser.net'}, 'deviceName': 'DEEBOT T9+', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/608b997e17c95b0008ff221f', 'ota': True, 'UILogicId': 'T9_PRO_G', 'materialNo': '110-2010-1102',
'pid': '608b9981fc527c00087fddf1', 'product_category': 'DEEBOT', 'model': 'T9_PLUS_ECO_INT', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': 'bobik', 'homeId': '626dd46d63a68e33483881e3', 'homeSort': 1, 'status': 1, 'offmap': True, 'otaUpgrade': {}}

rigid plinth
#

So is there a solution for this issue, running into same issue

#

they should of left it as a hacs integration if they were going to do this

compact totem
#

hmm wait I ve just opened a ticket but maybe my issue is the same as yours

young bear