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.
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.
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