already released
When you say released where? In a upcoming firmware? Or user driver? Running Hubitat 2.4.4.155 and went to look for anything under "Type" nothing is there for this device but the version I installed from this thread.
Ok I wouldn't expect the name to be night light. But that is good to know. Even the web site calls it a presence sensor. I am gong to stick witht he driver in this forum because I never got errors in my logs until I switched to the built in "nightlight driver"
THAT looks like a bug in the driver and should be reported
The built-in "Night Light R3" driver does not present as a presence device, nor does it actually report Occupancy (only Motion).
Thanks @jwjr, kind of figured that based on the error messages. What this tells me there isn't an built in driver yet for this device and I will continue to use the @John_Land driver.
1 Like
The best way to know if there is a built in driver is to pair the device without any competing custom driver code installed and see what system driver gets assigned.
There is no occupancy capability on HE, only motion, so that in itself isn’t informative.
Your errors might be explained by the driver switch (vs fresh pairing).
1 Like
Anyone seeing the Air Quality sensor just continue to report "0" it was reporting just fine over the weekend and now always zero.
dev:17012026-03-31 07:08:46.218 PMdebugFiltered Air Quality Index report: 0 ppb (good)
dev:17012026-03-31 07:08:46.216 PMdebugAir Quality Index 0x042E debug: enc=0x39 hex=00000000 unsigned=0 signed=null floatBE=0.0 floatLE=0.0 decoded=0.0 status=good
dev:17012026-03-31 07:08:17.238 PMdebugAir Quality Index 0x042E debug: enc=0x39 hex=00000000 unsigned=0 signed=null floatBE=0.0 floatLE=0.0 decoded=0.0 status=good
dev:17012026-03-31 07:07:48.210 PMdebugFiltered Air Quality Index report: 0 ppb (good)
dev:17012026-03-31 07:07:48.208 PMdebugAir Quality Index 0x042E debug: enc=0x39 hex=00000000 unsigned=0 signed=null floatBE=0.0 floatLE=0.0 decoded=0.0 status=good
dev:17012026-03-31 07:07:19.204 PMdebugAir Quality Index 0x042E debug: enc=0x39 hex=00000000 unsigned=0 signed=null floatBE=0.0 floatLE=0.0 decoded=0.0 status=good
dev:17012026-03-31 07:06:50.185 PMdebugFiltered Air Quality Index report: 0 ppb (good)
dev:17012026-03-31 07:06:50.184 PMdebugAir Quality Index 0x042E debug: enc=0x39 hex=00000000 unsigned=0 signed=null floatBE=0.0 floatLE=0.0 decoded=0.0 status=good
On Monday it was in the 200's and I know it should be higher today because in the kitchen we were using the stove.
mine is always 0 now too .. with either driver.. some issue with the recent hub update?
I did a catchall:
2026-03-31 07:14:15.297 PMdebugparse description: catchall: 0104 042E 01 01 0040 00 4ABE 00 00 0000 01 01 000086
0x042E with payload 000086 is worth investigating. The spontaneous report may contain the real AQI data in a non-standard format. The 000086 is intriguing — 0x86 is 134 decimal which would put it solidly in the "good" AQI band on THIRDREALITY's scale (0-500). That might actually be a real reading.
Could be a firmware bug also. I have had it powered up since Sunday afternoon 2 days.
This is from the comments in the driver I posted:
-
- Air Quality cluster 0x042E is decoded as a float/integer value and is now reported directly
-
using the sensor's own threshold scheme from the printed instruction sheet: -
0-500 good, 501-1000 ventilate, 1001-3000 warning, >3000 danger.
Technically, an AQI index of "0" is valid according to Third Reality's literature. However, to distinguish a lack of data being represented as "0" from an AQI index value, you could edit the driver as follows:
OLD CODE:
private static String classifyTvoc(Integer value) {
if (value == null) return null
if (value <= 500) return "good"
if (value <= 1000) return "ventilate"
if (value <= 3000) return "warning"
return "danger"
}
NEW CODE: -- EDITED to fix error in "0" assignment line.
private static String classifyTvoc(Integer value) {
if (value == null) return null
if (value == 0) return "possible error"
if (value <= 500) return "good"
if (value <= 1000) return "ventilate"
if (value <= 3000) return "warning"
return "danger"
}
i agree but i can tell you it is not really zero. so not sure what is going on.. it was working fine and just under 500 and then suddenly dropped to 0.. not sure if sensor is dead or what.
also error in code about should be == 0
What happens if you re-add it back to the hub?
This is a tough one I let the sensor jus continue running and I got a block of air quality and then it stopped again. A pattern is forming — every time it hits 0 ppb the device goes quiet on the attribute report path. The device firmware appears to treat 0 as a sentinel "no data" value and stops reporting until the sensor measures something above zero again.
dev:17012026-04-01 02:17:12.735 AMinfoMaster Bedroom-Multi Sensor motion is active
dev:17012026-04-01 02:01:19.145 AMinfoMaster Bedroom-Multi Sensor motion/presence cleared after 60s delay
dev:17012026-04-01 02:01:19.144 AMinfoMaster Bedroom-Multi Sensor occupancy is clear
dev:17012026-04-01 02:01:19.135 AMinfoMaster Bedroom-Multi Sensor motion is inactive
dev:17012026-04-01 01:01:07.612 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 0 ppb (good)
dev:17012026-04-01 01:00:09.605 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 1 ppb (good)
dev:17012026-04-01 12:55:48.537 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 9 ppb (good)
dev:17012026-04-01 12:55:19.518 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 16 ppb (good)
dev:17012026-04-01 12:27:46.089 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 0 ppb (good)
dev:17012026-04-01 12:22:56.000 AMinfoMaster Bedroom-Multi Sensor Air Quality Index is 8 ppb (good)
dev:17012026-03-31 11:56:49.576 PMinfoMaster Bedroom-Multi Sensor Air Quality Index is 0 ppb (good)
dev:17012026-03-31 11:56:20.561 PMinfoMaster Bedroom-Multi Sensor Air Quality Index is 10 ppb (good)
dev:17012026-03-31 11:55:51.627 PMinfoMaster Bedroom-Multi Sensor Air Quality Index is 12 ppb (good)
dev:17012026-03-31 11:51:30.482 PMinfoMaster Bedroom-Multi Sensor Air Quality Index is 10 ppb (good)
dev:17012026-03-31 11:51:01.482 PMinfoMaster Bedroom-Multi Sensor Air Quality Index is 5 ppb (good)
dev:17012026-03-31 11:22:21.970 PMinfoMaster Bedroom-Multi Sensor occupancy is occupied
dev:17012026-03-31 11:22:21.968 PMinfoMaster Bedroom-Multi Sensor motion is active
I just sent a service request to THIRDREALITY on this issue hopefully I will hear back.
See new 2026-04-01 version of my beta driver above -- it singles out AQI an value of "0" as "possible error". New THIRDREALITY Zigbee Smart Presence Sensor R3 - #16 by John_Land
