search

OnFreund / pyrisco

MIT License
9 stars 9 forks source link

Agility 3 - mono socket TCP board --- unsupported comands // max. concurrency to high #18

Closed jakob1911 closed 7 months ago

jakob1911 commented 7 months ago

Hello OnFreund,

as answered here https://github.com/home-assistant/core/issues/103380 i want to contribute with the following termes. For me the following was necessary to get my Agility 3 -RW032 - with mono socket TCP board to work --- together with HomeAssistant integration "Risco":

  1. "FSVER?" command is not known by my panel. My RW-Panel is using "PNLVER?" which i saw in the communication logs while working with risco configuration software. ----- You already fired a new version -- should be find with 0.5.9, but not tested right now !

  2. When creating the zones i ran into the next error -- not retriving any zone with homeassistant ---->> i figured out that the following two commands are as well not known by my Panel:

    • the command for the "tech" == "(f'ZLNKTYP{zone_id}?')"
    • the command for the "groups" == "(f'ZAREA&*{zone_id}?')"

Please see my snippset on how i modified to got it working (for me only):

image

  1. The hardest problem i had so figure out ---- Problem: HomeAssistant is sometimes not retrieving all zones after restart or init. The Problem got worser the more zones i added to the alarm system.....

My solution after lot of trying with the code --- i found the real problem: My old mono socket TCP panel in the Agility 3 gets overloaded with the fast requests when retrieving all the zones in the loop. --_>> My solution is to reduce the parameter "max concurrency" at risco_socket.py from 4 to 2

see the snippset:

image

I hope you can find solutions togehter with my input to reach out the older boards like mine finally. As in the previous reply, i really apprecitate your work and time on the project !

BR Jakob

OnFreund commented 7 months ago

For future reference, please use text rather than images for code. You can use markup to format it (and preferably show diffs). I released version 0.5.10 which skips the calls for tech and groups for legacy panels. As for max concurrency, we need to know it before we know the panel type, so we'll have to solve this on the HA side.

jakob1911 commented 7 months ago

Thanks for the fast implementation. Sorry i will use text with markup for the future.