@twkl wrote:
I’ve been using my xiaomi motion sensors with
zha_newsince I got them since they weren’t supported onzhabefore the custom quirks were released. They were working perfectly fine exactly the way I wanted them to. Then recently I decided to move to the officialzhasince it is maintained better and supports more devices.The motion sensors, however, work very differently. On
zha_new, the sensors would timeout every 5 seconds and would turn thebinary_sensorfor that sensor to on if there was any new motion after that 5 seconds. On the officialzhathe sensors timeout after 2 minutes of no motion. I very much prefer the method thatzha_newuses because it gives me more flexibility and more control over my automations.I know there is a hardware hack for the sensors to make them timeout after 5 seconds, but I don’t have the skills or the tools required to do it. But why would I need a hardware hack if it’s already possible to do in software? My question is why is
zha_newdifferent and how can we bring over that functionality to the officialzha?
Posts: 1
Participants: 1