RaspberryMatic can’t find any of my Homematic IP devices

DokwoN · February 3, 2022, 2:53pm

My problem:

RaspberryMatic can’t find any of my Homematic IP devices.

My setup:

• Raspberry Pi 4 Model B; 4 GB
• Home Assistant OS 7.2
• Addons installed: File editor (5.3.3), RaspberryMatic CCU (3.61.7.20220115)
• Telekom branded Wireless Stick

What I have tried:

Followed Jens Maus’ installation guide ( https://github.com/jens-maus/RaspberryMatic/wiki/Installation-HomeAssistant ) closely except for the last part „Add a home assistant automation to connect to the raspberrymatic addon“, but I believe that this would not prevent RaspberryMatic to discover my Homematic IP devices.

Speaking of Homematic IP: I found out that the Telekom USB-Stick is lacking a firmware update and hence can not communicate with tradional BidCos-RF. However, since all devices I am planning to operate are Homematic IP (door locks and thermostats), this should not be an issue either.

A previous problem that I ran into previously was the length of the USB cable. Since I extended it, RaspberrryMatic can discover the stick and is offering to search for devices. Unfortunately without finding anything.

RaspberryMatic CCU Logs:

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.1, OK
Identifying Homematic RF-Hardware: ....HmRF: none, HmIP: HMIP-RFUSB-TK/USB, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.2.14=>4.4.16, ERROR (4.2.14 != 4.4.16); HMIP-RFUSB-TK: 4.2.14, 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

Supervisor Logs:

22-02-03 15:17:14 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:14 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:14 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:14 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:14 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:20 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:17:21 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:21:01 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-02-03 15:23:47 INFO (MainThread) [supervisor.backups.manager] Found 8 backup files
22-02-03 15:23:47 INFO (MainThread) [supervisor.backups.manager] Found 8 backup files
22-02-03 15:25:13 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:25:13 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:25:13 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:25:13 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:25:13 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-02-03 15:46:01 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete

Config Logs:

[547644701712] Disconnected: Did not receive auth message within 10 seconds
14:16:42 – (WARNUNG) Home Assistant WebSocket API - Die Nachricht ist zum ersten Mal um 14:16:42 aufgetreten und erscheint 2 mal
[0x917F:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
12:23:34 – (WARNUNG) Zigbee Home Automation - Die Nachricht ist zum ersten Mal um 12:23:34 aufgetreten und erscheint 2 mal
Error doing job: Task exception was never retrieved
12:23:12 – (FEHLER) /usr/src/homeassistant/homeassistant/runner.py - Die Nachricht ist zum ersten Mal um 12:23:00 aufgetreten und erscheint 2 mal
Failed to parse broken GeneralFrame(header=CommandHeader(id=0x9F, subsystem=Subsystem.ZDO, type=CommandType.AREQ), data=b'\xAC\x9A\x84\x09\x43') as <class 'zigpy_znp.types.commands.ZDO.ParentAnnceRsp.Callback'>
12:23:12 – (WARNUNG) /usr/local/lib/python3.9/site-packages/zigpy_znp/api.py - Die Nachricht ist zum ersten Mal um 12:23:00 aufgetreten und erscheint 2 mal
Setup of homematic is taking over 10 seconds.
12:22:44 – (WARNUNG) /usr/local/lib/python3.9/asyncio/events.py
Detected integration that accessed discovery_info.__contains__('ssdp_location') instead of discovery_info.upnp.__contains__('ssdp_location') or discovery_info.ssdp_headers.__contains__('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:
12:22:40 – (WARNUNG) helpers/frame.py - Die Nachricht ist zum ersten Mal um 12:22:40 aufgetreten und erscheint 2 mal
Failed to initialize proxy for homeassistant-rf
12:22:34 – (WARNUNG) /usr/local/lib/python3.9/site-packages/pyhomematic/_hm.py - Die Nachricht ist zum ersten Mal um 12:22:34 aufgetreten und erscheint 2 mal

Extract from configuration.yaml:

homematic:
  interfaces:
    rf:
      host: de838cd8-raspberrymatic
      port: 2001
      resolvenames: json
      username: Admin
      password: supersecretpassword
    wired:
      host: de838cd8-raspberrymatic
      port: 2000
      resolvenames: json
      username: Admin
      password: supersecretpassword
    hmip:
      host: de838cd8-raspberrymatic
      port: 2010
      resolvenames: json
      username: Admin
      password: supersecretpassword
    groups:
      host: de838cd8-raspberrymatic
      port: 9292
      resolvenames: json
      username: Admin
      password: supersecretpassword
      path: /groups
  hosts:
    raspberrymatic:
      host: de838cd8-raspberrymatic
      username: Admin
      password: supersecretpassword
      
logger:
  default: debug

Does anyone know what I am missing here?

DokwoN · February 4, 2022, 1:30pm

Update: I ordered a proper RF-USB-Stick and will try if this will be able to detect my Homematic IP devices. Will post here if it works out.

northnorway · February 11, 2022, 12:02pm

I was happy to find this thread, as I am experiencing quite the same Problem, but with the original RF-USB-Stick: Raspberrymatic says “Es wurde keinerlei nutzbares HomeMatic Funkmodul/LAN-Gateway für die
homematic oder homematicIP Kommunikation im System gefunden.” (sorry for German message output; translated to english: No usable Gateway device found). My log file is also quite similar as shown above, especially the log entry

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

is also contained in my log file. As I am not an expert for HomematicIP, I would appreciate any helpful hint!

flux-i · February 11, 2022, 8:20pm

I get the exact same error message

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

It started after I switched from the old HomeMatic CCU add-on to Raspberrymatic.

Hope someone can help.

northnorway · February 11, 2022, 11:47pm

Finally, I found the simple reason for my problem: I forgot to disable protected mode for this addon. Now it´s working perfectly!

oischinger · February 12, 2022, 8:03am

I still have problems connecting any HomeMaticIP device via a HMIP-RFUSB. I guess the protected mode thing is just relevant for GPIO based modules anyway. Does anyone else still have problems?

flux-i · February 18, 2022, 10:43pm

Try installing the nightly build (snapshot version), it solved the problem for me.
Have a look here: https://community.home-assistant.io/t/homematic-hmip-rfusb-no-devices-found-after-switch-to-raspberrymatic/392114/4?u=flux-i
Cheers,
Timo