FIXED: Ecovacs Deebot 2019 & OZMO Series - Working Library

Installation Home Assistant OS
11

On Step 2 Iā€™ve created a folder under config/custom/components/ called deebot and I placed the files that you find in the link

Iā€™ve now try to do a pip3 install ozmo (pip does not work on Hassio) and I get this long log and an error

http://pasted.co/9f42e9a6

12

custom components live in subfolders under /custom_components/ not /custom/components/.

So youā€™d need something like /custom_components/ozmo/

13

Correct, this is my folder, I just wrote here in the wrong form

14

Lines 54 onwards are for your Yi cam / Yi-Hack-v4 integration. The first 53 or so are the Ozmo ones.

There doesnā€™t appear to be any error specific to the Ozmo package. Could you try to isolate the ozmo setup without all the other stuff going on? It looks like there are a whole load of things being installed at once:

Installing collected packages: pycryptodome, pyparsing, packaging, atomicwrites, more-itertools, wcwidth, py, zipp, importlib-metadata, pluggy, pytest, pytest-mock, wheel, pprintpp, repoze.lru, coverage, pytest-cov, pycountry, pycountry-convert, paho-mqtt, stringcase, ozmo
15

I really donā€™t know how to do itā€¦ :thinking:

16

What better way than giving back the community something in the first post :smiley:

I did the workaround by myself and at least I can now control the basic things of my D900.
For anyone who wantā€™s to use this too, Iā€™ve published the modified files as gist:

  • Save __init__.py, manifest.json and vacuum.py to config/custom_components/deebot
  • add deebot component to configuration.yaml (example in gist)

@woody4165
as far as I can see -

  • requirement ozmo==0.9.4 should be requirement ozmo==1.0
    but the easiest way is to just use the files from my gist.

1st Edith says:
As this post is now marked as solution, credits should also go to @Ligio for providing the fixed pip library

3 Likes
17

Iā€™ll try later at home with my deboot 930, do you have any way to obtain correct country and continent?

18

Thanks @SolTroy
Do I need to install ozmo via pip install?
I will try later, too.

19

Not now. This code automatically pulls in the new ozmo library via Home Assistant. If I understand correctly, when done like this, anything on PyPi can be imported into HA semi-automatically. EG: if you tell HA whatā€™s needed it can grab it from PyPi.

20

So, no more error during check, but no deebot device created.

BTW, I have an Ecovacs Ozmo 900

This is my log

2019-08-28 17:34:41 DEBUG (SyncWorker_6) [custom_components.deebot] Ecobot devices: [{'did': 'xxxxxx', 'name': 'E0001206219600470017', 'class': 'y79a7u', 'resource': '4RcC', 'nick': None, 'company': 'eco-ng', 'bindTs': 1566489318735, 'iotmq': True}]
2019-08-28 17:34:41 INFO (SyncWorker_6) [custom_components.deebot] Discovered Ecovacs device on account: xxxxxx with nickname None
2019-08-28 17:34:41 DEBUG (SyncWorker_6) [custom_components.deebot] Starting vacuum components

2019-08-28 17:34:45 DEBUG (SyncWorker_5) [custom_components.deebot.vacuum] Vacuum initialized: 22d8d3a2-5ef7-4637-82ad-43cd78f00408
2019-08-28 17:34:45 DEBUG (SyncWorker_5) [custom_components.deebot.vacuum] Adding Ecovacs Vacuums to Hass: [<Entity 22d8d3a2-5ef7-4637-82ad-43cd78f00408: off>]

It seems all ok, but searching for deebot or ecovacs in the entity name or attributes, nothing is found

This is my configuration.yaml

#ecovacs:
deebot:
  username: !secret ecovacs_username
  password: !secret ecovacs_password
  country: it
  continent: eu
21

Did you copy the files in the Gist linked to above?

Did you restart Home Assistant?

Have you checked the ā€œunused entitiesā€ page to see if a ā€œVacuumā€ section is present?

P.s. The last two lines of your log indicate that the Ozmo device has actually been added to your system.

22

Awesome thanks! Only works for me when using US/NA instead of NL/EU, but it works regardless.

23

Absolutely correct - I had nothing to install / manually doings.

24

@SolTroy Thanks for choosing this thread to start your HA community posting. I think youā€™ve just made things easier for many many people.

1 Like
25

Yes, copied the raw files in the custom_components/deebot folder

And yes, restart HA because configuration.yaml changed, checked and restarted.

The last tips showed me the entity name that was the one that I replaced in the log with xxxxx. So itā€™s the did field

Now I changed the entity name and this is the result

32

Thanks!!!

1 Like
26

Trying now with hassio. First time I push Start my 930 starts to clean, then I press return home, perfect. Now itā€™s charging but status that shows in ha is auto. Donā€™t refresh this status then i canā€™t start cleaning again.

27

Guess thatā€™s the issue mentioned on sucks github readme,
If it doesn't appear to work for your continent, try "ww", their world-wide catchall.

@Phill_Healey THX - Iā€™m pretty sure there will be more :grin:, ATM Iā€™m just ā€˜deep-divingā€™ into HA (coming from openHab)

1 Like
28

Like most things in HA, you need to give it some time to update. This can be almost instant on one occassion then time out on another. Eitherway clicking lots of buttons in the hope of somehow rectifying it, just adds to the load and makes things worse. Just restart HA and give your system some time between updates to the Ecovac. Hopefully it should rectify itself shortly. Everyone else here seems to be getting this working ok.

29

The flurry of activity over the last 30mins or so is amazing. It shows just how many people have been desperate to get their Ozmo working in HA.

Welcome to HA and PLEASE stick around. :wink:

30

ok sorry, iā€™m impacient :sweat_smile::sweat_smile: after a couple of minutes status changed to charging perfectly.

1 Like