# \[APP\]\[Pro\] MCOHome - Adds support for MCOHome Z-wave devices **URL:** \ **Category:** Apps\ **Tags:** app, z-wave, community-app\ **Created:** [August 22, 2018, 8:31pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159 "2018-08-22T20:31:56Z")\ **Posts on this page:** 20\ **Page:** 13
**Author:** ![bonaventure](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bonaventure/32/79712_2.png) [@bonaventure](https://community.homey.app/u/bonaventure)\ **Post date:** [October 30, 2023, 10:22am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/243 "2023-10-30T10:22:00Z")
And HOMEY PRO 2023 magically adjusted the time from CET DST to CET 2 nights before … ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [October 30, 2023, 1:44pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/244 "2023-10-30T13:44:07Z")
Oh, that would be great. However, I am not an expert with raw data. Do you know what the raw data command should be to set the time to 08:00 (a.m.) for example? ---
**Author:** ![bonaventure](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bonaventure/32/79712_2.png) [@bonaventure](https://community.homey.app/u/bonaventure)\ **Post date:** [October 30, 2023, 4:23pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/245 "2023-10-30T16:23:45Z")
CC TIME: > **[Z-Way Manual — Command Class Reference](https://z-wave.me/manual/z-way/Command_Class_Reference.html#SECTION0016300000000000000000)** > > Command Class Reference Then, the magic works like described here: > Time command class is described in SDS13782 (…)(Z-Wave Management Command Class Specification). Time CC is mandatory for all Z-Wave Plus Gateways and thus is the recommended method for a device to set its clock to the current local date and time. Time CC Version 2 adds time zones and daylight savings time support if desired however V1 provides the necessary data in most cases. > > The Z-Wave specification recommends having an association group to identify the time server node however the Gateway is expected to have an accurate time reference so using the Lifeline is acceptable. > > The Time CC does NOT have a date/time SET command. Thus, the hub cannot set the date/time and instead must wait for the device to GET it. When a device is included in a network, it must send a Time GET command within the first few minutes to accurately set its internal clock. The device should then periodically send a Time GET to ensure the internal clock remains accurate to the local time. Note that for certification purposes a device CONTROLs Time CC, it does not SUPPORT it. The Hub is required to SUPPORT Time CC. cited from: > **[Time vs. Clock vs. Time Parameters Command Classes Explained](https://drzwave.blog/2020/10/01/time-vs-clock-vs-time-parameters-command-classes-explained/)** > > There are three ways for a Z-Wave device to synchronize to the local date/time. The best solution is described and an algorithm presented. So, it heavily depends on the device following the rules. Regarding the MH7WH (which I run with HOMEY PRO2023, I can only say that it works. What I do not know is the frequency of updates. Maybe only once a day at 03:09a.m. … so one might be a bit patient… The homey shouldn’t be the problem as it supports ZW+ since 2016, AFAIK … ---
**Author:** ![Justin\_Koh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/justin_koh/32/10019_2.png) [@Justin\_Koh](https://community.homey.app/u/Justin_Koh)\ **Post date:** [December 22, 2023, 5:17pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/246 "2023-12-22T17:17:03Z")
Has the app been abandoned? ---
**Author:** ![Jonas\_Thessen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonas_thessen/32/81158_2.png) [@Jonas\_Thessen](https://community.homey.app/u/Jonas_Thessen)\ **Post date:** [December 23, 2023, 7:26am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/247 "2023-12-23T07:26:20Z")
FYI I’ve sent separate messages asking for help to both developer and the supporting developers, but no responses until today. Its sad - I moved to Homey after being using Fibaro for years - just for the flexibility/versatility but already thinking of going back, - ---
**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\ **Post date:** [December 24, 2023, 6:59am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/248 "2023-12-24T06:59:23Z")
@TedTolboom ---
**Author:** ![Mirek\_Kaspar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mirek_kaspar/32/78907_2.png) [@Mirek\_Kaspar](https://community.homey.app/u/Mirek_Kaspar)\ **Post date:** [January 8, 2024, 10:28pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/249 "2024-01-08T22:28:27Z")
Hello, since this app is apparently dead, I figured out how to control MH-8 FC4 thermostat - missing flow cards for fan and thermostat state. Instead of flow card I use RAW commands and ease set of text variables. I hope this helps for those missing flow cards for this device. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/7/27d613b22df12d2ed8cb21c1e5f1d2ced81f69e6.png) ---
**Author:** ![Grzegorz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grzegorz/32/78901_2.png) [@Grzegorz](https://community.homey.app/u/Grzegorz)\ **Post date:** [March 10, 2024, 9:58pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/250 "2024-03-10T21:58:03Z")
Are there any plans to add support for the MCO Home OS11 presence sensor? ---
**Author:** ![Dr.Broccoli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dr.broccoli/32/74848_2.png) [@Dr.Broccoli](https://community.homey.app/u/Dr.Broccoli)\ **Post date:** [April 29, 2024, 8:34am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/251 "2024-04-29T08:34:44Z")
Does this support the MH5-4A thermostat? If not, will it be supported? ---
**Author:** ![Mou5e](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mou5e/32/3870_2.png) [@Mou5e](https://community.homey.app/u/Mou5e)\ **Post date:** [May 28, 2024, 7:39pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/252 "2024-05-28T19:39:17Z")
Second this. Would really like to see this. ---
**Author:** ![Dak55](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dak55/32/111023_2.png) [@Dak55](https://community.homey.app/u/Dak55)\ **Post date:** [July 15, 2024, 6:39pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/253 "2024-07-15T18:39:47Z")
Same problem, I have the MCO MH8-FC which is detected as a generic device and doesnt work. Are there any solutions to this? ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [July 16, 2024, 11:55am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/255 "2024-07-16T11:55:07Z")
If a device isn’t supported by the App, then there is nothing what can be done, except to make a device request. See the first post for more information. ---
**Author:** ![Jonas\_Thessen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonas_thessen/32/81158_2.png) [@Jonas\_Thessen](https://community.homey.app/u/Jonas_Thessen)\ **Post date:** [July 16, 2024, 12:51pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/256 "2024-07-16T12:51:04Z")
Hello Dirk, how do I create a request for adding A new device? Going back in the treads - there’re some that have same issues that I have. Having devices that per type/function are supported but due to minor changes they have different device ID that the supported - MH-S311 supported but not MH-S311-SL, MH-S312 supported but not MH-S312-SL, MH8-FC4 supported but not MH8-FC… ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [July 16, 2024, 5:33pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/257 "2024-07-16T17:33:59Z")
As in the first post mentioned, you can ask here or on Slack. I guess it’s also possible on GitHub. But the best place, in my opinion, is Slack, because Ted is most active on Slack if he is mentioned within the request. ---
**Author:** ![Yair\_Regev](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yair_regev/32/104578_2.png) [@Yair\_Regev](https://community.homey.app/u/Yair_Regev)\ **Post date:** [July 31, 2024, 11:20am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/258 "2024-07-31T11:20:30Z")
Hi,New to Homey.I’ve added my Z-wave light switches (from MCO Home) and am facing a couple of issues: 1. An extra device is being added - which seems to control all the switches (for example if i have a 3 switch module i will get 3 devices added - 1 foreach physical switch + an extra switch to toggle all 3 on/off). I don’t need this extra switch - can it be removed/disabled/hidden somehow ? it makes a room look like it has 2 switches when it actually just has 1 2. When toggling the switch on/off in Homey - it is reflected in the physical switch on the wall. But when i toggle the physical switch on the wall, it isn’t reflected in Homey - how can this be fixed ? in the advanced settings the “master” switch shows up as node ID 10, and the switch 1 is on node ID 10.1 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/1/a181d42047d0a38b6e22f206fd5bf59885abf4a2.png) ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 1, 2024, 2:30pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/259 "2024-08-01T14:30:59Z")
> [@Yair\_Regev](#): > > can it be removed/disabled/hidden somehow ? No. The only thing you can do is to create a zone for „not needed devices“ and move this device into this zone. I use a similar zone e.g. for remote controls like Philips Hue Dimmer Switch. ---
**Author:** ![Yair\_Regev](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yair_regev/32/104578_2.png) [@Yair\_Regev](https://community.homey.app/u/Yair_Regev)\ **Post date:** [August 3, 2024, 9:18pm UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/260 "2024-08-03T21:18:08Z")
Hi, Some of my switches have a lot of association groups. I have the same type of switch in multiple rooms, and in each room it has a different number of associations groups. For example for a switch with 3 physical buttons I get 9 association groups as seen in the attached image ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e5e6268a11feed900cbe14d0c36caeeef418c9ac.png) Might this be because I removed and added the device a couple of times ? How can this be fixed ? Currently I need trial and error until I figure out which group relates to what physical button. ---
**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:** [August 4, 2024, 5:40am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/261 "2024-08-04T05:40:26Z")
Association groups are defined by the device itself, each group useally has their own purpose the device can report (to), group 1 is the main group (for zwave 500 and higher atleast) where all functions/values if the device is being send to. Group 2 - 9 are different functions of your device, separate buttons, or different sensors, check your devices manual for what functions if they are not specified when you open/edit said group’s setting. ---
**Author:** ![Yair\_Regev](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yair_regev/32/104578_2.png) [@Yair\_Regev](https://community.homey.app/u/Yair_Regev)\ **Post date:** [August 4, 2024, 6:20am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/262 "2024-08-04T06:20:31Z")
I looked at the manual - there shouldn’t be 9 groups When I edit the groups multiple groups say “switch 2” which is what happens when the second button is pressed - only one such group should exist. I wonder if adding/removing the device can cause Homey to add these duplicate groups. ---
**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:** [August 4, 2024, 7:15am UTC](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159/263 "2024-08-04T07:15:33Z")
No, that is not possible. [Previous page](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159.md?page=12) [Next page](https://community.homey.app/t/app-pro-mcohome-adds-support-for-mcohome-z-wave-devices/159.md?page=14)