L&S lighting zigbee module behaves wrongly when setting brightness

Aperta
  • Qualcosa non va?
#33,679 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, typescript
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
15.8k
Fork
2.1k
Merge medio
1g 6h
PR unite (30g)
38

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Koenkk/zigbee2mqtt

Tutte le issue di Koenkk/zigbee2mqtt

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.