[gelöst] Nach heutigem Update auf V 28629 Fehlermeldungen vom Modul HMCCUDEV

Begonnen von bmwfan, 10 März 2024, 16:57:14

Vorheriges Thema - Nächstes Thema

bmwfan

Hallo,

ich habe heute ein Update auf die oben genannte Version gemacht und habe jetzt vom Modul HMCCUDEV, die meine Heizkörperthermostate auslesen, folgende Fehlermeldungen im Log:
2024.03.10 16:45:17.835 1: HMCCU [myHMCCU3] Reading device config from CCU. This may take a couple of seconds ...
2024.03.10 16:45:26.502 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.502 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.503 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] HMCCUConf: Invalid parameter 000C9BE99C66F8:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.507 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.508 2: HMCCUDEV [HmIP_BWTH_000C9F29B0E46B_9] HMCCUConf: Invalid parameter 000C9F29B0E46B:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.519 2: HMCCUDEV [HmIP_BWTH_000C9D89A9FB21_9] HMCCUConf: Invalid parameter 000C9D89A9FB21:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.522 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.522 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.522 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.522 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.523 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.523 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.523 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.523 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.523 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] HMCCUConf: Invalid parameter 000C9BE98E7AB8:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.527 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.527 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.527 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.527 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.528 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.528 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.528 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.528 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.528 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] HMCCUConf: Invalid parameter 000C9A499EE32F:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.529 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:4 VALUES DURATION_UNIT 2 in role DIMMER_VIRTUAL_RECEIVER, command on-for-timer 1:V:DURATION_UNIT:0
2024.03.10 16:45:26.530 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:4 VALUES DURATION_UNIT 2 in role DIMMER_VIRTUAL_RECEIVER, command on-till 1:V:DURATION_UNIT:0
2024.03.10 16:45:26.530 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:4 VALUES COLOR 2 in role DIMMER_VIRTUAL_RECEIVER, command color V:COLOR:#color
2024.03.10 16:45:26.530 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:4 VALUES DURATION_UNIT 2 in role DIMMER_VIRTUAL_RECEIVER, command pct 1:V:DURATION_UNIT:0
2024.03.10 16:45:26.530 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:4 VALUES RAMP_TIME_UNIT 2 in role DIMMER_VIRTUAL_RECEIVER, command pct 3:V:RAMP_TIME_UNIT:0
2024.03.10 16:45:26.531 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:5 VALUES COLOR 2 in role DIMMER_VIRTUAL_RECEIVER, command color V:COLOR:#color
2024.03.10 16:45:26.531 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] HMCCUConf: Invalid parameter 0008DA49929255:6 VALUES COLOR 2 in role DIMMER_VIRTUAL_RECEIVER, command color V:COLOR:#color
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.535 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.536 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.536 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.536 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] HMCCUConf: Invalid parameter 000C9A49A7E499:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.538 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.538 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:10 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.538 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:10 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.538 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.539 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:11 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.539 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:11 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.539 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command toggle V:STATE:0,1
2024.03.10 16:45:26.539 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:12 VALUES ON_TIME 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:ON_TIME:?time
2024.03.10 16:45:26.539 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] HMCCUConf: Invalid parameter 000C9A4999F2BC:12 VALUES STATE 2 in role SWITCH_VIRTUAL_RECEIVER, command on-till V:STATE:1
2024.03.10 16:45:26.546 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] RPC server process started for interface BidCos-Wired with PID=29916
2024.03.10 16:45:26.550 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] Initializing RPC server CB2000000002178109 for interface BidCos-Wired
2024.03.10 16:45:26.551 1: HMCCURPCPROC [d_rpc178109BidCos_Wired] RPC server starting
2024.03.10 16:45:26.560 2: HMCCURPCPROC [d_rpc178109VirtualDevices] RPC server process started for interface VirtualDevices with PID=29917
2024.03.10 16:45:26.564 2: HMCCURPCPROC [d_rpc178109VirtualDevices] Initializing RPC server CB9292000002178109 for interface VirtualDevices
2024.03.10 16:45:26.564 1: HMCCURPCPROC [d_rpc178109VirtualDevices] RPC server starting
2024.03.10 16:45:26.573 2: HMCCURPCPROC [d_rpc178109BidCos_RF] RPC server process started for interface BidCos-RF with PID=29918
2024.03.10 16:45:26.577 2: HMCCURPCPROC [d_rpc178109BidCos_RF] Initializing RPC server CB2001000002178109 for interface BidCos-RF
2024.03.10 16:45:26.578 1: HMCCURPCPROC [d_rpc178109BidCos_RF] RPC server starting
2024.03.10 16:45:26.578 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] Callback server CB2000000002178109 created. Listening on port 7410
2024.03.10 16:45:26.579 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] CB2000000002178109 accepting connections. PID=29916
2024.03.10 16:45:26.586 2: HMCCURPCPROC [d_rpc178109HmIP_RF] RPC server process started for interface HmIP-RF with PID=29919
2024.03.10 16:45:26.590 2: HMCCURPCPROC [d_rpc178109HmIP_RF] Initializing RPC server CB2010000002178109 for interface HmIP-RF
2024.03.10 16:45:26.591 1: HMCCURPCPROC [d_rpc178109HmIP_RF] RPC server starting
2024.03.10 16:45:26.593 2: HMCCURPCPROC [d_rpc178109VirtualDevices] Callback server CB9292000002178109 created. Listening on port 14702
2024.03.10 16:45:26.594 2: HMCCURPCPROC [d_rpc178109VirtualDevices] CB9292000002178109 accepting connections. PID=29917
2024.03.10 16:45:26.603 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] RPC server CB2000000002178109 enters server loop
2024.03.10 16:45:26.604 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] Registering callback http://192.168.178.5:7410/fh2000 of type A with ID CB2000000002178109 at http://192.168.178.109:2000
2024.03.10 16:45:26.604 2: HMCCURPCPROC [d_rpc178109BidCos_RF] Callback server CB2001000002178109 created. Listening on port 7411
2024.03.10 16:45:26.605 2: HMCCURPCPROC [d_rpc178109BidCos_RF] CB2001000002178109 accepting connections. PID=29918
2024.03.10 16:45:26.616 2: HMCCURPCPROC [d_rpc178109HmIP_RF] Callback server CB2010000002178109 created. Listening on port 7420
2024.03.10 16:45:26.616 2: HMCCURPCPROC [d_rpc178109HmIP_RF] CB2010000002178109 accepting connections. PID=29919
2024.03.10 16:45:26.638 1: HMCCURPCPROC [d_rpc178109BidCos_Wired] RPC server CB2000000002178109 running
2024.03.10 16:45:26.689 2: HMCCURPCPROC [d_rpc178109BidCos_Wired] CB2000000002178109 NewDevice received 106 device and channel specifications
2024.03.10 16:45:26.722 2: HMCCURPCPROC [d_rpc178109HmIP_RF] RPC server CB2010000002178109 enters server loop
2024.03.10 16:45:26.723 2: HMCCURPCPROC [d_rpc178109HmIP_RF] Registering callback http://192.168.178.5:7420/fh2010 of type A with ID CB2010000002178109 at http://192.168.178.109:2010
2024.03.10 16:45:26.741 1: HMCCURPCPROC [d_rpc178109HmIP_RF] RPC server CB2010000002178109 running
2024.03.10 16:45:26.751 2: HMCCURPCPROC [d_rpc178109BidCos_RF] RPC server CB2001000002178109 enters server loop
2024.03.10 16:45:26.751 2: HMCCURPCPROC [d_rpc178109BidCos_RF] Registering callback http://192.168.178.5:7411/fh2001 of type A with ID CB2001000002178109 at http://192.168.178.109:2001
2024.03.10 16:45:26.783 1: HMCCURPCPROC [d_rpc178109BidCos_RF] RPC server CB2001000002178109 running
2024.03.10 16:45:26.785 1: HMCCURPCPROC [d_rpc178109BidCos_RF] Scheduled CCU ping every 300 seconds
2024.03.10 16:45:26.788 2: HMCCURPCPROC [d_rpc178109VirtualDevices] RPC server CB9292000002178109 enters server loop
2024.03.10 16:45:26.788 2: HMCCURPCPROC [d_rpc178109VirtualDevices] Registering callback http://192.168.178.5:14702/fh9292 of type A with ID CB9292000002178109 at http://192.168.178.109:9292/groups
2024.03.10 16:45:26.805 2: HMCCURPCPROC [d_rpc178109BidCos_RF] CB2001000002178109 NewDevice received 55 device and channel specifications
2024.03.10 16:45:27.007 2: HMCCURPCPROC [d_rpc178109HmIP_RF] CB2010000002178109 NewDevice received 206 device and channel specifications
2024.03.10 16:45:36.811 1: HMCCURPCPROC [d_rpc178109VirtualDevices] RPC server CB9292000002178109 running
2024.03.10 16:45:36.812 1: HMCCU [myHMCCU3] All RPC servers running
2024.03.10 16:45:36.843 2: HMCCURPCPROC [d_rpc178109VirtualDevices] CB9292000002178109 NewDevice received 8 device and channel specifications

Dies sind die installierten Versionen:
Latest Revision: 28629

File                        Rev   Last Change

fhem.pl                     28598 2024-03-05 15:57:09Z rudolfkoenig
96_allowed.pm               26004 2022-04-29 19:06:05Z rudolfkoenig
90_at.pm                    28610 2024-03-07 09:53:25Z rudolfkoenig
99_attrTmqtt2_ebus_Utils.pm 25044 2021-10-03 19:41:45Z Beta-User
98_autocreate.pm            23727 2021-02-12 20:31:37Z rudolfkoenig
57_CALVIEW.pm               17605 2018-10-23 16:37:40Z chris1284
98_cmdalias.pm              16300 2018-03-01 08:48:21Z rudolfkoenig
00_CUL.pm                   24815 2021-08-01 16:14:02Z rudolfkoenig
10_CUL_HM.pm                26934 2022-12-31 16:24:33Z martinp876
No Id found for 99_DockerImageInfo.pm
98_DOIF.pm                  28546 2024-02-23 20:11:05Z Damian
98_DOIFtools.pm             27854 2023-08-18 08:28:36Z Ellert
98_dummy.pm                 25606 2022-02-01 10:43:57Z rudolfkoenig
91_eventTypes.pm            23471 2021-01-04 19:24:21Z rudolfkoenig
72_FB_CALLLIST.pm           25271 2021-11-28 09:40:15Z markusbloch
72_FB_CALLMONITOR.pm        28165 2023-11-14 13:38:31Z jowiemann
01_FHEMWEB.pm               28329 2023-12-31 10:48:50Z rudolfkoenig
92_FileLog.pm               28451 2024-01-31 22:05:20Z rudolfkoenig
72_FRITZBOX.pm              28575 2024-03-01 09:46:59Z jowiemann
98_GEOFANCY.pm              18995 2019-03-22 20:09:53Z loredo
88_HMCCU.pm                 28629 2024-03-09 17:04:22Z zap
88_HMCCUCHN.pm              28629 2024-03-09 17:04:22Z zap
88_HMCCUDEV.pm              28611 2024-03-07 17:19:22Z zap
88_HMCCURPCPROC.pm          28611 2024-03-07 17:19:22Z zap
00_HMUARTLGW.pm             25203 2021-11-08 09:18:29Z mgernoth
95_holiday.pm               25187 2021-11-06 09:54:35Z rudolfkoenig
98_HTTPMOD.pm               27714 2023-06-29 15:30:07Z StefanStrobel
02_HTTPSRV.pm               20110 2019-09-05 17:30:20Z neubert
49_IPCAM.pm                 24924 2021-09-06 08:47:51Z delmar
36_JeeLink.pm               14707 2017-07-13 18:08:33Z justme1968
98_JsonList2.pm             26701 2022-11-14 09:51:02Z rudolfkoenig
36_LaCrosse.pm              25537 2022-01-21 17:54:29Z HCS
98_monitoring.pm            26892 2022-12-24 08:27:11Z Beta-User
10_MQTT2_DEVICE.pm          27935 2023-09-05 11:48:14Z rudolfkoenig
00_MQTT2_SERVER.pm          28191 2023-11-20 19:06:44Z rudolfkoenig
10_MQTT_GENERIC_BRIDGE.pm   25117 2021-10-25 11:05:19Z hexenmeister
91_notify.pm                28610 2024-03-07 09:53:25Z rudolfkoenig
73_PRESENCE.pm              18314 2019-01-18 13:49:05Z markusbloch
59_PROPLANTA.pm             23449 2021-01-01 09:56:49Z tupol
70_Pushover.pm              27466 2023-04-20 07:51:19Z rudolfkoenig
98_rain.pm                   6916 2014-11-08 11:28:26Z baumrasen
33_readingsGroup.pm         23844 2021-02-27 19:43:24Z justme1968
98_readingsWatcher.pm       25053 2021-10-07 07:39:29Z Wzut
10_RESIDENTS.pm             19533 2019-06-02 19:33:11Z loredo
86_Robonect.pm              17176 2018-08-19 17:20:49Z andi291
20_ROOMMATE.pm              19533 2019-06-02 19:33:11Z loredo
57_SSCal.pm                 26236 2022-07-16 16:31:39Z DS_Starter
49_SSCam.pm                 27242 2023-02-17 09:02:46Z DS_Starter
49_SSCamSTRM.pm             27054 2023-01-14 13:10:58Z DS_Starter
98_structure.pm             27209 2023-02-12 14:45:51Z rudolfkoenig
99_SUNRISE_EL.pm            24249 2021-04-14 05:45:49Z rudolfkoenig
98_SVG.pm                   28617 2024-03-08 15:05:47Z rudolfkoenig
42_SYSMON.pm                26358 2022-08-29 21:11:26Z hexenmeister
50_TelegramBot.pm           27218 2023-02-13 22:45:48Z viegener
98_telnet.pm                25754 2022-02-27 16:49:52Z rudolfkoenig
99_Utils.pm                 28529 2024-02-18 11:42:21Z rudolfkoenig
77_UWZ.pm                   25306 2021-12-06 05:27:48Z CoolTux
98_version.pm               26611 2022-10-28 16:32:29Z betateilchen
98_weblink.pm               26988 2023-01-07 09:18:42Z rudolfkoenig

AttrTemplate.pm             27145 2023-01-29 11:48:19Z rudolfkoenig
Blocking.pm                 23268 2020-12-01 11:48:48Z rudolfkoenig
Color.pm                    20813 2019-12-22 18:42:10Z justme1968
DevIo.pm                    27247 2023-02-18 21:22:32Z rudolfkoenig
FritzBoxUtils.pm            23727 2021-02-12 20:31:37Z rudolfkoenig
GPUtils.pm                  19666 2019-06-20 11:17:29Z CoolTux
HMCCUConf.pm                28629 2024-03-09 17:04:22Z zap
HMConfig.pm                 25160 2021-10-30 17:38:52Z martinp876
No Id found for HMConfig_SenTHPL.pm
HttpUtils.pm                27406 2023-04-07 16:52:19Z rudolfkoenig
Meta.pm                     26889 2022-12-23 15:04:11Z CoolTux
myUtilsTemplate.pm           7570 2015-01-14 18:31:44Z rudolfkoenig
myUtilsTemplate.pm           7570 2015-01-14 18:31:44Z rudolfkoenig
RESIDENTStk.pm              19788 2019-07-06 08:10:55Z loredo
RTypes.pm                   10476 2016-01-12 21:03:33Z borisneubert
SetExtensions.pm            25286 2021-12-03 10:16:56Z rudolfkoenig
TcpServerUtils.pm           28227 2023-11-29 12:33:32Z rudolfkoenig
UConv.pm                    21159 2020-02-09 14:04:27Z loredo
Unit.pm                     19614 2019-06-13 23:11:25Z loredo

doif.js                    24438 2021-05-14 18:08:18Z Ellert
f18.js                     27573 2023-05-15 08:39:17Z rudolfkoenig
fhemweb.js                 28198 2023-11-22 16:22:22Z rudolfkoenig
fhemweb_readingsGroup.js   15189 2017-10-03 17:53:27Z justme1968

Ich vermute Änderungen in einem Modul als Grund, weis aber nicht wie ich den Fehler beheben kann. JHat jemand eine Idee?

Grüße Jürgen
Synology DS720+ mit Docker-Container und Haupt-FHEM, HW-LAN, Jalousienaktoren; Raspi 3B+ mit piVCCU ohne FHEM-Instanz, CUL, JeeLink; Raspi 3B+ mit FHEM und HMUARTUSB,  Raspi 3B+ mit HMUARTGPIO, 1-wire, ebusd

betateilchen

#1
Idee: mal im richtigen Unterforum zu Homematic fragen, anstatt in den Anfängerfragen?

Und vorher dort im HMCCU Thread mal schauen, ob zum Update schon Fehlermeldungen gemeldet wurden...
-----------------------
Formuliere die Aufgabe möglichst einfach und
setze die Lösung richtig um - dann wird es auch funktionieren.
-----------------------
Lesen gefährdet die Unwissenheit!

