Thanks, I set up a flow. But now I can’t reach either of my devices. Unrelated I’m sure, but not able to test as login isn’t working. Tried logging in again. But same issue. Says unreachable
Don’t know. Internet issue or blocked URL?
New test version 1.2.1:
- Added error code capability and flow condition
98a2821e-8f48-4886-97b1-9ce617c79782
Changed password, tried again. Same thing happens. One second it looks like it’s up and running then going back to how it looks on image above
Hm, the 2FA issue again? I thought it was solved already ![]()
Did it ask for a 2FA code in repair mode or not?
The log is a bit irritating. After repair it says the token is not valid and tries log in with email/pw. And that second login in a secon does not seem to be something Ecovacs wants. I have to look what can be different in repair mode.
Is an app restart working as workaround?
The repair mode has some bugs. Let me check…just saw some code issues.
But I wonder why you get 2FA pincode requests. Because if a valid code is provided, the Homey will be a “known” device - independent of a wrong user/pw.
Thanks. T20 worked right away, but the t90 I had to remove and readd ![]()
ECOVACS ogin session expires every few days – DEEBOT T90 Pro Omni
Hello RonnyW,
I am using the ECOVACS DEEBOT T90 Pro Omni with the Homey Ecovacs Deebot app (version 1.1.3).
The integration works correctly initially, and I can control the robot from Homey. However, after a few days, the ECOVACS login session expires and the Homey Flow that starts cleaning stops working.
The robot still responds to commands from the official ECOVACS app, so the robot itself is working correctly. After logging in again, the Homey integration works again, but the same problem returns a few days later.
Could you please investigate whether the authentication session can be automatically refreshed, or whether there is another way to prevent these repeated logouts?
I can provide diagnostic logs if needed.
Thank you for your help.
Hi, today a new live version was approved. Version 1.1.5 added a new auth refresh, so the new version 2.x should keep the device alive.
Tried this code 322,(that’s the id it says in the app at least,when tank is empty), and error message logic. Neither worked. I think the homey app names it a bit different.
Is there a list of different errors or ids I can try?
Hello!
I hope I can get some help setting up my Ecovacs T9+ here.
After the old version of the app stopped working I installed the experimental Version 2.x.x (2.0.6 I guess). This helped to connect to the device again, but failed in flows cleaning a certain area.
Searching the forum i realized that there is a newer version 1.2.2 and installed it.
When connecting to my Ecovacs account it reported a wrong verification code (which I got by email) but added the device.
Shortly after adding the device the tile showed up with “Fehler” (German for “error”.
Trying to create a flow did not show me the list of rooms I added with the ecovacs app.
When repairing it seems to connect to my account and returns to the app without any error message - but still no list of rooms and still error message on the tile.
I deinstalled the app and reinstalled it. When connecting to my account it works with email/password only, not needing a new verification code (which was reported as wrong on the first time.
What can I do?
thank you for any help
Peter
I only know the codes used in the app:
Hi,
the 2FA code is only device specific and is needed if you want to access Ecovacs cloud from a new device (your Homey). If this is verified, your Homey is a ‘known’ device and 2FA is not needed for further logins.
Are other functions working right (start/stop)?
The new app (and the 2.x version for the older app) is using the new version of Ecovacs JavaScript module. This drops the old XML Api. I don’t know if your device is using it or if it’s using different way for rooms.
Did it work in the 1.x version of the old app and stopped with 2.x? Then it’s perhaps a reason.
You can try again and then send a diagnostics report. Please add also a screenshot of the flow card error. Thanks.
Hello Ronny !
Thank you for your quick response.
The device worked well with the old app until Ecovacs introduced a verification process. Consequently, I switched to version 2.0.6, which allowed me to reconnect the device to Homey. Unfortunately, I discovered that my flow for cleaning a specific room was not working. After reading this post, I found the current version, 1.2.2, and installed it as described above. While the connection between Homey and the device is stable, the list of individual rooms is missing when I try to create a flow that requires selecting a specific room; therefore, I cannot even set up the flow to see if an error message might appear. Furthermore, although the device responds to the function buttons in the app, it only moves 30–40 cm away from the charging station when “Start Cleaning” is selected, and then it simply stays there. As a first step, it is necessary to identify the cause of the missing room list.
a78d1206-17a7-47f7-8eef-85014a5d664a
I will check the report soon.
The ‘start’ button starts the auto clean function. This should be the same line the start button in Ecovacs app (where the presefined room sequenz is used).
As summary: Ecovacs is using a lot of different APIs and functionality across all the devices. The Ecovacs app is just a wrapper and it’s loading a separate ‘plugin’ for the device. The Homey app (and the used NodeJS module) tries to include what’s possible and known in a generic way. So it’s not easy to prodide it for all devices. At the end it’s a trial and error for every single device.


