HomeAssistant and HomeMatic IP - do I need the CCU or can I use it directly with RasbPi / HA?

I would and will define the profiles in the thermostats via ccu, because they are running on the thermostats, even without CCU or HA.

And in HA I switch then from auto (which uses the profiles above) to manual or off and set temperatures in manual mode via HA if needed whenever.

Yeah, I also found a service to activate vacation mode with a set end date. So I created a date helper to input my vacation return date before activating vacation mode. Can then also use this for other automations. So I’m pretty satisfied.

Hi Daniel,
Hi All,

may I ask you for your assistance?
I’m trying hard to switch to cloud-less HomeMatic-IP setup, but unfortunately I got stuck at the very beginning.

This is my config:
Version: core-2021.12.0, Installation Type:Home Assistant OS

USB-Stick: HmIP-RFUSB from Magenta Smarthome Version

dmesg:

[43470.813526] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[43470.918701] usb 1-1.1: New USB device found, idVendor=1b1f, idProduct=c020, bcdDevice= 1.00
[43470.918723] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[43470.918737] usb 1-1.1: Product: eQ-3 HmIP-RFUSB
[43470.918751] usb 1-1.1: Manufacturer: Silicon Labs
[43470.918764] usb 1-1.1: SerialNumber: 3014F5AC9400041D89927047
[43470.947781] usbcore: registered new interface driver cp210x
[43470.947873] usbserial: USB Serial support registered for cp210x
[43470.957432] cp210x 1-1.1:1.0: cp210x converter detected
[43470.964374] usb 1-1.1: cp210x converter now attached to ttyUSB1

Addon: HomeMatic CCU Current version: 11.3.0
Config:

hmip:
  - type: HMIP_CCU2
    device: /dev/ttyUSB1
hmip_enable: true
rf: []
rf_enable: false
wired: []
wired_enable: false

and network config is left untouched

Network	Container	Host				Description
2000/tcp	Disabled		HomematicWire	xmlrpc (Extern)
2001/tcp	Disabled		Homematic		xmlrpc (Extern)
2010/tcp	Disabled		HomematicIP		xmlrpc (Extern)
80/tcp	Disabled		ReGaHss Webinterface (Not required for Ingress)

I can start the web interface of CCU, but I cannot Teach-In any new device. I’ve got a new thermostat - HmIP eTRV-2. I tried to use homematic-manager, but it cannot connect to ccu. I scanned the open ports on my main HA address, there are only 22, 53, 5050 and 8086 from other services.

In the Addon log everything look fine:

[43470.813526] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[43470.918701] usb 1-1.1: New USB device found, idVendor=1b1f, idProduct=c020, bcdDevice= 1.00
[43470.918723] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[43470.918737] usb 1-1.1: Product: eQ-3 HmIP-RFUSB
[43470.918751] usb 1-1.1: Manufacturer: Silicon Labs
[43470.918764] usb 1-1.1: SerialNumber: 3014F5AC9400041D89927047
[43470.947781] usbcore: registered new interface driver cp210x
[43470.947873] usbserial: USB Serial support registered for cp210x
[43470.957432] cp210x 1-1.1:1.0: cp210x converter detected
[43470.964374] usb 1-1.1: cp210x converter now attached to ttyUSB1

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] certs.sh: executing... 
[cont-init.d] certs.sh: exited 0.
[cont-init.d] env.sh: executing... 
[cont-init.d] env.sh: exited 0.
[cont-init.d] hm_ip.sh: executing... 
[19:33:45] INFO: Setup HmIP-RF
[DEBUG] Start bootloader ...
[DEBUG] Bootloader running
[DEBUG] Request bootloader version ...
[INFO] SGTIN = 3014F5AC9400041D89927047
[INFO] Performing update with firmware file '/firmware/HmIP-RFUSB/hmip_coprocessor_update-2.8.6.eq3' ...
[DEBUG] Start application ...
[DEBUG] Application 'DualCoPro_App' running
[DEBUG] Request application version ...
[DEBUG] Request application version ...
[INFO] Updating coprocessor from version 4.2.14 to version 2.8.6
[DEBUG] Start bootloader ...
[DEBUG] Bootloader running
[INFO] Entering bootloader ...
[DEBUG] Start bootloader ...
[DEBUG] Already in Bootloader.
[DEBUG] Request bootloader version ...
[INFO] Bootloader version: 1.0.24
[DEBUG] Send update frames ...
[ERROR] No update performed.
[INFO] Exiting update tool.
[19:33:50] ERROR: HmIP update 2.8.6 fails!
[cont-init.d] hm_ip.sh: exited 0.
[cont-init.d] hm_rfd.sh: executing... 
[cont-init.d] hm_rfd.sh: exited 0.
[cont-init.d] hm_wired.sh: executing... 
...
...
...
2021-12-14 19:34:06,236 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: Checking all devices on all accesspoints for updates
2021-12-14 19:34:06,237 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: There are 0 APs queued with updatable devices (RF)
2021-12-14 19:34:06,238 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: There are 0 APs queued with updatable devices (WIRED)
2021-12-14 19:34:06,286 [INFO] LegacyAPIWorker - SYSTEM: LegacyAPIWorker Verticle or Worker started
2021-12-14 19:34:06,287 [INFO] VertxManager - SYSTEM: start of LegacyAPIWorker succeeded (f68f23e3-72a0-4081-aec9-41e6fb420f77)
172.30.32.2 - - [14/Dec/2021:19:34:06 +0100] "POST /api/homematic.cgi HTTP/1.1" 200 171 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
172.30.32.2 - - [14/Dec/2021:19:34:07 +0100] "POST /esp/system.htm?sid=@2k625zcGlD@&action=UpdateUI HTTP/1.1" 503 3488 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
2021-12-14 19:34:07,757 [INFO] LegacyInitializion - SYSTEM: LegacyInitializion Verticle or Worker started
2021-12-14 19:34:07,759 [INFO] VertxManager - SYSTEM: start of LegacyInitializion succeeded (c6de04b0-fc27-4aff-9b9c-4cab62a3b1d3)
2021-12-14 19:34:07,785 [INFO] VertxManager - SYSTEM: initial deployment complete 

From the debug logs related to

2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic.connection] HMConnection: Creating server object
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.__init__
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] createProxies: Creating proxies
2021-12-14 19:11:36 INFO (SyncWorker_2) [pyhomematic._hm] Creating proxy rf. Connecting to core-homematic:2001
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2021-12-14 19:11:36 INFO (SyncWorker_2) [pyhomematic._hm] Creating proxy wired. Connecting to core-homematic:2000
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2021-12-14 19:11:36 INFO (SyncWorker_2) [pyhomematic._hm] Creating proxy hmip. Connecting to core-homematic:2010
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2021-12-14 19:11:36 INFO (SyncWorker_2) [pyhomematic._hm] Creating proxy group. Connecting to core-homematic:9292/groups
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.__init__
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-rf
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-wired
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-hmip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-group
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.__init__: Setting up server
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.__init__: Registering RPC functions
2021-12-14 19:11:36 INFO (Thread-3) [pyhomematic._hm] Starting server at http://0.0.0.0:36985
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:36985', 'homeassistant-rf')
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2021-12-14 19:11:36 WARNING (SyncWorker_2) [pyhomematic._hm] Failed to initialize proxy for homeassistant-rf
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:36985', 'homeassistant-wired')
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2021-12-14 19:11:36 WARNING (SyncWorker_2) [pyhomematic._hm] Failed to initialize proxy for homeassistant-wired
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:36985', 'homeassistant-hmip')

and then many many entries like this:

