-
Notifications
You must be signed in to change notification settings - Fork 6
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
Restart after connection lost #5
Comments
I just pushed a new version that includes more resilient behavior for the socat process. It's been running stable for over a month for me. Give it a try and let me know if that fixed the disconnects.
|
thx -> testing it now. If it "survives" a day, it should be fine! |
still having problems logs D, discarding invalid data prior to message 7e 07 10 79 7e, |
That's a different issue. The socat changes address if you lose the TCP connection to your RS-485 to ethernet device. That actually looks like a normal debug with the new enhanced logging. It's every byte up until it gets a complete message. Thus the first 20-30 bytes could be "invalid date prior to message" right up until you get the last byte of the message. What is the symptom? |
At some point in time I am not able to control the whirlpool, using the home assistant control entities. Any ideas what I can do or provide to you to help finding the bug? Thx a lot for your help My System |
I'm running into the same thing. It's acting a bit like an overflow or memory leak. Your best bet would be to rule out my docker container and install balboa worldwide app directly and see if the problem persists. If it does, open an issue against the project with relevant logs, if not, let me know and I'll keep digging into the docker image. I just have a cron job that restarts the container nightly for now until I have more time to troubleshot. |
Just wondering if you ever got to the bottom of this? Have managed to get it set up and running - but after a while seems to become unresponsive until I restart the container within portioner. |
same here. connection drops after a while |
I've released a new version that uses a more stable connection method. Give version 2023.06 a try and see if that improves things for you. I've gone a week without needing to restart the container. Thanks to @supersebbo for the suggestion and research to address this. |
thanks a lot! i have already updated and give it a try |
sorry - very newbie user here - my docker-compose file has following: services: does this mean it should have already updated to the above image? |
Works great but when the WIFI2Serial bridge gets lost, I need to restart the container.
Is there an option like "restart: unless-stopped" but called "restart: on_connection-lost" ?
BR
Chris
The text was updated successfully, but these errors were encountered: