This is a weird one.
The display doesn't change while it reports changing temps to the hub.
(RH is not changing, but it's a non-changing 99% here, lol.)
It dropped off the mesh after a reboot earlier.
This one has done that before in the past.
Maybe it's a bad one.
The other one I've got running has had no problems.
I'll fool around with it and see if I can get it working right again.
Well, I removed the batteries for a little while.
It seems to be synced now.
Too early to declare victory though.
Yes, too early.
After being synced for the first reading or so, the display is locked again.
Log reads 71.9 and display is locked at 73.9.
Weird.
Well, something freed it up in the last several hours.
It's in agreement with another 3R temp/hum sensor, and the log and display are synced.
I have no idea, but it seems to work now, so it's all good.
Never mind. Display still "sticks". Weird.
I think it has something to do with the RH being a constant 99%.
Both of my displays, see picture below, were incorrect this morning.
The real temperature was around 64.
They reported correct temperatures to the hub, as seen in the logs.
Since this is not a one-off, I think @ThirdReality should get involved.
This 
It’s most probably a device firmware bug that has escaped the QA tests - unusual scenario when the humidity sensor is saturated.
I put one in the fridge.
RH got below 99%, display changes, nearly instantly.
Bring it out of fridge.
The RH went to 99%, and now the temp is stuck at 53F when it's really 68F.
It's the 99% RH that makes it get stuck.
Firmware update needed.
Interestingly, with a constant RH, 99%, temperature reports come in to the hub in 6 minute intervals, even with large temperature changes, coming from the fridge.
This is all firmware, since settings on the driver, of course, do nothing.
My observation when things were below a constant 99% RH, was that the RH readings were constantly bouncing back and forth, creating the chattiness complained about.
Generally speaking, I'd happily pay more for a device that just worked properly.
@velvetfoot its probably best to reach out to Third Reality directly as I doubt they frequent this forum:
https://www.3reality.com/support
They did when they wanted to provide a firmware update on some other device.
You were correct.
I sent them an email, (only a couple of days ago), and wound up working with them a bit.
They've reproduced the behavior and say that a firmware update will be forthcoming.
I take this as a very positive sign for ThirdReality, even though it initially slipped through QA/QC.
The firmware is live.
So far, I've updated one of my five sensors from the Hubitat device page.
Now, I just have to wait for a humid day, :).
I thought it interesting that "firmwareMT" still has a "15" in it, whereas SoftareBuild has a "17".
I figured, I'd check out device info in the "device" driver.
It came up with "Software Build Id:1.00.23".
Admittedly I don't understand what's going on, but I've had some exposure in the Hue motion problem days.
Hold on, this is what I'm getting now, a "17" in "firmwareMT", so that's a positive sign.
Kind of what I recall for the Hues: it takes a while, has to do something or other before the "Data" gets updated.
Well, it's raining again...
I'm happy to report that the firmware fix appears to work.
I am looking at the display right now, 99% humidity, and the log agrees with the changing temperature.
edit: I'll keep an eye on it for a while though.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
