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

Connection failed #31

Closed
tommedIO opened this issue Oct 28, 2020 · 5 comments
Closed

Connection failed #31

tommedIO opened this issue Oct 28, 2020 · 5 comments

Comments

@tommedIO
Copy link

tommedIO commented Oct 28, 2020

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:

valloxmv.0 2020-10-28 08:24:05.748 error (1981) Connection failed
valloxmv.0 2020-10-28 08:24:05.747 error (1981) socket hang up
valloxmv.0 2020-10-28 08:15:06.778 error (1981) Connection failed
valloxmv.0 2020-10-28 08:15:06.777 error (1981) socket hang up
valloxmv.0 2020-10-28 07:57:05.802 error (1981) read ECONNRESET
valloxmv.0 2020-10-28 07:57:04.757 error (1981) Connection failed
valloxmv.0 2020-10-28 07:57:04.756 error (1981) read ECONNRESET

Versions:

  • Adapter version: 1.1.1
  • JS-Controller version: 3.1.6
  • Node version: v10.22.1
  • Operating system: raspian
@hacki11
Copy link
Owner

hacki11 commented Oct 29, 2020

At first i recommend to verify the connection between iobroker and vallox device.
Please setup and log a continuous ping from iobroker os to vallox ip address including timestamps.
Then i would check if the ping has lost packets or latency increases during events where the iobroker adapter hast failed connections.

You could try to set log level to debug for valloxmv adapter, perhaps we can get more detailled error logs.

@mnemo70
Copy link

mnemo70 commented Jan 28, 2021

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. :-/

@hacki11
Copy link
Owner

hacki11 commented May 3, 2021

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?

@mnemo70
Copy link

mnemo70 commented Jun 18, 2021

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.

@hacki11
Copy link
Owner

hacki11 commented Aug 4, 2022

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?

@hacki11 hacki11 closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants