I believe the stock driver configures them with a reportable change of 0.5 C, with a minimum of ten seconds between reports, and a maximum of two hours. That is consistent with what I see on my devices.
Although the 0.5 C seems a little crude the accuracy of the device is +/- 0.2 C (which is fairly typical) so it is a reasonable and realistic choice.
Most batterypowered sensors will only report a change in state above a predefined delta, in order to prolong battery life. And a typical reporting period for a battery power temperature sensor is once every 15 minutes, which is considered sufficient for heating/cooling room control. If you start going much more often than that, you risk very short battery life.
The alternative is a Mainspowered sensor, which can report frequently, certainly once a minute. Is that an option for you?
There is another factor, which is the act of reporting in itself can raise the temperature around the sensor. For that reason, you will typically get the most frequent reporting from a device which uses an attached probe sensor, so that the sensor is at least a couple of centimeters away from the radio.
For example, Shelley recommends using a DS1820 B temperature probe attached to one of their relays if you need reporting quicker than every 10 minutes.
Here’s their FAQ:
So there are some options, but not in your typical self contained battery operated sensor.
I like the Sonoff SNZB02. They are fairly accurate/linear (although the humidity on most is about 6% off, I adjust with driver offset). They are usually about $10-$12 on ebay. I would get them from Sonoff direct. I use them on SmartThings and Hubitat both.
The sonoff SNZB02 sensor works very well for me, I have used it as a thermostat for two winters, reporting changes of 0.1°c and the battery still reports 100%.
These devices do not always accept reporting configuration changes when asleep.
It is best to configure during installation.
The events that are seen in the app never report repeated temperature values, although the device sends them and the driver emits the event.
That is why you can see events in the history every 5 minutes or every 2 hours for example, always informed of a change in temperature.
My driver configures the device with minimum interval, 30 sec, maximum 300 sec and reportable changes of 0.1°c so that it can be used as a thermostat.
If you want to change the reports you can do it in preferences, but not all devices accept them easily. The zigbee Smartthings Samjin (Aeotec) movement, multifunction, button, are fantastic at accepting configuration changes.
Using the CLI you can check if the device replies SUCCESS when the new configuration is sent.
Note! when you change from one driver to another, as in the stock drivers, the device configuration is not executed and it keeps the configuration it had in the previous driver.
My driver does do the configuration, but not all devices accept it outside of pairing mode and a driver change doesn’t wake up the device if it’s asleep.