thanks but ther is no option with setttings specific
Which version of z2m are you running?
1.18.1-1
My z2mqtt looks different
Yes, you’re using an older version (1.18.1 is more than a year old). Current version is 1.25.2.
Thanks, but I downloadet it from the home assistant addon store…
Have a wrong repository…
It has changed some time ago. The addon has been moved to a new repository:
1 Like
Any updates regarding 2021.11 version? I really need this 5s on that crapy sensor… 
Did you ever get this sorted out? I’ve noticed exactly the same behaviour, I’m stuck on detected all the time even though I know for sure there’s nothing causing it to be detected.
I’ve suffered a similar issue with one of my sensors, and when I was thinking that sensor was failing, another sensor started doing the same. In my case, I think the cause was the conbee stick or the phoscon software because I ended up with a full reset of the conbee, deleted hassio integration, deleted all my sensors, update/reflash firmware (on the conbee) and then re-add the conbee integration and re-add all my sensors. Since that, the issue is gone.
Don’t know for sure if it’s your case, but maybe it can help.
Same Problems here. A reset of the sensor, i pressed the sensor button for about 15 seconds, and the problem was gone.
Hmm, next day the problem was back…
Hi, does anyone have any details about how the hack worked on old sensors? Any pinouts, schematics, informations about circuit will be greatly appreciated.
I’m currently working around to bring this hack for newer sensor. I have some old and new sensors with production date of 01/2022. To my surprise when I swapped old sensor board to new mcu the behavior is still correct after 24h. I’ve also tested new sensor board with old mcu and after 24h the hack stopped working.
So I suppose there isn’t any software lock that keeps the new sensor for working with this hack. Something other must changed on sensor board, so this is why I’m searching for any details.
I think I saw it somewhere, but I can’t find it anymore, probably it was inside some youtube video…
Basically, it’s always making the sensor in reset mode, the same that happens when you press the physical button (that’s why it works for 24h).
I’ve no knowledge of circuits, but if you do, you might be able to see something about what the physical button is doing?
I would appreciate a lot if you find any solution as I have 3 of these just getting dust 
1 Like
I’ve tried today to somewhat reverse the circuit, but I’m just a beginner in electronics and don’t have a mircroscope, so it’s hard without proper tools.
I have also seen in some places explanation that this hack makes the button always pushed, but that can’t be the case, just because you can still reset and pair the sensor after the mod.
The hack connects something, I can’t find what, to the “positive” side of button, so probably it creates voltage at some place where normally should be ground…
I have a total of 5 sensors, but also 3 of them are the new version
I am a real newbee with HA but now i start to think i am really stupid. I have to edit a file to change the behavior of the motion sensor so i started to search which file i have to edit. I found i have to edit the ‘devices.yaml’.
Oke next question when the H… do i find this file.
I ended with installing file editor, studio code server and i even installed a Samba server to acces all the files of HA. BUT I STILL CAN T FIND THE DEVICES.YAML, WTF?
Is there anyone who can tell me what file and where i have to change/add the code into 
Thanks,
Rob
i’ve just mod the new motion sensor E1 (RTCGQ15LM)
btw, it is not work on it
it stick on 1 min detect
also, it cannot turn 5sec detect when i press the reset button
Hmm, i have a few xiaomi sensors applied with pencil hack, today updated my deconz addon to 6.18.0 , and now all 3 xiaomi sensors are in “motion detected state” ??
anyone else seeing this too ?
