@Voxen not at this moment.
When I have time, I will first implement some other thermostats, then use those implementations for the MCO thermostats.
@Voxen not at this moment.
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
Could you please add MH7 support? Any ideas when it will be made available? Many thanks!
I cannot seems to include the following to Homey:
- MCO Touch Switch (1 gang)
- MCO Touch Switch (4 gang)
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.
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.
Once this SDK2 version is stable (incl. 1,92 FW), I will use it for implementing support of other thermostats, like the MH7(H).
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.
@Juergen which version of the MH7 thermostat do you have?
I’ve just added support for the MH7 thermostat (without humidity measurement) to the development branch on GitHub: https://github.com/TedTolboom/com.mcohome/tree/development
If this is this right version, you could give it a try to install this version of the app via the CLI.
I’ll add support for the MH7H (with humidity measurement) in the next days.
version 1.1.3 is available in the app store
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”!!!
Hello, I would like to ask you, if there is plan to integrate and add support of MH8 thermostats.
@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.
No feedback received yet…?!
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.
A minor update has been uploaded to the app store:
Thank you for this app!
Unfortunately I can’t get the app to work with mine CO2 Monitor.
(Date: 2018-11-23) EU Z-Wave plus
The message in homey after adding the device:
'“Er is geen geschikte Homey App gevonden voor dit apparaat.
Het apparaat is toegevoegd als Basic- Z-Wave apparaat.”
“Could not find a suitable Homey App for this device.
The device is added as a basic Z-wave device”
Maybe there is a difference in the newest iteration of the device?
Please tell me if I van provide some information so the device is properly recognized in the App.
Thanks for reporting. I guess MCOHOME used new product- and or productType-ID’s for the latest generation.
Can you post the ID’s of the device when added as generic Z-wave device?
Thank you for your dedicated support!
This is the information that Homey shows
(I couldn’t select the text for copy/paste so I hope I didn’t make an error…)
Node ID: 8
Fabrikant ID: 351
Product type ID: 2306
Product ID: 20738
Firmware version: 21250
Device class (basic): BASIC_TYPE_ROUTING_SLAVE
Device class (generic): GENERIC_TYPE_SENSOR_MULTILEVEL
Device class (specific): SPECIFIC_TYPE_ROUTING_SENSOR-MULTISENSOR