Conclusion, there is no debug error message when the problem occurs.
I made a daily reconnect timer. It reconnects around midnight.
Version 0.0.33
-
robotic vacuum ecovacs-deebot ozmo 950 and etc
-
Too bad, the deebot device didn’t start last night (tried activating it with rules) from pimatic, it did work with the deebot app.
Also this morning the deebot device in pimatic was empty, tried removing the device and did a discover devices scan but it is no longer found.
So I uninstalled the deebot plugin, rebooted pimatic, installed the plugin again and tried a discovery but still no robot to be found.
Everything works well in the official deebot app. -
0.0.34 is connecting again, the robot is also found again and responds to commands from pimatic.
If you need access I can give it but I’m not at home right now to see if the robot does respond to commands you send to it. -
The deebot has started 3 days in a row. Looks like the problem is solved.
-
Ah too bad: the robot is not responding to the buttons again tonight. When starting it from the official app the device on pimatic gets updated but I cannot send any commands to it again. Perhaps after the restart at midnight it will work again, will see tomorrow.
-
The nightly reset seem to have worked. I’ll keep an eye on it in the next week to see if it keeps working.
-
@bertreb said in robotic vacuum ecovacs-deebot ozmo 950 and etc:
I can change the restart timer from once a day to once per x hours, if the error happens within 24 hours.
Looks like the timer is working fine now so for me you can leave it as it is. Thanks (again 😅)