Hello together, my name is Johann and I am new in this forum.
3 years ago I installed a smart home with homematic ip, using a CCU3. It works very well, but now I want to install some lights (matter /zigbee) and in some months I would like to add a viessmann heating (Vi Care). And in the future… Who knows…
At this point the decision to make is between Home Assistant and Homey pro, which I would prefer, because I am not a „Pro".
My questions are the following:
When I integrate the CCU, will I be able to use all components, which had been connected with this CCU before ( Hmip SWDM W, Hmip WTH 2, Hmip Falmot C12, Hmip eTRV 2I9F, Hmip SWSD 2, Hmip PS 2, Hmip SMO A2, Hmip RC 8).
In case the system will not work properly using the Homey- Homematic app: will it be posssible to return to homematic app and CCU3 without connecting all items piece by piece?
Generally what would you think: should I try the (easier) way using a Homey Pro or the Home Assistant the more suitable solution.
I read a lot in this forum, but please forgive me, if I have overlooked appropriate answers.
Currently, only the devices listed in the Homey App Store are supported: Homematic | Homey Supported: HmIP-FALMOT-C12, HmIP-RC8 Not supported: HmIP-SWDM-2, HmIP-WTH-2, HmIP-eTRV-2I9F, HmIP-SWSD-2, HmIP-PS-2, HmIP-SMO-A2
The Homematic devices remain connected to the CCU3; Homey simply uses the CCU3 to control these devices. This means you can control the devices simultaneously using both the original Homematic app and the Homey smartphone app.
Honestly, if your starting point is Homematic IP, like mine, since the majority of my smart home is built around it, there’s currently no real alternative to Home Assistant. Homey would also be my platform of choice, but at the moment there is no Homematic IP app for it outside of the CCU ecosystem and it is not longer actively maintained. The HCU and the Homematic IP Access Point are clearly the devices eQ-3 is focusing on and I would most likely prioritize in the event of an official Homey integration.
The old CCU-supported Homey app will probably still work with the components that were already supported back then. Personally, however, I would not rely on an app that is no longer being maintained and has not seen active development for years. In contrast, the Home Assistant integration is being actively developed for the CCU, the Access Point, and now also the HCU.
Of course, it also depends on which Homematic components you have and whether the old, no-longer-maintained Homey app already supports them. If it does, I might lean toward Homey. But in your case, that does not seem to be the case.
I wish it were the other way around as well, but for now, it simply seems logical to start with Home Assistant, at least until eQ-3 officially supports Homey via a certified plugin. And even if that happens, it will most likely only support the HCU, since it is the only device that supports plugins.
PS: I even tried integrating the Homematic devices (that were already connected to Home Assistant via a fairly stable integration) into Homey using one of the Home Assistant apps for Homey. Even though it works, it’s still a makeshift solution
In my opinion, it’s simply more honest to answer this way and not let you run into frustration, even though I really think Homey is great. However, in a Homematic setup like your smart home, it just doesn’t make sense yet. That doesn’t mean you shouldn’t check back here later, though. Maybe something will change on eQ3’s side, and Abe did mention that they’re working on an app, although that would only be for the HCU, if the app ever gets released.
The Homematic HCU isn’t exactly cheap either, so for now your money is probably better spent on a HCU to at least have a chance of using a Homey app in the future. There’s also Homey Self-Hosted solution, which could become interesting for you down the line if things develop further, as it wouldn’t require additional hardware.
Hello, I am using HomeMatic app for Homey and it works great for my sensors (40 window contacts). However, I have a HmIP-DLD (Door Lock Drive) which is not being detected/supported. Could you please consider adding support for this device? I am happy to provide device logs or testing if needed.
OpenCCU Local is my fork of the original homey-matic app. I have adapted and extended it for local integration between OpenCCU and Homey Pro. Credit goes to the original developers and contributors; the project remains open source under the MIT license.
Key changes compared with the original version:
Modernized for Homey Apps SDK v3 with a TypeScript foundation.
Direct local communication without requiring MQTT, CCU-Jack or RedMatic.
Expanded Homematic IP support, including selected Wired devices and heating groups.
Flow integration for OpenCCU programs and system variables, plus system widgets.
Improved device discovery, reconnection handling and sanitized diagnostics.
Missing your device in the list? If no matching device or family entry is available, try “Generic OpenCCU device” when adding it. Available features depend on the datapoints the app can detect and map; full functionality is not guaranteed.
The app is under active development, and some device models still need testing on real hardware.
Thank you very much for your effort. It’s really great to finally see some progress being made here.
Unfortunately, I think a lot of people here are actually looking for a solution for the HCU, or even the Access Point, if that is possible at all. Personally, I never really got comfortable with the CCU interface.
Would it also be possible to adapt the solution for the HCU? As far as I understand it, the new plugin strategy for the HCU is intended to continue supporting unofficial developer plugins alongside certified plugins.
Users who have already been using developer plugins, for example the Home Assistant plugin, already have developer mode enabled on their HCU anyway.
Thanks a lot for the information. I saw that yesterday as well. I reached out to eQ-3 via Instagram, and they gave me a rather vague and carefully worded response. However, it did seem to suggest that some communication or initial contact has already taken place between Athom and eQ3.
That said, eQ-3 has been extremely closed off in recent years. They have also been reluctant to support technologies such as Matter, and mDNS, which would be required for things like the full support for the HomeKit plugin for the HCU, is still blocked. You can read more about all of this here. When you ask they do not answer.
Personally, I believe that even if there are discussions or contacts taking place, eQ-3 will continue to prioritize its own strategy rather than putting the interests and needs of its customers first. That said, they do offer great products, which is one of the reasons I’m still with them. The other reason is the community.
Over the past few years, most of the real progress has come from the community, such as the Home Assistant plugin for the HCU. eQ-3 itself has done very little to support these efforts so far.
I therefore have serious doubts about which certified plugins will actually be approved for the HCU. I’m sure eQ-3 will want to retain a significant degree of control over that process. So once again, I’m hoping that someone from the community will step up and make it happen, just as the community has done so many times before.
Supported: HmIP-FALMOT-C12, HmIP-RC8
Not supported: HmIP-SWDM-2, HmIP-WTH-2, HmIP-eTRV-2I9F, HmIP-SWSD-2, HmIP-PS-2, HmIP-SMO-A2
