I want to add support for “Deebot T50 OMNI” to use with the Home assistant Ecovacs Integration.
Maybe someone can assist getting started to figure out the configuration requirements to add this bot model?
If anyone is searching for a solution too, there is an update from Ecovacs itself to add Matter-support for the following Ecovacs Vacuums soon:
1 Like
Update: They start releasing Matter Support in Germany today. After connecting I got only 5 Entities, missing the main vacuum entity for controlling the device
I just got the T50 Max Pro and while it’s recognized by both the official ECOVACS HA integration in 2025.5.3 and Matter there is missing functionality in both.
I tried adding it to Apple Home app via Matter and functionality looks complete there (can select rooms, start jobs etc) so it looks like the lacking Matter support is on the HA side not the bot itself.
1 Like
I’m seeing the same issue with the limited entities for the main vacuum for the T80 Omni.
I’ve tagged an open Roborock ticket on matter support. It looks like it’s an issue with the matter server component.
1 Like
Got the T50 Pro omni max, via ‘online’ I can’t start or pause it, no controlling possible yet. Via Matter the same issues as anybody else. I hope I can start the robot via HA soon then via the app from ecovacs…
1 Like
If anyone is interested I managed to get some more functionality working with my T50 Max Pro Omni by swapping the hardware configuration file for one for Deebot X2 Omni. I can now start, pause and stop. Select work mode and few other things. The status is still always “docked”.
To do this you need to do the following (the changes are not permanent and will probably get overwritten with every HA update):
- SSH into your HAOS or use the Terminal addon
- execute the following commands:
docker exec -it $(docker ps -f name=homeassistant -q) bashcd /usr/local/lib/python3.13/site-packages/deebot_client/hardware/deebotmv c8rj4y.py c8rj4y.py.oldln -svfT p7l7iu.py c8rj4y.py
- restart Home Assistant
The c8rj4y in the commands above is the hardware ID for T50 Max Pro Omni. If you want to try this for other hardware you can find your hardware ID on the Device info card.
Make a manual backup of your HA before messing with it just in case.
1 Like
I followed your steps and I confirm what you said.
I can control the robot.
The only thing I can’t see is the map.
Do you have this problem too?
Yeap. No map.
I’ve read that the map is an issue on newer bots with AI obstacle avoidance - I assume there is a new map API (unsupported AImap messages) . Hopefully they will add support with time.
Hello :
Thank you very much for your comments, I am trying to add my Ecovacs Omni T50 Pro to Home assistant, however, I have a previous problem. It does not allow me to update the robot, I have bought it in Spain and it has arrived with version 1.57.32 and currently there is 1.110.0, however, when I try to update when I hit the update button after 3 seconds in 0% I get an update error. I try again. The ecovacs technical service does not know how to solve it and I have tried everything.
Thanks.
Try creating a hotspot on your cellphone and connecting the robot to it, doing the update and then reconnecting it to your home wifi. Sometimes your router, DNS provider or ISP block access to a website a device needs to update.
After many attempts, it has been updated, it seems that it is a very common problem. Thank you for your support.
Are you on HomeAssistant OS? If you are make sure you copy the first command in its entirety. Oh and I only tested it with Advanced SSH & Web Terminal with disabled protection mode.
My instructions are for HAOS, for other types of setup you will have to figure out how to get to the HA container shell (the first command that seems to fail on your system). As I don’t know specifics of your setup I can’t really assist you with that.
i have this one:
Im new on this, so i dont know how to do it, i canot play and pause the vaccum right now with matter.
Thanks you
Hi again:
with you addon its works, but the command mv not working:
Its the hardware ID this one?
Thanks you
Update your HomeAssistant, you are running old version with an old version of Deebot client library and that is probably why the mv command fails. You can try skipping it and just doing the last command but I can’t tell if this will work.
It would be best if you update first, test if the bot is working and if you have issues starting the job then do the steps I described.
1 Like
Thank´s you. Now its working.
New HA update just dropped and as expected reverted all the changes so you need to redo above set of commands.
But that inspired me to try to merge some of hardware configuration files I tested before (specifically qhe2o2.py for N20 Pro Plus and p7l7iu.py for X2 Omni) and I managed to create a config file with limited support for station functionality.
It adds Station status and Auto Empty button. As far as I can tell the library does not support station functions other than Auto Empty so that is all that we have.
Bot Status and Station Status are still not updating - I assume that the API is different than for other/older bots but those might start working at some point when the library gets updated.
Map also still does not work.
To grab my hardware config file you have to:
- SSH into your HAOS or use the Terminal addon
- execute the following commands:
docker exec -it $(docker ps -f name=homeassistant -q) bashcd /usr/local/lib/python3.13/site-packages/deebot_client/hardware/deebotmv c8rj4y.py c8rj4y.py.oldwget https://raw.githubusercontent.com/ClassicGOD/client.py/refs/heads/dev/deebot_client/hardware/deebot/c8rj4y.py
- restart Home Assistant
if you want to try it with other hardware than T50 Max Pro Omni you have replace the last 2 commands with:
mv [your_hw_id].py [your_hw_id].py.oldwget https://raw.githubusercontent.com/ClassicGOD/client.py/refs/heads/dev/deebot_client/hardware/deebot/c8rj4y.py -O [your_hw_id].py
1 Like