-
Notifications
You must be signed in to change notification settings - Fork 64
Cant connect to Ecovacs(Deebot) T50 Omni #152
Description
Hello, i recently installed the package with docker on a raspberry pi 4 (10.10.50.200).
So far it works fine and homeassistant (10.10.50.50) can connect without any problems.
In my Router (Unifi UDM Pro SE) i have set up the required dns redirects (ecovacs domains) and also noticed that the vacuum is trying to reach some other Ip adresses in china wich i then have also blocked.
Now i have the Problem that my vaccum is not showing up in bumper and is also not controllable via the app.
Does anyone have an idea on how to get it working?
Edit: I checked the debug logs once again and now its telling me that my vaccum "Deebot T50 Omni" is not supported.
2025-07-29 10:54:54.648 WARNING (MainThread) [homeassistant.components.ecovacs.controller] Device "DEEBOT T50 OMNI" not supported. More information at https://github.com/DeebotUniverse/client.py/issues/612: {'did': '2cba92fa-5577-4103-8523-d22ddde96c10', 'name': 'E02C34673G1FPP9B0390', 'class': 'mezar1', 'resource': 'vnvDVU8V', 'company': 'eco-ng', 'bindTs': 1753523163369, 'service': {'jmq': 'jmq-ngiot-eu.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-eu.ww.ecouser.net'}, 'deviceName': 'DEEBOT T50 OMNI', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/67288127ec0f096170bddb8f', 'ota': True, 'UILogicId': 'faraday_ww_h_keplerh5', 'materialNo': '110-2466-0202', 'pid': '66a9d7200fc79852ea826032', 'product_category': 'DEEBOT', 'model': 'FARADAY_MAX_B_INT', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': None, 'homeId': '68824ae137b5f200070beb2a', 'homeSort': 1, 'status': 1, 'otaUpgrade': {}}
Seems like the model "mezar1" is not supported :/
I have already checked Deebot Issue 612 but I am a little stuck. Can anyone help me trace the data traffic?