-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Binding stops working in different connection cases #34
Comments
There was an issue where a scheduled task to read data from PLC was interrupted while trying to reconnect. PLC was sebsequently connected, but no data was read. Issue is fixed now. You can try new release: |
Looks like it worked perfectly now :-) Thanks for fixing this bug. Works since 15 days in my setup without any problems. Good job with this binding, not sure why it is not in the official OH bindings? :-) |
* Added update mode * Fix reconnect issue #34 * Space between data in one area increased to 128 * Version update * Startup delay to ensure binding initialization completed
Hello Docbender,
i found some issues with the binding when there are connection problems or after the restart of the complete openhab.
My setup:
Issue description:
In some cases the binding stops working. In the openhab bindings page it still shows "online" in the bridge and also on the devices, but it doesn't send or read data to and from the plc. I also got that issue sometimes on only one device and other ones still work as normal.
Cases where this does happen:
So for me it looks like, if there was a connection issue during a data transfer, the binding then freezes and had to restart again manualy to get back working.
Fast solution for get it working again:
Pause and start the bridge first, then do the same thing on all the devices.
Maybe you could take a look into your binding and get this problem fixed. If i could help you with logs or something else, let me know what you need :-)
Thank you for keeping this binding alive!
Best regards,
Marcel
The text was updated successfully, but these errors were encountered: