search

Ligio / hacc-ozmo

Home Assistant Custom Component for Ecovacs Deebot Ozmo 900
MIT License
63 stars 30 forks source link

The log show concurrent error with ozmo integration #37

Open Marcoske23 opened 2 years ago

Marcoske23 commented 2 years ago

I have a deebot 500 series. Work perfectly with this integration but in log show this error:

2022-04-21 07:41:15 ERROR (mqtt_schedule_thread) [ozmo] call to iotdevmanager failed with {'ret': 'fail', 'errno': 4200}

Logger: ozmo
Source: /usr/local/lib/python3.9/site-packages/ozmo/__init__.py:855
First occurred: 7:41:15 a. m. (12 occurrences)
Last logged: 10:41:22 a. m.

call to iotdevmanager failed with {'ret': 'fail', 'errno': 4200}

What could it be? or just ignore it?

MichelEhmen commented 2 years ago

I have the same problem. I am on 2022.4.7 and my Deebot is not responding anymore.

Marcoske23 commented 2 years ago

I have the same problem. I am on 2022.4.7 and my Deebot is not responding anymore.

Is deebot 500 too? Today Homeassistant removed the custom component apparently because deebot folder was eliminated

seouk85 commented 2 years ago

Same issue for me with debbot 901 in Home assistant OS 2022.5.5

rschoolm commented 1 year ago

SOLVED: Turned out my deebot 901 was disconnected from wireless. I had to turn off the vac, restart my router, and power vac back on.

Initial ISSUE: I have the same issue. Deebot 901 indicates "Error". Automations are failing.

Running Home Assistant 2022.12.7 Error Log: ERROR (mqtt_schedule_thread) [ozmo] call to iotdevmanager failed with {'ret': 'fail', 'errno': 4200}