Basic homematic configuration

Configuration
1

Hi all,

I’m new to HA but have some experience in Homematic (CCU2).
I just discovered HA yesterday and had to install immediately since it looked very promising.
My problem now is how to initially configure a regular CCU2 (a real one, not on Raspberry Pi). The entries I found here do not really fit my needs since the config seems to have a different structure now. Can anyone please give me a very asic instruction how (and where) to configure the CCU2-access? And then how to access the items connected to my CCU2 (mainly heating and temperature control + window sensor)

Thank you in advance!

Carsten

2

Did you check out the documentation?

Did you already try to configure something yourself? If so, please show your non-working config.

3

Yes, I did check the documentation and to be honest it does not help me.
I just cannot figure out where I have to enter what to get the add-on to work (there is the /config/configuration.yaml as well as an config part in each add-on, I know that; but I do not know how to fill them correctly)
I also have Tradfri-equipment which worked immediately, my tasmota-flashed devices do not show as well.
I’m coming from Openhab which is extremely complex and hoped that HA would be a biti simpler but at the moment I’m a bit in doubt.
I’m pretty sure that it actually is only a tiny little bit that I’m missing, so I’m ver sure that someone can give me the correct hint as where to start.
Thank you so far as well as coming answers!

Carsten

4

You need to enter the config in configuration.yaml and it should look somethi g like the example on the docs page https://www.home-assistant.io/integrations/homematic/#example-configuration-with-multiple-protocols-and-some-other-options-set

1 Like
5

Hi,
this is my configuration.yaml now based on the docs:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

homematic:
  interfaces:
    rf:
      host: 192.168.178.31
      resolvenames: json
      username: carsten
      password: 123456
    wired:
      host: 192.168.178.31
      port: 2000
      resolvenames: json
      username: carsten
      password: 123456
    ip:
      host: 192.168.178.31
      port: 2010
    groups:
      host: 192.168.178.31
      port: 9292
      resolvenames: json
      username: carsten
      password: 123456
      path: /groups
  hosts:
    ccu2:
      host: 192.168.178.31
      username: carsten
      password: 123456

What do I need to enter on the add-on config section?
And how do I see my devices now?

6

The configuration you have already seems fine. What add-on are you talking about? Are you using hassio? I think there might be some confusion.
There is an add-on for hassio which turns your system into a CCU (which requires the hardware like the pi-based solutions have). But as long as you are using your existing CCU all you need is the config you have posted above and restart Home Assistant. You should then see the devices in the Home Assistant UI. If not, there could be helpful information in the Home Assistant logs.

2 Likes
7

Now thank you both!
I had my breakthrough with Homematic and found all my devices. Thanks to this I think I now have a better understanding of the docs and will be able to also install my wemo-devices.

Carsten

1 Like
8

Hello to all,

it is not very helpful when a thread finished without to inform what was the solution exactly in this case :frowning:

I am at the moment are confronted with the same situation.
So I have one Raspi as an Rasbian-Homematic. A second Raspi I installed HomeAssistant OS. Now I try to get the device information from the Homatic to the Homeassistant, but without success.

What was I doing until now:
On Homematic side the firewall configuration following ports are Free.
22;
80;
443;
2000;
2001;
2010;
9292;
42000;
42001;
42010;
49292
I think I don’t need all, but at first better is better :slight_smile:
-XML-RPC API
-Script API
-Mediola access
have all full access. I think Mediola is not neccercary, but better is better :slight_smile:
IP address from the HA-Raspi is defined.

in the HA-Raspi I was changing the configuration.yaml in different variants. This means the values with and without quotations mark. I get in both cases no error notification in the logfiles! (unbelieveable)
The only warning is, the …“Setup of homematic is taking over 10 seconds.”
I was working exactly by follow the instruction from the HA and I use the example configuration from there, but I use of course my datas like IP address, name and passwords.

In the section hosts, like

hosts:
    ccu2:
      host: 127.0.0.1
      port: 2001
      username: "Admin"
      password: "secret"

When I use the host name ccu2 (or ccu3) I get every time a error. So until now I comment it out by using the #. I think this is not the rigth way, or is the description in the integration site wrong?

I hope some one can help me.

Regards Uwe

9

Then where’s you interfaces section of the configuration? The hosts section only provides the hub-entity, which containes the system-variables of HomeMatic. To get the devices, you have add an entry for each protocol (HomeMatic classic, wired, IP, whetever you have) in the interfaces section.

10

