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
0.38 - Websockets error: object has no attribute 'drain' #5887
Comments
Please remove your |
Sorry, correction: remove |
That did it, thanks Paulus. Is this clearing the deps always required when updating? |
It's related to a bug that we already had but is sadly being discovered in 0.38. We're working on a fix. |
0.38.1 should be out shortly with a temporary fix for this issue. |
@balloob No need to delete the |
@balloob -- Even after upgrading to 0.38.1 I'm seeing this: https://gist.github.com/brianjking/85eeffb30e6423742e719bb83f45b63e |
@brianjking are you using a server like nginx in between? |
@balloob Yes, I'm using this NGINX setup. My configuration files are here. |
You have not correctly setup your NGINX to forward websocket connections. See https://home-assistant.io/ecosystem/nginx/ |
The nginx setup I am using works fine prior to 0.38/0.38.1.
What changed on the nginx page you posted to work with websockets?
…On Feb 12, 2017 14:39, "Paulus Schoutsen" ***@***.***> wrote:
You have not correctly setup your NGINX to forward websocket connections.
See https://home-assistant.io/ecosystem/nginx/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5887 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGePAUdC54Q7kbpNYDDQhmaD9XHJ7Nnoks5rb24SgaJpZM4L-XZE>
.
|
The difference in 0.38 is that we do everything through the websocket instead of falling back to event stream and Rest API. Your setup probably has been broken for a while. |
Home Assistant release (
hass --version
):0.38
Python release (
python3 --version
):3.4.2
Component/platform:
Description of problem:
When I try to access the frontend, I enter my password and see a "Loading Data" screen that doesn't load anything. I just updated to 0.38 and was able to access once, but after a restart I haven't been able to get back in. Configuration shows no errors, home-assistant.log shows the error below repeating every second.
Expected:
Should be able to access frontend, should not receive websockets error.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
Some errors in the Chrome console:
The text was updated successfully, but these errors were encountered: