Skip to content

ZG-104PLV (Excellux PIRIV01): illuminance field always null, actual value in misspelled 'illumiance' field #31626

@qspawn

Description

@qspawn

What happened?

The standard 'illuminance' property in the MQTT payload is always null. The actual lux value is published under 'illumiance' (missing the 'n'). This appears to be a datapoint mapping error in the converter. The 'illumiance' field updates correctly and responds to light changes.

Example payload:
{"illumiance": 8664, "illuminance": null, ...}

What did you expect to happen?

The 'illuminance' field to contain the lux value, consistent with all other Z2M devices.

How to reproduce it (minimal and precise)

Pair an Excellux ZG-104PLV (PIRIV01) and observe the MQTT payload on zigbee2mqtt/[device_name]. The illuminance field will be null while illumiance contains the actual value.

Zigbee2MQTT version

2.92

Adapter firmware version

6.10.3.0 build 297

Adapter

EZSP (Sonoff ZBDongle-Plus V2)

Setup

Add-on on Home Assistant OS, Intel N95 x86-64

Device database.db entry

IEEE Address: 0xa4c1386ca904a87f Manufacturer: Excellux Model ID: PIRIV01 Z2M Definition: ZG-104PLV Firmware: 2026010601

Debug log

No response

Notes

Workaround: manual MQTT sensor in HA configuration.yaml reading value_json.illumiance directly from the state topic.

{
"battery": 100,
"illumiance": 0,
"illumiance_calibration": 5,
"illumiance_v0": 7385,
"illumiance_v1": 10000,
"illumiance_warning": "low",
"last_seen": "2026-04-06T00:00:50-04:00",
"linkquality": 184,
"presence": "false",
"sampling_interval": 5,
"vibration": false,
"vibration_sensitivity": 20,
"illuminance": null,
"illuminance_warning": null
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    problemSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions