# \[APP\]\[Pro\] Ecovacs Deebot - You relax. DEEBOT delivers

**URL:** <https://community.homey.app/t/app-pro-ecovacs-deebot-you-relax-deebot-delivers/158711>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [August 24, 2026, 6:45pm UTC](https://community.homey.app/t/app-pro-ecovacs-deebot-you-relax-deebot-delivers/158711 "2026-08-24T18:45:44Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 28, 2026, 6:22pm UTC](https://community.homey.app/t/app-pro-ecovacs-deebot-you-relax-deebot-delivers/158711/22 "2026-08-28T18:22:30Z")

</div>

New **test version 1.0.5**

- changed authentication.

> **[Ecovacs Deebot | Homey](https://homey.app/en-us/app/com.ecovacs.deebot/Ecovacs-Deebot/test/)**
>
> You relax. DEEBOT delivers

With this update I still try to find a solution for the auth issue (verification needed on 2nd login).  
I found similar issues for HomeAssistant. For some users, a changed password solved the isseu. For others, only a changed login logic solved it. The app now tries to login with a cached token if it’s still valid. If it’s outdated, a normal login with user+pw is done.

The update will cause a validation error if login is done via email/pw. This can happen now or in some days when the token times out. It his happens, just repair the device, login data shoud be prefilled. Then do another 2FA verification and hopefulle it’s working then 🙂

@Linden85 @Radon FYI and try 👍

As additional information the HA issue thread:

> <https://github.com/home-assistant/core/issues/177870>
>
> \### The problem
> 
> After adding the Ecovacs integration, Home Assistant requests d…evice verification by email.
> 
> The verification code is accepted and Home Assistant reports that reauthentication was successful.
> 
> Immediately afterwards, however, the Ecovacs config entry cannot authenticate and shows:
> 
> Device verification required
> 
> In some attempts, a second Ecovacs config entry is created.
> 
> Deleting the entries, restarting Home Assistant, and adding the integration again produces the same result.
> 
> \### What version of Home Assistant Core has the issue?
> 
> core-2026.8.0b2
> 
> \### What was the last working version of Home Assistant Core?
> 
> Unkown
> 
> \### What type of installation are you running?
> 
> Home Assistant OS
> 
> \### Integration causing the issue
> 
> Ecovacs
> 
> \### Link to integration documentation on our website
> 
> https://www.home-assistant.io/integrations/ecovacs/
> 
> \### Diagnostics information
> 
> \_No response\_
> 
> \### Example YAML snippet
> 
> \`\`\`yaml
> 
> \`\`\`
> 
> \### Anything in the logs that might be useful for us?
> 
> \`\`\`txt
> Config entry '\<redacted\>' for ecovacs integration could not authenticate: Device verification required
> \`\`\`
> 
> \### Additional information
> 
> The issue is reproducible on a fresh Home Assistant Green installation.
> 
> The device verification flow itself completes successfully and Home Assistant displays that reauthentication was successful. However, the config entry immediately enters another reauthentication state.
> 
> Home Assistant Core: 2026.8.0b2
> Home Assistant OS: 18.2
> Supervisor: 2026.07.5
> Country/region: Germany

> <https://github.com/home-assistant/core/issues/177870#issuecomment-5230709001>
>
> \### The problem
> 
> After adding the Ecovacs integration, Home Assistant requests d…evice verification by email.
> 
> The verification code is accepted and Home Assistant reports that reauthentication was successful.
> 
> Immediately afterwards, however, the Ecovacs config entry cannot authenticate and shows:
> 
> Device verification required
> 
> In some attempts, a second Ecovacs config entry is created.
> 
> Deleting the entries, restarting Home Assistant, and adding the integration again produces the same result.
> 
> \### What version of Home Assistant Core has the issue?
> 
> core-2026.8.0b2
> 
> \### What was the last working version of Home Assistant Core?
> 
> Unkown
> 
> \### What type of installation are you running?
> 
> Home Assistant OS
> 
> \### Integration causing the issue
> 
> Ecovacs
> 
> \### Link to integration documentation on our website
> 
> https://www.home-assistant.io/integrations/ecovacs/
> 
> \### Diagnostics information
> 
> \_No response\_
> 
> \### Example YAML snippet
> 
> \`\`\`yaml
> 
> \`\`\`
> 
> \### Anything in the logs that might be useful for us?
> 
> \`\`\`txt
> Config entry '\<redacted\>' for ecovacs integration could not authenticate: Device verification required
> \`\`\`
> 
> \### Additional information
> 
> The issue is reproducible on a fresh Home Assistant Green installation.
> 
> The device verification flow itself completes successfully and Home Assistant displays that reauthentication was successful. However, the config entry immediately enters another reauthentication state.
> 
> Home Assistant Core: 2026.8.0b2
> Home Assistant OS: 18.2
> Supervisor: 2026.07.5
> Country/region: Germany

---

_[View the full topic](https://community.homey.app/t/app-pro-ecovacs-deebot-you-relax-deebot-delivers/158711)._