Hello danielperna84 and thank you very much for your answer!

Yes of course is my configuration.yaml longer.
Here my actual, but also not working Homatic section configuration. Please watch for the # sign to uncomment ccu3. When I remove it, then a error message appears.

homematic:
  interfaces:
    rf:
          host: 192.168.178.29
          resolvenames: "json"
          username: "hass-gast"
          password: "secret"
    groups:
          host: 192.168.178.29
          port: 9292
          resolvenames: "json"
          username: "hass-gast"
          password: "secret"
          path: /groups
    hosts:
#      ccu3:
          host: 192.168.178.29
          port: 2001
          username: "hass-gast"
          password: "secret"

When I remove the # before ccu3 appears following error message.

Invalid config for [homematic]: [ccu3] is an invalid option for [homematic]. Check: homematic->homematic->interfaces->hosts->ccu3. (See /config/configuration.yaml, line 14). Please check the docs at Homematic - Home Assistant

regards Uwe

12

You can’t just comment out that one line and leave the following ones there. That’s a syntax error.

You also have the hosts-part nested within the interfaces. That’s not how it should be.

And finally: 2001 is most likely not the correct port in the hosts section. If you haven’t set a port yourself on your CCU, don’t configure one here.

Anyways, from the data you have provided you configuration should look like this:

homematic:
  interfaces:
    rf:
      host: 192.168.178.29
      resolvenames: "json"
      username: "hass-gast"
      password: "secret"
    groups:
      host: 192.168.178.29
      port: 9292
      resolvenames: "json"
      username: "hass-gast"
      password: "secret"
      path: "/groups"
  hosts:
    ccu3:
      host: 192.168.178.29
      username: "hass-gast"
      password: "secret"
13

danielperna84 thanks for your answer.
I was using the example configuration from the Home Assistant page. And there is in the hosts section also the port 2001 declared.
But now I was trying your configuration suggestion without port 2001 and it works also not.
the error message as follows:

2021-05-09 22:35:16 ERROR (MainThread) [homeassistant.config] Invalid config for [homematic]: [ccu3] is an invalid option for [homematic]. Check: homematic->homematic->interfaces->hosts->ccu3. (See /config/configuration.yaml, line 14). Please check the docs at Homematic - Home Assistant
2021-05-09 22:35:16 ERROR (MainThread) [homeassistant.setup] Setup failed for homematic: Invalid config.

By the way by line 14 starts the homematic block with homematic:

I have no idea what can I do.

regards Uwe

14

You’re right regarding the docs mentioning port 2001 there. I was mixing things up. Still, as you don’t seem to be using HomeMatic IP devices (in that case the documentation tells you to use port 2010), 2001 (the default) should be working. Hence you still don’t need it in your configuration.

That being said, the error message you have posted indicates, that you have not exactly used the configuration I have posted for you. Indentation - the whitespace on each line before the keywords start - is very important. In the configuration you have posted hosts is on the same level as rf and groups. That’s why I have fixed your configuration how it should be.

So please copy it, and don’t do anything to it besides setting the correct username / password. It has to look exactly like I have posted it.

15

Hello danielperna84,

thank you very much for the hint. Yes you are to be right the indentation was the reason for the ccu3-error!
Now the Homematic appears in the GUI, but without devices. :frowning:
Today I was updating the Homematic from version 3.53.30 to 3.57.5 but it was not helpful. The same result in the HA-GUI.
Big Questionmarks and why?

regards Uwe

16

i can see the CCU3 but no devices.
Can someone give me a hint?
Here my actual HA configuration depend to the Homematic:

homematic:
    interfaces:
        rf:
            host: 192.168.178.29
            resolvenames: "json"
            username: "hass-gast"
            password: "secret"

        groups:
            host: 192.168.178.29
            port: 9292
            resolvenames: "json"
            username: "hass-gast"
            password: "secret"
            path: /groups
    hosts:
        ccu3:
            host: 192.168.178.29
            username: "hass-gast"
            password: "secret"

I was also trying to open all ports inside the Homematic, but no devices appears.
My Homematic devices are at the moment heating thermostates and door- and window switches.
Has someone experience?

Bildschirmfoto vom 2021-05-22 14-23-08

17

As I have mentioned above, you have to add port 2010 (to the rf block) for homematic IP devices in case you are using those.

18

late but better now.
It works with the port information!

19

Meanwhile a new integration for Homematic has been developed, which is available as a custom component. I highly recommend to switch to this.