Ecovacs - component not loading #18054
Comments
christensonautohome
changed the title
|
found this in my log... this is among the last log files for ecovacs. this appears after the message saying it's taking over 60 seconds |
|
|
I'm not sure if this is the same error, but mine works fine on 0.80.3, but breaks on 0.81.0 or newer. Here are the relevant logs: |
|
These issues are being handled by the supporting library: https://github.com/wpietri/sucks/issues Please direct these issues to over there. |
|
I'm seeing the same issue as @kmlucy. Works in 80.3, errors in every 81.X version. It appears that the sleekxmpp has changed between versions. I wonder if @OverloadUT can shed any light on what the issue might be. Nm, I see that there is an open issue in the sucks repo as @dgomes mentioned. |
|
It may be an upstream issue, but something changed between 0.80.3 and 0.81.0. Until the upstream issue gets resolved, can we reverse whatever change caused this problem to pop up? |
|
Should l close my ticket? It seems as though this is being checked into here. |
|
The last change on the ecovacs platform was updating the supporting library. It would seam unwise to revert that update. We can leave this issue open for reference, I've already marked it as "waiting-for-upstream" |
|
Just FYI, I was able to get the Ecovacs component working again by reverting to the dependencies from 0.80. I run in Docker, so a simple Dockerfile with: fixes the problem. I'm not sure if reverting will cause problems for other components, but I haven't noticed any to date. |
I also revered mine, I've tried sleekxmpp 1.3.1 & 1.3.2 and in all occasions i'm seeing the ping error still. Don't suppose you know how to resolve this? Basically the times out the ping to the bot and that only time you get a status update is when it first initiates the connection on home assistant. |
|
@DemiMelfice What ping error are you referring to? My N79 updates fine. |
I see the following error: 2018-11-21 03:49:01 WARNING (SyncWorker_5) [sucks] Ping did not reach VacBot. Will retry. 2018-11-21 03:49:01 DEBUG (SyncWorker_5) [sucks] *** Error type: cancel 2018-11-21 03:49:01 DEBUG (SyncWorker_5) [sucks] *** Error condition: remote-server-timeout it then loads: after this is loads everthing such as GetCleanState, GetChargeState, GetBatteryInfo, GetLifeSpan and then the following: 2018-11-21 03:49:02 DEBUG (event_thread_0) [sucks] *** error = get_life_span 2018-11-21 03:49:02 DEBUG (event_thread_0) [sucks] *** error = get_life_span 2018-11-21 03:49:31 DEBUG (event_thread_0) [sucks] *** sending ping *** when the vacuum cleaner is running it doesn't update within HA. I have a R98 |
|
I haven't seen any of those errors with mine. |
|
Can I ask you to check your init.py and confirm if at line 44 it looks like this: |
|
Which |
|
Sorry the one under sucks components folder. I have HA in a docker so mines is located @ ./usr/local/lib/python3.6/site-packages/sucks/__init.py |
|
I have the same code you posted in mine, but it starts at line 126. My |
|
Thanks, I connect to the EU/UK and i'm using a R98. I believe everything else I have is the same set up as yours. |
|
Has this issue been solved yet? I am hoping it is because I bought an Ecovacs N79S hoping I could set up and control it with Hass.io. Please say it's fixed. |
|
It is not fixed yet. |
|
You think it's gonna be fixed seeing that it's been so long since the issue was opened. I might have to return my ecovacs and buy a different brand.
On Thursday, December 20, 2018, 4:37:20 PM EST, h4nc <[email protected]> wrote:
It is not fixed yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I'm waiting for the fix since some months. I think it will be fixed. There is a workarround somewhere in the thread (i think). My workarrount for now is to use ir commands provided by my broadlink rm mini to turn on the ecovacs. Would be better with the component, but yeah ... I hope it will be fixed |
|
Sure wish I could find a workaround but I am not as verse. I am new to home automation and am learning each day. |
|
The workaround is to install the previous dependencies: If you use Docker, you can just use kmlucy/docker-home-assistant instead of homeassistant/home-assistant for now. |
|
Any update on this? Is the problem with the sucks library? If so, I tested out the library on its own on my Ecovac N79S and both the master branch (https://github.com/wpietri/sucks) and the latest PR (wpietri/sucks#63) worked just fine. Edit: to clarify I tested sucks library on my windows box, not on hassio, which looks like the env having issues |
Hi, any news? |
|
Any new on getting this working? I'm a Hass.io user. |
|
I am happy to report that I have a stopgap fix submitted to the upstream library: wpietri/sucks#67 |
|
Hey there @OverloadUT, mind taking a look at this issue as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
|
Woohoo!! so excited for this to start working! Thanks so much OverloadUT! |
|
Thanks a lot OverloadUT! Keep on the good work! Cheers |
|
So does this work for hassio users too again? Or do we have to wait for an update? Does someone know if this will work with 0.92? Don't available yet for hassio users. |
|
I prey it makes it into the coming 0.92 release as well :) |
|
Thanks @OverloadUT - you are awesome! @h4nc @skynet01 This didn't make it into 0.92.0, but keep an eye on the release notes for 0.92.1 - failing that it should be included in 0.93.0 |
|
So nice to see this working again in 0.92.1 Thank you so much @OverloadUT |
|
Just checked and we are back in business !! Great... |
|
Hi, thanks for the work to the component, but I still have problems loading this. Here are my logs: This is the entry in configuration.yaml: |
|
I don’t have the vacuum: section you have. Only ecovacs: ... |
|
I removed the vacuum section, restarted and now HA shows a new vacuum entity :-) |
|
BTW it works now, but this is a warning that shows up in the logs: |
|
@OverloadUT First it worked fine, but lately I takes serveral HA-restarts until it starts without an error. Does someone else have this issue too?
and |
|
No issues here !! |
|
I have the exact same problem...
Den tors 16 maj 2019 kl 22:37 skrev whadat1 <[email protected]>:
… No issues here !!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18054>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACEQRS6XNSSMAJYALOCZCLPVXAZTANCNFSM4GAQY2MQ>
.
|
|
Same problem, log entry: |
|
I also have a similar issue: I hope this is somehow helpful |
|
This is the error I get:
ERROR (MainThread) [homeassistant.setup] Error during setup of component
ecovacs
File
"/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py",
line 156, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
future.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result
raise self._exception
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in
run
result = self.fn(*self.args, **self.kwargs)
File
"/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/ecovacs/__init__.py",
line 49, in setup
config[DOMAIN].get(CONF_CONTINENT))
File "/srv/homeassistant/lib/python3.6/site-packages/sucks/__init__.py",
line 126, in __init__
login_response = self.__call_login_by_it_token()
File "/srv/homeassistant/lib/python3.6/site-packages/sucks/__init__.py",
line 185, in __call_login_by_it_token
'token': self.auth_code}
File "/srv/homeassistant/lib/python3.6/site-packages/sucks/__init__.py",
line 177, in __call_user_api
"failure {} ({}) for call {} and parameters {}".format(json['error'],
json['errno'], function, params))
RuntimeError: failure set token error. (0) for call loginByItToken and
parameters {'todo': 'loginByItToken', 'country': 'SE', 'resource':
'SCP9YFC7', 'realm': 'ecouser.net', 'userId':
'000000000000000_xxxxxxxxxxxxxxxxxxxxxxxx', 'token':
'se_000000000000000000000000'}
Den fre 17 maj 2019 kl 20:52 skrev Rudertier <[email protected]>:
… I also have a similar issue:
2019-05-17 20:49:16 ERROR (MainThread)
[homeassistant.components.websocket_api.http.connection.1789064144] <iq
id="608ecf2b-9365-46f0-95de-4bla-1BEF" to="
***@***.***/atom" from="
***@***.***/27d63er421431bdabc326301ec1a8f5e22"
type="set"><query xmlns="com:ctl"><ctl td="Clean"><clean type="auto"
speed="standard" /></ctl></query></iq> Traceback (most recent call last):
File
"/usr/local/lib/python3.7/site-packages/homeassistant/components/websocket_api/commands.py",
line 121, in handle_call_service connection.context(msg)) File
"/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1138,
in async_call self._execute_service(handler, service_call)) File
"/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1160,
in _execute_service await handler.func(service_call) File
"/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_component.py",
line 194, in handle_service required_features File
"/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py",
line 316, in entity_service_call future.result() # pop exception if have
File
"/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py",
line 337, in _handle_service_platform_call await getattr(entity,
func)(**data) File
"/usr/local/lib/python3.7/site-packages/homeassistant/components/vacuum/__init__.py",
line 301, in async_turn_on partial(self.turn_on, **kwargs)) File
"/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs) File
"/usr/local/lib/python3.7/site-packages/homeassistant/components/ecovacs/vacuum.py",
line 144, in turn_on self.device.run(Clean()) File
"/usr/local/lib/python3.7/site-packages/sucks/__init__.py", line 416, in
run self.send_command(action.to_xml()) File
"/usr/local/lib/python3.7/site-packages/sucks/__init__.py", line 413, in
send_command self.xmpp.send_command(xml, self._vacuum_address()) File
"/usr/local/lib/python3.7/site-packages/sucks/__init__.py", line 482, in
send_command c.send() File
"/usr/local/lib/python3.7/site-packages/sleekxmppfs/stanza/iq.py", line
233, in send raise IqTimeout(self) sleekxmppfs.exceptions.IqTimeout: <iq
id="608ecf2b-9365-46feqwre-4c6f92c7b97e-1BEF" to="
***@***.***/atom" from="
***@***.***/27d63eqer1bdabc326301ec1a8f5e22"
type="set"><query xmlns="com:ctl"><ctl td="Clean"><clean type="auto"
speed="standard" /></ctl></query></iq>
I hope this is somehow helpful
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18054>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACEQRTJ57AONFES57TIOVLPV35G7ANCNFSM4GAQY2MQ>
.
|
|
Same problem here, with a Deebot OZMO 930 |
|
This issue is closed. No point in adding comments in issue which is closed. So created new one... |
|
New issue: |
and others
Home Assistant release with the issue:
using HASSIO - 0.81.2
Last working Home Assistant release (if known):
Can't remember if it was 0.79 or if it might have been working in 0.80 (I think 0.80)
Operating environment (Hass.io/Docker/Windows/etc.):
Pi3+
Component/platform:
ecovacs
Description of problem:
It appears the setup is taking too long and as a result the component is no loading.
Problem-relevant
configuration.yamlentries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: