One quick thing that would help work around this is if I could adjust the waitress timeout. It would not fix the underlying issue, but allowing for a longer timeout might prevent things crashing under high load (ie. HA autoconfiguration, when the main loop is overloaded because Z2M generates a LOT of entities for my HA and Zigbee processing gets delayed, or a bunch of zigbee commands hits the concurrency limiter, since the timer is set pre-concurrency limit).
It would be nice if the waitress timeout could be adjusted in the configuration (similar to how the concurrency limit can be).
Right now, I have an issue where things can timeout after 10s for a combination of reasons, primarily
One quick thing that would help work around this is if I could adjust the waitress timeout. It would not fix the underlying issue, but allowing for a longer timeout might prevent things crashing under high load (ie. HA autoconfiguration, when the main loop is overloaded because Z2M generates a LOT of entities for my HA and Zigbee processing gets delayed, or a bunch of zigbee commands hits the concurrency limiter, since the timer is set pre-concurrency limit).
It would be nice if the waitress timeout could be adjusted in the configuration (similar to how the concurrency limit can be).