Nero
19. November 2025 um 15:56
1
Hallo zusammen,
nach Umstellung auf OpenCCU läuft mein Open Thread Border Router nicht mehr.
Nach längere Analyse scheint es so zu sein, das OpenCCU und OTBR sich gegenseitig stören.
Solange OpenCCU läuft, bekomme ich OTBR nicht zum laufen, sobald OpenCCU gestopt ist, läuft OTBR einwandfrei.
SETUP wie folgt:
Proxmox VM
OpenCCU per USB Stick : eQ-3 HmIP-RFUSB
OTBR per USB Stick: Sonoff Zigbee 3.0 USB Dongle Plus
Auszug aus OTBR Log:
[INFO\]-RCP_HOS-: OpenThread log level changed to 5
49d.17:20:48.934 \[D\] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET
49d.17:20:48.934 \[D\] P-SpinelDrive-: Waiting response: key=0
49d.17:20:50.936 \[W\] P-SpinelDrive-: Wait for response timeout
49d.17:20:50.936 \[I\] P-SpinelDrive-: co-processor self reset successfully
49d.17:20:50.936 \[D\] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:20:50.936 \[D\] P-SpinelDrive-: Waiting response: key=1
49d.17:20:52.938 \[W\] P-SpinelDrive-: Wait for response timeout
49d.17:20:52.938 \[D\] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:20:52.938 \[D\] P-SpinelDrive-: Waiting response: key=1
49d.17:20:52.941 \[D\] P-SpinelDrive-: Received spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_IS, key:PROTOCOL_VERSION, major:4, minor:3
49d.17:20:54.939 \[W\] P-SpinelDrive-: Wait for response timeout
49d.17:20:54.939 \[C\] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.17:20:54.940 \[D\] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:20:54.940 \[D\] P-SpinelDrive-: Waiting response: key=1
49d.17:20:56.941 \[W\] P-SpinelDrive-: Wait for response timeout
[16:46:06\] WARNING: otbr-agent exited with code 1 (by signal 0).
Hat jemand ein ähnliches Problem? Konnte bisher im Netz nicht wirklich was finden.
LG
Christian
by HarryP: Code-/Logzeilen formatiert (bitte immer in </> einbinden)
s.a.: (Neues Update & Features - Hier in der Community 🫶 )
Baxxy
19. November 2025 um 16:09
2
Nero:
Proxmox VM
Etwas unpräzise.
Heißt wohl HA-OS läuft als VM unter Proxmox.
Und OpenCCU dann als AddOn in der HA-OS-VM?
Hast du im OpenCCU-AddOn CUxD als AddOn installiert?
Das schnappt sich, wenn nicht anders konfiguriert, alle “Sticks”.
Liest sich erstmal wie das hier:
offen 09:48AM - 07 Nov 25 UTC
bug-report
platform/ha-addon
### Describe the issue you are experiencing
After migrating from deprecated Ras… pberryMatic CCU to the Open CCU i facing issues with my matter/thread network.
In my opinion OpenCCU is claiming all serialports and disconnecting other working connections for other dongles then its own.
Hopefully it can be fixed.
### Describe the behavior you expected
OpenCCU should be configureable to use only one speific serielconeccted Dongle. So it doesnt destroy other connections.
### Steps to reproduce the issue
1. OpenCCU up and running and fully configured:
- Skyconnect/ZBT1 or any other Dongle using serial cannot be flashed. It brackes connection after some seconds.
2. OpenCCU stopped
- Skyconnect/ZBT1 can fully integrate and flashed by onboard toolstack
- Matter/Thread Network established
- OpenThread Border Router Addon up and running stabil
3. OpenCCU starting again
- OpenThread Border Router gets RadioTimeouts and stops
- OpenCCU gets up and running normal
4. Stopping OpenCCU und Starting OpenThread Border Router
- OpenThread Border Router starts working as normal
### What is the version this bug report is based on?
3.83.6.20251025
### Which base platform are you running?
rpi5 (RaspberryPi5, ARM64/aarch64)
### Which HomeMatic/homematicIP radio module are you using?
HmIP-RFUSB
### Anything in the logs that might be useful for us?
```txt
Here are the logs at the time OpenCCU starting:
OpenCCU:
Identifying host system: Raspberry Pi 5 Model B Rev 1.0 (oci), OK
Initializing RTC Clock: rpi-rtc soc@107c000000:rpi_rtc, OK
Running sysctl: OK
Checking for UserFS Resize: not required
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Running seedrng: OK
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.3, OK
Identifying Homematic RF-Hardware: ....HmRF: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-xhci-hcd.0-1.1, HmIP: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-xhci-hcd.0-1.1, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.4.18, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting sshd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: not required
Setting LAN Gateway keys: not required
Starting hs485d: disabled
Starting multimacd: .......OK
Starting rfd: .OK
Starting HMIPServer: ..........OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.83.6.20251025 (oci_arm64)
here of OpenThreadBorder Router same Time:
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::38b7:38ff:fe13:c43d/veth7b4c7d5/35
00:14:38.474 [W] P-RadioSpinel-: radio tx timeout
00:14:38.475 [W] P-RadioSpinel-: RCP failure detected
00:14:38.475 [W] P-RadioSpinel-: Trying to recover (1/2)
00:14:40.476 [W] P-RadioSpinel-: Wait for response timeout
00:14:40.477 [W] P-RadioSpinel-: RCP failure detected
00:14:40.477 [W] P-RadioSpinel-: Trying to recover (2/2)
00:14:42.477 [W] P-RadioSpinel-: Wait for response timeout
00:14:42.477 [W] P-RadioSpinel-: RCP failure detected
00:14:42.477 [C] P-RadioSpinel-: Too many rcp failures, exiting
00:14:42.477 [C] Platform------: RecoverFromRcpFailure() at radio_spinel.cpp:2063: Failure
[10:31:01] WARNING: otbr-agent exited with code 1 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all -- anywhere anywhere PKTTYPE = unicast
DROP all -- anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all -- anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all -- anywhere anywhere PKTTYPE = unicast
ACCEPT all -- anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
[10:31:01] INFO: OTBR firewall teardown completed.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service otbr-agent-rest-discovery: stopping
s6-rc: info: service otbr-agent-rest-discovery successfully stopped
s6-rc: info: service otbr-agent-configure: stopping
s6-rc: info: service otbr-agent-configure successfully stopped
s6-rc: info: service otbr-agent: stopping
s6-rc: info: service otbr-agent successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service banner: stopping
s6-rc: info: service mdns: stopping
s6-rc: info: service banner successfully stopped
Default: mDNSResponder (Engineering Build) (Oct 28 2025 07:42:47) stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[10:31:01] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
```
### Additional information
_No response_
Generell würde ich empfehlen OpenCCU als eigenständige VM auf dem Proxmox laufen zu lassen.
1 „Gefällt mir“
Nero
20. November 2025 um 08:00
3
ja, genau so ist das Setup bei mir…sorry für die unpräzise Beschreibung.
ABER, genau das was du geschrieben hast, war das Problem…vielen DANK!!
Habe nun auch deine Empfehlung umgesetzt und OpenCCU als eigene VM laufen.
Passt nun wieder alles!
Danke dir, Problem somit gelöst.
LG
Christian
miami
20. November 2025 um 10:56
4
Wie hast Du denn die USB-Sticks an die VMs weitergegeben?
Ich habe das über Hersteller/Geräte ID gemacht. Funktioniert bei mir den Sticks für HmIP und Duofern sowie Bluetooth problemlos.
VM mit HA:
VM mit OpenCCU:
Nero
21. November 2025 um 09:04
5
Ich habe alle varianten durch, bei keinem hab ich es zum laufen bekommen.
Erst durch das trennen von OpenCCU auf ne eigene VM läuft nun alles wieder, so wie es sein soll.
Vg
Christian