aqara p1 motion sensor - illumination value is not updating properly / also even the device is inside dark room nonsense value of illuminance":65534"lx; is presented.

[heapxor]

What happened?

It is often reporting 656xx lux of illuminance.
Basically unusable for any type of automation ... as a result that lux are completely reporting nonsense values.

motion_sensitivity
detection_interval
both are not able to be changed ....
Publish 'set' 'motion_sensitivity' to 'motion-sensor-xxx' failed: 'Error: Write 0x54ef44100043e436/1 aqaraOpple({"268":{"value":3,"type":32}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4447,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))'

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.25.1-1

Adapter firmware version

0.0.0_0005

Adapter

sonoff usb 3.0 stick

Debug log

No response

[Otnow]

It is often reporting 656xx lux of illuminance. Basically unusable for any type of automation ... as a result that lux are completely reporting nonsense values.

Please record a debug log that captures the moment of the problem.

---

motion_sensitivity detection_interval both are not able to be changed .... Publish 'set' 'motion_sensitivity' to 'motion-sensor-xxx' failed: 'Error: Write 0x54ef44100043e436/1 aqaraOpple({"268":{"value":3,"type":32}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4447,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))'

Immediately after changing the settings of the sensor, you need to press the button on it so that it wakes up and accepts the changes.

[heapxor]

@Otnow thanks,
it was also mentioned here >
https://www.reddit.com/r/homeassistant/comments/ud22gp/comment/i6jk62g/?utm_source=share&utm_medium=web2x&context=3
https://community.smartthings.com/t/aqara-motion-sensor-lux-readings/242209/10
home-assistant/core#34392

I set in configuration
advanced:
log_level: debug
but where is that log? the moment when it happens is random - it absolutely doesnt read lx number correctly ... interval of reading are random, it goes from 0 to 6554 randomly etc... ;(

the room was dark so lx = 0 even its reports "illuminance":65534,
then i made movement, it still reports
"illuminance":65534,

debug 2022-05-26 03:04:47Received Zigbee message from 'Chodba-routre-power-socket', type 'attributeReport', cluster 'genBasic', data '{"65506":53,"65508":0,"appVersion":74}' from endpoint 1 with groupID 0 debug 2022-05-26 03:04:59Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"illuminance":131070}' from endpoint 1 with groupID 0 debug 2022-05-26 03:04:59lumi.motion.ac02: unknown key illuminance with value 131070 debug 2022-05-26 03:04:59lumi.motion.ac02: Processed data into payload {} info 2022-05-26 03:04:59MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":30,"illuminance":65534,"linkquality":134,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3165}' debug 2022-05-26 03:05:20Received Zigbee message from 'Chodba-routre-power-socket', type 'readResponse', cluster 'haElectricalMeasurement', data '{"activePower":36,"rmsCurrent":256,"rmsVoltage":235}' from endpoint 1 with groupID 0 info 2022-05-26 03:05:20MQTT publish: topic 'zigbee2mqtt/Chodba-routre-power-socket', payload '{"child_lock":"UNLOCK","current":0.26,"energy":3.76,"indicator_mode":"off/on","linkquality":58,"power":36,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"update_available":false,"voltage":235}' debug 2022-05-26 03:05:20Received Zigbee message from 'Kavovar-power-socket', type 'readResponse', cluster 'haElectricalMeasurement', data '{"activePower":0,"rmsCurrent":0,"rmsVoltage":236}' from endpoint 1 with groupID 0 info 2022-05-26 03:05:20MQTT publish: topic 'zigbee2mqtt/Kavovar-power-socket', payload '{"child_lock":"UNLOCK","current":0,"energy":0.69,"indicator_mode":"off/on","linkquality":21,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"update_available":false,"voltage":236}' info 2022-05-26 03:05:31MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":30,"illuminance":65534,"linkquality":134,"motion_sensitivity":"high","occupancy":false,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3165}'

here i powered off light (i assume with light on it was ~15lx)
but no change even light is off now it shows

I have same sensor in other room, so i tried to change motion_sensitivity, so i changed it and pressed the button as was suggested - and it was changed correctly and during that press LX was recalculated and now are showing correct value...

debug 2022-05-26 03:10:23Received MQTT message on 'zigbee2mqtt/spalen0x54ef44100043e20b/set' with data '{"detection_interval":20}' debug 2022-05-26 03:10:23Publishing 'set' 'detection_interval' to 'spalen0x54ef44100043e20b' debug 2022-05-26 03:10:23Received MQTT message on 'zigbee2mqtt/spalen0x54ef44100043e20b/get' with data '{"detection_interval":""}' debug 2022-05-26 03:10:23Publishing get 'get' 'detection_interval' to 'spalen0x54ef44100043e20b' debug 2022-05-26 03:10:24Received Zigbee message from 'spalen0x54ef44100043e20b', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.motion.ac02"}' from endpoint 1 with groupID 0 info 2022-05-26 03:10:25MQTT publish: topic 'zigbee2mqtt/spalen0x54ef44100043e20b', payload '{"battery":100,"detection_interval":20,"illuminance":16,"linkquality":134,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3166}' debug 2022-05-26 03:10:26Received Zigbee message from 'spalen0x54ef44100043e20b', type 'readResponse', cluster 'aqaraOpple', data '{"258":20}' from endpoint 1 with groupID 0 debug 2022-05-26 03:10:26lumi.motion.ac02: Processed data into payload {"detection_interval":20} info 2022-05-26 03:10:26MQTT publish: topic 'zigbee2mqtt/spalen0x54ef44100043e20b', payload '{"battery":100,"detection_interval":20,"illuminance":16,"linkquality":131,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3166}' debug 2022-05-26 03:10:29Received Zigbee message from 'spalen0x54ef44100043e20b', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[1,33,94,12,3,40,27,4,33,0,0,5,33,1,0,8,33,5,1,10,33,0,0,12,32,1,19,32,0,20,32,0,100,16,1,101,33,12,0,105,32,20,106,32,3,107,32,0],"type":"Buffer"}}' from endpoint 1 with groupID 0 debug 2022-05-26 03:10:29lumi.motion.ac02: Processed buffer into data {"1":3166,"3":27,"4":0,"5":1,"8":261,"10":0,"12":1,"19":0,"20":0,"100":1,"101":12,"105":20,"106":3,"107":0} debug 2022-05-26 03:10:29lumi.motion.ac02: unknown key 8 with value 261 debug 2022-05-26 03:10:29lumi.motion.ac02: unknown key 12 with value 1 debug 2022-05-26 03:10:29lumi.motion.ac02: unknown key 19 with value 0 debug 2022-05-26 03:10:29lumi.motion.ac02: unknown key 20 with value 0 debug 2022-05-26 03:10:29lumi.motion.ac02: unknown key 107 with value 0 debug 2022-05-26 03:10:29lumi.motion.ac02: Processed data into payload {"voltage":3166,"battery":100,"temperature":27,"state":"ON","illuminance":12,"detection_interval":20,"motion_sensitivity":"high"} debug 2022-05-26 03:10:29lumi.motion.ac02: Processed data into payload {"voltage":3166,"battery":100,"temperature":27,"state":"ON","illuminance":12,"detection_interval":20,"motion_sensitivity":"high"} info 2022-05-26 03:10:29MQTT publish: topic 'zigbee2mqtt/spalen0x54ef44100043e20b', payload '{"battery":100,"detection_interval":20,"illuminance":12,"linkquality":131,"motion_sensitivity":"high","occupancy":true,"state":"ON","temperature":27,"update":{"state":null},"update_available":null,"voltage":3166}' info 2022-05-26 03:10:43MQTT publish: topic 'zigbee2mqtt/spalen0x54ef44100043e20b', payload '{"battery":100,"detection_interval":20,"illuminance":12,"linkquality":131,"motion_sensitivity":"high","occupancy":false,"state":"ON","temperature":27,"update":{"state":null},"update_available":null,"voltage":3166}'

So it looks like once sensor goes to some idle / sleep mode - LX is not read properly? just my dumb guess.
Yeah, seems i am correct, after update of the sensors - motion_sensitivity - then i moved it back to the dark room, but number of LX stays the same ~12; then i powered on light in the room - nothing - no reading/change ... powering off the light again no change.

