Zigbee2mqtt: Müller Licht 404049D missing actions

Feature requests
,
1

Hello everyone,
I have a Müller Licht 404049D remote control supported by Zigbee2mqtt. In Gladys, only the « On » and « Off » actions are supported. Would it be possible to support the other actions ( brightness_step_up, brightness_step_down, brightness_move_up, brightness_move_down, brightness_stop, color_temperature_move, color_move, scene_1, scene_2, scene_3, scene_4, scene_5, scene_6) ?

Thanks in advance :grinning:
![image|358x

2

Hi @Tolkyen :slight_smile:

We’ll add this remote to Gladys no problem!

Do you have development skills or not?

Here’s an example of a PR that adds button types on Zigbee2mqtt:

If you don’t have the skills, I’ll take care of it no problem!

3

Hi @pierre-gilles :grinning:,
I’ll see what I can do. I’m setting up a dev environment to check. I might manage to pull it off :sweat_smile:

4

Awesome :slight_smile:

You have a tutorial on the site :

For this one, I recommend following the PR I linked above and doing exactly the same.

For your DEV environment, I recommend connecting the environment to your remote Zigbee2mqtt to get the remote control into your DEV Gladys.

If you want help, don’t hesitate — I’m always here to help!

5

Hi @Tolkyen,

I’m getting back to you on this — do you still have this need in Gladys and do you need help with the PR?

If so, we can absolutely help you or even do it… it’s quite simple!

6

I’m going through the requests related to zigbee2mqtt and I’ve noted it on my to-do list.

7

Hi @pierre-gilles,

I had started the dev, then got stuck on one point and afterwards went on vacation. Indeed, help would be welcome. I don’t have much time to develop right now. But I’ve been getting back into it for a week, drawing inspiration from your livecoding on Sonos (great performance, by the way)

8

I’ll let you carry on then, but don’t hesitate if you have any questions or if you want us to resume development.

1 Like
9

Thanks @_Will_71. I’ll go over all that and ask for help depending on the difficulties I might encounter :grimacing:

1 Like
10

Don’t hesitate at all @Tolkyen !

For this kind of Zigbee device, it really only takes 10 minutes to integrate ^^

If you want us to jump on a 5-minute call to debug something at your place, don’t hesitate.

11

I just realized what I’m stuck on. A large part of this remote’s actions need to be declared in order to be recognized. The sticking point is with the color_temperature_move and color_move actions, which require retrieving information that is not in « Exposes » but in « State », which in my view requires handling something specific while the Zigbee2mqtt integration is meant to be generic. I hope I’ve been clear. As a result, I’m losing interest in color control via the remote :disappointed:

12

Which information is missing? :slight_smile:

Do you have examples of objects to send for these two actions?

13

Here is what we have in Expose:

image
image626×281 4.8 KB

14

Do you have an example of an object sent by Zigbee2mqtt?

(By connecting to the MQTT broker with an MQTT client, you should be able to retrieve that easily)

15

Here are the examples retrieved with an MQTT client (MQTT.fx).

On color_move, I get this: {\"action\":\"color_move\",\"action_color\":{\"x\":0.7,\"y\":0.3},\"action_group\":16387,\"action_transition_time\":0,\"last_seen\":\"2025-02-10T18:30:10.634Z\",\"linkquality\":185}

On color_temperature_move, here is the response: {\"action\":\"color_temperature_move\",\"action_color_temperature\":153,\"action_group\":16387,\"action_transition_time\":10,\"last_seen\":\"2025-02-10T18:32:33.806Z\",\"linkquality\":167}

16

Thanks for the objects!

In itself we already have special cases:

It doesn’t bother me to have another special case for this remote, it’s a shame but sometimes we have no choice :slight_smile:

17

Good evening, I feel like I haven’t explained myself well or that I’ve missed something. I’ve properly accounted for special cases for elements that are exposed.
In this case, creating the device only generates the features mapped from Zigbee2mqtt and managed by Gladys that are exposed in Zigbee2mqtt.

image
image399×450 4.23 KB

Consequently, the remote control does not have features for color or temperature, features to store states and be able to use them in scenes.
The trick could be to force the Zigbee2mqtt integration to add the « useful » features but that seems like a lot just for that.
I don’t want to get into an overengineered setup for these two points.

18

Thanks for the clarification!

Indeed, that could be a solution.

Just to understand the need, how do you use this remote control and what would you like to do with it once it’s integrated into Gladys?

19

The goal is to be able to use color management, light temperature, the brightness of an RGB bulb, as well as ambient lighting scenes assignable to the six scene buttons. For scene button management, that works. Same for brightness. The remaining problem is managing the light temperature and color, as explained previously.
Managing a light group (action_group) could be a bonus but it’s not my priority.

20

But more concretely, how are you going to use it in Gladys?

The idea is to create a scene that listens to the remote control’s color change and applies that color to bulbs in your home?