Skip to content
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

Websocket error in 0.80.1 #17532

Closed
tjntomas opened this issue Oct 16, 2018 · 2 comments
Closed

Websocket error in 0.80.1 #17532

tjntomas opened this issue Oct 16, 2018 · 2 comments

Comments

@tjntomas
Copy link

tjntomas commented Oct 16, 2018

Home Assistant release with the issue: 0.80.1

Last working Home Assistant release (if known): 0.76.2

Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 18.04 running Home Assistant in a virtual enviroment as per the advanced installation guide.

Component/platform:

Description of problem:

Log fills upp with:

2018-10-12 21:21:09 ERROR (Thread-10) [websocket] error from callback <bound method Listener.on_open of <Listener(Thread-11, initial daemon)>>: on_open() missing 1 required positional argument: 'ws'
2018-10-12 21:21:09 ERROR (Thread-10) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-11, initial daemon)>>: on_message() missing 1 required positional argument: 'message'
2018-10-12 21:21:12 ERROR (Thread-10) [websocket] error from callback <bound method Listener.on_close of <Listener(Thread-11, initial daemon)>>: on_close() missing 1 required positional argument: 'ws'

The same errors are repeated in the log every minute or so and the frontend stops responding and automations have minute-long delays.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):


The problem goes away when downgrading the websocket-client in the virtual environment to version 0.48 with:

$ pip install websocket-client==0.48.0

@awarecan
Copy link
Contributor

@tjntomas
Copy link
Author

Strange. I had websocket-client 0.53.0 after a new install of Home Assistant in a venv. Anyway, obviously not caused by the installer then, so I will close the issue.

@home-assistant home-assistant locked and limited conversation to collaborators Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants