How to install when already using another deebot integration?

[djmvt]

I cannot seem to figure out how to install this for my deebot ozmo 900 vacuum. Problem is that I already have a deebot integration installed wit haccs, that one supports my deebot 950 but doesn't support the deebot 900. The official ecovacs integration doesn't support both vacuums. But this custom integration is called deebot. Just like the haccs integration is.

Any workaround for this?

[vannetta]

I cannot seem to figure out how to install this for my deebot ozmo 900 vacuum. Problem is that I already have a deebot integration installed wit haccs, that one supports my deebot 950 but doesn't support the deebot 900. The official ecovacs integration doesn't support both vacuums. But this custom integration is called deebot. Just like the haccs integration is.

Any workaround for this?

I'm in the same situation. It would be possibile to change the name of the folder and the domain input in the code?

[djmvt]

@vannetta I forgot about this but your comment made me try what you sugested:

I've downloaded the zip and changed the directory name to deebot900. I've changed manifest.json to this:

{ "domain": "deebot900", "name": "Ecovacs Deebot 900", "version": "1.0.1", "documentation": "https://www.home-assistant.io/components/ecovacs", "requirements": [ "ozmo==1.0.4" ], "dependencies": [], "codeowners": [ "@Ligio" ] } Then I added this in configuration.yaml: deebot900: username: [email protected] password: deebotpass country: 2 letter countrycode continent: 2 letter continent code

for now this seems to work, both my deebot 900 and 950 are now available and working in Home assistant.

I wanted to clone this repository and make the changes available in github but I'm not a programmer at all so I don't know how to do that.

[vannetta]

I'm going to try too and send a feedback 😉

[vannetta]

It really works! I also rename the domain in init.py

[djmvt]

@vannetta yes, forgot to mention init.py, changed the domain there too. I did notice a problem though: the state of the vacuum got updated a few times but it seems stuck now at "docked". It still receives commands from home assistant but it looks like the feedback coming from the deebot server isn't picked up right. Charging level and brush states do get updated so I assume this is server related.

[dev4jam]

@djmvt I've followed your steps exactly. But after restart I don't see any deebot entities. How did you understand that it works?