# Aeotec Micro switch gen 2 dsc26 “missing capability listener”

**URL:** <https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490>\
**Category:** Devices\
**Created:** [June 16, 2021, 8:01pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490 "2021-06-16T20:01:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [June 16, 2021, 8:01pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/1 "2021-06-16T20:01:19Z")

</div>

I’m getting the error “Missing Capability Listener: onOff” when I try to control my DSC26 gen 2 micro switch.

Brand new Homey user, though long-time Automator previously with Indigo. I’ve got a large fleet of Z-Wave devices to migrate. I have successfully migrated a couple of TKB plug sockets without issue. Adding the DSC26 works fine (done at \<10cm range) but then when I try to control the device I get the error message.

Any ideas? Thank you in advance!

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [June 16, 2021, 8:12pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/2 "2021-06-16T20:12:22Z")

</div>

Reboot the aeotec app,  
if that doesn’t fix it, reboot Homey,  
if that still doesn’t fix it you’ll have to re-include your device into Homey.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [June 16, 2021, 8:53pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/3 "2021-06-16T20:53:26Z")

</div>

Thank you Caseda. I did all of those in that order and still exactly the same issue. Anything else I can try? Error message sounded more like an error in the code, no?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [June 16, 2021, 9:13pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/4 "2021-06-16T21:13:56Z")

</div>

> [@Jonathan\_Draper](#):
>
> Error message sounded more like an error in the code, no?

Correct, it does sound like it, but usually that isn’t the case.  
This time though (having looked at the code 3 times), it does seem an error in the code, you’ll have to contact **Aeotec** support for a fix though. (error most likely is: “Basic” should be fully capitalized, they will know where to look for then)  
Weird that you are the first one to notice this one.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [June 16, 2021, 9:20pm UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/5 "2021-06-16T21:20:33Z")

</div>

Fantastic, I will do that - thank you so much for your help. Hopefully they can get this fixed.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [June 17, 2021, 9:54am UTC](https://community.homey.app/t/aeotec-micro-switch-gen-2-dsc26-missing-capability-listener/48490/6 "2021-06-17T09:54:33Z")

</div>

I’ve been advised by Aeotec support that this problem has now been fixed and will be included in the next update.
