# Issues with MCOHome Switches **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave, homey-pro\ **Created:** [July 31, 2023, 4:47pm UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618 "2023-07-31T16:47:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![wysie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wysie/32/82919_2.png) [@wysie](https://community.homey.app/u/wysie)\ **Post date:** [July 31, 2023, 4:47pm UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618/1 "2023-07-31T16:47:39Z")
Hi all, new here and looking for some help, thanks! I’m using Homey Pro 2023 with MCOHome switches. Flows and switches work perfectly fine when triggered using Homey app/website, but if I press the physical button the results vary a lot. For example, I’ve a flow to emulate a 2-way switch (I tried with groups and associations but for some reason some of them can’t work [the groups added aren’t triggering], or I can’t even add the device [Homey automatically removes the ., e.g. if I add 22.1 it becomes 22, which is incorrect]). So I’ve 4 basic flows as follows: 1. Switch that is connected to light turns on, another unconnected switch also turns on (to simulate a 2-way) 2. Switch that is connected to light turns off, another unconnected switch also turns off (to simulate a 2-way) 3. Simulated 2-way unconnected switch turns on, the actual connected switch also turns on 4. Simulated 2-way unconnected switch turns off, the actual connected switch also turns off 1 and 2 works fine most of the time, but 3 and 4 almost never works, and I’ve no idea why :(. This seems related to [[App][Pro] MCOHome App (v1.4.0 | TEST v1.5.3) - #226 by Miel\_Krijnen](https://community.homey.app/t/app-pro-mcohome-app-v1-4-0-test-v1-5-3/159/226?page=7). Thank you! ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 1, 2023, 12:02am UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618/2 "2023-08-01T00:02:57Z")
There’s no need, it’s even a bit annoying, to [double post](https://community.homey.app/t/app-pro-mcohome-app-v1-4-0-test-v1-5-3/159/235) your questions 🤗 ---
**Author:** ![wysie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wysie/32/82919_2.png) [@wysie](https://community.homey.app/u/wysie)\ **Post date:** [August 1, 2023, 1:36am UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618/3 "2023-08-01T01:36:59Z")
Deleted the other post, thanks. ---
**Author:** ![wysie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wysie/32/82919_2.png) [@wysie](https://community.homey.app/u/wysie)\ **Post date:** [August 1, 2023, 5:27am UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618/4 "2023-08-01T05:27:11Z")
I did more testing, found out that this issue only happens to 4-gang switches on MCOHome. The dimmers, 2-gang, etc. all update the status just fine. Checking the developers tools, all the other switches show up as “Secure (⨯)”, but the 4-gangs show up as “Secure (Unauthenticated)”. Update: I downloaded the MCOhome source from GitHub and added in ““security”: [“none”]” to drivers.compose.json for the 4-gang switches. Now I’m able to add them as “Secure (⨯)”, unfortunately still no status update on the Homey app after using the physical switches. ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [January 31, 2025, 2:28am UTC](https://community.homey.app/t/issues-with-mcohome-switches/85618/5 "2025-01-31T02:28:20Z")
Archived on January 31, 2025, 2:28am UTC