[APP][Pro] < Ecovacs Deebot > - Verbind je Ecovacs Deebot 950type

I’m working on a new app version. It will get a new app ID. That means you can install both apps parallel to do a manual migration.

The neew app uses the new ecovacs-deebot module version. This allows to reduce the amount of needed additional modules and get a smaller memory usage.
There are some changes for capabilities and flows, so it’s better to make a new app because this would break devices.
Benefit: I also try to add more support for API V2 devices where most app functions don’t work currently. This needs some time because it needs changed in the underlying module.

If you are just starting with Ecovacs app, it would be better so wait a short time to start directly with the new one .-)

Worked great! Thanks :grin:

“Unfortunately, it still doesn’t work for me after this update. I have the X8 Pro Omni and a Deebot T30 Pro.”

Can you please restart the app, then send me a diagnostics report. I’m curious what API response is sent :thinking:

a66e7df7-9cf0-4ee9-800a-656c35246481

Error is: DeviceVerificationRequired: Please update to the latest version to continue.
During login, I can see several PIN code errors (but only that there was an error, not which exactly).
What happened for you during pairing after inserting the PIN code?

Nevertheless new test version 2.0.2 with some more logging.

Please update, then do repair again with user/pw + PIN. If you really can’t proceed the PIN question, make another diagnostics report.

“After entering the 2FA code, the vacuums are found and successfully added. You can see the flow cards, but subsequently, they show up as ‘unavailable’ in the device overview.”

Ah yes, after PIN log messages are device init and the error.
That’s strange. The API requests a device verification after 2FA :thinking:

Is a repair possible? Is there also a new 2FA needed or is it just asking for email/pw and then it’s done?

55fcb7a2-5b25-4f5b-9aba-c8c5050ccf30

With the repair Option i dont recieve any 2fa code by email after removing the deebots and Reading i see after a wile no device available

I receive a 2FA code and after entering it the app tries to load my robot but ends in a 1004 error

App version 2.0.2

I can see that the error is caused by a device verification request. That request that is used during login to request the 2FA code.

I have no idea what’s causing the API to send this error after successful verification.
I can’t give you a solution, but I will check if there are other similar causes in other apps to find the reason.

It looks like an auth error (perhaps invalid authToken). But I can’t say what’s wrong. Perhaps a similar issue like the other one with verification request. I’ll try to find information, at Github or so.

Thank you Ronny! You are the best.

I am very unhappy, because I purchased this robot ad it was the only one with an app on Homey then.

You can add it via Matter. I also used the Matter variant for the last year. You don’t have all optioms, but clan/stop etc. is supported.

And let’s see if it’s an API issue and a fix is found (by HA community).

I didn’t know that Deebot supports Matter. Haven’t seen any code.

But will have a look

In Ecovacs app open the device, go to device settings. In the list is an entry “Matter ecosystem”. There you can add the device to Homey.

No Matter Ecosystem at all.

Model T9+ might be too old for Matter

You can also try to remove the Homey app registration from your Ecovacs account (should be listed as Pixel 7, the JS-module is using this ID). Perhaps that clears a cache at Ecovacs server.

@Linden85 @Austriacus

Do you have one or two Deebots?

Only reasing I can imagine is adding a second device. Currently, the HomeyID is used for 2FA as device ID (to add further devices on this Homey without 2FA request).

Question is then, whether Ecovacs requests a new 2FA code is a second bot is added to Ecovacs app.

i have 2 deebots