# Zigbee2mqtt: Müller Licht 404049D missing actions

**URL:** <https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951>\
**Category:** Demande de fonctionnalités\
**Tags:** zigbee2mqtt, feature-integration\
**Created:** [May 24, 2024, 3:07pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951 "2024-05-24T15:07:56Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [May 24, 2024, 3:07pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/1 "2024-05-24T15:07:56Z")

</div>

Hello everyone,  
I have a Müller Licht 404049D remote control supported by Zigbee2mqtt. In Gladys, only the «&nbsp;On&nbsp;» and «&nbsp;Off&nbsp;» 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 😀  
![image|358x

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [May 31, 2024, 1:18pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/2 "2024-05-31T13:18:45Z")

</div>

Hi @Tolkyen 🙂

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:

> <https://github.com/GladysAssistant/Gladys/pull/2009>
>
> \### Pull Request check-list
> 
> To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items:
> 
> \- \[\] If your changes affects code, did your write the tests?
> \- \[x\] Are tests passing? (\`npm test\` on both front/server)
> \- \[x\] Is the linter passing? (\`npm run eslint\` on both front/server)
> \- \[x\] Did you run prettier? (\`npm run prettier\` on both front/server)
> \- \[x\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front)
> \- \[x\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging.
> \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
> \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com).
> \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com).
> 
> NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
> 
> \### Description of change
> 
> Add philips hue dimmer switch 324131092621
> 
> \[Philips Hue Dimmer Switch\](https://community.gladysassistant.com/t/zigbee2mqtt-ajout-telecommande-philips-hue-dimmer-switch/8675)

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

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [June 2, 2024, 11:31am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/3 "2024-06-02T11:31:12Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [June 3, 2024, 8:31am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/4 "2024-06-03T08:31:43Z")

</div>

Awesome 🙂

You have a tutorial on the site :

> **[Contribuer sur Gladys Assistant | Gladys Assistant](https://gladysassistant.com/fr/docs/dev/developing-a-service/)**
>
> Gladys Assistant est un projet open-source, et tout son code est disponible sur Github.

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!

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 6, 2025, 2:42pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/5 "2025-02-06T14:42:15Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\
**Post date:** [February 6, 2025, 8:28pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/6 "2025-02-06T20:28:40Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 6, 2025, 10:15pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/7 "2025-02-06T22:15:34Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\
**Post date:** [February 6, 2025, 10:34pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/8 "2025-02-06T22:34:48Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 6, 2025, 10:45pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/9 "2025-02-06T22:45:06Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 7, 2025, 8:10am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/10 "2025-02-07T08:10:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 9, 2025, 12:35pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/11 "2025-02-09T12:35:10Z")

</div>

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 «&nbsp;Exposes&nbsp;» but in «&nbsp;State&nbsp;», 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 😞

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 10, 2025, 8:02am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/12 "2025-02-10T08:02:36Z")

</div>

> [@Tolkyen](#):
>
> The sticking point is with the actions `color_temperature_move` and `color_move` which require fetching information that is not in ‹&nbsp;Exposes&nbsp;› but in ‹&nbsp;State&nbsp;›

Which information is missing? 🙂

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

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 10, 2025, 12:06pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/13 "2025-02-10T12:06:58Z")

</div>

Here is what we have in Expose:

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/9/7/97ec5df0c244456c13caee8f6c66f1730e1fdd8d.png)

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 10, 2025, 1:03pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/14 "2025-02-10T13:03:45Z")

</div>

> [@Tolkyen](#):
>
> To use the `color_temperature_move` action, you need to retrieve the value of `action_color_temperature`, which is not in Expose since the action does not determine whether it increases or decreases.

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)

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 10, 2025, 6:33pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/15 "2025-02-10T18:33:31Z")

</div>

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}`

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 11, 2025, 7:50pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/16 "2025-02-11T19:50:50Z")

</div>

Thanks for the objects!

In itself we already have special cases:

> <https://github.com/GladysAssistant/Gladys/blob/master/server/services/zigbee2mqtt/exposes/enumType.js#L136>

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

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 12, 2025, 11:36pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/17 "2025-02-12T23:36:23Z")

</div>

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](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/d/3/d3319629090e123eeb21c1844812d7c6e69be405.png)  
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 «&nbsp;useful&nbsp;» features but that seems like a lot just for that.  
I don’t want to get into an overengineered setup for these two points.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 13, 2025, 7:36am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/18 "2025-02-13T07:36:23Z")

</div>

Thanks for the clarification!

> [@Tolkyen](#):
>
> The trick might be to force the Zigbee2mqtt integration to add the «&nbsp;useful&nbsp;» features, but that seems like a lot just for that.

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?

---

<div class="post-metadata">

**Author:** ![Tolkyen](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/t/ba8739/32.png) [@Tolkyen](https://community.gladysassistant.com/u/Tolkyen)\
**Post date:** [February 13, 2025, 12:03pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/19 "2025-02-13T12:03:52Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 7:36am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951/20 "2025-02-14T07:36:16Z")

</div>

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?

[Next page](https://community.gladysassistant.com/t/zigbee2mqtt-muller-licht-404049d-actions-manquantes/8951.md?page=2)
