So I gave it a try, and this is what I get in logs, changing from High to Medium and back to High again:
Is it doing what you hoped? I don't see it going to inactive, and the active minutes timer is at 11m after the change back to High, I'd assume from what you said that if the setting change worked to force re-calibrate that the active timer would restart. Should this setting change work w/both Gassgs driver (which I'm using), and your mmWave driver as well?
Yes, both custom drivers can dynamically change the Linptech parameters (the Preferences); only the commands are different.
I don't see the presence being reset from these logs...
When I have the chance, I will try to test it myself.
Another WAF casualty here waiting for the verdict on this. Going around the house re-plugging all the Linptechs is a PITA. Bathroom lights not turning on is fatal.
OK, two-week update on Linptechs stability w/the scheduled power cycle/reboot replaced by changing the Motion Sensitivity setting. So far so good, but it's only been two weeks so still plenty of time for things to go south. 
Have you had a chance to test/look at this?
Sweet! Did you end up just re-setting the same sensitivity or do you set it to different one before returning to the original one?
I just bounce it from current desired level, to another level, and then back to desired.
I wonder if just re-setting to the desired level is enough.
Yeah, wasn't sure, so I decided better to change it and change it back.
If I was sure which of my Linptech had been hanging up I could have done one each way to see if it made a difference, but since I lost track of which two it was... 
Maybe worth testing and reporting back here 
.
In case this answers any questions here is one of mine that changes sensitivity when my AC runs. Presence does not change
Since @danabw is already running the experiment, I delegated it to him 
How long have you been running that automation, and during that time did you have any of the sensors lock up?
Also if you had the sensors around for a while before you started using that automation, did you ever have them lock up?
Looked back thru this topic and got help setting it up Feb 27. It has locked up once or twice at the most.
@danabw, my tests show inconsistent results. Sometimes, the motion is reset when I change parameters/preferences, but most of the time, it is not. So, I may have confused myself with another type of mmWave sensor.
Is the device still responsive when a Linptech sensor gets stuck in an 'active' state? Does it respond to Ping() commands?
Thanks for the update.
I never tried a ping so don't know...
I don't have any that are getting stuck at this point so I can't check on that, maybe someone else here will have an event and can test it and see.
My few Linptech Sensors still reporting Illuminance when Motion is stuck.
So, somewhat they are alive.
I did not try ping.
After changing to "device" and back and much gnashing of teeth it turns out that our cleaning person jarred the Tuya TS0225_LINPTECH 24Ghz plug loose. Ping works as well
Presumably you're referring to Ping working when the sensor is reporting normally...if you can try a Ping and report results if it stops reporting motion, that would be useful info in our quest to keep these suckers alive and breathing over time (for those of us who've had them stop reporting on occassion).
Heading towards three weeks doing the Sensitivity setting change and zero issues w/all five of my sensors.
Woot! Can you change some of them to re-set the same sensitivity (instead of changing it to a different setting) and some to ping? As a part of A/B/C testing?
If things work reliably w/the current setup for five weeks or more I'm going to call it good/looks safe, and let my current setup ride for now. Holidays coming up, and not the best time to do a bunch of testing as we'll have family coming into town and WAF needs to be carefully conserved...wife will not be happy if her sister says that the bathroom light keeps turning off. 
Download the Hubitat app
