cool, so we can delete that automation after the first restart of HA, its not needed anymore, only if you want to go back to the 90 sec default setiing
so in other words, you see the “motion deteced” / “not detected” state in phoscon changing every 5 sec?
so also, the binary sensor in HA actually changing every 5 sec?
Yes in Phoscon, and Yes in binary sensor 
I’ve left the automation in, so it’s easy to change the duration.
Plus, if anyone is looking in the windows they probably think I’ve gone crazy walking back and forth the past few hours!
cool, gonna try out , thnx for feedback
And btw, there is no impact on battery with this duration change?
Too early to say I imagine, there should be some hit I guess.
ok, tested it out, indeed the “motion not detected” state is indeed trigger after 5 sec in phoscon
however, after the 5 sec , i dont see any new “motion detected” anymore
so i can dance for 60 seconds, before i see the new motion detected message
so set the duration for 60 seconds instead of 90 , is indeed better, i dont have the 30 sec ghost then
using conbee 1 here
Yeah I can confirm this. My lights do turn off, but won’t turn back on if it’s too fast. But this is different per sensor, so it’s very strange. Also I have to mention that somehow one of my sensors doesn’t work with the script. It still stays on after 5s. And I’ve come to realise that the sensors al have different scan intervals it seems. One stopt after 2min, another after 5min.
I think I’m just gonna do the hardware mod and be done with it. Consistency is key with home automation.
Yes, i can confirm the different scan interval… I have some with 2 min, other with 5… Seems it’s since the new .74 update… Do you also recent installed .74 and noticed the different scan interval?
I installed 6 sensors at my brother’s. They were never opened before and it was a new install. So I used the sensors as they came out the blx.
Which .74 update do you mean? I have the sensors connected via Conbee II and Deconz btw.
Yes, I also opened this in GitHub…
Someone else confirming this is an issue since .74 deconz… If he rollsback to .73 , the sensors are back at the default scan interval/timeout… 2 min instead of 5
Ah yes, I have updated Deconz add-on to 5.3 (which updates to 0.74 according to the changelog). I suppose somehow the automation to change it to 5 seconds doesn’t stick to one of my sensors, which explains why it’s suddenly 5min.
Guess the hardware mod is the only real solution. It does baffle me why we can’t just change the scan inverval on a firmware basis through either Deconz or HA
ok, too bad i cant rollback in hassos, to indeed confirm it as an issue with .74 
I have not updated Deconz on my own setup fortunately. But since it might be a bug and I don’t know how to roll back, I haven’t updated mine yet. So I cannot confirm if it’s due to the update.
I’ve tried the solution posted by marcelod (the automation service one) and after deleting and adding the sensor it works as expected, but after some time suddenly I experienced the problem about the sensor trigger after 5 seconds but is not capable of detecting new motion for about 60sec later.
The strange part is if i delete the sensor, re-pair it in the deconz addon and run the automation again it will work for sometime.
I use conbee II as a gateway and using the 5.3 version of the Deconz addon.
Any Ideas or suggestions of what to do?
1 Like
Did you do the hardware mod? Because without mod it won’t work as already mentioned before.
I have done one sensor soldering and 2 sensors modded with electric paint. Electric paint is really easy to use cheap and works like a charm.
2 Likes
My bad here, you are totally right without the mod the solution works for some hours and then it gets back to the 1 minute refresh time between states.
I end up doing the hardware mod soldering (didn’t know about that electric paint, which looks more easy to use) + the automation by marcelod and now everything works as expected.
2 Likes
I used this method and everything seemed to be working fine. The sensor is reset after 5 seconds and is ready for operation again. But after motion detection and reset after 5 seconds, there are repeated false motion detection after 30 seconds and after 100 seconds . I replaced the python script by rest_command but the result was repeated. I think the sensor sends out three motion detection signals within 2 minutes of motion detection. Maybe I have a defective sensor?
I run hassio 0.105.5 on rpi3b+ with HUSBZB-1 and zha integrations
I don’t see any strange behaviour on any of my sensors, no false motions detected so far.
Probably a defective sensor.
I used this automation before without the mod and had issues of it not sensing motion after 5s. I did the mod now and applied this automation. These together seem to work! I did the mod today, but noticed the lux levels refreshed every 5s, but the motion state not. I saw your comment and applied this automation as well and now it seems to work. After 5s the motion stops and I can trigger it straight away
Gonna keep testing to make sure it actually works properly.
1 Like
There is no software mod possible, it’s the hardware that’s needs to register