Too frequent sensor reporting, Zigbee Third Reality 3RTHS0224Z

I have a couple of these Zigbee temp/humidity sensors (Third Reality 3RTHS0224Z). They seem to work fine except I can't seem to dial back the self reporting frequency. I don't need the numerous inbound reports but whatever I try in preferences the device seems to report adhoc, no apparent pattern to how it reports.

Any ideas?

1 Like

You might want to try the @kkossev driver below. I use this for all my Zigbee temp/humid sensors, and I end up suggesting it to people a lot for issues like this.

The advanced preferences give you control over reporting frequency.

Above, I'm making them report more often, but you could also make them report less often.

Note: This driver rounds temps to tenths. I see you have it reporting in hundredths like I do.
I changed line 1266:

From:
map.value = Math.round((tempCorrected - 0.05) * 10) / 10
To:
map.value = Math.round((tempCorrected) * 100) / 100

To get mine reporting two decimals.

3 Likes

Where you able to disable Humidity reporting?

No but so far about 80 inbound messages to hub. 74 are temp the others are RH

So mostly a temp problem but not sure what is driving the many updates

1 Like

@mike.maxwell i can confirm the inbuilt driver temp and humidity preferences don’t seem to be working on the Third Reality temp and humidity sensor with a display.

1 Like

Make sure the TR battery-powered sleepy device is awake when you click the Save Preferences button. Briefly press the pairing button on the device, or quickly change the humidity, at the same time as clicking Save to ensure the settings are received.

2 Likes

Thank you for the advise. I tried that this morning and it didn’t help. Hopefully @mike.maxwell can chime in and confirm if some of this is controlled via driver like some other devices that I use.

Just to add another $0.02 to the pot... I also use the kkosev driver; and his was the ONLY one which allowed me to dial back the frequency (I've been using it so long, there may be others now).

Anyways, here are the settings I use:

And here are my reporting logs for that device:

As you can see, I have both the temperature and the humidity reporting close to once every hour.

From what I can tell; setting the temperature and humidity sensitivity settings to a higher offset results in less reporting intervals. However, too high, and they may never report. That's why I changed the "Maximum time between reports" to 3600 (1 hour).

With this configuration; if the temp always stays within 0.5 degrees, it will only report once an hour. However, if the temp changes more then 0.5 degrees (at any time); it will generate a report. The same with humidity.

Hope this helps.

3 Likes

Yes I am using this same driver as well. I have been able to change all the config parameters and in the logs see they are confirmed changed by the sensor. Except one. I can't seem to change the Temperature sensitivity field. It is preferences page is stuck at 0.0 but sends delta 50 to the device which is 0.5 degrees C. I wanted to bump that higher but no joy.

There seems to be a bug in the driver blocking me from raising the temp sensitivity field. Anyone seeing this issue? Is there a work around where I could send the config change to the sensor through another tool? See row 10 of log below, delta=50. I would like delta=500.

Any suggestions appreciated.

image

1 Like

@CuriousB thank you for catching this - I see where the problem is now. I’ve already fixed the same issue (decimal-type preferences being reset after the changes in HE platform 2.4.0.x) in some of my other drivers, but this one slipped through the cracks.

2 Likes

OK I just tested a driver patch from the author and it fixes my problem. So expect that update soon.

..."Tuya Temperature Humidity Illuminance LCD Display with a Clock"...

image

.
FYI
A general note to those using Third Reality, Inc Model: 3RTHS0224Z sensor...

This is the driver for this device despite the (narrow) name of the driver. In fact the driver is for a broad range of temp/humidity sensors. They are listed in the top half of the driver code if you want to explore. I was wondering if I was using the wrong driver but in fact it is purpose designed for the sensor above (plus many others).

2 Likes