Ecovacs DeebotN79s suddenly missing component lifespan values

amccourt commented 4 years ago

The problem

Ecovacs integration has stopped adding component lifespan values to the vacuum state. This was working previously with my Ecovacs Deebot N79s vacuum. I also notice that sometimes status and battery attributes are also missing from the vacuum state, usually when the vacuum is off or charging.

Environment

Home Assistant Core release with the issue: 0.110.0
Last working Home Assistant Core release (if known): 0.109.6 (started noticing issues on this release)
Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant
Integration causing this issue: Ecovacs
Link to integration documentation on our website: Ecovacs
Problem-relevant configuration.yaml

ecovacs:
    username: !secret ecovacs-username
    password: !secret ecovacs-password
    country: !secret ecovacs-country
    continent: !secret ecovacs-continent

Traceback/Error logs

Debugging sucks i can see that it is retrieving the correct value for the SideBrush vacuum component (expecting 95)

RECV: <iq to="xxx@ecouser.net/xxx" type="set" id="xxx" from="xxxx@xxx.ecorobot.net/atom"><query xmlns="com:ctl"><ctl id="" ret="ok" errno="" type="SideBrush" val="095" total="365" /></query></iq>

But when HomeAssistant sets the vacuum config:

DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=vacuum.xxx, old_state=None, new_state=<state vacuum.xxx=off; fan_speed_list=['normal', 'high'], error=None, friendly_name=xxx, supported_features=2043 @ 2020-05-20T13:25:12.996511-04:00>>

The state is missing component_side_brush as well as component_filter which were both present previously.

Additional information

amccourt commented 4 years ago

Update: Literally minutes after writing this post, after days of waiting to see if the component lifespans would return on their own, they showed back up in the entity state. Still not sure what causes this or how to replicate the issue though.

probot-home-assistant[bot] commented 4 years ago

ecovacs documentation ecovacs source _{^{(message by IssueLinks)}}

probot-home-assistant[bot] commented 4 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! _{^{(message by CodeOwnersMention)}}

jes1417 commented 4 years ago

I have a n79s, after every reboot the integration loses the attributes. They won't reappear until the vacuum has ran almost a full charge, the time required for each to re-populate is different for each attribute. And after every reboot they go missing again. It has always been like this I wish the integration would store the values throigh the reboots. I reboot often due to many ui and config changes and I have template sensors for the attributes but they are basically always None % and are almost useless. Screenshot_20200520-211107

amccourt commented 4 years ago

@jes1417 Ah that makes sense, have been updating UI a lot lately and rebooting frequently.

neegbeah commented 4 years ago

I was able to confirm that even on the latest release, it was functional but not showing my entities or the state changes.

Update: The state are changing. But there maybe some problem over time

jes1417 commented 4 years ago

It would be nice if we could get HA to remember the sensor values so they are not lost on every reboot.

stale[bot] commented 4 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

jes1417 commented 4 years ago

Still an issue

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core