Good question I never used this feature. It states it will adjust sensitivity as needed but I never tried it.
Ok, so I have the mm turned on even thought I have chosen only Pir.
I did press the wake button and it ack the press with the 15 min warning.
On all 3 of the ones I was trying to commission, a press of the Wake button does not flash any blue LED. It works for a discovery or firmware rest though.
All 3 show Occupied on motion so nothing is taking my Prefs.
Ah, the exploration. 
So I understand. When you press the button. Just a quick one press the device doesn't blink the blue light 6 or 7 times? Does it blink any light?
You are saying though that if you press the button 10 times it resets the device and you get the slow pulsing violet light? Or are you saying the one press resets the sensor?
No lights blink on any of them with one press.
Yes, 10 times, violet pulsing.
Holding results in flashing for pairing.
They are all reporting data and seem to work.
Just can't set the Prefs.
That I do not understand. The five I have in service on my Aqara hub and this one I have in service on my HE beta hub all blinks the blue light 6 or 7 times on a single press.
I do have one though you kinda got hit the sweet spot on the button when you press it for the button to work. I wonder if you are experiencing something like that.
If i press the button I get the 15 min warning in the Current States.
I guess I'll firmware reset #1 and start fresh again.
Then move on to 2 and 3 when I figure this out.
Then I assume that means the device has woken up and reporting that back to hub. Sounds like the hub and the device is not communicating the changes.
When you changed to this driver did you completely remove the sensor from your hub before you reset it?
If not try that. Completely remove it from your hub, reset the sensor with the 10 button presses, then rejoin it using this driver.
I did remove one completely and reset it with no change.
I have reset #1 and will remove it and start "real" fresh again.
Pain they are in pistons already. 
Man this is weird.
I had more options in the Prefs like distance so I set it to 1-4, did a Save and refreshed, that Pref is now gone. It's like a vestigial Pref from the old P1 driver or when you pick Pir only it is removed as it's only a mmWave option.
Good news is Pir is not changing Room State now.
Is Adaptive Sensitivity useful for is that only mmWave?
That is weird it is like it is still mixing up the drivers. I have no idea about the adaptive sensitivity. I have never used it.
I didn't get the Generic sensor component though.
What do you mean the generic sensor component?
1 Like
The child device with temp/humidity/Lux
They all had that when I first installed them. Maybe that's left over from the issue.
They key takeaway here is get rid of Line 190 of the P1 driver before attempting to add the FP300.
With this driver you won't get child devices. They were removed instead placing those reading in the current state list along with motion. I posted my current state list in the start of this thread. Go look at it. If yours does not look like this then your devices are not connected properly or there is bless over and confusion from the two drivers.
Did this fix your issue?
1 Like
Yes. I think the first one through the hoop is working.
Crazy, I get a blue blink when I press the Wake button now.
@ogiewon
Sorry for clogging your release.
I lied. I'm back to the same old issue on Pir #1,2 and 3.
I blew out and set up #2/#3 again as I thought this was settled.
All went fine the after a bit I get the mmWave Occupied again so the Pir only didn't take.
#2 in the bathroom turns on the light well before I'm in the door so that's mmWave working.
It didn't take my humidity offset either when in update mode; had to try a few times.
Good thing I'm going on holidays.
I will have to wait and let @ogiewon comment if he has any more ideas. I am out of them. Mine did not work like that at all. Sorry I can't help more.
1 Like
I am not sure that the sensor will actually fully stop reporting PIR (pirDetection) if you select mmWave only. Or stop reporting mmWave (roomState) if you select PIR only.
Internally, the driver uses this pair of attributes AND the selected mode of Presence detection to determine the status of the Hubitat standard “motion” attribute.
IMHO, I really can’t understand why anyone would want to use PIR only, or mmWave only, instead of BOTH. The major selling feature of this sensor is that it combines PIR (for speed) with mmWave (for room occupancy) into a single battery powered device.
Have you updated the firmware on your FP300 devices via the Aqara mobile phone app? Perhaps that would explain why yours are not blinking the blue LED 6-7 times when you wake up the device via its physical button?
The User Preferences page is Data Driven now. If you select Presence Detection Mode of “PIR Only” and click Save, all of the mmWave-specific user preferences become hidden. Likewise if you select “mmWave Only” and click Save, PIR-specific preferences are hidden. The same holds true for the Temp/Humid reporting as well as the Illuminance reporting sections.
This is to only present to the user the settings that are applicable based on the current configuration of the sensor. This is exactly how the Aqara mobile phone app behaves.
Hope this helps to clarify things.
2 Likes
