-
Notifications
You must be signed in to change notification settings - Fork 7
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
Connection failed #31
Comments
At first i recommend to verify the connection between iobroker and vallox device. You could try to set log level to debug for valloxmv adapter, perhaps we can get more detailled error logs. |
Looks like this is the problem I reported at #danielbayerlein/vallox-api#24. The Vallox CPU cannot handle too frequent connections, at least in my ValloxPlus 270 MV. I'm still thinking about a fix. The currently used non-Promise WebSocket-module needs special handling. :-/ |
I have read your comments on vallox-api but i can not reproduce with my device. Do you think you can come up with a solution or do you have a suggestion on how to work around that limitation of your device? |
As stated above it's a problem with the websocket implementation of the underlying vallox-api, but I'm not able to provide a fix at the moment, since this reaches deep into Promises and I'm not really familiar with that. |
I often have a "network error" message when accessing vallox Web UI with my mobile browser. This seems to be a vallox firmware issue. Did you solve your issue? Can we close this? |
First: Thank you for that great Adapter. I'm very happy with it.
Describe the bug
The Adapter ist running fine - the most time. Sometime it has connection problems. Roundabout 10 times a day, the IOBroker log shows this massage:
Versions:
The text was updated successfully, but these errors were encountered: