@SergL Mine has been reliable with presence reporting both before and after the update.
The old driver should have worked, but try the new one here:
And a HUGE shout-out to @Hubitrep for allowing me to use his code at
That code helped add new and significant functionality to the existing driver created by my CCC team (Coding Claude & ChatGPT).
@John_Land thanks for the updated driver. I was somehow running .16. This one has way more features! You should consider adding it to HPM
Btw how’s your R3 at reporting AQI? Do you find it accurate?
V. 1.6 was the prior published (on Github) version, so you weren’t behind. The latest version has been augmented by borrowing a huge amount of time & effort from @Hubitrep who investigated the new firmware recently made available from ThirdReality.
As for AQI – I have no clue how to calibrate any of my sensors (temp, humidity, air pressure, AQI, etc.) since I don’t have any lab rated devices to compare them against. Like the man with two watches, I never know what time (temp, RH%, etc.) it is.
R3 firmware update from v1.00.20 — no OTA image offered
C-8, R3 on firmware v1.00.20, using John_Land's v0.19 driver. updateFirmware executes cleanly (zigbee.updateFirmware() returns without error), but no image is ever transferred.
What the device does after each request: issues a ZDO Match_Descriptor_req to 0x0000, profile 0x0104, input cluster 0x0019 — hunting for the OTA upgrade server. It retries with backoff at roughly 1, 5, and 10 minutes, then gives up. Sequence numbers 0x4E through 0x51 across one attempt. That backoff pattern means it never found a server to talk to; a device mid-transfer stops re-discovering.
Nothing in the hub log at any point — the unfiltered log across the whole window shows no OTA activity beyond the driver's own request line.
Confirmed still on old firmware afterward: attributes 0xF002–0xF006 all return status 0x86, and cluster 0x042E reports a flat 0.0 float, so TVOC is dead as expected on this build.
@mike.maxwell — does Hubitat's hosted image for 3RPL01084Z cover v1.00.20 as a source version? Everyone who's reported success here started from 1.00.27 or later. Has anyone updated an R3 from 1.00.20?
Our hosting only checks for a later software version, if one exists it’s applied. Are you getting firmware is up to date message after executing the update command?
Sounds like not…
What’s unusual is that we host many third reality firmware files across two different firmware vendors and I've not heard of this issue before
