-
Notifications
You must be signed in to change notification settings - Fork 26
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
websockets not closing correctly? #59
Comments
Not fixed. Behavior still the same with v1.0.6. Strange things start happen after call of onObjectChange().
Also, after the steps above, changes made to any controls in frontend are no longer stored.. e.g. try to change anything (turn off light) and reload the page. |
Sorry I cannot reproduce your behavior. |
here is the log from adapter restart until second update of objects https://pastebin.com/CmnjpkpY |
I'm having the same issue.. |
Are there any news on this topic?.. Lovelace is unusable.. |
This seems to be fixed in PR and https://github.com/algar42/ioBroker.lovelace |
Describe the bug
Everything works fine until we close and re-open browser or open front-end from another device. In this case it looks like the previous ws client is not destroyed and server continue to broadcast to closed connections. As a result with each new connection we get increasing number of data sent to the clients and states update on page reload and/or on another device stop working...
To Reproduce
At this stage
a) on page reload we get old data (looks like connection with new client does not init correctly).
b) we start getting duplicated state_updates from server, i.e. server sends data to the closed connection from point 1.
Here at the picture only one front-end opened, but states are duplicated:
If can't repeat the issue, try to re-load page/ re-open browser couple of times.. at some point you'll see it
The text was updated successfully, but these errors were encountered: