zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

IKEA LED1923R5 (GU10 rgbw) and LED2111G6 (E14 rgbw) freeze controlled by z2m and Philips 929003017102/RDM004 (Hue Wall Switch Module)

Open SkyhawkXava opened this issue 1 year ago • 6 comments

Hello,

I am using the

  • Signify Hue Wall Switch Module (RDM004)

to directly bind with the following:

  • IKEA LED1923R5 (TRADFRI bulb GU10, color/white spectrum, 345/380 lm), firmware version 1.0.38
  • IKEA LED2111G6 (TRADFRI bulb E14, color/white spectrum, globe, opal, 806 lm), firmware version 1.0.38

I have the following problem: When I turn on the above-mentioned lamps via the Hue Wall Switch and then turn off via Z2M (or HA) and after that I try to turn the lamps back on using the Hue Wall Switch again (due to the existing "on" status in the switch module after pressing the switch twice; 1st "off" command, 2nd "on" command.), the lamps remain off. Afterward, the lamps cannot be turned on by any means. (Although the on/off status changes according to Z2M, the lamps remain off. Only after disconnecting the lamps from the power supply do they start working again.)

It seems that after z2m turns off the lamps, the subsequent "off" command from the hue wall switch module causes the above lamps to freeze.

Apparently, this behavior can also be reproduced with ZHA as the Zigbee coordinator. (See: https://community.home-assistant.io/t/philips-hue-wall-module-issue-with-ikea-gu10-bulbs/802481)

Any other combination of "on" or "off" commands from z2m or the hue wall switch module seem to be unproblematic. With all other Zigbee light bulbs, this issue does not occur.

What did you expect to happen?

That the lamps can be switched on with the hue wall switch after the lamps have been switched on with the hue wall switch and then switched off again with z2m.

How to reproduce it (minimal and precise)

1.) Add/pair IKEA LED1923R5 (GU10 rgbw) or LED2111G6 (E14 rgbw) bulbs to z2m. 2.) Add/pair a hue wall switch module to z2m. 3.) Bind the hue wall switch module directly to IKEA LED1923R5 (GU10 rgbw) or LED2111G6 (E14 rgbw) bulbs. 4.) Turn on the IKEA LED1923R5 (GU10 rgbw) or LED2111G6 (E14 rgbw) bulbs with hue wall switch module. 5.) Turn off the IKEA LED1923R5 (GU10 rgbw) or LED2111G6 (E14 rgbw) bulbs with z2m. 6.) Turn on the IKEA LED1923R5 (GU10 rgbw) or LED2111G6 (E14 rgbw) bulbs again with hue wall switch module by pressing the switch two times (first sends "off", second sends "on"). 7.) The light is freezed. (Until it was disconnected from the power again.)

Zigbee2MQTT version

1.42.0

Adapter firmware version

7.2.1.0 build 144

Adapter

EZSP v10

Setup

Add-on on Home Assistant OS

Debug log

No response

SkyhawkXava avatar Dec 17 '24 13:12 SkyhawkXava

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Feb 21 '25 00:02 github-actions[bot]

No Solutoon yet. Is there a possible way or workaround in z2m?

SkyhawkXava avatar Feb 23 '25 19:02 SkyhawkXava

I installed the new firmware version 1.0.44 (changelog) (firmware date: 20240523). But unfortunately, the problem still persists.

SkyhawkXava avatar Feb 25 '25 12:02 SkyhawkXava

Have the same issue. Wall switch messes things up. Tried third party software but same situation. Will move my bulbs outdoors to work with hue sensor which seems to go well with the bulbs.

Wojciech-creator avatar Feb 28 '25 07:02 Wojciech-creator

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Apr 30 '25 00:04 github-actions[bot]

Unfortunately, the problem still persists. Is there a way to work around it? Has anyone listened in on the commands (via sniffer) of the Hue Wall Switch Module?

SkyhawkXava avatar May 04 '25 11:05 SkyhawkXava

I have exactly the same problem with Ikea LED2005R5 (TRADFRI bulb GU10, white spectrum, 345/380 lm) with firmware 3.0.21.

christophhaase avatar May 24 '25 19:05 christophhaase

I have exactly the same problem as well

ChristianPorsche avatar Jul 18 '25 07:07 ChristianPorsche

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Sep 17 '25 00:09 github-actions[bot]

Not stale, at least on my end the issue still persists.

TibiIius avatar Sep 22 '25 14:09 TibiIius

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Nov 22 '25 00:11 github-actions[bot]