Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

“No capabilities found for 1vxt52. Using fallback“ for Deebot X1 Omni #506

Open
4 tasks done
swests opened this issue Jan 14, 2024 · 3 comments
Open
4 tasks done

Comments

@swests
Copy link

swests commented Jan 14, 2024

Checks

  • I have searched the existing issues and no issue is describing my issue
  • I have checked the FAQ
  • I have checked the documentation
  • I have installed the latest version

The problem

Get this on startup.

Diagnostics information

Latest HA, all updates applied

Anything in the logs that might be useful for us?

As above, when starting the integration I get “ No capabilities found for 1vxt52. Using fallback” for a (partially) supported Deebot X1 Omni

Additional information

No response

@swests swests added the bug Something isn't working label Jan 14, 2024
@markus99

This comment was marked as outdated.

@edenhaus
Copy link
Contributor

The warning specifies that the library doesn't know which features your bot supports. Ecovacs is not sharing it, so we must manually add it for each model.
The fallback has only some entities.

Please open a PR to add the capability file for your bot. I cannot do it as I don't know which features your bot has.

@edenhaus edenhaus removed the bug Something isn't working label Jan 27, 2024
@markus99
Copy link

TY. So, I know enough to be dangerous and did a little digging. Opened this: DeebotUniverse/client.py#405 First PR ever, so only think it's correct. Appears my Ozmo T8+ is same as capabilities file already created for another model. Anyhow, hope it helps. If not, the fallback is working fine and the warning is only that, a warning and I can keep ignoring. Thx again!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants