Homematic CCU3 not connecting

Configuration
1

Hi all,

so it turns out I’m slightly too dumb to figure out how to connect my new Homematic CCU3 with HA. Home Assistant 0.82.1 on hass.io on a RPi3, and my various ZigBee/Sonos bits are fine. The CCU3 is running the latest 3.41.11 firmware.

My HA setup runs on 192.168.2.60, and the CCU3 resolves to 192.168.2.137.

My configuration looks like this:

homematic:
  interfaces:
    ip: 
      host: 192.168.2.137
      port: 2000
      resolvenames: json
      username: ha
      password: xxx
  hosts:
    ccu3:
      host: 192.168.2.137
      username: ha
      password: xxx

(The password is obviously edited.)

Unfortunately, the HA logs are not quite so enlightening:

2018-11-18 16:55:49 INFO (MainThread) [homeassistant.loader] Loaded homematic from homeassistant.components.homematic
2018-11-18 16:55:49 INFO (MainThread) [homeassistant.setup] Setting up homematic
2018-11-18 16:55:49 INFO (SyncWorker_3) [pyhomematic._hm] Creating proxy ip. Connecting to http://192.168.2.137:2000
2018-11-18 16:55:49 INFO (SyncWorker_3) [pyhomematic._hm] Creating proxy ccu3. Connecting to http://192.168.2.137:2001
2018-11-18 16:55:49 INFO (Thread-2) [pyhomematic._hm] Starting server at http://0.0.0.0:39615
2018-11-18 16:55:49 WARNING (SyncWorker_3) [pyhomematic._hm] Failed to initialize proxy

What I’ve tried:

  • Using the “Admin” user on the CCU3 instead of the “ha” guest. No change.
  • Checked that the ports on the CCU3 are open - I can connect to the 2001/2010/80/2000 ports on the IP.
  • When I connect to via a browser, I do get prompted for credentials and get an empty response.
  • I’ve tried using local_ip, local_port, callback_ip to see if maybe it was being confused by the HASS.IO setup (I found those parameters elsewhere), but that didn’t change anything.
  • I have a HM-LC-Dim1T-CV connected to the CCU3 which I can control via the CCU3, so there should be at least one light to retrieve, so it’s also not being confused by an empty list.
  • That light has also been assigned a shortname.
  • Triggering “homematic.reconnect” makes no difference either.
  • Tried the other ports (2000, 2001, 2010, 9292) with no change.

I’m a bit at a loss. I’d appreciate help, because I’d love to benefit from the choice of Homematic devices!

Thanks in advance.

2

Your configuration should more look like this:

homematic:
  interface:
    ip:
      host: 192.168.2.137
      port: 2010
      resolvenames: json
      username: ha
      password: xxx
    rf:
      host: 192.168.2.137
      port: 2001
      resolvenames: json
      username: ha
      password: xxx
  hosts:
    ccu3:
      host: 192.168.2.137
      username: ha
      password: xxx

That being said, the CCU3 supports authentication for the XML-RPC API. The library Home Assistant is using to communicate does not support authentication yet though. And also we don’t yet support SSL. So if one of those two is enabled on your CCU3, then you have to turn it off until we have added support. There’s an open Pull Request to handle authentication, but it has not been merged yet and is therefore not available for your installation.

Hope this helps.

3

That being said, the CCU3 supports authentication for the XML-RPC API.

Woho. You are indeed correct! That’s the bit of knowledge I missed. I had assumed that with all the username/password in the configuration, leaving the authentication on (which is the CCU default) was needed. But indeed, now the connection is established and I can dim my lights.

Thanks so much!