-
-
Notifications
You must be signed in to change notification settings - Fork 24
Closed
Labels
problemSomething isn't workingSomething isn't working
Description
What happened?
- I'm using a motion sensor, which is also reporting illuminance.
- It is reporting
illuminance_lux
andilluminance
as MQTT messages - In the zigbee2mqtt adapter these two values are represented as
illuminance
andilluminance_raw
- In the node-red adapter, I'm processing the
illuminance
value - Whenever a new message arrives, I get two values in node-red: The value for
illuminance
andilluminance_raw
First one is the raw value and second one is the lux value
Also in the adapter itself, it seems that the raw value is not updated unless the adapter is restarted:
What did you expect to happen?
Both values are updated and separated accordingly.
Is there same regex matching that is too broad?
How to reproduce it (minimal and precise)
No response
Adapter version
abc738c (current git)
Log
zigbee2mqtt.0 | 2022-12-04 16:36:13.794 | info | MQTT publish: topic 'zigbee2mqtt/MotionFrontDoor/illuminance_lux', payload '2' |
---|---|---|---|
zigbee2mqtt.0 | 2022-12-04 16:36:13.794 | debug | Device: MotionFrontDoor/illuminance_lux not found, queue state in incStatsQueue! |
zigbee2mqtt.0 | 2022-12-04 16:36:13.791 | info | MQTT publish: topic 'zigbee2mqtt/MotionFrontDoor/illuminance', payload '3064' |
zigbee2mqtt.0 | 2022-12-04 16:36:13.790 | debug | Device: MotionFrontDoor/illuminance not found, queue state in incStatsQueue! |
zigbee2mqtt.0 | 2022-12-04 16:36:13.789 | info | MQTT publish: topic 'zigbee2mqtt/MotionFrontDoor', payload '{"battery":100,"illuminance":3064,"illuminance_lux":2,"last_seen":"2022-12-04T16:36:13+01:00","linkquality":69,"motion_sensitivity":"high","occupancy":false,"occupancy_timeout":0,"temperature":3.07,"update":{"state":"idle"}}' |
Metadata
Metadata
Assignees
Labels
problemSomething isn't workingSomething isn't working