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

[Bug]: zwavejs2mqtt does not reconnect if the TCP (ser2net) serial port was drop #4660

Closed
3 tasks done
dick902 opened this issue May 26, 2022 · 9 comments · Fixed by #5715
Closed
3 tasks done

[Bug]: zwavejs2mqtt does not reconnect if the TCP (ser2net) serial port was drop #4660

dick902 opened this issue May 26, 2022 · 9 comments · Fixed by #5715
Assignees
Labels
bug Something isn't working

Comments

@dick902
Copy link

dick902 commented May 26, 2022

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Zwavejs2Mqtt version

6.10.0

ZwaveJS version

9.3.0

Describe the bug

This is a similar issues as zwave-js/zwave-js-ui#1246.
Once the TCP serial connection drop, it will nerve reconnect until manual restart zwavejs2mqtt or press the SAVE button in the setting menu (another method to restart) also make the TCP serial port reconnect.

I had tested with v4.3.1 and found the issues was resolved before.
But it is happening again on v5.x.x and v6.x.x of zwavejs2mqtt again.

To Reproduce

  1. Connect the Z-Wave dongle via ser2net
  2. Stop ser2net
  3. Wait for the lost connection in zwavejs2mqtt
  4. Restart ser2net

Expected behavior

After 4., the TCP serial port connection should be auto-restored.

Additional context

No response

@dick902 dick902 added the bug Something isn't working label May 26, 2022
@robertsLando
Copy link
Member

@dick902 Could you upload logs please? I need to see the errors that are thrown

@dick902
Copy link
Author

dick902 commented May 26, 2022

@dick902 Could you upload logs please? I need to see the errors that are thrown
zwavejs2mqtt_2022-05-26.log

Pls. find attached file as my log file in debug level.
Log file seems show nothing about the TCP serial connection had interrupted.
In the control panel at not showing anything the TCP serial connection had interrupted.
In this log file, I had restart ser2net service at Line 11779, and the connection had broken here.

@robertsLando
Copy link
Member

I think the problem so is that zwavejs ins't catching the close event or isn't reconnecting

@dick902 could you also upload zwavejs driver logs please?

cc @AlCalzone

@dick902
Copy link
Author

dick902 commented May 26, 2022

I think the problem so is that zwavejs ins't catching the close event or isn't reconnecting

@dick902 could you also upload zwavejs driver logs please?

zwavejs_2022-05-26.log
zwavejs2mqtt_2022-05-26.log

cc @AlCalzone

Pls. find attached files.
Seems also not had anything related TCP serial disconnected

@AlCalzone AlCalzone transferred this issue from zwave-js/zwave-js-ui May 30, 2022
@AlCalzone AlCalzone self-assigned this May 30, 2022
@kvs
Copy link

kvs commented Oct 9, 2022

I'm seeing the same issue - everything works fine, ser2net machine restarts properly but zwavejs never notices it was gone so it never receives anything from the zwave-stick again. Maybe a periodic status-poll from the stick would be enough to trigger a tcp-closed and reconnect (ie. a keepalive function)?

@robertsLando
Copy link
Member

We need to wait for @AlCalzone to come back from his parental leave in order to fix this

@chrish987
Copy link

Having recently moved to a remote zwave stick I am experiencing this same issue. The last comment is that AlCalzone is away - do we know for how long and when this issue might be fixed?

@AlCalzone
Copy link
Member

👉🏻 #5129

@chrish987
Copy link

is there any ETA on this one being looked at?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants