Closed inputd closed 5 years ago
Hey there @OverloadUT, mind taking a look at this issue as its been labeled with a integration (ecovacs
) you are listed as a codeowner for? Thanks!
This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.
Please do not change our issue template
Please do not change our issue template
Sorry; corrected
Hi there,
This is actually not a bug. The error attribute is there to indicate what the most recent error thrown by the vacuum is. This can be used in automations to trigger on the vacuum getting stuck, the vacuum failing to find its charger, and other such errors. It's null when there is no most recent error such as on startup. There's a bit more info in the documentation: https://www.home-assistant.io/components/ecovacs/#handling-errors
Got it - thank you!
Home Assistant release with the issue: 0.92.1
Last working Home Assistant release (if known): 0.92.1 (was a broken platform previously)
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Component/platform: ecovacs
Description of problem:
First off: thank you for all the work put into just getting the component working again!
The component now loads, and the commands all work. However, there is a field in the component now called "error" with a value of "null". From looking at the documentation, I believe this is supposed to be the lifespan of your filter. There are no errors in the logs. Here's what the entity attributes look like in the "states" tab:
status: charging
battery_level: 99 battery_icon: mdi:battery-charging-100 fan_speed: normal fan_speed_list: normal,high error: null friendly_name: vacuum supported_features: 2043
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: HAssio 2.11 Supervisor 162