L&S lighting zigbee module behaves wrongly when setting brightness

Open
  • Is something wrong?
#33,679 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
backend

Research direction

Start by checking the L&S device definition for model 756200030 and how brightness commands are handled when the light is off. Reproduce with the reported MQTT topic and payload while the light is off, then compare the reported power state with the physical light. Done means brightness changes without an incorrect power state, with a regression test covering the reproduction.

Written by the indexing model from the issue text.

Description

problem
What happened?

I am using Zigbee2MQTT as separate docker container together with a homeassistant docker container.
Pairing and connecting the L&S lighting module (https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/756200030.md) worked fine as well as the control in general. The only thing I noticed is:

When the light is on and I change the brightness via MQTT message or zigbee2mqtt GUI, the device accepts the brightness and all is fine.
When the light is off and I change the brightness via MQTT message or zigbee2mqtt GUI, the device accepts the brightness (according to zigbee2mqtt GUI and MQTT messages), BUT the power state turns on, while the light stays off.

topic used: "PREFIX/LIGHTNAME/11/set"
payload used: { "brightness": VALUE }

I am, unsure, if this is a problem in zigbee2mqtt or in the device itself. Before connecting with L&S, I wanted to check here.

Thanks, André

What did you expect to happen?

I expected, that the power state reflects always the light state.
Additionally I expected that changing the brightness does not change the power state.

How to reproduce it (minimal and precise)

Connect the device to zigbee2mqtt. Make sure the light is set off and brightness is set to 254. You can do this with the original zigbee remote control for the light control MEC module.
Now send a MQTT message to the device to change the brightness. You will notice, that the device changes the brightness value, but also the power state gets switched to "on", while the light in reality stays off.

Zigbee2MQTT version

2.14.3

Adapter firmware version

0x26780700

Adapter

ConBee II

Setup

Running HomeAssistant, mosquitto and zigbee2mqqt in separate Docker containers.
HomeAssistant is used to control the smart home. In this test, I only used MQTT Explorer to send MQTT messages via zigbee2mqtt. HomeAssistant was out of the loop for the test.

Device database.db entry

IEEE-Adr: 0x180df9fffe8d2723 ; NetworkAdr: 0xFD08 ; Definition: 756200030 ; Type: router ; Firmware-ID: 4.09.03-027

Debug log

No response

Notes

No response

Dominant language
TypeScript
Stars
15.8k
Forks
2.1k
Avg merge
1d 6h
Merged PRs (30d)
38

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Koenkk/zigbee2mqtt

All issues in Koenkk/zigbee2mqtt

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.