It appears to be improved so far, but of course I would prefer to be running up to date builds of Hass.IO and plugins. I’ve restored to a backup (I’m running in a VM) to see if they stop the behaviour. The only routers I have in the zigbee network are the Xiaomi plugs. But the thread you linked goes back much further. This has been working for quite a while for me without issue, which is why I was thinking it could have had something to do with an update. All plugs, sensors, etc are in the same place as always.

I’m only assuming it may be some update that is causing it as nothing else has changed within the system. Just wondering if anyone has any idea what might be happening, or what logs, etc I could provide that may assist. Thinking it may have been a battery issue (though the battery was reporting as 100% in Hass.IO), I have changed the battery on one of the Aqara sensors with no change to the behaviour. I have several of the Xiaomi Mija motion sensors and they continue to work without issue. This only seems to happen with the Xiaomi Aqara sensors. If I don’t restart Hass.IO then some time later when I walk past again I get the response again. If I restart Hass.IO they seem to work fine again for a bit and then eventually when I walk past them again they won’t trigger. Or perhaps they are picking up the motion but not sending the info to Hass.IO. Over the past couple of weeks, I’ve found that my Xiaomi Aqara motion sensors aren’t detecting motion when I go past them. I also have several Xiaomi plugs acting as routers.

I’m running latest build of Hass.IO core, mosquitobroker, zigbee2mqtt and zigbee2mqttassistant via a CC2531 USB stick.

Fallout 1 motion sensor