Is that hw bug or software bug? :(
Seems that device is reading LX correctly only once button is pressed and few more seconds then no update of LX reading even its changing.

thanks!

[heapxor]

@Otnow

here i simulated the following scenario, device was showing illuminance 65534; i created movement and powered on the light, still was showing 65534;
then i pressed the button illumination 29 was immediately reported;
debug 2022-05-26 03:21:53Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.motion.ac02"}' from endpoint 1 with groupID 0 debug 2022-05-26 03:21:58Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[1,33,53,12,3,40,27,4,33,0,0,5,33,1,0,8,33,5,1,10,33,0,0,12,32,1,19,32,0,20,32,0,100,16,0,101,33,29,0,105,32,30,106,32,3,107,32,0],"type":"Buffer"}}' from endpoint 1 with groupID 0 debug 2022-05-26 03:21:58lumi.motion.ac02: Processed buffer into data {"1":3125,"3":27,"4":0,"5":1,"8":261,"10":0,"12":1,"19":0,"20":0,"100":0,"101":29,"105":30,"106":3,"107":0} debug 2022-05-26 03:21:58lumi.motion.ac02: unknown key 8 with value 261 debug 2022-05-26 03:21:58lumi.motion.ac02: unknown key 12 with value 1 debug 2022-05-26 03:21:58lumi.motion.ac02: unknown key 19 with value 0 debug 2022-05-26 03:21:58lumi.motion.ac02: unknown key 20 with value 0 debug 2022-05-26 03:21:58lumi.motion.ac02: unknown key 107 with value 0 debug 2022-05-26 03:21:58lumi.motion.ac02: Processed data into payload {"voltage":3125,"battery":100,"temperature":27,"state":"OFF","illuminance":29,"detection_interval":30,"motion_sensitivity":"high"} debug 2022-05-26 03:21:58lumi.motion.ac02: Processed data into payload {"voltage":3125,"battery":100,"temperature":27,"state":"OFF","illuminance":29,"detection_interval":30,"motion_sensitivity":"high"} info 2022-05-26 03:21:58MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":30,"illuminance":29,"linkquality":131,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3125}' info 2022-05-26 03:22:10MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":30,"illuminance":29,"linkquality":131,"motion_sensitivity":"high","occupancy":false,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3125}' debug 2022-05-26 03:22:17Saving state to file /config/zigbee2mqtt/state.json debug 2022-05-26 03:22:20Received Zigbee message from 'Chodba-routre-power-socket', type 'readResponse', cluster 'haElectricalMeasurement', data '{"activePower":35,"rmsCurrent":287,"rmsVoltage":236}' from endpoint 1 with groupID 0

afterwards i powered off light, dark room lx ~0-1 ; even device reports

