I have some Xiaomi motion sensors do not become “detected” when there is body motion. But if I wait one minute and move, they work again. So far I have tried v2.15.0, v2.14.1, v2.13.4, it does not happen in other old versions.
Maybe this is a software bug and any sugguestions?
Please consider a motion sensor as a sleeping end device reports motion and immediately goes back to sleep. For approx. 1 min (depending on the device) it therefore retains the status “motion” even if the initial motion was immediately terminated again. Only after this 1 min does it report the status “no movement”.
We need to look at the setup. Can you please answer these questions please.
The deCONZ and firmware versions can be found in the Phoscon App: Menu > Settings > Gateway, and also in the deCONZ GUI: Menu > Help > About deCONZ.
host system (Raspberry Pi 3B+ / 4B / PC / NAS):
Answer:
execution method (Raspbian / Ubuntu / Home Assistant deCONZ add-on / Marthoc Docker container / Windows / Virtual Machine):
Answer:
Is the operating system or deCONZ used with a graphical user interface (GUI, desktop, XServer) or headless?:
Answer:
device (ConBee I / ConBee II / RaspBee I / RaspBee II):
Answer:
firmware version (format 26xxyy00):
Answer:
deCONZ Version (Format 2.xx.yy):
Answer:
Is the ConBee I / II connected to a USB 2.0 or USB 3.0 (blue) socket? - only relevant for ConBee I/II:
Answer:
Is a USB extension used? (yes / no) - only relevant for ConBee I/II:
Answer:
Are other USB or serial devices connected to the host system? (yes / no) - If yes: which ones?):
Answer:
Is a home automation system, other software or third-party apps used in addition to deCONZ / Phoscon App? (yes / no) - If yes: which ones?):
Answer:
Have you tried changing the Zigbee channel or other settings as a solution? (yes / no) - If yes: which ones?):
Answer:
If Raspberry Pi: which power supply is used? (original / manufacturer+model) Specify volts and amps: (e.g. 5.0V, 1.0A):
Answer:
if Raspberry Pi: On which image base is the system set up?: (Phoscon / Raspbian / Raspberry Pi OS / Home Assistant …):
Answer:
If Raspberry Pi: Is an SD card or an SSD used?:
Answer:
If Raspberry Pi: Which way was deCONZ installed? (APT repository / dpkg / via a plug-in).
Answer:
host system (Raspberry Pi 3B+ / 4B / PC / NAS):
Answer: PC
execution method (Raspbian / Ubuntu / Home Assistant deCONZ add-on / Marthoc Docker container / Windows / Virtual Machine):
Answer: docker container inside a proxmox LXC conatiner
Is the operating system or deCONZ used with a graphical user interface (GUI, desktop, XServer) or headless?:
Answer: headless
device (ConBee I / ConBee II / RaspBee I / RaspBee II):
Answer: ConBee II
firmware version (format 26xxyy00):
Answer: 26700700
deCONZ Version (Format 2.xx.yy):
Answer: 2.14.01 / 2022/2/6
Is the ConBee I / II connected to a USB 2.0 or USB 3.0 (blue) socket? - only relevant for ConBee I/II:
Answer: USB 3.0
Is a USB extension used? (yes / no) - only relevant for ConBee I/II:
Answer: yes
Are other USB or serial devices connected to the host system? (yes / no) - If yes: which ones?):
Answer: Yes, Coral USB Accelerator, USB Accelerator | Coral
Is a home automation system, other software or third-party apps used in addition to deCONZ / Phoscon App? (yes / no) - If yes: which ones?):
Answer: yes, running Home Assistant in a separate VM in the same host machine
Have you tried changing the Zigbee channel or other settings as a solution? (yes / no) - If yes: which ones?):
Answer: no, currently is 15
If Raspberry Pi: which power supply is used? (original / manufacturer+model) Specify volts and amps: (e.g. 5.0V, 1.0A):
Answer:
if Raspberry Pi: On which image base is the system set up?: (Phoscon / Raspbian / Raspberry Pi OS / Home Assistant …):
Answer:
If Raspberry Pi: Is an SD card or an SSD used?:
Answer:
If Raspberry Pi: Which way was deCONZ installed? (APT repository / dpkg / via a plug-in).
Answer: