I am interested in this potential solution.
How exactly this is implemented?
Is this a some sort of dedicated "sensor recovery" rm rule or few actions in each rule where sensor is used? The problem for the debugging is a very long (a month+) time frame for problem to happen.
Please let me know the results of yours testing.
Description of the this might do it work-around is here:
I've set up a simple rule to change sensitivity on my Linptech sensors weekly (rather than power-cycling them). Initial results are not showing what Kkossev expected, but maybe after looking at things he can adjust the driver to make it behave as he thought it would.
1 Like
Thank you very much for the info.
I missed this very important discussion.
1 Like
I think I tried most mmwave sensors out there, and for me what works best is the Linptech sensor connected to a Tuya bridge, who is connected to HE over Matter.
Paired strait to HE indeed it drops of the network about every month, but on a Tuya bridge it stays rock stable.
Apart from the bedrooms, every room has a Linptech sensor now.
1 Like
For bathrooms my solution is one PIR and one contact sensor. As long as the door is closed the light won't turn off so it doesn't matter what the motion sensor wants to do.
The mmW I was testing in the office had the same problem. It would become unresponsive. I gave up messing with it since my custom app is working well with two PIR sensors. I might try it again some day but it isn't a priority.
Maybe Linptech has a built-in time bomb on purpose but Tuya bridge knows how to reset a timer. It looks like @kkossev is working on the solution.
1 Like
Sure, Contact Sensor is a perfect solution. Unfortunately in my case bathroom door is near always open, specifically while shower is taken for humidity control.
I agree, the contact switch is primarily there for guests. Otherwise that's where the custom code comes in. Multiple triggers cause it to stay on longer after the motion times out. This is great except at bedtime. For that I have exceptions and when the hub is in bedtime mode the lights only stay on for as long as the motion is triggered. (You can also press the off button on the light switch but I never think of that. I haven't used the switches in years. 
)
I am using the Aqara FP1, 2 FP1E's and 3 FP2's. The FP1 is odd but works decently and its only odd due to the fact you can't pair it to an american hub and am using KKossovs driver for it along with one of the FP1E's. One of the FP1E's is paired to an aqara hub and using the xigbee over matter transfer. I wanted to compare the 2 ways and both are fast and solid with no issues with automations. The FP2's are a different story. They are working but tend to get ghosts if you move to fast in the room, something I am good at. But for the FP2's its a setup procedure that you have to do. First, never auto setup, ever and it took a couple of days to get it positioned correctly. They like corners better than walls around eye height. They do not like reflective surfaces so do point them at that and if you don't have a choice the exclusion zone is useful. Always set your walls first in the room layout, then your zones, don't forget to go through and define what the zone is used for. then add your stickers for furniture. Then add your exits then your interference zones. This seems to keep them from creating ghosts so easily. But for the first couple of days I did constantly check it and anytime I saw a ghost in the room I would let it go through the AI empty room process. You can also hold down on the icon that is a ghost and set it as an interference source. They are slow to first detect you but it works reliable and I am using them in my bedroom. Only one time have they gone haywire at night and that was the night I had bad storms and the whole device went weird
3 Likes
