HMCCU Raspimatic Update 3.41.11.20181126 - FHEM hängt sich mit CUxD auf

[Depechem]

Habt ihr das aktuelle Raspimatic Update 3.41.11.20181126 geladen und CCU und FHEM neu gestartet?

Scheinbar hängt seitdem mein FHEM.
Gibts bei euch auch Probleme oder habt ihr eine Idee?

Code Auswählen Erweitern

2018.12.04 19:56:12.763 1: HMCCU: [d_ccu] No RPC device defined for interface CUxD
2018.12.04 19:56:12.769 1: HMCCU: [d_ccu] Creating new RPC device d_rpcCUxD
2018.12.04 19:58:20.082 1: define d_rpcCUxD HMCCURPCPROC 192.168.2.199 CUxD: Cannot connect to CCU 192.168.2.199 interface CUxD
2018.12.04 19:58:20.083 1: HMCCU: [d_ccu] Definition of RPC device failed.
2018.12.04 19:58:20.083 1: HMCCU: [d_ccu] Cannot connect to CCU 192.168.2.199 interface CUxD

Code Auswählen Erweitern

2018.12.04 21:31:49.118 1: PERL Wr interface HmIP-RF with PID=3221
2018.12.04 21:32:42.534 2: CCURPC: [d_rpcHmIP_RF] Initializing RPC server CB201000220ARNING: Use of uninitialized value $value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 6061, <GEN1842> line 1.
2018.12.04 21:32:38.861 1: HMCCURPCPROC: [d_rpcBidCos_RF] Stopping RPC server CB2001002200
2018.12.04 21:32:38.890 1: HMCCURPCPROC: [d_rpcBidCos_RF] Deregistering RPC server http://192.168.2.200:7411/fh2001 with ID CB2001002200 at http://192.168.2.199:2001
2018.12.04 21:32:38.945 1: HMCCURPCPROC: [d_rpcBidCos_RF] Callback for RPC server CB2001002200 deregistered
2018.12.04 21:32:38.974 2: HMCCURPCPROC: [d_rpcBidCos_RF] Sending signal INT to RPC server process CB2001002200 with PID=2872
2018.12.04 21:32:38.975 2: CCURPC: [d_rpcBidCos_RF] CB2001002200 received signal INT
2018.12.04 21:32:38.975 1: CCURPC: [d_rpcBidCos_RF] RPC server CB2001002200 stopped handling connections. PID=2872
2018.12.04 21:32:38.976 2: CCURPC: [d_rpcBidCos_RF] Number of I/O errors = 0
2018.12.04 21:32:39.976 1: HMCCURPCPROC: [d_rpcHmIP_RF] Stopping RPC server CB2010002200
2018.12.04 21:32:40.005 1: HMCCURPCPROC: [d_rpcHmIP_RF] Deregistering RPC server http://192.168.2.200:7420/fh2010 with ID CB2010002200 at http://192.168.2.199:2010
2018.12.04 21:32:40.069 1: HMCCURPCPROC: [d_rpcHmIP_RF] Callback for RPC server CB2010002200 deregistered
2018.12.04 21:32:40.098 2: HMCCURPCPROC: [d_rpcHmIP_RF] Sending signal INT to RPC server process CB2010002200 with PID=2873
2018.12.04 21:32:40.099 2: CCURPC: [d_rpcHmIP_RF] CB2010002200 received signal INT
2018.12.04 21:32:40.100 1: CCURPC: [d_rpcHmIP_RF] RPC server CB2010002200 stopped handling connections. PID=2873
2018.12.04 21:32:40.101 2: CCURPC: [d_rpcHmIP_RF] Number of I/O errors = 0
2018.12.04 21:32:41.227 1: HMCCURPCPROC: [d_rpcHmIP_RF] RPC server process CB2010002200 terminated.
2018.12.04 21:32:41.228 2: HMCCURPCPROC: [d_rpcHmIP_RF] Stop I/O handling
2018.12.04 21:32:41.318 1: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server process CB2001002200 terminated.
2018.12.04 21:32:41.350 1: HMCCU: [d_ccu] All RPC servers inactive
2018.12.04 21:32:41.380 2: HMCCURPCPROC: [d_rpcBidCos_RF] Stop I/O handling
2018.12.04 21:32:42.316 2: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server process started for interface BidCos-RF with PID=3220
2018.12.04 21:32:42.352 2: CCURPC: [d_rpcBidCos_RF] Initializing RPC server CB2001002200 for interface BidCos-RF
2018.12.04 21:32:42.410 1: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server starting
2018.12.04 21:32:42.497 2: HMCCURPCPROC: [d_rpcHmIP_RF] RPC server process started fo0 for interface HmIP-RF
2018.12.04 21:32:42.542 2: HMCCURPCPROC: [d_rpcBidCos_RF] Callback server CB2001002200 created. Listening on port 7411
2018.12.04 21:32:42.547 2: CCURPC: [d_rpcBidCos_RF] CB2001002200 accepting connections. PID=3220
2018.12.04 21:32:42.594 1: HMCCURPCPROC: [d_rpcHmIP_RF] RPC server starting
2018.12.04 21:32:42.710 2: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server CB2001002200 enters server loop
2018.12.04 21:32:42.711 2: HMCCURPCPROC: [d_rpcHmIP_RF] Callback server CB2010002200 created. Listening on port 7420
2018.12.04 21:32:42.715 2: CCURPC: [d_rpcHmIP_RF] CB2010002200 accepting connections. PID=3221
2018.12.04 21:32:42.744 2: HMCCURPCPROC: [d_rpcBidCos_RF] Registering callback http://192.168.2.200:7411/fh2001 of type A with ID CB2001002200 at http://192.168.2.199:2001
2018.12.04 21:32:42.848 1: HMCCURPCPROC: [d_rpcBidCos_RF] RPC server CB2001002200 running
2018.12.04 21:32:42.984 2: HMCCURPCPROC: [d_rpcHmIP_RF] RPC server CB2010002200 enters server loop
2018.12.04 21:32:43.018 2: HMCCURPCPROC: [d_rpcHmIP_RF] Registering callback http://192.168.2.200:7420/fh2010 of type A with ID CB2010002200 at http://192.168.2.199:2010
2018.12.04 21:32:43.083 1: HMCCURPCPROC: [d_rpcHmIP_RF] RPC server CB2010002200 running
2018.12.04 21:32:43.120 1: HMCCU: [d_ccu] All RPC servers running
2018.12.04 21:32:43.228 2: CCURPC: [d_rpcHmIP_RF] CB2010002200 NewDevice received 10 device and channel specifications
2018.12.04 21:32:43.237 2: CCURPC: [d_rpcBidCos_RF] CB2001002200 NewDevice received 74 device and channel specifications

[zap]

lies mal das

https://homematic-forum.de/forum/viewtopic.php?f=26&t=46844

also entweder Firewall Einstellungen oder die richtige Version von CUxD neu installieren

[Depechem]

lies mal das

https://homematic-forum.de/forum/viewtopic.php?f=26&t=46844

also entweder Firewall Einstellungen oder die richtige Version von CUxD neu installieren

Vielen Dank,
das neue CuXD 2.2 ist rausgekommen.
Nun läuft alles.

Gruß Thomas