DeebotUniverse / Deebot-4-Home-Assistant

Home Assistant integration for deebot vacuums
https://deebot.readthedocs.io/integrations/home-assistant/
GNU General Public License v3.0
179 stars 37 forks source link

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

Open swests opened 5 months ago

swests commented 5 months ago

Checks

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

markus99 commented 5 months ago

Seeing the same here. Only a warning, so not critical, but is a log item:

This error originated from a custom integration.

Logger: deebot_client.hardware.deebot
Source: custom_components/deebot/controller.py:78
Integration: Deebot 4 Home Assistant (documentation, issues)
First occurred: 11:21:34 AM (1 occurrences)
Last logged: 11:21:34 AM

No capabilities found for [redacted]. Using fallback.
edenhaus commented 5 months ago

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.

markus99 commented 5 months ago

TY. So, I know enough to be dangerous and did a little digging. Opened this: https://github.com/DeebotUniverse/client.py/pull/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!