Here's the results from a test:
Step 1:
Using the parameter driver, I set the reporting configuration for temperature: min = 60s, max 120s, delta .5C (60, 120, 50).
I let the device configure, and then queried the reporting configuration and it confirmed the same values.
Read Reporting Configuration clusterId: 0402 status: 00 direction: 00 attr: 0000 datatype: 29 min: 003C max: 0078 delta: 0032
min = 60s, max = 120s, delta = 50 (.5C)
Step 2:
Changed to built in driver. Set temperature to "every 5 minutes". Pressed "save preferences" and then "configure". Logs showed that the device reported the report configuration had been saved.
2021-11-25 10:43:02.359 am inforeporting configuration for Temperature Measurement (cluster 0x0402) suceeded
2021-11-25 10:43:02.355 am debugdescMap: [raw:catchall: 0104 0402 01 01 0040 00 BF61 00 00 0000 07 01 00, profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:BF61, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
Changed to parameter driver and queried cluster 0x402's reporting to see what the built in driver had sent:
Read Reporting Configuration clusterId: 0402 status: 00 direction: 00 attr: 0000 datatype: 29 min: 012C max: 012C delta: 07D0
min = 300s, max = 300s, delta = 2000 (20 deg C). So this is in line with the "every 5 minutes" setting from the built in driver (min/max both 5 minutes) although a 20 deg delta seems an odd choice but since min/max are so low it shouldn't matter. But.... I waited for multiples of 5 minutes and never got a temperature update..... So it seems the device is waiting for a 20C change before sending anything? The max update setting appears to not matter, either because min/max are the same or some other bug/design issue?
Step 3:
Then went back to built in driver, and set to "On 0.25C change". Pressed "save preferences" and then "configure". Device got changes.
2021-11-25 10:59:16.738 am inforeporting configuration for Temperature Measurement (cluster 0x0402) suceeded
Changed to parameter driver
and queried cluster 0x402's reporting again:
Read Reporting Configuration clusterId: 0402 status: 00 direction: 00 attr: 0000 datatype: 29 min: 012C max: A8C0 delta: 0032
min = 300, max = 43200, delta = .5C?
So when using "on 025C change", the parameters appear to be min = 5 minutes, max = 60 hours (!) and delta as .5C? I'm going to retest this in case I did something wrong as the delta should be 25 not 50.
Step 4:
Then went back to built in driver, and set to "On 1C change". Pressed "save preferences" and then "configure". Device got changes.
2021-11-25 11:26:02.335 am inforeporting configuration for Temperature Measurement (cluster 0x0402) suceeded
Changed to parameter driver and queried cluster 0x402's reporting again:
Read Reporting Configuration clusterId: 0402 status: 00 direction: 00 attr: 0000 datatype: 29 min: 0001 max: FD20 delta: 0064
min = 1s, max = 64800s (!) and delta = 1C.
In this configuration, temperature updates seem to be coming in at most at 2F intervals, which would be about right for a 1C delta.
Some side comments:
- While testing the settings with the built in driver and doing a "save preferences" (and sometimes )"configure" button wouldn't always report in the logs the "reporting configuration for Temperature Measurement (cluster 0x0402) suceeded". I didn't figure out if "configure" was even needed, or if sometimes it would cancel the pending "save preferences" or if it was just waiting for the device to wake up to check in for parameter changes. Some guidance here would be appreciated. When setting a new reporting interval, is "save preferences" enough to get that change to the device the next time it wakes up?
- "succeeded" in the built in driver log message is misspelled.