-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ecovacs authentification and device registry issues #16186
Comments
Self.device is now allocated for device registry information in entity component. |
But the Ecovacs code doesn't seem to respect that and currently crashes. |
have you tried the latest beta? we have changed device registry to use device_info to clarify what it does |
I understand why I missed it originally, the component was merged around the same time as device registry so it didn't get picked up by my grep for components using self.device. So there shouldn't be an issue any more |
I am not sure I am following. Yes, as I mentioned the PRs were merged around the same time and hence the Ecovacs code wasn't updated appropriately. Why do you say there shouldn't be an issue anymore? The latest beta still has Ecovacs trying to assign to |
Just downloaded the latest beta version (0.77.0b2) but I'm having errors, which I think are the same (1004). I've set mine configuration as BR / WW. Got the logs copied here: https://pastebin.com/F9zuBAch |
@bartvm yes the issue is gone, the previous usage of self.device with device registry has moved to self.device_info. |
The issue pasted by @leofuscaldi looks more like an authentication issue than with overridden methods |
@leofuscaldi's issue seems to be the one from wpietri/sucks#34 |
@Kane610 Got it! I didn't understand what you meant at first with |
@bartvm I think so.. but how do I fix the line? What is the sucks/init.py location? |
It's in your traceback: |
@bartvm exactly. Thanks for the help, it works now! |
Changing the self.uid to the uid that is given by ecovac is working (with debug you can see which userid you are given). But, then it gives the following errors:
Anyone knows how to fix this? EDIT: Fix it like this, by updating those modules: But then this problem pops up:
Fixed that by editing cert.py according to this post: fritzy/SleekXMPP#478 Should i have another version of xmlstream or what is causing all this? |
With other versions I am back to this error:
|
Tony, I think it'd be best to create that one as a new issue so we can keep the issues separate. The previous two issues in this thread are different. |
I am closing this issue, as the original problem related to |
Home Assistant release with the issue: 0.77.0b0
Last working Home Assistant release (if known): n/a
Operating environment (Hass.io/Docker/Windows/etc.): Ubuntu 18.04.1 LT
Component/platform: https://rc--home-assistant-docs.netlify.com/components/ecovacs/
Description of problem: I installed the pre-release of 0.77 to test with my Deebot N79S. I ran into the following errors:
I got authentication errors like those reported in wpietri/sucks#34 and had to apply the fix from that unmerged PR to continue.
Secondly, #15980 turned
device
into a read-only property but seems to have failed to update the Ecovacs code (that was added the day before) which tries to write to theself.device
attribute. Replacingself.device
withself._device
everywhere in https://github.com/home-assistant/home-assistant/blob/0.77.0b0/homeassistant/components/vacuum/ecovacs.py seems to fix it.Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: n/a
The text was updated successfully, but these errors were encountered: