[gelöst] HMCCU Geräte funktionieren nach CCU-Neueinrichtung nicht

[Mort]

Hallo,

mir hat's nach einem Stromausfall die SD vom Pi 3B+ zerhauen, auf dem die CCU3 lief. Also habe ich RaspberryMatic neu geflashed und ein Backup eingespielt.
Bei HMCCU selbst sieht nach einem "set on" alles ganz OK aus. State ist "running/OK", rpcstate ist "running" (procrpc), die Readings sind aktuell und sehen korrekt aus.
Aber bei den Geräten sind die Readings veraltert und jeglicher "set"-Versuch wird mit "Device state doesn't allow set commands" abgelehnt.
Im Logfile fällt mir vor allem "Update success=0 failed=12" auf. Aber warum? An den Seriennummern hat sich ja nichts geändert.

Code Auswählen Erweitern

2022.10.27 13:22:58 1: HMCCU [ccu] CCU port 8181 is reachable
2022.10.27 13:22:58 1: HMCCU [ccu] Initialized version 5.0 222930908
2022.10.27 13:22:58 1: HMCCU [ccu] Initializing device
2022.10.27 13:22:58 2: HMCCU [ccu] Deleting old CCU configuration data
2022.10.27 13:22:58 2: HMCCU [ccu] Updating device table
2022.10.27 13:22:58 1: HMCCU [ccu] Read 16 devices with 200 channels from CCU tattoine
2022.10.27 13:22:58 1: HMCCU [ccu] Read 0 programs from CCU tattoine
2022.10.27 13:22:58 1: HMCCU [ccu] Read 2 virtual groups from CCU tattoine
2022.10.27 13:23:03 2: HMCCURPCPROC [d_rpc178046HmIP_RF] CCU interface HmIP-RF doesn't support RPC multicalls
2022.10.27 13:23:03 1: HMCCURPCPROC [d_rpc178046HmIP_RF] Initialized version 5.0 222930908 for interface HmIP-RF with I/O device ccu
2022.10.27 13:23:03 2: HMCCURPCPROC [d_rpc178046BidCos_RF] CCU interface BidCos-RF supports RPC multicalls
2022.10.27 13:23:03 1: HMCCURPCPROC [d_rpc178046BidCos_RF] Initialized version 5.0 222930908 for interface BidCos-RF with I/O device ccu
2022.10.27 13:23:03 2: HMCCURPCPROC [d_rpc178046VirtualDevices] CCU interface VirtualDevices doesn't support RPC multicalls
2022.10.27 13:23:03 1: HMCCURPCPROC [d_rpc178046VirtualDevices] Initialized version 5.0 222930908 for interface VirtualDevices with I/O device ccu
2022.10.27 13:23:04 0: HMCCU [ccu] Scheduling post FHEM initialization tasks in 12 seconds
2022.10.27 13:23:16 1: HMCCU [ccu] Reading device config from CCU. This may take a couple of seconds ...
2022.10.27 13:23:16 2: HMCCU [ccu] Reading Device Descriptions for interface VirtualDevices
2022.10.27 13:23:16 2: HMCCU [ccu] Read 16 Device Descriptions for interface VirtualDevices
2022.10.27 13:23:16 2: HMCCU [ccu] Reading Paramset Descriptions for interface VirtualDevices
2022.10.27 13:23:18 2: HMCCU [ccu] Read 13 Paramset Descriptions for interface VirtualDevices
2022.10.27 13:23:18 2: HMCCU [ccu] Reading Peer Descriptions for interface VirtualDevices
2022.10.27 13:23:18 2: HMCCU [ccu] Read 0 Peer Descriptions for interface VirtualDevices
2022.10.27 13:23:18 2: HMCCU [ccu] Reading Device Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Read 52 Device Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Reading Paramset Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Read 153 Paramset Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Reading Peer Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Read 0 Peer Descriptions for interface BidCos-RF
2022.10.27 13:23:18 2: HMCCU [ccu] Reading Device Descriptions for interface HmIP-RF
2022.10.27 13:23:19 2: HMCCU [ccu] Read 148 Device Descriptions for interface HmIP-RF
2022.10.27 13:23:19 2: HMCCU [ccu] Reading Paramset Descriptions for interface HmIP-RF
2022.10.27 13:23:30 2: HMCCU [ccu] Read 274 Paramset Descriptions for interface HmIP-RF
2022.10.27 13:23:30 2: HMCCU [ccu] Reading Peer Descriptions for interface HmIP-RF
2022.10.27 13:23:30 2: HMCCU [ccu] Read 11 Peer Descriptions for interface HmIP-RF
2022.10.27 13:23:30 2: HMCCU [ccu] Read device configuration in 14.6870880126953 seconds: devices/channels=216 parametersets=440 links=11
2022.10.27 13:23:30 2: HMCCU [ccu] RPC device for interface VirtualDevices: d_rpc178046VirtualDevices
2022.10.27 13:23:30 2: HMCCU [ccu] RPC device for interface BidCos-RF: d_rpc178046BidCos_RF
2022.10.27 13:23:30 2: HMCCU [ccu] RPC device for interface HmIP-RF: d_rpc178046HmIP_RF
2022.10.27 13:23:30 2: HMCCURPCPROC [d_rpc178046VirtualDevices] RPC server process started for interface VirtualDevices with PID=5325
2022.10.27 13:23:30 2: HMCCURPCPROC [d_rpc178046VirtualDevices] Initializing RPC server CB9292178021178046 for interface VirtualDevices
2022.10.27 13:23:30 1: HMCCURPCPROC [d_rpc178046VirtualDevices] RPC server starting
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046BidCos_RF] RPC server process started for interface BidCos-RF with PID=5326
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046BidCos_RF] Initializing RPC server CB2001178021178046 for interface BidCos-RF
2022.10.27 13:23:31 1: HMCCURPCPROC [d_rpc178046BidCos_RF] RPC server starting
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046HmIP_RF] RPC server process started for interface HmIP-RF with PID=5327
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046VirtualDevices] Callback server CB9292178021178046 created. Listening on port 14702
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046VirtualDevices] CB9292178021178046 accepting connections. PID=5325
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046HmIP_RF] Initializing RPC server CB2010178021178046 for interface HmIP-RF
2022.10.27 13:23:31 1: HMCCURPCPROC [d_rpc178046HmIP_RF] RPC server starting
2022.10.27 13:23:31 2: HMCCU [ccu] RPC server start: 3 started, 0 already running, 0 failed to start
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046VirtualDevices] RPC server CB9292178021178046 enters server loop
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046BidCos_RF] Callback server CB2001178021178046 created. Listening on port 7411
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046BidCos_RF] CB2001178021178046 accepting connections. PID=5326
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046VirtualDevices] Registering callback http://192.168.178.21:14702/fh9292 of type A with ID CB9292178021178046 at http://192.168.178.46:9292/groups
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046HmIP_RF] Callback server CB2010178021178046 created. Listening on port 7420
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046HmIP_RF] CB2010178021178046 accepting connections. PID=5327
2022.10.27 13:23:31 2: HMCCURPCPROC [d_rpc178046VirtualDevices] CB9292178021178046 NewDevice received 16 device and channel specifications
2022.10.27 13:23:41 1: HMCCURPCPROC [d_rpc178046VirtualDevices] RPC server CB9292178021178046 running
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046HmIP_RF] RPC server CB2010178021178046 enters server loop
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046HmIP_RF] Registering callback http://192.168.178.21:7420/fh2010 of type A with ID CB2010178021178046 at http://192.168.178.46:2010
2022.10.27 13:23:41 1: HMCCURPCPROC [d_rpc178046HmIP_RF] RPC server CB2010178021178046 running
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046BidCos_RF] RPC server CB2001178021178046 enters server loop
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046BidCos_RF] Registering callback http://192.168.178.21:7411/fh2001 of type A with ID CB2001178021178046 at http://192.168.178.46:2001
2022.10.27 13:23:41 1: HMCCURPCPROC [d_rpc178046BidCos_RF] RPC server CB2001178021178046 running
2022.10.27 13:23:41 1: HMCCU [ccu] All RPC servers running
2022.10.27 13:23:41 2: HMCCU [ccu] Updating 12 of 12 client devices matching devexp=.* filter=ccudevstate=active,ccuif=VirtualDevices|BidCos-RF|HmIP-RF
2022.10.27 13:23:41 1: HMCCURPCPROC [d_rpc178046BidCos_RF] Scheduled CCU ping every 300 seconds
2022.10.27 13:23:41 2: HMCCU [ccu] Update success=0 failed=12
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046BidCos_RF] CB2001178021178046 NewDevice received 52 device and channel specifications
2022.10.27 13:23:41 2: HMCCURPCPROC [d_rpc178046HmIP_RF] CB2010178021178046 NewDevice received 148 device and channel specifications


Irgendeine Idee?

[Mort]

OK, ich habe die Ursache. Das Attribut "disable" wurde irgendwie für alle Devices gesetzt - evtl., als die CCU nicht erreichbar war oder die Geräte auf der neuen noch fehlten (also vor dem Update)? Ich hing da noch zu sehr bei Status und "readonly".