# Support for EAP225-Wall

**URL:** <https://forum.openwrt.org/t/support-for-eap225-wall/71462>\
**Category:** For Developers\
**Created:** [August 10, 2020, 8:29pm UTC](https://forum.openwrt.org/t/support-for-eap225-wall/71462 "2020-08-10T20:29:31Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![svanheule](https://forum.openwrt.org/user_avatar/forum.openwrt.org/svanheule/32/88134_2.png) [@svanheule](https://forum.openwrt.org/u/svanheule)\
**Post date:** [August 13, 2020, 7:59pm UTC](https://forum.openwrt.org/t/support-for-eap225-wall/71462/6 "2020-08-13T19:59:25Z")

</div>

And by using KEY\_LIGHTS\_TOGGLE for the LED button, there is a trigger to use for toggling the LED. An example script can be found in the other topic linked below, and should probably go on the wiki if this device gets merged.

> [@Toggle LED with push button](https://forum.openwrt.org/t/toggle-led-with-push-button/71599/4):
>
> The hardware.button wiki page lists KEY\_LIGHTS\_TOGGLE as one of the supported keys, for which I can add a script in /etc/rc.button/lights\_toggle. To disable the LED(s), I could probably just loop over all buttons and set trigger to 'none' and default to '0'. That would mean I lost all user config though, so I'll have a look at how to avoid that. Edit: Found a similar use case for KEY\_LIGHTS\_TOGGLE Edit: DTS entry: led { label = "LED button"; linux,code = \<KEY\_LIGHTS\_TOGGLE\>; gpios = \<&…

---

_[View the full topic](https://forum.openwrt.org/t/support-for-eap225-wall/71462)._