Reconnection error every minutes with mh201

[marcob79]

Reconnection error every minutes with mh201

[FredBlo]

It seems the gateway is refusing a command which, in monitoring mode, is probably the 'keep alive' call.
Is this enabled on the gateway config node (every 60 sec) ? If it is, try disabling to check whether this is a possible root cause

[marcob79]

Yes, that's seems root cause. I set it to 0 and now I didn't get the error anymore. Do you think it could be fine to leave it in this way? Do you suggest to try to upgrade my mh201 firmware in case (if I will be able to do that and if there is a newer firmware) and try to enable keep alive again? Thanks Il ven 21 mag 2021, 14:26 FredBlo ***@***.***> ha scritto:

…

It seems the gateway is refusing a command which, in monitoring mode, is probably the 'keep alive' call. Is this enabled on the gateway config node (every 60 sec) ? If it is, try disabling to check whether this is a possible root cause — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APZCFFUXDLCXJANIRCZTKJTTOZGNRANCNFSM45G2OH6A> .

[FredBlo]

During my tests, I only had to enable keep alive in the F455. The other gateways I tested (MH202, MyHomeServer1 and F459) never closed the connection, so keep alive was not necessary.
However, if you have a technical network interruption, it is not always detected. In such a case, the keep alive tries to connect, it fails (since connection was lost, but unaware), and automatically reconnects.
So I would advice to let a keep alive once every 60 minutes just in case.

PS : if a new firmware exists for your MH201, I advice to upgrade. Bticino does not make many firmware updates... only when really necessary... so if there is one, enjoy it ;-)

I will check if there are other 'keep alive' commands which I could use for next version & keep you posted

[FredBlo]

Hi @marcob79,

Fyi, I just released v2.2.0 (which inludes support for scenario (CEN/CEN+) management).
I also included a fix to better manage keep alive which should allow you to enable it again without having the side-effect encountered before.

Let me know if it worked for you :-)

[FredBlo]

let's consider it's okay now...

[marcob79]

Hi, sorry for late feedback.
I checked with 2.2.1 and it is fine as you said.
Thanks

[FredBlo]

OK @marcob79 , tks for feedback !