Homematic (HMIP-RFUSB): no devices found after switch to RaspberryMatic

Configuration
1

Hi there,

I recently switched from HomeMatic CCU add-on to RaspberryMatic following the official guide.

Now Homematic does not work anymore. I tried to restore the sbk-backup file. Despite message “System backup has been imported successfully” the device list stays empty after restart. The hardware (HMIP-RFUSB) worked fine all the time, so I am rather certain that its a software issue.

The log shows following error which might be related:

Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.16, ERROR ( != 4.4.16)

Here is the full log:

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying onboard hardware: oci, OK
Initializing RTC Clock: no hardware found
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.4, OK
Identifying Homematic RF-Hardware: ...HmRF: none, HmIP: none, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.16, ERROR ( != 4.4.16)
Identifying Homematic RF-Hardware: ...HmRF: none, HmIP: none, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: not required
Starting rfd: no BidCos-RF hardware found
Starting HMIPServer: .........OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK

P.S. : I tried to use a backup to restore the previous HA state but it seems a “full” HA backup is not enough since it does not cover the OS and also not the add-ons from the store. So I didn’t get the old Homematic CCU add-on back nor the old device (its still /dev/raw-art).

Hope someone can help.

2

I think you will receive better support in the RaspberryMatic section of the HomeMatic Forum. I believe there was someone with a similar problem over there.

3

Ok, will check it out. Thanks for the hint.

4

After reading https://github.com/jens-maus/RaspberryMatic/issues/1707, I tried with the nighty build aka “RaspberryMatic (snapshot)” version (3.61.7.20220212-be487fa). With this, I could import my backup and got all my devices back.

Instead of

Identifying Homematic RF-Hardware: ...HmRF: none, HmIP: none, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.16, ERROR ( != 4.4.16)
Identifying Homematic RF-Hardware: ...HmRF: none, HmIP: none, OK

the log now says:

Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.4, OK
Identifying Homematic RF-Hardware: ....HmRF: HMIP-RFUSB/eQ-3 [email protected], HmIP: HMIP-RFUSB/eQ-3 [email protected], OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.4.16, not necessary, OK

One big step further! :slight_smile:
However, HA could not get any devices from RaspberryMatic:

Here is the log with debug output enabled and my YAML config.
Any ideas?

2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic.connection] HMConnection: Creating server object
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.__init__
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] createProxies: Creating proxies
2022-02-13 23:26:14 INFO (SyncWorker_0) [pyhomematic._hm] Creating proxy rf. Connecting to de838cd8-raspberrymatic-dev:2001
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2022-02-13 23:26:14 INFO (SyncWorker_0) [pyhomematic._hm] Creating proxy wired. Connecting to de838cd8-raspberrymatic-dev:2000
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2022-02-13 23:26:14 INFO (SyncWorker_0) [pyhomematic._hm] Creating proxy hmip. Connecting to de838cd8-raspberrymatic-dev:2010
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2022-02-13 23:26:14 INFO (SyncWorker_0) [pyhomematic._hm] Creating proxy groups. Connecting to de838cd8-raspberrymatic-dev:9292/groups
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2022-02-13 23:26:14 INFO (SyncWorker_0) [pyhomematic._hm] Creating proxy raspberrymatic. Connecting to de838cd8-raspberrymatic-dev:2001
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Getting local ip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] LockingServerProxy.__init__: Got local ip 172.30.32.1
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-rf
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-wired
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-hmip
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-groups
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] RPCFunctions.__init__: iterating proxy = homeassistant-raspberrymatic
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.__init__: Setting up server
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.__init__: Registering RPC functions
2022-02-13 23:26:14 INFO (Thread-3) [pyhomematic._hm] Starting server at http://10.0.10.8:43359
2022-02-13 23:26:14 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:43359', 'homeassistant-rf')
2022-02-13 23:26:15 DEBUG (SyncWorker_0) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2022-02-13 23:26:15 WARNING (SyncWorker_0) [pyhomematic._hm] Failed to initialize proxy for homeassistant-rf
2022-02-13 23:26:15 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:43359', 'homeassistant-wired')
2022-02-13 23:26:16 DEBUG (SyncWorker_0) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2022-02-13 23:26:16 WARNING (SyncWorker_0) [pyhomematic._hm] Failed to initialize proxy for homeassistant-wired
2022-02-13 23:26:16 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:43359', 'homeassistant-hmip')
2022-02-13 23:26:17 DEBUG (SyncWorker_0) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2022-02-13 23:26:17 WARNING (SyncWorker_0) [pyhomematic._hm] Failed to initialize proxy for homeassistant-hmip
2022-02-13 23:26:17 DEBUG (SyncWorker_0) [pyhomematic._hm] ServerThread.proxyInit: init('http://172.30.32.1:43359', 'homeassistant-groups')
2022-02-13 23:26:18 DEBUG (SyncWorker_0) [pyhomematic._hm] proxyInit: Exception: [Errno 111] Connection refused
2022-02-13 23:26:18 WARNING (SyncWorker_0) [pyhomematic._hm] Failed to initialize proxy for homeassistant-groups
2022-02-13 23:26:18 INFO (SyncWorker_0) [pyhomematic._hm] Skipping init for homeassistant-raspberrymatic
2022-02-13 23:26:20 DEBUG (SyncWorker_6) [pyhomematic._hm] ServerThread.getAllSystemVariables: Getting all System variables via JSON-RPC
2022-02-13 23:26:20 DEBUG (SyncWorker_6) [pyhomematic._hm] RPCFunctions.jsonRpcPost: Method: Session.login
2022-02-13 23:26:20 DEBUG (SyncWorker_6) [pyhomematic._hm] RPCFunctions.jsonRpcPost: API-Endpoint: http://de838cd8-raspberrymatic-dev:80/api/homematic.cgi

  local_ip: 10.0.10.8
  interfaces:
    rf:
      host: de838cd8-raspberrymatic-dev
      port: 2001
      resolvenames: json
      username: Admin
      password: xxx
    wired:
      host: de838cd8-raspberrymatic-dev
      port: 2000
      resolvenames: json
      username: Admin
      password: xxx
    hmip:
      host: de838cd8-raspberrymatic-dev
      port: 2010
      resolvenames: json
      username: Admin
      password: xxx
    groups:
      host: de838cd8-raspberrymatic-dev
      port: 9292
      resolvenames: json
      username: Admin
      password: xxx
      path: /groups
  hosts:
    raspberrymatic:
      host: de838cd8-raspberrymatic-dev
      username: Admin
      password: xxx
5

The Connection refused errors indicate, that there is some sort of connectivity issue. Either network or firewall. I don’t know how it is with the RaspberryMatic Add-On out of the box, but I know RaspberryMatic itself has a firewall, and there you have to allow access from Home Assistant. That’s also mentioned in the Docs.

6

Thanks again for pointing me to the right direction. Despite choosing “Relaxed” security setting in the install wizard of RaspberryMatic, the firewall blocked all access (ports and XML-RPC API)
After opening it, HA could find the devices… :slight_smile: :+1: