Ok. Commando back, after restart work all.
Fan speed change nothing work
robotic vacuum ecovacs-deebot ozmo 950 and etc
Ok. Commando back, after restart work all.
Fan speed change nothing work
Ok my wrong I have in the rules with [1] not work an when I type only the 1 work
I did it because pimatic had suggested it to me in the rules
Ok, thats fine. It had in an earlier version the brackets [] around the number. But in the newer version not.
The suggestion should not be there. I released version 0.0.20 with small improvement with the names for the waterlevel
Ok.
Waterlevel variable say unbekannt
Can implement the same as for fan
Here for water set level
SetWaterLevel 1
SetWaterLevel 2
SetWaterLevel 3
SetWaterLevel 4
@heiko1988 said in robotic vacuum ecovacs-deebot ozmo 950 and etc:
SetWaterLevel
You can test version 0.0.21
deebot <device.id> waterlevel [1..4] | $waterlevel-variable
Yeah, works perfect
So I have direct the next
Custom area
The command:
vacbot.run(“CustomArea”, “start”, “1890.000000,-1661.000000,288.000000,-3069.000000”, “1”);
comma-separated list of exactly 4 position values for x1,y1,x2,y2 (e.g. -3975.000000,2280.000000,-1930.000000,4575.000000)
cleanings
1, 2
The Koordinaten in a variable is best.
Then have custom area, can run the vacuum after breakfast only unter the table
Can pleas implement
I think then we have the most features for a vacuum robot
Hi, i will look at it but…
I think we need to move the issues and requests for this plugin to the github issue page and give the forum some rest
Just to start could you put the request in there?
Yes is ok
I have open a ticket on github
github feature request
There seems to be an issue with certain deebots losing connection after approximately 24 hours, it is described here: https://github.com/mrbungle64/ioBroker.ecovacs-deebot
(See known issues)
It looks like this is also the case for the library that is used in this plugin.
Is there a way to implement this “restart” solution in pimatic?
I’ve tried setting some rules that should start the robot for a short time but still connection is lost after about 24 hours.
No nothing. Just an executed message from the rules but the robot is no longer responsive. Status info also doesn’t get updated.
After testing it seems it is not working, it’s even sooner than 24h before it simply doesn’t respond to the pimatic plugin. The device itself gets updated when trying to control the robot with the ecovacs app so in pimatic it still shows current status, battery info etc. But controlling with pimatic is impossible.
Only after a reboot of pimatic it starts working again for a few hours.
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.