I’ve recently started with Home Assistant. The first day everything went very smooth. I installed it, added lights, added 3 motion sensors and added a couple of automations. Everything worked brilliantly. And the things I did on the first day still do.
On the second day I tried adding more motion sensors. Unfortunately they were all stuck in the ‘detected’ state.
On the third day I replaced all the batteries they came with with rechargeable batteries, then new old skool batteries and then batteries I was already using for other things in the house, but unfortunately all the motion sensors from day two were still stuck in the ‘detected’ state.
On the fourth day I tried all kinds of different workflows and stuff like developer tools > statuses > set status to ‘off’. Still they were stuck saying ‘detected’. By the way, if I set the status to off manually, then they stay ‘undetected’ for 5 to 30 seconds before getting stuck in ‘detected’ again.
Today is the fifth day. I’ve added 6 more motion sensors of 2 different types, all with new batteries. All 6 motion sensors are stuck in their ‘detected’ state.
I don’t really believe I could add 3 sensors on the first day and they all still work fine and then add 9 more sensors and they all turn out to be DOA. So I must be doing something wrong. And that’s why I am here, because I have no idea on how to approach this issue.
Reconfiguring the sensors fails: it does ‘binding’ and ‘reporting’ and then fails. The details are as follows:
Have the same problem with 2 motion sensors. They worked fine for a few days but now remain in status detected. Also no clue on how to reset this status or why it remains this way.
I have exactly the same issue. I am using Silvercrest MotionSensors as OP. i thought it might be the distance to the next zigbee gateway, so i ordered 4 Zigbee PowerPlugs (NOUS) to have some more gateways. But,… no success, the motion sensor gets stuck in “motion detected” nearly every day.
Of course i could write a small skript or nodered-flow to put it back into “no motion” after a while, but 1. it seems very hacky and 2. i would like to understand the reason for this issue.
btw: RSSI for this sensor is -74. I know, it’s not the best, but it detects motion without any error. Only the switch back to “no motion detected” does not work in 40%
Bumping, same issue here. Just started with HA a few months ago so a relatively small, non-complex environment. Motion sensor gets stuck in Detected until I interact with it in anyway (any config change) then it clears up.
The original post was two years ago. You’re more likely to get help if you start a new thread giving details of your problem and your setup. Are you using ZHA or Z2M, for example? What Zigbee coordinator? Also details of the motion sensors - there seem to be several different “Silvercrest Smart Motion Sensor”.
Good points, thank you. I just saw the last reply and thought it said 25, it was last year though.
Your advice led me down a path of figuring it may be an issue with the device’s config in Zigbee.
I am using the Zigbee Home Automation with Sonoff Zigbee 3.0 USB Dongle Plus V2 on a Raspberry Pi 5 running Raspbian. HA is the full version in a docker container. But I found this forum post after searching my device model, which seems to imply an issue with the config:
