[2.4.3.177] C8Pro JS Zooz ZSE11 reporting false illuminance values

dnickel · January 16, 2026, 8:37pm

As of today my Zooz lux was always 10000-30000 in direct sunshine; it was yesterday.
Today it's lucky to get 4-500 and as I type this it's down to 109.
Tried rebooting the device, config, refresh but no change.
The driver was changed.
Any suggestions before I gfo forf a full power off/reboot of the hub?

EDIT:
I posted this and seconds later the lux jumped to 30000.

Refresh trace

2026-01-16 12:30:20.828|DRIVER   all queues idle
2026-01-16 12:30:20.826|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -75 dBm -                                  └─[NotificationCCReport] -                                      notification type:   7 -                                      notification status: 255 -                                      notification state:  idle -                                      event parameters:    0x08
2026-01-16 12:30:20.823|CNTRLR   [Node 184] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2026-01-16 12:30:20.821|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.818|SERIAL « 0x011800a800000100b80a7105000000ff0700010800b5007f7fcc              (26 bytes)
2026-01-16 12:30:20.814|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.812|SERIAL « 0x011d00a97500000100b57f7f7f7f00000300000000030100007f7f7f7f7ff4    (31 bytes)
2026-01-16 12:30:20.799|DRIVER « [RES] [SendDataBridge] -                                    was sent: true
2026-01-16 12:30:20.797|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.794|SERIAL « 0x010401a90152                                                       (6 bytes)
2026-01-16 12:30:20.791|SERIAL « [ACK]                                                                   (0x06)
2026-01-16 12:30:20.787|SERIAL » 0x011300a9000100b805710400ff0025000000007523                        (21 bytes)
2026-01-16 12:30:20.785|DRIVER » [Node 184] [REQ] [SendDataBridge] -                                  │ source node id:   1 -                                  │ transmit options: 0x25 -                                  │ callback id:      117 -                                  └─[NotificationCCGet] -                                      V1 alarm type: 0
2026-01-16 12:30:20.784|DRIVER   one or more queues busy
2026-01-16 12:30:20.457|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -75 dBm -                                  └─[MultilevelSensorCCReport] -                                      sensor type: Humidity -                                      scale:       Percentage value -                                      value:       34
2026-01-16 12:30:20.454|CNTRLR   [Node 184] [~] [Multilevel Sensor] Humidity: 34 => 34             [Endpoint 0]
2026-01-16 12:30:20.451|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.448|SERIAL « 0x011300a800000100b805310505012200b5007f7f5f                        (21 bytes)
2026-01-16 12:30:20.430|DRIVER « [REQ] [SendDataBridge] -                                    callback id:            116 -                                    transmit status:        OK, took 10 ms -                                    routing attempts:       1 -                                    protocol & route speed: Z-Wave, 100 kbit/s -                                    routing scheme:         LWR -                                    ACK RSSI:               -75 dBm -                                    ACK channel no.:        0 -                                    TX channel no.:         0
2026-01-16 12:30:20.428|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.427|SERIAL « 0x011d00a97400000100b57f7f7f7f00000300000000030100007f7f7f7f7ff5    (31 bytes)
2026-01-16 12:30:20.415|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.412|SERIAL « 0x010401a90152                                                       (6 bytes)
2026-01-16 12:30:20.410|SERIAL « [ACK]                                                                   (0x06)
2026-01-16 12:30:20.406|SERIAL » 0x011200a9000100b8043104050025000000007498                          (20 bytes)
2026-01-16 12:30:20.402|DRIVER   one or more queues busy
2026-01-16 12:30:20.076|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -75 dBm -                                  └─[MultilevelSensorCCReport] -                                      sensor type: Illuminance -                                      scale:       Lux -                                      value:       373
2026-01-16 12:30:20.073|CNTRLR   [Node 184] [~] [Multilevel Sensor] Illuminance: 534 => 373        [Endpoint 0]
2026-01-16 12:30:20.072|CNTRLR   [Node 184] [Multilevel Sensor] Illuminance: metadata updated      [Endpoint 0]
2026-01-16 12:30:20.070|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:20.069|SERIAL « 0x011400a800000100b8063105030a017500b5007f7f00                      (22 bytes)
2026-01-16 12:30:19.916|DRIVER « [REQ] [SendDataBridge] -                                    callback id:            115 -                                    transmit status:        OK, took 10 ms -                                    routing attempts:       1 -                                    protocol & route speed: Z-Wave, 100 kbit/s -                                    routing scheme:         LWR -                                    ACK RSSI:               -75 dBm -                                    ACK channel no.:        0 -                                    TX channel no.:         0
2026-01-16 12:30:19.913|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.912|SERIAL « 0x011d00a97300000100b57f7f7f7f00000300000000030100007f7f7f7f7ff2    (31 bytes)
2026-01-16 12:30:19.897|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.894|SERIAL « 0x010401a90152                                                       (6 bytes)
2026-01-16 12:30:19.892|SERIAL « [ACK]                                                                   (0x06)
2026-01-16 12:30:19.885|DRIVER » [Node 184] [REQ] [SendDataBridge] -                                  │ source node id:   1 -                                  │ transmit options: 0x25 -                                  │ callback id:      115 -                                  └─[MultilevelSensorCCGet] -                                      sensor type: Illuminance -                                      scale:       Percentage value
2026-01-16 12:30:19.880|DRIVER   one or more queues busy
2026-01-16 12:30:19.552|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -75 dBm -                                  └─[MultilevelSensorCCReport] -                                      sensor type: Air temperature -                                      scale:       Celsius -                                      value:       33.5
2026-01-16 12:30:19.547|CNTRLR   [Node 184] [Multilevel Sensor] Air temperature: metadata updated  [Endpoint 0]
2026-01-16 12:30:19.545|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.542|SERIAL « 0x011400a800000100b80631050122014f00b5007f7f10                      (22 bytes)
2026-01-16 12:30:19.525|DRIVER « [REQ] [SendDataBridge] -                                    callback id:            114 -                                    transmit status:        OK, took 10 ms -                                    routing attempts:       1 -                                    protocol & route speed: Z-Wave, 100 kbit/s -                                    routing scheme:         LWR -                                    ACK RSSI:               -76 dBm -                                    ACK channel no.:        0 -                                    TX channel no.:         0
2026-01-16 12:30:19.523|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.521|SERIAL « 0x011d00a97200000100b47f7f7f7f00000300000000030100007f7f7f7f7ff2    (31 bytes)
2026-01-16 12:30:19.512|DRIVER « [RES] [SendDataBridge] -                                    was sent: true
2026-01-16 12:30:19.509|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.509|SERIAL « 0x010401a90152                                                       (6 bytes)
2026-01-16 12:30:19.505|SERIAL « [ACK]                                                                   (0x06)
2026-01-16 12:30:19.500|SERIAL » 0x011200a9000100b804310401002500000000729a                          (20 bytes)
2026-01-16 12:30:19.497|DRIVER » [Node 184] [REQ] [SendDataBridge] -                                  │ source node id:   1 -                                  │ transmit options: 0x25 -                                  │ callback id:      114 -                                  └─[MultilevelSensorCCGet] -                                      sensor type: Air temperature -                                      scale:       Celsius
2026-01-16 12:30:19.495|DRIVER   one or more queues busy
2026-01-16 12:30:19.157|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -75 dBm -                                  └─[VersionCCReport] -                                      library type:      Enhanced Slave -                                      protocol version:  7.18 -                                      firmware versions: 2.10 -                                      hardware version:  2
2026-01-16 12:30:19.155|DRIVER   all queues idle
2026-01-16 12:30:19.134|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.134|SERIAL « 0x011d00a97100000100b57f7f7f7f00000300000000030100007f7f7f7f7ff0    (31 bytes)
2026-01-16 12:30:19.132|SERIAL » [ACK]                                                                   (0x06)
2026-01-16 12:30:19.129|SERIAL « 0x010401a90152                                                       (6 bytes)
2026-01-16 12:30:19.128|SERIAL « [ACK]                                                                   (0x06)
2026-01-16 12:30:19.105|DRIVER » [Node 184] [REQ] [SendDataBridge] -                                  │ source node id:   1 -                                  │ transmit options: 0x25 -                                  │ callback id:      113 -                                  └─[VersionCCGet]
2026-01-16 12:30:19.104|DRIVER   one or more queues busy

chrisbvt · January 16, 2026, 8:55pm

I just cleared snow off my Lux sensor today, since I was getting low readings. Not your issue, I take it?

dnickel · January 16, 2026, 8:58pm

Inside my office facing the sun.
Confuse a bit, snow? Mine sure looks like indoor only.

jtp10181 · January 17, 2026, 6:13pm

Need to know what driver, and what firmware the device is running.

dnickel · January 17, 2026, 6:48pm

Using your driver Q Sensor driver 1.2.2. FW 2.10
I have another identical one facing the backyard but it rarely gets direct sunlight so I haven't noticed this issue.
I only noticed tis as the lights were coming on in the house yesterday but it was brilliant sunshine so I went investigating.
It was strange that it was just slowly dropping in direct sunlight.

dnickel · January 17, 2026, 7:32pm

Interesting, just did it again.
Ok here:

Wrong here:

Recovered here:

Managed to grab a bit of 184:


2026-01-17 11:35:50.037|DRIVER   all queues idle
2026-01-17 11:35:50.035|SERIAL » [ACK]                                                                   (0x06)
2026-01-17 11:35:50.032|SERIAL « 0x0107013ba2a1a1a3c3                                                 (9 bytes)
2026-01-17 11:35:50.030|SERIAL « [ACK]                                                                   (0x06)
2026-01-17 11:35:50.027|SERIAL » 0x0103003bc7                                                         (5 bytes)
2026-01-17 11:35:50.025|DRIVER » [REQ] [GetBackgroundRSSI]
2026-01-17 11:35:50.025|DRIVER   one or more queues busy
2026-01-17 11:35:36.902|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -77 dBm -                                  └─[MultilevelSensorCCReport] -                                      sensor type: Humidity -                                      scale:       Percentage value -                                      value:       33
2026-01-17 11:35:36.900|CNTRLR   [Node 184] [~] [Multilevel Sensor] Humidity: 34 => 33             [Endpoint 0]
2026-01-17 11:35:36.897|CNTRLR   [Node 184] [Multilevel Sensor] Humidity: metadata updated         [Endpoint 0]
2026-01-17 11:35:36.893|SERIAL » [ACK]                                                                   (0x06)
2026-01-17 11:35:36.892|SERIAL « 0x011300a800000100b805310505012100b3007f7f5a                        (21 bytes)
2026-01-17 11:35:34.260|DRIVER « [Node 184] [REQ] [BridgeApplicationCommand] -                                  │ RSSI: -77 dBm -                                  └─[MultilevelSensorCCReport] -                                      sensor type: Air temperature -                                      scale:       Celsius -                                      value:       34.2
2026-01-17 11:35:34.258|CNTRLR   [Node 184] [~] [Multilevel Sensor] Air temperature: 33.9 => 34.2  [Endpoint 0]
2026-01-17 11:35:34.255|CNTRLR   [Node 184] [Multilevel Sensor] Air temperature: metadata updated  [Endpoint 0]
2026-01-17 11:35:34.254|SERIAL » [ACK]                                                                   (0x06)
2026-01-17 11:35:34.250|SERIAL « 0x011400a800000100b80631050122015600b3007f7f0f                      (22 bytes)
2026-01-17 11:35:26.502|CNTRLR   [Node 184] [~] [Multilevel Sensor] Illuminance: 1615 => 2419      [Endpoint 0]
2026-01-17 11:35:26.499|CNTRLR   [Node 184] [Multilevel Sensor] Illuminance: metadata updated      [Endpoint 0]
2026-01-17 11:35:26.498|SERIAL » [ACK]                                                                   (0x06)
2026-01-17 11:35:26.495|SERIAL « 0x011400a800000100b8063105030a097300b3007f7f08                      (22 bytes)
2026-01-17 11:35:20.036|DRIVER   all queues idle
2026-01-17 11:35:20.034|SERIAL » [ACK]                                                                   (0x06)
2026-01-17 11:35:20.031|SERIAL « 0x0107013b9e9c9ca1fd                                                 (9 bytes)
2026-01-17 11:35:20.030|SERIAL « [ACK]                                                                   (0x06)
2026-01-17 11:35:20.026|DRIVER » [REQ] [GetBackgroundRSSI]
2026-01-17 11:35:20.024|DRIVER   one or more queues busy

dnickel · February 17, 2026, 8:20pm

Still scratching my head on this one, maybe the device is faulty.
Full sun and 300ish lux. An hour before it was 30K.
Power cycle and back to 30K within a couple of minutes.
The only real change was FW 2.10.
Trying the built-in one for a while which I suspect is based on yours? @jtp10181

chrisbvt · February 17, 2026, 8:33pm

Maybe not the case, but I had a lux sensor I was using outside, and it got full direct sunlight it overloaded the sensor or something and it would give false readings like that. I could not point it directly at the sky or that would happen at mid-day when it was sunny,

My Ecowitt lux sensor on my weather station does not do that, and it is positioned flat on top. I think some lux sensors just don't like looking directly at the sun, but that may not be your issue if has worked looking at the sky in the past. Sounds like sensor issue though, not a hub issue.

hydro311 · February 17, 2026, 8:44pm

I have a Zse11 that I use exclusively for lux -- it's pointed at the sky (behind a window), and can get up to several hours straight of unobstructed sun in the mornings.

In all lighting conditions, its reported lux values have always been what I'd expect them to be.

Mine's on 2.10 and Jeff's driver as well, but I'm back on ZIP these days.

My guess is the borked reporting here has to do with JS, but I'm admittedly pretty jaded about JS these days.

dnickel · February 18, 2026, 1:46am

I have 2 and the second one never fails BUT it is in the back yard and never exposed to direct sunlight.

jtp10181 · February 18, 2026, 1:58am

It is either Zwave JS bugs or a faulty device. I doubt the driver will make a difference.

I dont see any lux reports in your Zwave logs up above.

If using my driver you need to enable Trace logging to see the full message sent to the driver from the zwave stack.

dnickel · February 18, 2026, 2:09am

I had trace logs earlier in the post twice but I didn't see anything bad but I'm no expert on anything, ask my wife.

I could try swapping the back device with my front device and see if the one that never sees 30K white out conditions does the same thing.

jtp10181 · February 18, 2026, 2:16am

There are no trace logs, only debug logs and zwave logs.
Only one of the zwave logs has illuminance in it, and there is only one entry which is not a helpful one. It is showing what looks like a normal change.

[Node 184] [~] [Multilevel Sensor] Illuminance: 534 => 373

Your zwave logs also have tons of extra spaces or tabs in them for some reason, even if I copy and paste into something else. So they are very annoying to look at.

I grabbed the raw hex for that one message and made AI decode it for me. This should be the exact message the device sent to the hub before Zwave JS parsed it.

dnickel · February 18, 2026, 2:32am

Ok.
For the ZW logs I use the Download button on the screen. It creates a zwave.log and I just copy and paste that into the post; maybe there's a better way?
When this happens I'm just aware of it when the lighting rules act inappropriately.
If I turn on Debug for most devices it seems to auto-cancel after a short length of time so I'm not sure how to make it stay on.

The device seems to top out at 30K and possibly reset to 0 and start slowly incrementing again.
I'm going to sway devices as I have 2 and see if the problem persists.

jtp10181 · February 18, 2026, 2:51am

My driver should have an option to set Trace logging indefinitely. That will only show the message data after its already parsed by Zwave JS unfortunately. Really need to see the Zwave JS log to see the raw message and what JS did with it.

Why dont you just take one and point a really bright flashlight at it while zwave logging in running? Thats how I always test the lux on motion sensors.