Once i started tracking distance the value updated and it is no longer 0, but it does not update in realtime.
A lot less details on Matter. I will test it so see how often does the temperature updates. That is the only setting i am missing, the threshold for temperature reporting.
Unfortunately the default Temp reporting threshold is 1C which is too much for a heating system control. This cannot be changed on Thread, at least not yet until future firmware upgrades.
The default temperature report time is 5 min which is ok, but if you need instant response the Z2M is the way to go.
Are these sensors calibrated?
I’ve got two of them sitting on my desk, 1cm apart and they show different values. All settings are the same, 0.2 C Temperature Threshold, 60s temperature and humidity check, 5% humidity and illuminance threshold.
They should show the same values.
Right next to them i have a calibrated Testo sensor which shows 24.0 C and 47.4 RH.
1 Like
Ran into your same issue and initially I also thought that target distance would be constantly updated.
Then I realised what it’s purpose is - it’s intended to return your position once when you press start_tracking_distance (while you’re at the edge of where you want your sensor to start/stop tracking.
It’s intended so you can figure out which toggles to set to false in the “Detection Range” settings, so you can reliably switch off detection at certain ranges without having to guess the distance.
You can set an offset in the Settings (Specific) section in Z2M if you want, but it looks like only your Hallway one requires it. The Living Room one is within 1 degree/1%, so I wouldn’t worry too much about it.
I checked mine against a professionally calibrated kitchen thermometer, and it was within .1-.3 degrees, which was good enough for me.
It took more than 1 hour but they are now somewhat stable and showing about the same temperature. This is because of thermal inertia.
And that brings the question, does setting 0.2C threshold help? It does respond faster and more often but it actually measures the temperature inside the sensor which is affected by thermal intertia. So choosing Thread for Mesh Network could be a better option. In that case it would report temperature every 5 min, which is not that bad, but i get better signal.
Regarding the distance, i would have prefered it to show the actual distance to the target every time.
Unless you can physically feel a difference between 24.6 & 24.8, then you’re eating away at the battery life unnecessarily. I’ve gone ahead and set the T&H sampling to “low” and I’m still happy with the results because personally, I don’t need extreme granularity.
This is my temperature reading spiking from when I turned on the oven around 6-7m away from the sensor. All I’m interested in is seeing the spike (which was reported in <5 minutes), not the actual value:
That would kill the battery, then you would have preferred it if the battery lasted longer. If you want frequent readings, set up an automation to “press” the track target distance button every time it detects motion (and every x interval until it stops detecting motion).
You’ll probably end up with a flat battery every 6 months or less, but you’ll get what you wanted.
I will try again with Thread. If i get updates every 5 min it should be ok. But only if it reports even a 0.1 C change. I need this rapid response because i control the central heating with these sensors. Independent room heating in an apartment. And i do not want the system to overheat the room until i get an update, or let the room get chilly until it updates.
So far they seem to be stable and have close values.
1 Like
This now seems like a very nice sensor.
As it is a battery sensor I don’t expect it but is it not spamming the zigbee network as some of the chineese versions on 230V ?
It’s not spamming, but it does report frequently due to its nature.
Right now it’s in the 3rd place of the most chatty zigbee devices for me, right below power monitoring devices. This is in an area with constant high activity.
Still tweaking and playing around with settings to find that sweet spot, but this is what I see when I look at the zigbee Health tab
Thanks @ShadowFist.
That’s indeed a low frequency as I had another device reporting multiple messages per second continously.
1 Like
Found an issue with this setup
If you get a power loss for ex a few hours and the temperature drops with a few degrees, these sensors do not update the value once you reboot the hub.
It only changes on threshold or every 3600 sec, default value for reporting, even though it has 300 sec measure interval. I has to sense a 0.2C change in orther to report.
It has that option to restart the sensor in the settings .
I had to press the button on it to update but the restart should also work.
Got a bunch of these using them with (Matter over) Thread.
While I’m disappointed in the number of entities exposed to HA, they do the job I want them to do. And am happy with them after jumping through some hoops.
Ran into some issues with them disconnecting. Update the ZBT-2 to firmware OpenThread RCP 2.7.2.0 which solved that issue. Hopefully it gets released soon as a regular firmware.
Also had an issue where the occupancy state got stuck on detected. Found out this is an issue when the default value is changed.
Contacted Aqara support and got this response in typical support fashion:
Zigbee2MQTT and comparable third-party USB dongles are not officially supported by Aqara. Full product functionality may be limited or unavailable.
We would recommend that you get the Aqara hub to connect the Aqara Zigbee devices to the Aqara Home app first.
Then, using the Hub with Aqara Advanced Bridge functionality (Aqara Hub M3/Hub M2/Hub M1S/Hub M100/Hub E1, Aqara Camera Hub G5 Pro/Camera Hub G3/Doorbell Camera Hub G410), you can connect to Home Assistant. You will also need the HA matter controller
And go to Home Assistant Settings — Devices & services — Add integration — Add Matter device — Scan QR code, and scan the Hub’s Matter QR code (found in the hub manual or Aqara home app —Settings — Device page — Expose to Matter);Through the Aqara Advanced Bridge function, Aqara scenes or private functions can be bridged to third-party Matter ecosystems.
With the this response I worry if Aqara will take this serious and fix this in a firmware update, or that we’ll have to “fix” this through a workaround in HA.
I’d be using them with ZHA (or Z2M). The Thread support is nowhere near as good.
Treat it like any standard level 1 support gibberish and ignore their advice.
“You have a problem with one of our products? Why not buy another of our products & see if it fixes your issue?”
Someone on their own forums has posted about the issue you’re seeing with Thread way back in November. Guess what? He was using their hub.
I’ve been testing & tweaking mine via Z2M since the end of December. Still working out the kinks(there are a lot!) because each change is followed by at least a couple of days monitoring.
Once I’m happy with the results, I’ll post my settings here. For the impatient among you what I have discovered so far is:
- Don’t disable the PIR. Somehow the mmwave sensor reports false negatives without it.
- Set the sensitivity to low, especially if using PIR for initial detection. Any other setting will cause multiple false triggers on the PIR, even if you’re snoring 3 rooms away.
2 Likes
Got two of these recently, they were extremely hard to get (took me two months to finally successfully order them and get them delivered).
One is running Matter/Thread in my bathroom and working without issues (the lack of customisability in Thread mode doesn’t bother me with this one, as the defaults + lowered sensitivity are enough for that room). Works great for night trips to the bathroom, controlling a lightstrip. I no longer need to be moving to keep the light on. 
The other is running Zigbee (via ZBT-1, ZHA and Cemizm’s quirk), and it behaves kinda weird with detecting people leaving the covered zone. PIR is disabled (at least that’s what the quirk thinks) and the areas for monitoring are the quirk’s 0-1 and 1-2 meter zones.
Detecting presence works great - if I come closer than two meters, it turns on the lights. However, to stop detecting presence I need to go much farther away (like 6-7 meters) or, if I’m in the 2-6 meters zone, I need to… stop moving. Which suggests that PIR is still getting involved here, even though it’s disabled.
Now, I’m not sure if this is just how these sensors are, or if it’s a problem with my specific one, or maybe there’s something wrong with the ZHA quirk. Anyone having similar issues?
I finally was able to get two fron Amazon. I placed one in the toilet area and one in a walk-in closet. They are replacing PIR sensors which were rock solid detecting motion but terrible at presence.
Mine are integrated into Home assistant as Zigbee going through the Aqara hub and integrated with the Homekit integration. All elements are exposed even though there is only presence and no separate PIR/presence sensors, only one combined sensor called Presence.
So far they have worked great keeping the lights on while i an on those rooms. I plan to purchase 2 more, when tjey are available again.
1 Like
They’re so (so) good. I not have 10 of them deployed. ZHA and custom quirk. I just noticed, however, that all my settings (sensitivity, distances, PIR and/or mmWave…) have all been reset. Any idea how/why? Known issue?
Sigh… I’m old… I hate acronyms. Had to google that Z… blah blah blah junk. I finally got a hold of three devices. Been waiting over a year for these. I have “Zigbee2MQTT” in my Home Assistant. Are you guys using the Aqara app initially to update the devices prior to switching them to Z or it does not make a difference?
You only need the app at the very beginning to switch the sensor to Zigbee mode, since it’s in Matter mode out of the box. You only need to do this once, and the protocol switch should automatically apply the latest firmware on the device.
After that, you’ll be able to update firmware directly inside Z2M (now you know what the acronym means 
).
Currently updating mine from build 34 to build 41, whatever that means. Should be done in an hour.
1 Like
Thank you for verifying the install. It is setup now. Just need to figure out where to mount it in the room and the detection range. I won’t remember what Z2M means, I am old and retain information for about 5 minutes. I even forgot about this post until I received an email - lol. I should probably get this problem checked out but I keep forgetting to ask the doc.
1 Like
If it’s so bad, I suggest you don’t install the FP300 at all. Otherwise a week from now you’ll be wondering why the lights are turning on by themselves when you walk into the room
1 Like