# Support for MediaPlayback, KeypadInput, and LevelControl clusters in media devices

**URL:** <https://community.gladysassistant.com/t/matter-support-des-clusters-mediaplayback-keypadinput-et-levelcontrol-pour-les-appareils-media/10223>\
**Category:** Demande de fonctionnalités\
**Tags:** in-progress, feature-integration, matter\
**Created:** [May 12, 2026, 10:08am UTC](https://community.gladysassistant.com/t/matter-support-des-clusters-mediaplayback-keypadinput-et-levelcontrol-pour-les-appareils-media/10223 "2026-05-12T10:08:07Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![b3n.0](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/b3n.0/32/3458_2.png) [@b3n.0](https://community.gladysassistant.com/u/b3n.0)\
**Post date:** [September 6, 2026, 11:31am UTC](https://community.gladysassistant.com/t/matter-support-des-clusters-mediaplayback-keypadinput-et-levelcontrol-pour-les-appareils-media/10223/22 "2026-09-06T11:31:51Z")

</div>

I realize that my last message is absolutely incomprehensible…

But while reading the topic about the possibility for integrations to declare their own widgets, I already found an answer to part of my questions.

> [@Allow integrations to declare their own dashboard widgets (JSON schema)](https://community.gladysassistant.com/t/permettre-aux-integrations-de-declarer-leurs-propres-widgets-de-dashboard-schema-json/10641?u=b3n.0):
>
> The need Today, all dashboard widgets are developed in the core of Gladys. An integration (especially an external one, via the SDK) cannot propose a widget specific to its domain, although this is often where the data makes the most sense: solar production tracking, status of a robot vacuum, charging schedule of an electric car, etc. The proposal Allow an integration to declare one or more widgets via a JSON schema, on the same principle as the configuration pages of external integrations. Th…

If I understand correctly, today, we cannot really «&nbsp;plug in&nbsp;» information or actions into Gladys that do not exist in the Gladys core. And, consequently, we cannot really display them in the dashboard or use them in scenes either.

This is exactly where I agree with the topic of widgets: if, in the future, an external integration could declare its own data, actions, and possibly triggers, we could then have an integration capable of filling in any gaps in the Gladys core, without necessarily having to add each specific feature in Gladys.

So, I think that it is rather this interaction between the core and external integrations that I was trying to understand in my previous message.

---

_[View the full topic](https://community.gladysassistant.com/t/matter-support-des-clusters-mediaplayback-keypadinput-et-levelcontrol-pour-les-appareils-media/10223)._
