Handle the out of Memory error by counting subsequent timeouts - keep alive - Implement ConnectionError

[jakob1911]

Hello OnFreund,

i tested a few things regarding the "out of Memory error" home-assistant/core#119138 over the last weeks, just right before you updated your repository -- in fact i came a bit late with this now :)

I don´t know if my changes would fit your standard. But in fact it solves the problem with out of memory in my case compleatly.
(i´m using pyrisco with HomeAssistant in local) !

• Created parameter "max_timeout_keep_alive_subseq" in pyrisco
  --> If a "Timeout CLOCK" happens 3 times subseqently, i´m raising an error "ConnectionError"
  In my test together with HomeAssistant Integration i checking for the error the same way you do for "ConnectionResetError" (init_.py) and starting a reload of the Integration when "ConnectionError" is raised by pyrisco.

I would be happy if you can take parts of my changes for everyone´s needs.

Best regards

Jakob

[rhalutz]

Hi @jakob1911 — cross-linking #44, which I just opened against the same class of symptom (CLOCK keep-alive timing out repeatedly after the panel drops the session).

The two PRs take different angles:

• This PR (Handle the out of Memory error by counting subsequent timeouts - keep alive - Implement ConnectionError #22): detect the disconnect by counting consecutive CLOCK timeouts and then raise.
• Cancel pending futures and exit listener on EOF / unexpected exceptions #44: fix the root cause — the _listen loop currently doesn't exit on asyncio.IncompleteReadError (graceful EOF) and doesn't cancel pending futures, so the keep-alive sits in asyncio.wait_for for the full 10s before raising. With that fixed, the timeouts you're counting shouldn't happen in the first place.

Posting so @OnFreund has both visible side-by-side and can pick whichever framing fits best. Not trying to step on your PR — happy to defer or close mine if the maintainer prefers the timeout-counting approach.

[OnFreund]

Thanks @rhalutz. I like your approach better - I'll try to review in the next few days. One thing that did pop out in a cursory look is OSError which I think is casting a pretty wide net, and I'd prefer something more specific. I'll review more thoroughly and we'll continue the conversation there.