bmwfan

@Betateilchen:
Hatte schon im Homematic-Thread geschaut, aber nichts gefunden. Deswegen bei Anfängerfragen gepostet.
Synology DS720+ mit Docker-Container und Haupt-FHEM, HW-LAN, Jalousienaktoren; Raspi 3B+ mit piVCCU ohne FHEM-Instanz, CUL, JeeLink; Raspi 3B+ mit FHEM und HMUARTUSB,  Raspi 3B+ mit HMUARTGPIO, 1-wire, ebusd

JoWiemann

Zitat von: bmwfan am 10 März 2024, 19:31:07@Betateilchen:
Hatte schon im Homematic-Thread geschaut, aber nichts gefunden. Deswegen bei Anfängerfragen gepostet.

Hallo,

hm. Und was ist mit diesem Post: https://forum.fhem.de/index.php?action=profile;u=45065

Verschiebe doch bitte Deinen Post in das Unterforum. Das ist bei Anfänger echt nicht richtig aufgehoben. Anfänger ist für Benutzer, die sich mit Fhem nicht auskennen. Nicht für Fehlermeldungen.

Grüße Jörg
Jörg Wiemann

Slave: RPi B+ mit 512 MB, COC (868 MHz), CUL V3 (433.92MHz SlowRF); FHEMduino, Aktuelles FHEM

Master: CubieTruck; Debian; Aktuelles FHEM

zap

Ist vermutlich keine kritische Meldung. Gibts ein Gerät, das sich nicht mehr schalten lässt oder bei dem on-for-timer nicht mehr funktioniert?
2xCCU3, Fenster, Rollläden, Themostate, Stromzähler, Steckdosen ...)
Entwicklung: FHEM auf AMD NUC (Ubuntu)
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: FULLY, Meteohub, HMCCU, AndroidDB

bmwfan

Guten Morgen,

@JoWiemann:
Hatte über den Verschieben-Button unten links den Thread nach Homematic verschoben und finde ihn auch dort. Ist das nicht das richtige Unterforum? Wenn nicht, wohin soll ich den Thread verschieben?
Der Link führt auf ein Profil?

@zap:
Es laufen einige Thermostate, Rolladenaktoren und Fensterkontakte darüber. Bisher ist mir noch nicht aufgefallen, dass ein Schaltvorgang nicht mehr funktioniert. Ich verwende zwar viele DOIF, aber wenige on-for-timer.
Synology DS720+ mit Docker-Container und Haupt-FHEM, HW-LAN, Jalousienaktoren; Raspi 3B+ mit piVCCU ohne FHEM-Instanz, CUL, JeeLink; Raspi 3B+ mit FHEM und HMUARTUSB,  Raspi 3B+ mit HMUARTGPIO, 1-wire, ebusd

zap

Bitte mal das heutige Update installieren und prüfen, ob der Fehler noch auftritt.
2xCCU3, Fenster, Rollläden, Themostate, Stromzähler, Steckdosen ...)
Entwicklung: FHEM auf AMD NUC (Ubuntu)
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: FULLY, Meteohub, HMCCU, AndroidDB

bmwfan

Update war erfolgreich. Fehlermeldungen sind weg.

Danke und Grüße

Jürgen
Synology DS720+ mit Docker-Container und Haupt-FHEM, HW-LAN, Jalousienaktoren; Raspi 3B+ mit piVCCU ohne FHEM-Instanz, CUL, JeeLink; Raspi 3B+ mit FHEM und HMUARTUSB,  Raspi 3B+ mit HMUARTGPIO, 1-wire, ebusd