Cant connect to Ecovacs(Deebot) T50 Omni #152

Open
opened 2025-07-29 09:30:55 +02:00 by mario-to-lowercase · 3 comments
mario-to-lowercase commented 2025-07-29 09:30:55 +02:00 (Migrated from github.com)

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?

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](https://github.com/DeebotUniverse/client.py/issues/612) but I am a little stuck. Can anyone help me trace the data traffic?
VincentSC commented 2026-01-07 12:00:09 +01:00 (Migrated from github.com)
It's added there https://github.com/DeebotUniverse/client.py/pull/1308 Maybe use their fork instead? https://github.com/DeebotUniverse/bumper
VincentSC commented 2026-01-07 12:05:49 +01:00 (Migrated from github.com)

Ah, I now get it. https://github.com/DeebotUniverse/client.py is fork from deebotozmo, which is in turn a fork from sucks. And https://github.com/DeebotUniverse/bumper is a fork from this repo. So you should use everything from https://github.com/DeebotUniverse instead, to get this working.

I'm looking into buying the same vacuum cleaner. Which was the IP you blocked?

Ah, I now get it. https://github.com/DeebotUniverse/client.py is fork from deebotozmo, which is in turn a fork from sucks. And https://github.com/DeebotUniverse/bumper is a fork from this repo. So you should use everything from https://github.com/DeebotUniverse instead, to get this working. I'm looking into buying the same vacuum cleaner. Which was the IP you blocked?
mario-to-lowercase commented 2026-01-25 18:23:12 +01:00 (Migrated from github.com)

Thanks for the reply. Will give it a try.

I'm looking into buying the same vacuum cleaner. Which was the IP you blocked?

Regarding the IP's i changed my firewall to block china in general but if it helps i can filter the IPs out again.

Thanks for the reply. Will give it a try. > I'm looking into buying the same vacuum cleaner. Which was the IP you blocked? Regarding the IP's i changed my firewall to block china in general but if it helps i can filter the IPs out again.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: mia/bumper#152
No description provided.