-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Comments
@dick902 Could you upload logs please? I need to see the errors that are thrown |
Pls. find attached file as my log file in debug level. |
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 |
zwavejs_2022-05-26.log
Pls. find attached files. |
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)? |
We need to wait for @AlCalzone to come back from his parental leave in order to fix this |
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? |
👉🏻 #5129 |
is there any ETA on this one being looked at? |
Checklist
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
Expected behavior
After 4., the TCP serial port connection should be auto-restored.
Additional context
No response
The text was updated successfully, but these errors were encountered: