Note: Product Identification numbers have been added based on available information, but is still incomplete. If your touch panel switch is not recognized properly, please send me a message.
MCOHome Touch Panel Dimmer
A glass panel dimmer with 1 capacitive touch buttons.
A glass panel dimmer with 2 capacitive touch buttons.
Supported devices:
Touch panel dimmer 1x: MH-P311, MH-P411, MH-P511
Touch panel dimmer 2x: MH-DT311
MCOHome Shutter Panel
A glass shutter panel with 2 capacitive touch buttons.
Supported devices:
Touch shutter panel: MH-C321
MCOHome Micro-dimmer
A Z-Wave enabled 1-load in-wall dimmer
Supported devices:
Micro dimmer: MH-P220
MCOHome Micro-switch
A Z-Wave enabled 1-load in-wall relay
Supported devices:
Micro switch: MH-S220
MCOHome MH7(H) Thermostat
Z-Wave enabled programmable heating thermostat.
Supported devices:
Heating thermostat (MH7): MH7-EH, MH7-WH
Heating thermostat (MH7H): MH7H-EH, MH7H-WH
MCOHome CO2 monitor
Monitor CO2 concentration in air.
Supported devices:
CO2 monitor (MH9-CO2): MH9-CO2-WA, MH9-CO2-WD
MCOHome PM2.5 monitor
Monitor the air quality in terms of Atmospheric particulate matter (PM2.5).
What are you planning to support in the near future?
There are quite a few thermostats for controlling electric floor heating, which is supported by Homey
IheaIT wanted to buy, but the manufacturer does not ship it now
Previously it was working fine albeit a little laggy. I did a factory restore for the homey. And reset the MCO touch switch by pressing the button 10 times. After that I can’t seems to include the MCO touch switch to Homey. I am able to re-include the Aeotec sensors and philips bridge. Only MCO touch switch got problem.
Thanks for your hard work on the shutter panels.
BUT…
Support for MH7 devices is asked for more than one year. When will this be integrated in the app? Moving it every month is not a solution.
Luckily enough, I’m doing this work in my spare time as a hobby my family is classifying as gone (a bit) out of control.
The source code of the MCOHome is app is public and open to any contributions to add support for still missing devices. I’m even supporting newly starting community developers in their start-up. Let me know if anyone is interested.
I’ve updated the MCOHome app to include the start-level and stop-level dim cards for all dimming devices.
Version 1.1.3 is awaiting app store approval.
I’ve just uploaded the v1.2.0 update to the app store for approval; adding support for the MH7(H) thermostats.
Current status: available in the app store
The V1.2.0 app update is available in the app store; looking forward to your feedback on the MH7 implementation!
Thank you very much for the added MH7 Thermostats!
I now have the app installed on Homey and started using it for stopping the electric heating in my bathroom.
For now everything seems to work perfectly. Will post something if it is not.
I tried to connect my 1 button touch panel to Homey, but failed.
Could you advise on how to do so, as I can connect the rest (2 & 4 buttons), just not the 1 button.
I already thought that this is a spare time project. I fully understand it because I had the same experience with my family and my community projects and work on Fibaro HC2 and FHEM. I am currently working on an S0 reader device for energy, water and gas and I would love to get your support. I will contact you the next days via PM (son is currently sick and priorities are a bit shifted at the moment).
To your question: I have multiple MH7 (for water and electrical heating). I will test your implementation and provide feedback AND thanks for your assistance to make the world easier and automated. The 2-button MCO’s are working really great with your “app”!!!
@TedTolboom, will there be a SDKv2 app in the future? I’m using this app a lot, otherwise it seems that I’m not able to update to Homey 2.0 when this is stable.
I’ll check if I can get access to one of the MH8 thermostats. If so, I will add support for it.
The app is native SDKv2; has been defined based on SDKv2 from the start.
But that doesn’t really matter. The only SDKv1 apps that are definitely not working are the ones having an app settings page or that use the homey-API. That is not applicable for most Z-wave apps (using the meshdriver).
Do note that Homey 2.0 is still an experimental release; with still quite some issues to be resolved; like the trigger cards not always working. Check the EN of NL topics on this forum for more info, before upgrading.