I'm trying to figure out how often my temperature and humidity sensor is sending measurements. For this the debug logging has to be enabled but 30 minutes is not enough. I would like to run debug logging whole night.
As seen here, the debug log shows that temperature and humidity values are received but Hubitat C-7 (2.3.8.139) does not show the values.
Go to Logs > Scheduled Jobs, find a job listed for this device name that likely corresponds with disabling debug logging (in built-in drivers, this method is normally called "logsOff" and runs 30 minutes after being enabled, but this can vary with third-party code), and hit the delete (trash can) icon in the "Actions" column:
Thanks. I enabled the debugging and then deleted the timer.
But why are not all measurents shown? Does hubitat ingores measurements if eg. temperature has not changed?
By default, the platform will filter out events that do not represent a state change, e.g., if two successive readings of the same temperature or humidity come in. This is because most automations, being driven by events where events represent an actual change, work best this way.
Someone may be able to help you find a way to do whatever it is you're looking for if you share more information about what that is -- unless it's just wondering if the device/driver is working correctly, which it seems to be (though without seeing events or Current States can't be said for sure).
I mostly monitor temperatures so all temperature measurements are valuable. If the tempeature does not change for eg. 5 hours I don't know if the sensor is working or not. I have had a sensor failure and another time is was just that temperature had not changed.
Another thing is that I don't know how accurate the shown temperature is. My sensors reports temperatures every 30 minutes or sooner if temperature has changed more than 0.6 C but sometimes temperature is send every 5 to 15 minutes even the change is lower than 0.6 C. Sensor reports eg. temperature 20.00 C at 00:00. Next change shown by Hubitat is 21.12 C at 00:30. At 00:15 temperature can be between 19.40 and 20.60 C if sensor has not send an update. If sensor sends an update 20.00 C at 00:15 it's know that temperature is exactly 20.00 C. This information is lost if Hubitat filters out the update 20.00C at 00:15.
Also if I want to plot temperatures by using limear interpolation, I there's an error at 00:15. If I use "square steps" there's probably an inaccuracy between 00:15 and 00:30 because temperature won't suddenly increase from 20.00 C to 21.12 C.
Another thing I noticed is that the sensor reports humity by using two decimals but hubitat does not show any decimals and filters out all measurements if only the decimal part is changing. Here's an example where the sensor sends humity updates 29.76 %, 29.79 %, 29.80 %, 29.84 %, and 29.90 %.
07:14:20.832debugdescMap: [raw:287E0104050A000021A00B, dni:287E, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:0BA0, clusterInt:1029, attrInt:0] **29.76 %**
06:44:21.053debugdescMap: [raw:287E0104050A000021A30B, dni:287E, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:0BA3, clusterInt:1029, attrInt:0] **29.79 %**
06:14:21.240debugdescMap: [raw:287E0104050A000021A40B, dni:287E, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:0BA4, clusterInt:1029, attrInt:0] **29.80 %**
05:44:21.496debugdescMap: [raw:287E0104050A000021A80B, dni:287E, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:0BA8, clusterInt:1029, attrInt:0] **29.84 %**
05:14:21.679debugdescMap: [raw:287E0104050A000021AE0B, dni:287E, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:0BAE, clusterInt:1029, attrInt:0] **29.90 %**
A yet another problem. I have added an atribute last update alongside the temperature. The temperature updates live but the last update time requires me to reload the page. In the picture below tha date is from yesterday but the temperature is from 4/16/2024 11:44:18.708.
Hubitat standard is to round the relative humidity readings to whole numbers only (integers). The typical humidity sensors have 2% .. 5% absolute measurement error.
What is your device and which driver it uses?
Yes the error is much higher than the resolution two decimals but accurary is lower. The difference between those five measurements in the above is less than 0.14 %.
I have selected 'Generic Zigbee Temperature/Humidity Sensor'. I'm currently testing three different sensors: Tuya _TS0201 TZ3000_xr3htd96 and TS0207 _TZ3000_nlsszmzl, Aqara Temperature and Humidity Sensors with barometer (WSDCGQ11LM).
Probably there are some good reasons for the stock HE ‘Generic Zigbee Temperature/Humidity Sensor’ driver to report the T/H readings that way.
As you are using Tuya and Aqara sensors, you may try some of the community-developed drivers listed here.
The healthStatus online/offline attribute should solve this issue as well.
Default to 1 % resolution is good but I wish this could be configurable. Temperature defaults to two decimals but eg. Home Assistant shows only one decimal.
Those three sensors side by side. Connected to Home Assistant. Should be sealed in airtight box for better comparision. Additional note: these are humidity readings! I forgot to mension that 
Looks good!
The problem is when the temperature doesn’t change for a long time, then the graph doesn’t look so pretty …
Yes.
I forgot to tell that those are humidity readings. The more decimals the higher possibility for values changing.
Download the Hubitat app
