Then you misunderstood something or received incorrect information. The API for the Homematic IP Access Point is not identical to the Connect API for the Homematic IP Home Control Unit.
The statement you quoted from SukramJ on another forum is simply false. To communicate with the Homematic IP Home Control Unit, it requires the Connect API released by eQ-3 and either a remote plugin or an installed plugin.
The problem, or rather the challenge, is not to write a remote plugin or an installed plugin based on the documentation provided by eQ-3 for the Connect API.
The problem is that a normal user would also have to activate developer mode to even be able to use or install such a plugin. This would then result in the loss of support from the manufacturer eQ-3 for the Homematic IP Home Control Unit.
It is therefore essential for a manufacturer like Athom that the plugin is a certified one, meaning it must be approved by eQ-3. Only if the plugin is certified does the user not need to activate developer mode.
So it’s up to the manufacturer eQ-3, and as announced here in the past, they must ensure that plugins created by other cooperation partners are also certified by eQ-3 and listed as certified plugins. Only then can you install it normally as a user without being forced to activate developer mode yourself and thereby losing support.
eQ-3 Announcement (24.10.2024):
”In the next expansion phase, eQ-3 plans to release officially certified plug-ins that have been tested for functionality and safety. The company will announce further information at a later date.”
So you as a user and other manufacturers like Athom have no choice but to wait until eQ-3 enters this phase and allows certified plugins, which you can then use as an end user of such a system.