2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.newDevices: interface_id = homeassistant-hmip, dev_descriptions = [{'TYPE': 'HmIP-RCV-50', 'SUBTYPE': 'RCV50', 'ADDRESS': 'HmIP-RCV-1', 'RF_ADDRESS': 11776343, 'CHILDREN': ['HmIP-RCV-1:0', 'HmIP-RCV-1:1', 'HmIP-RCV-1:2', 'HmIP-RCV-1:3', 'HmIP-RCV-1:4', 'HmIP-RCV-1:5', 'HmIP-RCV-1:6', 'HmIP-RCV-1:7', 'HmIP-RCV-1:8', 'HmIP-RCV-1:9', 'HmIP-RCV-1:10', 'HmIP-RCV-1:11', 'HmIP-RCV-1:12', 'HmIP-RCV-1:13', 'HmIP-RCV-1:14', 'HmIP-RCV-1:15', 'HmIP-RCV-1:16', 'HmIP-RCV-1:17', 'HmIP-RCV-1:18', 'HmIP-RCV-1:19', 'HmIP-RCV-1:20', 'HmIP-RCV-1:21', 'HmIP-RCV-1:22', 'HmIP-RCV-1:23', 'HmIP-RCV-1:24', 'HmIP-RCV-1:25', 'HmIP-RCV-1:26', 'HmIP-RCV-1:27', 'HmIP-RCV-1:28', 'HmIP-RCV-1:29', 'HmIP-RCV-1:30', 'HmIP-RCV-1:31', 'HmIP-RCV-1:32', 'HmIP-RCV-1:33', 'HmIP-RCV-1:34', 'HmIP-RCV-1:35', 'HmIP-RCV-1:36', 'HmIP-RCV-1:37', 'HmIP-RCV-1:38', 'HmIP-RCV-1:39', 'HmIP-RCV-1:40', 'HmIP-RCV-1:41', 'HmIP-RCV-1:42', 'HmIP-RCV-1:43', 'HmIP-RCV-1:44', 'HmIP-RCV-1:45', 'HmIP-RCV-1:46', 'HmIP-RCV-1:47', 'HmIP-RCV-1:48', 'HmIP-RCV-1:49', 'HmIP-RCV-1:50', ''], 'PARENT': '', 'PARENT_TYPE': '', 'INDEX': 0, 'AES_ACTIVE': 1, 'PARAMSETS': ['MASTER'], 'FIRMWARE': '1.0.0', 'AVAILABLE_FIRMWARE': '0.0.0', 'UPDATABLE': False, 'FIRMWARE_UPDATE_STATE': 'UP_TO_DATE', 'VERSION': 1, 'FLAGS': 9, 'LINK_SOURCE_ROLES': '', 'LINK_TARGET_ROLES': '', 'DIRECTION': 0, 'GROUP': '', 'TEAM': '', 'TEAM_TAG': '', 'TEAM_CHANNELS': [], 'INTERFACE': '', 'ROAMING': 0, 'RX_MODE': 1}, {'TYPE': 'MAINTENANCE', 'SUBTYPE': '', 'ADDRESS': 'HmIP-RCV-1:0', 'RF_ADDRESS': 0, 'CHILDREN': [], 'PARENT': 'HmIP-RCV-1', 'PARENT_TYPE': 'HmIP-RCV-50', 'INDEX': 0, 'AES_ACTIVE': 1, 'PARAMSETS': ['MASTER', 'VALUES'], 'FIRMWARE': '1.0.0', 'AVAILABLE_FIRMWARE': '', 'UPDATABLE': False, 'FIRMWARE_UPDATE_STATE': 'UP_TO_DATE', 'VERSION': 1, 'FLAGS': 9, 'LINK_SOURCE_ROLES': '', 'LINK_TARGET_ROLES': '', 'DIRECTION': 0, 'GROUP': '', 'TEAM': '', 'TEAM_TAG': '', 'TEAM_CHANNELS': [ ...................................

and …

2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.createDeviceObjects: iterating interface_id = hmip
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic.devicetypes.generic] HMGeneric.__init__: device_description: HmIP-RCV-1 : {'TYPE': 'HmIP-RCV-50', 'SUBTYPE': 'RCV50', 'ADDRESS': 'HmIP-RCV-1', 'RF_ADDRESS': 11776343, 'CHILDREN': ['HmIP-RCV-1:0', 'HmIP-RCV-1:1', 'HmIP-RCV-1:2', 'HmIP-RCV-1:3', 'HmIP-RCV-1:4', 'HmIP-RCV-1:5', 'HmIP-RCV-1:6', 'HmIP-RCV-1:7', 'HmIP-RCV-1:8', 'HmIP-RCV-1:9', 'HmIP-RCV-1:10', 'HmIP-RCV-1:11', 'HmIP-RCV-1:12', 'HmIP-RCV-1:13', 'HmIP-RCV-1:14', 'HmIP-RCV-1:15', 'HmIP-RCV-1:16', 'HmIP-RCV-1:17', 'HmIP-RCV-1:18', 'HmIP-RCV-1:19', 'HmIP-RCV-1:20', 'HmIP-RCV-1:21', 'HmIP-RCV-1:22', 'HmIP-RCV-1:23', 'HmIP-RCV-1:24', 'HmIP-RCV-1:25', 'HmIP-RCV-1:26', 'HmIP-RCV-1:27', 'HmIP-RCV-1:28', 'HmIP-RCV-1:29', 'HmIP-RCV-1:30', 'HmIP-RCV-1:31', 'HmIP-RCV-1:32', 'HmIP-RCV-1:33', 'HmIP-RCV-1:34', 'HmIP-RCV-1:35', 'HmIP-RCV-1:36', 'HmIP-RCV-1:37', 'HmIP-RCV-1:38', 'HmIP-RCV-1:39', 'HmIP-RCV-1:40', 'HmIP-RCV-1:41', 'HmIP-RCV-1:42', 'HmIP-RCV-1:43', 'HmIP-RCV-1:44', 'HmIP-RCV-1:45', 'HmIP-RCV-1:46', 'HmIP-RCV-1:47', 'HmIP-RCV-1:48', 'HmIP-RCV-1:49', 'HmIP-RCV-1:50', ''], 'PARENT': '', 'PARENT_TYPE': '', 'INDEX': 0, 'AES_ACTIVE': 1, 'PARAMSETS': ['MASTER'], 'FIRMWARE': '1.0.0', 'AVAILABLE_FIRMWARE': '0.0.0', 'UPDATABLE': False, 'FIRMWARE_UPDATE_STATE': 'UP_TO_DATE', 'VERSION': 1, 'FLAGS': 9, 'LINK_SOURCE_ROLES': '', 'LINK_TARGET_ROLES': '', 'DIRECTION': 0, 'GROUP': '', 'TEAM': '', 'TEAM_TAG': '', 'TEAM_CHANNELS': [], 'INTERFACE': '', 'ROAMING': 0, 'RX_MODE': 1}
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.createDeviceObjects: created HmIP-RCV-1 as SUPPORTED device for HmIP-RCV-50
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.createDeviceObjects: adding to self.devices_all
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic._hm] RPCFunctions.createDeviceObjects: adding to self.devices
2021-12-14 19:11:36 DEBUG (SyncWorker_2) [pyhomematic.devicetypes.generic] HMGeneric.__init__: device_description: HmIP-RCV-1:0 : {'TYPE': 'MAINTENANCE', 'SUBTYPE

The Teach-In Process has found one device HmIP-RC V-50, which I do not have and cannot even delete.

I cannot however connect the new thermostat. When I try to do it over cloud-system, which I use for the rest of my homematic devices it appears in the mobile app within a second. I ignore it and do not connect.

Due to the potential disconnection from cloud (ongoing warning for the HomeMatic Cloud Integration) I have to migrate to offline version.

Any idea would be very much appreciated.

Thanks!

Which dongle are you referring to? HmIP-RFUSB or the Telekom SmartHome one for example? The add-on 530 you are referring to is claimed to be deprecated referring to the RaspberryMatic CCU add-on replacing it. Does this replacement also support the dongles or just real CCUs?

Apart from being limited to Homematic IP actors, does the dongle have any disadvantages over a CCU? For example, what about the bi-directional communication? Does it also apply to the dongle solution?

Thanks!

1 Like