Anthony

> ServiceMonitor also did not work for me. > > What worked for me was to patch my aws-node ds like: > > ```shell > kubectl patch daemonset aws-node -n...

> IMO, there's nothing wrong with asking (as a user of this project) if there may be a desire to add this functionality this year or if it's longer off,...

> I notice you are a sponsor @acki Christopher, so "We need this" is a fair comment. Multi-user is a huge request though, almost as big as the rest of...

Same issue here: - Latest version of zigbee2mqtt docker image (previously reproduced with an image from beginning of 2023) - Key well found via lsusb: Bus 001 Device 006: ID...

Small update: - after few restart of the docker container, "Coordinator firmware version" is well found but "Error: get network parameters Error:TIMEOUT" continue. - I kept the docker compose up...

Finally it worked during 1 week (until now)... I tried to add a new device & boom, error is back since 1h

> The solution is trivial :) Service is already running, stop it and start it again. VM: zigbee2mqtt $: sudo systemctl stop zigbee2mqtt $: npm start It's not the same...

In addition, like mentioned 2 weeks ago. All worked well after few hours of restart, z2mqtt was stable during few days. Tried to allow pairing: ``` Zigbee2MQTT:error 2023-12-15 21:13:33: Request...

Tried also on different USB port (with or without cable): same issue Tried with a DB reset (reset the z2mqtt conf): same issue Tried to check on bios what goes...

Workaround at this time: switched zigbee2mqtt to raspberry (docker) and all works in addition of the N100 mini computer (HA/mosquitto)...