and nothing is inside the log ... so apparently illumination is not reading / pushing updates at all ;(

thanks

[Otnow]

@heapxor, Aqara motion sensors report illuminance only at the moment of motion detection, when a button is pressed and without any conditions, once every ~ 55 minutes, i.e. they do not react to the fact of changing the level of illuminance.

The RTCGQ14LM model uses a converter from RTCGQ12LM, for which 0 Lux illuminance at the moment of motion detection corresponds to the message from the sensor {"illuminance": 65536}, i.e. illuminance = msg.data['illuminance'] - 65536.

Apparently, the manufacturer in the RTCGQ14LM model has changed the formula for calculating illuminance.

Accordingly, we need to see exactly what values ​​the sensor will send at different levels of illuminance.

Please record the following 3 debug logs:

• the moment the movement starts and then once button press in a completely dark place (or you can cover the sensor with something opaque) to see the value that the sensor will send with a guaranteed illuminance level of 0 Lux

• the moment the movement starts and then once button press inn medium light conditions (usual conditions)

• the moment the movement starts and then once button press in high light conditions (for example, you can bring the sensor close to a bright lighting lamp)

[heapxor]

@Otnow
yes, thanks. i was not aware of that... but makes sense now. Even tho / there was motion etc...and it shows

instead of ~0lx.

i tried to simulate your points with debug on.
1)
debug 2022-05-26 21:59:15Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"illuminance":131070}' from endpoint 1 with groupID 0 debug 2022-05-26 21:59:15lumi.motion.ac02: unknown key illuminance with value 131070 debug 2022-05-26 21:59:15lumi.motion.ac02: Processed data into payload {} info 2022-05-26 21:59:15MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":65534,"linkquality":87,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3120}' debug 2022-05-26 21:59:23Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.motion.ac02"}' from endpoint 1 with groupID 0 debug 2022-05-26 21:59:28Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[1,33,29,12,3,40,27,4,33,0,0,5,33,1,0,8,33,5,1,10,33,130,37,12,32,1,19,32,0,20,32,0,100,16,0,101,33,254,255,105,32,20,106,32,3,107,32,0],"type":"Buffer"}}' from endpoint 1 with groupID 0 debug 2022-05-26 21:59:28lumi.motion.ac02: Processed buffer into data {"1":3101,"3":27,"4":0,"5":1,"8":261,"10":9602,"12":1,"19":0,"20":0,"100":0,"101":65534,"105":20,"106":3,"107":0} debug 2022-05-26 21:59:28lumi.motion.ac02: unknown key 8 with value 261 debug 2022-05-26 21:59:28lumi.motion.ac02: unknown key 12 with value 1 debug 2022-05-26 21:59:28lumi.motion.ac02: unknown key 19 with value 0 debug 2022-05-26 21:59:28lumi.motion.ac02: unknown key 20 with value 0 debug 2022-05-26 21:59:28lumi.motion.ac02: unknown key 107 with value 0 debug 2022-05-26 21:59:28lumi.motion.ac02: Processed data into payload {"voltage":3101,"battery":100,"temperature":27,"state":"OFF","illuminance":65534,"detection_interval":20,"motion_sensitivity":"high"} debug 2022-05-26 21:59:28lumi.motion.ac02: Processed data into payload {"voltage":3101,"battery":100,"temperature":27,"state":"OFF","illuminance":65534,"detection_interval":20,"motion_sensitivity":"high"} info 2022-05-26 21:59:28MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":65534,"linkquality":80,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3101}'

debug 2022-05-26 22:03:56Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"illuminance":65552}' from endpoint 1 with groupID 0 debug 2022-05-26 22:03:56lumi.motion.ac02: unknown key illuminance with value 65552 debug 2022-05-26 22:03:56lumi.motion.ac02: Processed data into payload {} info 2022-05-26 22:03:57MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":16,"linkquality":83,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3101}' debug 2022-05-26 22:04:04Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.motion.ac02"}' from endpoint 1 with groupID 0 debug 2022-05-26 22:04:09Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[1,33,31,12,3,40,27,4,33,0,0,5,33,1,0,8,33,5,1,10,33,130,37,12,32,1,19,32,0,20,32,0,100,16,0,101,33,15,0,105,32,20,106,32,3,107,32,0],"type":"Buffer"}}' from endpoint 1 with groupID 0 debug 2022-05-26 22:04:09lumi.motion.ac02: Processed buffer into data {"1":3103,"3":27,"4":0,"5":1,"8":261,"10":9602,"12":1,"19":0,"20":0,"100":0,"101":15,"105":20,"106":3,"107":0} debug 2022-05-26 22:04:09lumi.motion.ac02: unknown key 8 with value 261 debug 2022-05-26 22:04:09lumi.motion.ac02: unknown key 12 with value 1 debug 2022-05-26 22:04:09lumi.motion.ac02: unknown key 19 with value 0 debug 2022-05-26 22:04:09lumi.motion.ac02: unknown key 20 with value 0 debug 2022-05-26 22:04:09lumi.motion.ac02: unknown key 107 with value 0 debug 2022-05-26 22:04:09lumi.motion.ac02: Processed data into payload {"voltage":3103,"battery":100,"temperature":27,"state":"OFF","illuminance":15,"detection_interval":20,"motion_sensitivity":"high"} debug 2022-05-26 22:04:09lumi.motion.ac02: Processed data into payload {"voltage":3103,"battery":100,"temperature":27,"state":"OFF","illuminance":15,"detection_interval":20,"motion_sensitivity":"high"} info 2022-05-26 22:04:09MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":15,"linkquality":87,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3103}' info 2022-05-26 22:04:18MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":15,"linkquality":87,"motion_sensitivity":"high","occupancy":false,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3103}'

debug 2022-05-26 22:06:53Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"illuminance":65716}' from endpoint 1 with groupID 0 debug 2022-05-26 22:06:53lumi.motion.ac02: unknown key illuminance with value 65716 debug 2022-05-26 22:06:53lumi.motion.ac02: Processed data into payload {} info 2022-05-26 22:06:53MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":180,"linkquality":76,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3103}' debug 2022-05-26 22:06:59Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.motion.ac02"}' from endpoint 1 with groupID 0 debug 2022-05-26 22:07:04Received Zigbee message from 'motion-sensor-chodba-aqara', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[1,33,82,12,3,40,27,4,33,0,0,5,33,1,0,8,33,5,1,10,33,130,37,12,32,1,19,32,0,20,32,0,100,16,0,101,33,199,0,105,32,20,106,32,3,107,32,0],"type":"Buffer"}}' from endpoint 1 with groupID 0 debug 2022-05-26 22:07:04lumi.motion.ac02: Processed buffer into data {"1":3154,"3":27,"4":0,"5":1,"8":261,"10":9602,"12":1,"19":0,"20":0,"100":0,"101":199,"105":20,"106":3,"107":0} debug 2022-05-26 22:07:04lumi.motion.ac02: unknown key 8 with value 261 debug 2022-05-26 22:07:04lumi.motion.ac02: unknown key 12 with value 1 debug 2022-05-26 22:07:04lumi.motion.ac02: unknown key 19 with value 0 debug 2022-05-26 22:07:04lumi.motion.ac02: unknown key 20 with value 0 debug 2022-05-26 22:07:04lumi.motion.ac02: unknown key 107 with value 0 debug 2022-05-26 22:07:04lumi.motion.ac02: Processed data into payload {"voltage":3154,"battery":100,"temperature":27,"state":"OFF","illuminance":199,"detection_interval":20,"motion_sensitivity":"high"} debug 2022-05-26 22:07:04lumi.motion.ac02: Processed data into payload {"voltage":3154,"battery":100,"temperature":27,"state":"OFF","illuminance":199,"detection_interval":20,"motion_sensitivity":"high"} info 2022-05-26 22:07:04MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":199,"linkquality":83,"motion_sensitivity":"high","occupancy":true,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3154}' info 2022-05-26 22:07:15MQTT publish: topic 'zigbee2mqtt/motion-sensor-chodba-aqara', payload '{"battery":100,"detection_interval":20,"illuminance":199,"linkquality":83,"motion_sensitivity":"high","occupancy":false,"state":"OFF","temperature":27,"update":{"state":null},"update_available":null,"voltage":3154}'

is that OKay for fixing the code? thanks

[Otnow]

@heapxor, thanks, but I still can't understand the logic of high illuminance values, because I do not see the dynamics of their changes:

1. high value (65534 presumably corresponds to 0 Lux): {"illuminance":131070}

2. normal value (16 Lux): {"illuminance":65552}

3. normal value (180 Lux): {"illuminance":65716}

I expected to see different high light values in all 3 cases, but it was only in 1 case.

Ideally, we need to sniff the traffic between the sensor and the native Aqara hub in order to see the exact correspondence between the received illuminance value from the sensor and the value displayed in the Aqara Home app.

Do you have such an opportunity?

[TheJulianJES]

ZHA users are experiencing the same issue: zigpy/zha-device-handlers#1541 (comment)

[Otnow]

@TheJulianJES, thanks. Do I understand correctly that high illuminance values ​​come from the sensor only in the dark?

[TheJulianJES]

@Otnow This is what it looks like to me at the moment. There are still multiple different (very large) values that are sent in the complete darkness. I'm not sure if they have a special meaning.

I'm currently trying to figure out the number above which illuminance should be set to 0 (and how and when these values are sent in general).

[Otnow]

@TheJulianJES, good. Does the sensor report very low illuminance values like 1, 2, 3 Lux?

[heapxor]

@Otnow to me 65534 something was reported mostly when i simulated dark/ covered sensor.

it got flipped to 65x again... there is dark at moment
other sensor reports low lx

[Otnow]

@heapxor, ok, thanks.

I think the quick fix is to consider high illuminance values as 0 Lux.

Accordingly, it is necessary to find out the upper limit, above which the values ​​are considered high.

I suggest that 1000 Lux should be considered the upper limit, as this value is the maximum in the Aqara Home app when specifying a condition in automation for a colleague RTCGQ12LM:

Does anyone have the opportunity to see this value in the Aqara Home app for RTCGQ14LM?