[digiplex] Handle erroneous responses and restart the bridge

[rmichalak]

Better handling of erroneous messages that may be received from the alarm system.

Based on the behavior of my alarm system, in case of an erroneous message there's only one way to restore proper communication: restart the bridge connection.

Supersedes: #17829 #17864

Closes #17828

[rmichalak]

@jlaur This is a compilation of my and your changes (including your test file).
I backported these changes to my old version of OH (2.5) and I will let it work for a week to make sure it's stable.

[jlaur]

Thanks for taking care of this! Otherwise LGTM. Since most of the code origins from #17864 it would be best to have someone else review.

[lsiepel]

@rmichalak this is marked as draft, is it ready to review and merge or are you waiting for something else?

[jlaur]

is it ready to review and merge or are you waiting for something else?

See #18035 (comment). So it should be ready for review, but is still under test.

[lsiepel]

Thanks, LGTM.

Let's wait for test confirmation.

[rmichalak]

Okay, so I've just encountered a first malformed response: G01N008A01 - each number should have 3 digits but in this case two of them only have two and thus the whole message is shorter than expected... I may be smarter in parsing these things, but anyway... it's not a message that should appear on the line, according to Paradox documentation.

The good news is that the fix works (restarts the connection as expected), so we can merge it.

I will keep checking for these malformed messages as perhaps it's not necessary to restart the connection in each case. But that's a separate task.