markferry
markferry
Should i be suspicious of the `"client_module": "mqtt_io.mqtt.asyncio_mqtt",` in the normalized config? Do I need to explicitly switch it to anyio-mqtt?
Upgraded to Debian 11 (Bullseye) with python3.9. Same behaviour (`2.6.6` and `develop` work but has the same rising CPU issue) Enabled more logging. Config: ```yaml mqtt: host: 192.168.x.x topic_prefix: mqtt-io/library...
Not workable.
While not ideal, restarting (the service) is an effective workaround. (Use cron or systemd's [`RuntimeMaxSec`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#RuntimeMaxSec=))
 Looks good. Nice work!
>  > > unfortunately for me the issue seems not to be solved. i there anything a user has to do beside of updating the raspberry? Did you install...
This issue wasn't actually about #301. But trying to find a workaround for #301 is how I discovered this issue in the first place. Either way I think feature/trio has...
aiomqtt have now released a paho-mqtt v2 version: https://github.com/sbtinstruments/aiomqtt/releases/tag/v2.1.0
This also breaks for python projects when combining coverage reports produced by test runs using different python versions - a common scenario. The workaround is to combine coverage _databases_ beforehand...
Shorter log: ```log # play Party 1 stream (canard + kitchen) , [2021-07-30T20:06:05.794634 #676586] INFO -- : MISCONFIGURED: Party 1 I, [2021-07-30T20:06:05.794842 #676586] INFO -- : Going to reconfigure group...