# KaKu, support or workaround for AYCT-303 remote control?

**URL:** <https://community.homey.app/t/kaku-support-or-workaround-for-ayct-303-remote-control/94135>\
**Category:** Devices\
**Created:** [November 9, 2023, 7:21am UTC](https://community.homey.app/t/kaku-support-or-workaround-for-ayct-303-remote-control/94135 "2023-11-09T07:21:09Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Gerben\_Nieuwland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerben_nieuwland/32/82613_2.png) [@Gerben\_Nieuwland](https://community.homey.app/u/Gerben_Nieuwland)\
**Post date:** [February 11, 2024, 2:19pm UTC](https://community.homey.app/t/kaku-support-or-workaround-for-ayct-303-remote-control/94135/13 "2024-02-11T14:19:34Z")

</div>

After some searching around and comparing payload of the AYCT-303 with the config in the example repo of Athom on Github I figured out that (except of the group button and dim) you can use the AYCT-102 as device to make the regular switch function work.

Find the config of the different buttons below:

| AYCT-303 | | AYCT-102 | | |
| --- | --- | --- | --- | --- |
| Button | State | Channel | Button | State |
| 1 | On | 1 | 2 | On |
| 1 | Off | 1 | 2 | Off |
| 2 | On | 1 | 3 | On |
| 2 | Off | 1 | 3 | Off |
| 3 | On | 1 | 4 | On |
| 3 | Off | 1 | 4 | Off |
| 4 | On | 2 | 1 | On |
| 4 | Off | 2 | 1 | Off |

---

_[View the full topic](https://community.homey.app/t/kaku-support-or-workaround-for-ayct-303-remote-control/94135)._