New test version 1.1.3:
- Added ‘clean zones’ flow action.
- Canged T30Gen2 device support.
@ricercar FYI
New test version 1.1.3:
@ricercar FYI
I’ve tested most of the then cards with my X8 and T30 OmniPro (multi zones included) and they work fine.
Thanks a lot !!!
Hi Ronny,
When trying to open the Ecovacs app, I only get a log file error screen. Can’t get too any login screen. This is on Self hosted windows and Ecovacs app 1.1.3.
Not sure if anyone else has had this?
Hi, can you please add a screenshot? Where/when exactly comes the log screen? Or perhaps a screen recording to see what’s happening.
I haven’t seen this before, so I’m courious if it’s a bug in Homey or in WebGUI.
You can also send it via PM. Thanks.
Hi!
So far I am really happy with this new app. Thank you for the hard work!
I am still running the test versions and I figured that I have to restart the app daily or sometimes during the day. Otherwise the deebot does not respond to any action I would send. Does somebody else face this issue?
And other than that, I found a few spelling mistakes of the individual labels in German language. E.g. “Parkpposition” or “Waterdurchfluss”. Is there a way to report this or help with the correction?
Ups, haven’t seen it (I’m german, too) ![]()
That’s the disadvantage when developing in english and only use KI-Translation ![]()
Just make a comment here and I’ll update the texts. These ones are already fixed for the next version. Thanks ![]()
I will akso check the restart problem…
Haha, now I understand somehow ![]()
Let me list my findings:
WHEN cards
AND cards
THEN cards
I should read the texts before deploying… Thanks for checking.
Edit: All fixed ![]()
I also got the auth error. It seems, the auto token update provided by the module is not working. Still searching for a reason…
The auth token is valid for ~7days. So if you get an error after one day, Ecovacs invalidates the token before it’s end of validity ![]()
Has anyone used the cleaning report to trigger an action? I tried to test it but the trigger card for when a new cleaning report is available does not react.
At least I can tell that there is a cleaning report available as the Ecovacs app tells me when a cleaning is finished.
It’s not that important but I wanted to use cleaning time to sum up the individual operation time of all the inventory (brush, mops, dust bin, etc.) myself to trigger a notification for maintenance
That’s not a built in functionality. The old app had such a trigger so I tried to add it also.
But it’s based on the devcice state. The old devices only had cleaning/idle. The newer ones have a combination of robot/station state.
I tried to use robot state (if it changed to idle). Then a clean log list is requested and if it returns, the trigger is fired. It’s still a trial&error state and don’t know if the clean log is already ready when the robot changed from cleaning to idle.
Which device are you using?