@RonnyW https://github.com/user-attachments/files/30132306/ecovacs-email-auth-patch-2026.7.2.tar.gz
Look at the authentication.py file
Hi Ronny,
I can request Athom to first move the app to you?
We can trasnfer the ownership of the app to you via Athom. Then you are the one in charge?
Yes, we can transmit the app. I’ll send you my code via PM.
Then let’s what I can do with the app later 
Sounds like a plan, I will transfer it as soon as i have your code.
I took over the app. Thanks @Menno_van_Hout
But it will take a while to adapt the app after reading the changelog of the used module:
And there are breaking changes like dropped XML API (old devices).
So no promise at
Let’s see how I can adapt it.
Just my 2 cents
Also me is not able to login to my ecovacs account via the homey app.
When looking into my account via Web and ecovacs app, changing my password several times and now reading these posts I would like to add an information regarding password login
It’s correct, for changing the password ecovacs sends a code which you have to put in before setting the new password. But once you have changed your password you can login to your account via the ecovacs android app (Ecovacs Home V 3.14.0) using your email and password. No code needed then anymore.
I don’t understand much of these processes, but I think it could be an interesting aspect.
@Austriacus thats because its not a two step login.
The Ecovacs cloud now require a device verification, and if you register your device once in the login you dont need the code anymore. Its a one time thing.
But its needed in Homey the first login to register your device 
I adjusted the app to use the new pair logic incl. 2FA.
So far so good.
But while testing with my T80, I saw some missing states. Old devices (or devices with a “dumb” station seem to have only one state while new devices have two states, one for the robot and one for the station.
Also the app currently uses state capabilities of type string. That means the state is only text (english). There is no translated description and no dropdown selection in flows. If you are using it in flows, you have to check for this exact string.
That’s why I’m not sure if it would be better to update the curent app with a “last” working version and start over with an new app. If I change capabilities and flow cards, this will break the flows for many users. But on the other side, when switching to another app, you have to adjust your logic the same way.
Any suggestions or ideas? I mean, you are the users using this app, so you should have a choice 
In the meantime I can upload the app as new test version.
@Olivier FYI
Hi Ronny,
Already a great thank of all your help and update of the app. Could you inform me about the exact version nr your updated Ecovacs Deebot app has? And where I can download your last (test) version? In Homey app library, or within GitHub?
I will then test your updated version asap, and give you my feedback.
To answer on your request, I’m not a user yet, so I still have no flows yet. If I could have a working Ecovacs Deebot app which can connect with my Deebot N30 Pro, I would be very happy.
But I also do understand your question on building a new app from scratch to overcome some problems and limitations. You have my blessings.
I just uploaded the test version 2.0.0
For newer Deebots, I assume the status capability is not working/updated. So it’s just to test the authentication 
Hi Ronny, I’ve installed your updated version 2.0. The authentication (2FA) is working! 
I’ve seen for the 1st time my Deebot N30 Pro within Homey. Many thanks for your help and great skills already.
I’ve noticed that not all settings of my Deebot N30 Pro from the Ecovacs app are visible in Homey or can be selected/used in flows. Could it be that the Homey app Ecovacs Deebot is communicating with a general library of settings, and not specifically with my own N30 Pro Deebot library? I send you some printscreens of the Ecovacs app and also of the Homey screens of my Deebot N30 Pro. For example: cleaning logs are not visible in Homey, only vacuum (stofzuigen) is not an option I can select in Homey, or vacuum + mopping (stofzuigen + dweilen) is also not selectable,….
Usage of water during mopping (dweilen) en suction power (zuigkracht stofzuigen) is perfect selectable.
The cleaning speed and also 1x or 2x passes of cleaning is not selectable. So there is no perfect match within Homey with the settings of my Deebot N30 Pro of the Ecovacs app. I assume this is because some mismatch in communication between libraries. This is my 1st feedback already, and I will test some flows and deeper within the possible settings. But I’m already very happy and thankful that Homey can communicate with my Deebot N30 Pro. Congrats to you.Thx. Olivier
Thanks a lot. The 2FA worked and I got my T30 Omni Pro available again in Homey 
Hi Ronny,
Hi Ecovacs Deebot users,
I’ve tested my N30 Pro within Homey, and I can not create any flow with a specific dedicated room as target. Always the Deebot starts to clean in the room where the station in located, not outside that specific area. In the flows, I do see the option of the different rooms of my groundfloor (with identical names as in my Ecovacs app), but the “rooms” function is not working. Can somebody advice me what is going wrong, or how to solve this. Thx.
I got the 2fa, but it says it wasn’t correct. Then I get to this page.
Tried re-installing to see if I could get the 2fa again, but it only comes to that place after typing in user/pass. I have t20 and t90 pro 
13 18:23:44 [log] onShowView(check_account)
13 18:23:43 [log] onAccountChanged()
13 18:23:43 [log] onAccountChanged()
13 18:23:43 [log] onAccountChanged()
13 18:23:42 [log] onAccountChanged()
13 18:23:42 [log] onAccountChanged()
13 18:23:42 [log] onAccountChanged()
13 18:23:41 [log] onAccountChanged()
13 18:23:41 [log] onAccountChanged()
13 18:23:41 [log] onAccountChanged()
13 18:23:40 [log] onAccountChanged()
13 18:23:39 [log] onAccountChanged()
13 18:23:38 [log] onAccountChanged()
13 18:23:38 [log] onAccountChanged()
13 18:23:37 [log] onAccountChanged()
13 18:23:36 [log] onAccountChanged()
13 18:23:36 [log] onAccountChanged()
13 18:23:36 [log] onAccountChanged()
13 18:23:35 [log] onAccountChanged()
13 18:23:35 [log] onAccountChanged()
13 18:23:31 [log] getAccount:
13 18:22:16 [log] appdebug: false
13 18:22:16 [log] Driver Vacuum has been initialized
13 18:22:15 [log] [App] Ecovacs Deebot is started
13 18:22:15 [log] [App] nl.onzewifi.deebott9 V2.0.0
@RonnyW Strangely enough, after updating to the latest test version, I see the following notification.
This message seems to be the error message from the API.
Did you re-auth using the repair function? After an API change from Ecovacs, you have to auth again one time with 2FA via eMail.
yes I recieve the e-mail but then after adding the Deebots I see this message ..really strange
New test version 2.0.1:
- Fixes device list issue
It’s possible that you have Ecovacs devices in your account thet are not a DEEBOT. This could cause an initial device entry, which seems to result in an error i device list view. Hopefulle this test version fixes it.
@Radon @Austriacus perhaps also @Linden85 FYI and test
