It seems that the device gets overwhelmed with parallel requests and returning BUSY status codes, from the server logs
2022-06-16 22:32:30 pulver chip.IM[486980] INFO Received status response, status is 0x9c (BUSY)
This happens e.g. when async_added_to_hass is called in parallel for multiple entities. For a Matter Node which exposes multiple devices (like the All Cluster examples) this gets problematic.
Ideally we should synchronize calls on a per Matter Node.
It seems that the device gets overwhelmed with parallel requests and returning BUSY status codes, from the server logs
This happens e.g. when
async_added_to_hassis called in parallel for multiple entities. For a Matter Node which exposes multiple devices (like the All Cluster examples) this gets problematic.Ideally we should synchronize calls on a per Matter Node.