Guten Tag,
ich nutze einen RasperypiMatic als CCU
Die devices die dort angeschlossen sind lassen sich mit get d_ccu createDev anlegen und kommunizieren auch.
Beim Anlegen des HmIP-FAL24-C6, der bei mir V_Heizung_1_Stock heist kommt die Meldung :
"
Results of create command:
Not detected CCU devices:
V_Heizung_1_Stock = 000615699CED0A [V_Heizung_1_Stock]
"
und es wird nichts angelegt.
Was kann ich tun ? welche Info ist noch wichtig?
Besten Dank schon mal
[code]Type list <name> for detailed info.
Global:
global (no definition)
MQTT2_SERVER:
myMQTT2_SERVER (Initialized)
FHEMWEB:
WEB (Initialized)
WEB_192.168.178.136_49312 (Connected)
WEB_192.168.178.136_49313 (Connected)
WEB_192.168.178.136_49314 (Connected)
WEB_192.168.178.136_49315 (Connected)
WEB_192.168.178.136_49316 (Connected)
MQTT2_DEVICE:
MQTT2_Siegfrieds_Dallas_1_1 (???)
HMCCU:
d_ccu (inactive/OK)
HMCCUCHN:
S_Bad_Fussboden (18.3)
S_PC (19.3)
S_Wohnzimmer (25.7)
HMCCURPCPROC:
d_rpc178003BidCos_RF (inactive/OK)
d_rpc178003HmIP_RF (inactive/OK)
d_rpc178003VirtualDevices (inactive/OK)
eventTypes:
eventTypes (active)
notify:
initialUsbCheck (active)
FileLog:
FileLog_MQTT2_Siegfrieds_Dallas_1_1 (active)
FileLog_S_Bad_Fussboden (active)
FileLog_S_PC (active)
FileLog_S_Wohnzimmer (active)
Logfile (active)
SVG:
SVG_FileLog_MQTT2_Siegfrieds_Dallas_1_1_1 (initialized)
SVG_FileLog_S_Bad_Fussboden_1 (initialized)
SVG_FileLog_S_PC_1 (initialized)
SVG_FileLog_S_Wohnzimmer_1 (initialized)
autocreate:
autocreate (active)
dummy:
myDummy (
[/code]???)
Bitte ein list der Homematic-Devices, z.B.
list d_ccu
usw. für die anderen Devices, den Inhalt dann hier posten.
Viele Grüße Gisbert
list d_ccu
Save config
-- STATUS --
Heizung
Homematic
MQTT2_DEVICE
TempLog
Unsorted
_HOMEMATIC
icoEverything Everything
Logfile
Commandref
Remote doc
Edit files
Select style
Event monitor
Internals:
CCUNum 1
Clients :HMCCUDEV:HMCCUCHN:HMCCURPCPROC:
DEF 192.168.178.3 waitforccu=180
FUUID 637a8472-f33f-e8dd-b0f7-3701b3653923760f
NAME d_ccu
NOTIFYDEV global,TYPE=(HMCCU|HMCCUDEV|HMCCUCHN)
NR 16
NTFY_ORDER 50-d_ccu
RPCState inactive
STATE inactive/OK
TYPE HMCCU
ccuaddr BidCoS-RF
ccuchannels 203
ccudevices 17
ccuif BidCos-RF
ccuinterfaces HmIP-RF,VirtualDevices,BidCos-RF
ccuip 192.168.178.3
ccuname HM_RCV_50BidCoS_RF
ccustate active
ccutype CCU2/3
config 5.0
firmware 3.65.11.20221005
host 192.168.178.3
prot http
version 5.0 213011850
READINGS:
2022-11-22 20:25:28 count_channels 203
2022-11-22 20:25:28 count_devices 17
2022-11-22 20:25:28 count_groups 0
2022-11-22 20:25:28 count_interfaces 3
2022-11-22 20:25:28 count_programs 12
2022-11-22 20:13:41 rpcstate inactive
2022-11-22 20:17:32 state OK
hmccu:
ccuDevList "_Rollo_Buero_#k_Fenster",4_fach_1,Garage,Garage_ext1,HM_RCV_50BidCoS_RF,HmIP_RCV_50HmIP_RCV_1,S_Bad_Fussboden,S_PC,S_Wohnzimmer,V_Heizung_1_Stock,_Rollo_Bad,_Rollo_Buero,_Rollo_Schlafzimmer,_T_Garten_Fenster,_T_Garten_Tuer,_T_oben,_unten_Taster
ccuSuppDevList "_Rollo_Buero_#k_Fenster",4_fach_1,Garage,Garage_ext1,S_Bad_Fussboden,S_PC,S_Wohnzimmer,V_Heizung_1_Stock,_Rollo_Bad,_Rollo_Buero,_Rollo_Schlafzimmer,_T_Garten_Fenster,_T_Garten_Tuer,_T_oben,_unten_Taster
defaults 0
evtime 0
evtimeout 0
rpccount 0
rpcports 2001,9292,2010
updatetime 1669145128
adr:
4_fach_1:
address NEQ1138746
addtype dev
valid 1
4_fach_1:0:
address NEQ1138746:0
addtype chn
valid 1
Bad:
address 000615699CED0A:2
addtype chn
valid 1
Bad rauf:
address NEQ1487016:4
addtype chn
valid 1
Bad runter:
address NEQ1487016:3
addtype chn
valid 1
B�ro 1:
address 000A97098ED06C:7
addtype chn
valid 1
Garage:
address NEQ1263862
addtype dev
valid 1
Garage ext:
address REQ0632285:1
addtype chn
valid 1
Garage ext 1:
address REQ0632285:2
addtype chn
valid 1
Garage:0:
address NEQ1263862:0
addtype chn
valid 1
Garage_ext1:
address REQ0632285
addtype dev
valid 1
Garage_ext1:0:
address REQ0632285:0
addtype chn
valid 1
GaragenTaster:
address NEQ1487242:19
addtype chn
valid 1
HM-LC-Sw1-Pl-CT-R1 NEQ1263862:1:
address NEQ1263862:1
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:10:
address NEQ1487016:10
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:11:
address NEQ1487016:11
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:12:
address NEQ1487016:12
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:13:
address NEQ1487016:13
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:14:
address NEQ1487016:14
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:15:
address NEQ1487016:15
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:16:
address NEQ1487016:16
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:17:
address NEQ1487016:17
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:18:
address NEQ1487016:18
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:19:
address NEQ1487016:19
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:20:
address NEQ1487016:20
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:5:
address NEQ1487016:5
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:6:
address NEQ1487016:6
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:7:
address NEQ1487016:7
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:8:
address NEQ1487016:8
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487016:9:
address NEQ1487016:9
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:10:
address NEQ1487242:10
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:11:
address NEQ1487242:11
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:12:
address NEQ1487242:12
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:13:
address NEQ1487242:13
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:14:
address NEQ1487242:14
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:15:
address NEQ1487242:15
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:16:
address NEQ1487242:16
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:17:
address NEQ1487242:17
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:18:
address NEQ1487242:18
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:20:
address NEQ1487242:20
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:5:
address NEQ1487242:5
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:6:
address NEQ1487242:6
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:7:
address NEQ1487242:7
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:8:
address NEQ1487242:8
addtype chn
valid 1
HM-PB-4Dis-WM-2 NEQ1487242:9:
address NEQ1487242:9
addtype chn
valid 1
HM-RC-4-3 NEQ1138746:1:
address NEQ1138746:1
addtype chn
valid 1
HM-RC-4-3 NEQ1138746:2:
address NEQ1138746:2
addtype chn
valid 1
HM-RC-4-3 NEQ1138746:3:
address NEQ1138746:3
addtype chn
valid 1
HM-RC-4-3 NEQ1138746:4:
address NEQ1138746:4
addtype chn
valid 1
HM-RC-Key4-3 REQ0632285:3:
address REQ0632285:3
addtype chn
valid 1
HM-RC-Key4-3 REQ0632285:4:
address REQ0632285:4
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:1:
address BidCoS-RF:1
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:10:
address BidCoS-RF:10
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:11:
address BidCoS-RF:11
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:12:
address BidCoS-RF:12
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:13:
address BidCoS-RF:13
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:14:
address BidCoS-RF:14
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:15:
address BidCoS-RF:15
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:16:
address BidCoS-RF:16
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:17:
address BidCoS-RF:17
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:18:
address BidCoS-RF:18
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:19:
address BidCoS-RF:19
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:2:
address BidCoS-RF:2
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:20:
address BidCoS-RF:20
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:21:
address BidCoS-RF:21
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:22:
address BidCoS-RF:22
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:23:
address BidCoS-RF:23
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:24:
address BidCoS-RF:24
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:25:
address BidCoS-RF:25
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:26:
address BidCoS-RF:26
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:27:
address BidCoS-RF:27
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:28:
address BidCoS-RF:28
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:29:
address BidCoS-RF:29
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:3:
address BidCoS-RF:3
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:30:
address BidCoS-RF:30
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:31:
address BidCoS-RF:31
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:32:
address BidCoS-RF:32
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:33:
address BidCoS-RF:33
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:34:
address BidCoS-RF:34
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:35:
address BidCoS-RF:35
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:36:
address BidCoS-RF:36
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:37:
address BidCoS-RF:37
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:38:
address BidCoS-RF:38
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:39:
address BidCoS-RF:39
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:4:
address BidCoS-RF:4
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:40:
address BidCoS-RF:40
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:41:
address BidCoS-RF:41
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:42:
address BidCoS-RF:42
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:43:
address BidCoS-RF:43
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:44:
address BidCoS-RF:44
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:45:
address BidCoS-RF:45
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:46:
address BidCoS-RF:46
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:47:
address BidCoS-RF:47
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:48:
address BidCoS-RF:48
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:49:
address BidCoS-RF:49
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:5:
address BidCoS-RF:5
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:50:
address BidCoS-RF:50
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:6:
address BidCoS-RF:6
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:7:
address BidCoS-RF:7
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:8:
address BidCoS-RF:8
addtype chn
valid 1
HM-RCV-50 BidCoS-RF:9:
address BidCoS-RF:9
addtype chn
valid 1
HM_RCV_50BidCoS_RF:
address BidCoS-RF
addtype dev
valid 1
HM_RCV_50BidCoS_RF:0:
address BidCoS-RF:0
addtype chn
valid 1
HmIP-FAL24-C6 000615699CED0A:10:
address 000615699CED0A:10
addtype chn
valid 1
HmIP-FAL24-C6 000615699CED0A:6:
address 000615699CED0A:6
addtype chn
valid 1
HmIP-FAL24-C6 000615699CED0A:7:
address 000615699CED0A:7
addtype chn
valid 1
HmIP-FAL24-C6 000615699CED0A:8:
address 000615699CED0A:8
addtype chn
valid 1
HmIP-FAL24-C6 000615699CED0A:9:
address 000615699CED0A:9
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:1:
address HmIP-RCV-1:1
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:10:
address HmIP-RCV-1:10
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:11:
address HmIP-RCV-1:11
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:12:
address HmIP-RCV-1:12
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:13:
address HmIP-RCV-1:13
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:14:
address HmIP-RCV-1:14
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:15:
address HmIP-RCV-1:15
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:16:
address HmIP-RCV-1:16
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:17:
address HmIP-RCV-1:17
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:18:
address HmIP-RCV-1:18
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:19:
address HmIP-RCV-1:19
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:2:
address HmIP-RCV-1:2
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:20:
address HmIP-RCV-1:20
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:21:
address HmIP-RCV-1:21
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:22:
address HmIP-RCV-1:22
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:23:
address HmIP-RCV-1:23
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:24:
address HmIP-RCV-1:24
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:25:
address HmIP-RCV-1:25
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:26:
address HmIP-RCV-1:26
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:27:
address HmIP-RCV-1:27
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:28:
address HmIP-RCV-1:28
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:29:
address HmIP-RCV-1:29
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:3:
address HmIP-RCV-1:3
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:30:
address HmIP-RCV-1:30
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:31:
address HmIP-RCV-1:31
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:32:
address HmIP-RCV-1:32
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:33:
address HmIP-RCV-1:33
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:34:
address HmIP-RCV-1:34
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:35:
address HmIP-RCV-1:35
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:36:
address HmIP-RCV-1:36
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:37:
address HmIP-RCV-1:37
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:38:
address HmIP-RCV-1:38
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:39:
address HmIP-RCV-1:39
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:4:
address HmIP-RCV-1:4
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:40:
address HmIP-RCV-1:40
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:41:
address HmIP-RCV-1:41
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:42:
address HmIP-RCV-1:42
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:43:
address HmIP-RCV-1:43
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:44:
address HmIP-RCV-1:44
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:45:
address HmIP-RCV-1:45
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:46:
address HmIP-RCV-1:46
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:47:
address HmIP-RCV-1:47
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:48:
address HmIP-RCV-1:48
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:49:
address HmIP-RCV-1:49
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:5:
address HmIP-RCV-1:5
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:50:
address HmIP-RCV-1:50
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:6:
address HmIP-RCV-1:6
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:7:
address HmIP-RCV-1:7
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:8:
address HmIP-RCV-1:8
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:9:
address HmIP-RCV-1:9
addtype chn
valid 1
HmIP-WTH-2 000A97098ED06C:3:
address 000A97098ED06C:3
addtype chn
valid 1
HmIP-WTH-2 000A97098ED06C:4:
address 000A97098ED06C:4
addtype chn
valid 1
HmIP-WTH-2 000A97098ED06C:5:
address 000A97098ED06C:5
addtype chn
valid 1
HmIP-WTH-2 000A97098ED06C:6:
address 000A97098ED06C:6
addtype chn
valid 1
HmIP-WTH-2 000A97098ED86C:3:
address 000A97098ED86C:3
addtype chn
valid 1
HmIP-WTH-2 000A97098ED86C:4:
address 000A97098ED86C:4
addtype chn
valid 1
HmIP-WTH-2 000A97098ED86C:5:
address 000A97098ED86C:5
addtype chn
valid 1
HmIP-WTH-2 000A97098ED86C:6:
address 000A97098ED86C:6
addtype chn
valid 1
HmIP-WTH-2 000A97098ED86C:7:
address 000A97098ED86C:7
addtype chn
valid 1
HmIP_RCV_50HmIP_RCV_1:
address HmIP-RCV-1
addtype dev
valid 1
HmIP_RCV_50HmIP_RCV_1:0:
address HmIP-RCV-1:0
addtype chn
valid 1
PC:
address 000A97098ED06C:1
addtype chn
valid 1
PC 1:
address 000A97098ED06C:2
addtype chn
valid 1
PC 2:
address 000615699CED0A:4
addtype chn
valid 1
Pumpe:
address 000615699CED0A:1
addtype chn
valid 1
R_K_Z:
address NEQ1688009:1
addtype chn
valid 1
Radiator:
address 000615699CED0A:3
addtype chn
valid 1
Rollo Büro kleines Fenster:
address MEQ1893449:1
addtype chn
valid 1
Rollo_Badezimmer:
address NEQ1688560:1
addtype chn
valid 1
Rolo Schlafz:
address NEQ1688542:1
addtype chn
valid 1
S_Bad Fußboden 1:
address 000A97098ED065:1
addtype chn
valid 1
S_Bad_Fussboden:
address 000A97098ED065
addtype dev
valid 1
S_Bad_Fussboden:0:
address 000A97098ED065:0
addtype chn
valid 1
S_Fußboden 2:
address 000A97098ED065:2
addtype chn
valid 1
S_Fußboden 3:
address 000A97098ED065:3
addtype chn
valid 1
S_Fußboden 4:
address 000A97098ED065:4
addtype chn
valid 1
S_Fußboden 5:
address 000A97098ED065:5
addtype chn
valid 1
S_Fußboden 6:
address 000A97098ED065:6
addtype chn
valid 1
S_Fußboden 7:
address 000A97098ED065:7
addtype chn
valid 1
S_PC:
address 000A97098ED06C
addtype dev
valid 1
S_PC:0:
address 000A97098ED06C:0
addtype chn
valid 1
S_Wohnzimmer:
address 000A97098ED86C
addtype dev
valid 1
S_Wohnzimmer:0:
address 000A97098ED86C:0
addtype chn
valid 1
Schlafz rauf:
address NEQ1487016:2
addtype chn
valid 1
Schlafzimmer runter:
address NEQ1487016:1
addtype chn
valid 1
V_Heizung_1_Stock:
address 000615699CED0A
addtype dev
valid 1
V_Heizung_1_Stock:0:
address 000615699CED0A:0
addtype chn
valid 1
WohnZ:
address 000A97098ED86C:1
addtype chn
valid 1
WohnZ 1:
address 000615699CED0A:5
addtype chn
valid 1
Wohnz Fenster:
address OEQ0268310:1
addtype chn
valid 1
Wohnz Fenster down:
address NEQ1487242:3
addtype chn
valid 1
Wohnz Fenster up:
address NEQ1487242:4
addtype chn
valid 1
Wohnz T�r:
address OEQ0268274:1
addtype chn
valid 1
Wohnz T�r down:
address NEQ1487242:1
addtype chn
valid 1
Wohnz T�r up:
address NEQ1487242:2
addtype chn
valid 1
Wohnzimmer:
address 000A97098ED86C:2
addtype chn
valid 1
_Rollo_Bad:
address NEQ1688560
addtype dev
valid 1
_Rollo_Bad:0:
address NEQ1688560:0
addtype chn
valid 1
_Rollo_Buero:
address NEQ1688009
addtype dev
valid 1
_Rollo_Buero:0:
address NEQ1688009:0
addtype chn
valid 1
_Rollo_Buero_ k_Fenster:
address MEQ1893449
addtype dev
valid 1
_Rollo_Buero_ k_Fenster:0:
address MEQ1893449:0
addtype chn
valid 1
_Rollo_Schlafzimmer:
address NEQ1688542
addtype dev
valid 1
_Rollo_Schlafzimmer:0:
address NEQ1688542:0
addtype chn
valid 1
_T_Garten_Fenster:
address OEQ0268310
addtype dev
valid 1
_T_Garten_Fenster:0:
address OEQ0268310:0
addtype chn
valid 1
_T_Garten_Tuer:
address OEQ0268274
addtype dev
valid 1
_T_Garten_Tuer:0:
address OEQ0268274:0
addtype chn
valid 1
_T_oben:
address NEQ1487016
addtype dev
valid 1
_T_oben:0:
address NEQ1487016:0
addtype chn
valid 1
_unten_Taster:
address NEQ1487242
addtype dev
valid 1
_unten_Taster:0:
address NEQ1487242:0
addtype chn
valid 1
ccu:
chncount 203
delay 180
delayed 0
devcount 17
gcount 0
ifcount 3
prgcount 12
sync 1
timeout 180
ccuTypes:
supported HM-LC-Bl1-FM,HM-LC-Bl1-FM,HM-LC-Bl1-FM,HM-LC-Bl1-FM,HM-LC-Bl1PBU-FM,HM-LC-Bl1PBU-FM,HM-LC-Sw1-Pl-CT-R1,HM-PB-4Dis-WM-2,HM-PB-4Dis-WM-2,HM-RC-4-3,HM-RC-Key4-3,HmIP-FAL24-C6,HmIP-WTH-2,HmIP-WTH-2,HmIP-WTH-2
unsupported HM-RCV-50,HmIP-RCV-50
control:
dev:
000615699CED0A:
addtype dev
channels 11
direction 0
interface HmIP-RF
name V_Heizung_1_Stock
type HmIP-FAL24-C6
valid 1
000615699CED0A:0:
addtype chn
channels 1
direction 0
name V_Heizung_1_Stock:0
valid 1
000615699CED0A:1:
addtype chn
channels 1
direction 2
name Pumpe
valid 1
000615699CED0A:10:
addtype chn
channels 1
direction 2
name HmIP-FAL24-C6 000615699CED0A:10
valid 1
000615699CED0A:2:
addtype chn
channels 1
direction 2
name Bad
valid 1
000615699CED0A:3:
addtype chn
channels 1
direction 2
name Radiator
valid 1
000615699CED0A:4:
addtype chn
channels 1
direction 2
name PC 2
valid 1
000615699CED0A:5:
addtype chn
channels 1
direction 2
name WohnZ 1
valid 1
000615699CED0A:6:
addtype chn
channels 1
direction 2
name HmIP-FAL24-C6 000615699CED0A:6
valid 1
000615699CED0A:7:
addtype chn
channels 1
direction 1
name HmIP-FAL24-C6 000615699CED0A:7
valid 1
000615699CED0A:8:
addtype chn
channels 1
direction 1
name HmIP-FAL24-C6 000615699CED0A:8
valid 1
000615699CED0A:9:
addtype chn
channels 1
direction 1
name HmIP-FAL24-C6 000615699CED0A:9
valid 1
000A97098ED065:
addtype dev
channels 8
direction 0
interface HmIP-RF
name S_Bad_Fussboden
type HmIP-WTH-2
valid 1
000A97098ED065:0:
addtype chn
channels 1
direction 0
name S_Bad_Fussboden:0
valid 1
000A97098ED065:1:
addtype chn
channels 1
direction 1
name S_Bad Fußboden 1
valid 1
000A97098ED065:2:
addtype chn
channels 1
direction 2
name S_Fußboden 2
valid 1
000A97098ED065:3:
addtype chn
channels 1
direction 1
name S_Fußboden 3
valid 1
000A97098ED065:4:
addtype chn
channels 1
direction 2
name S_Fußboden 4
valid 1
000A97098ED065:5:
addtype chn
channels 1
direction 1
name S_Fußboden 5
valid 1
000A97098ED065:6:
addtype chn
channels 1
direction 2
name S_Fußboden 6
valid 1
000A97098ED065:7:
addtype chn
channels 1
direction 1
name S_Fußboden 7
valid 1
000A97098ED06C:
addtype dev
channels 8
direction 0
interface HmIP-RF
name S_PC
type HmIP-WTH-2
valid 1
000A97098ED06C:0:
addtype chn
channels 1
direction 0
name S_PC:0
valid 1
000A97098ED06C:1:
addtype chn
channels 1
direction 1
name PC
valid 1
000A97098ED06C:2:
addtype chn
channels 1
direction 2
name PC 1
Sowohl die d_ccu als auch die RPCs stehen auf "inactive/OK". Die sollten aber auf "running/OK" stehen.
Irgendwas scheint mit der Kommunikation zwischen RasperypiMatic und FHEM nicht zu stimmen.
Bitte die sichere Neuverbinden-Variante ausprobieren:
- FHEM runterfahren
- RasperypiMatic runterfahren
- RasperypiMatic wieder starten
- warten bis die UI von RasperypiMatic erreichbar ist
- nochmal 2-3 Minuten warten, weil die nach dem Start recht viel zu tun hat
- FHEM wieder starten
- prüfen, ob das jetzt auf "running/OK" steht
Wenn nicht, bitte mal die relevanten Zeilen aus dem FHEM Logfile posten
Besten Dank für Deine Antwort. Wie Du bestimmt schon erkannt hast ist es ein Testaufbau
da sind wohl die Ports nicht frei, aber wo ändere ich die. In der CCU Software hab ich da schon was gefunden, ob es das richtige ist ?
ich nutze RaspiMatic
Ich habe folgendes:
2022-11-23_13:08:07 Logfile clear
2022.11.23 13:11:34 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process started for interface BidCos-RF with PID=29153
2022.11.23 13:11:34 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Initializing RPC server CB2001178100178003 for interface BidCos-RF
2022.11.23 13:11:34 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server starting
2022.11.23 13:11:34 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process started for interface HmIP-RF with PID=29154
2022.11.23 13:11:34 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Initializing RPC server CB2010178100178003 for interface HmIP-RF
2022.11.23 13:11:34 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server starting
2022.11.23 13:11:34 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Can't create RPC callback server CB2001178100178003. Port 7411 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:11:34 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Can't create RPC callback server CB2010178100178003. Port 7420 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Checking if RPC server process is running
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process not running. Cleaning up
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process CB2001178100178003 not runnning
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Stop I/O handling
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Checking if RPC server process is running
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process not running. Cleaning up
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:11:59 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process CB2010178100178003 not runnning
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Stop I/O handling
2022.11.23 13:11:59 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:12:01 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process started for interface HmIP-RF with PID=29155
2022.11.23 13:12:01 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Initializing RPC server CB2010178100178003 for interface HmIP-RF
2022.11.23 13:12:01 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server starting
2022.11.23 13:12:01 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process started for interface BidCos-RF with PID=29156
2022.11.23 13:12:01 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Initializing RPC server CB2001178100178003 for interface BidCos-RF
2022.11.23 13:12:01 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server starting
2022.11.23 13:12:01 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Can't create RPC callback server CB2010178100178003. Port 7420 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:12:01 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Can't create RPC callback server CB2001178100178003. Port 7411 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Checking if RPC server process is running
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process not running. Cleaning up
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process CB2010178100178003 not runnning
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Stop I/O handling
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Checking if RPC server process is running
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process not running. Cleaning up
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:12:26 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process CB2001178100178003 not runnning
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Stop I/O handling
2022.11.23 13:12:26 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:14:37 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process started for interface BidCos-RF with PID=29170
2022.11.23 13:14:37 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Initializing RPC server CB2001178100178003 for interface BidCos-RF
2022.11.23 13:14:37 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server starting
2022.11.23 13:14:37 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process started for interface HmIP-RF with PID=29171
2022.11.23 13:14:37 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Initializing RPC server CB2010178100178003 for interface HmIP-RF
2022.11.23 13:14:37 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Can't create RPC callback server CB2001178100178003. Port 7411 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:14:37 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server starting
2022.11.23 13:14:37 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Can't create RPC callback server CB2010178100178003. Port 7420 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Checking if RPC server process is running
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process not running. Cleaning up
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process CB2001178100178003 not runnning
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Stop I/O handling
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Checking if RPC server process is running
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process not running. Cleaning up
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:15:02 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process CB2010178100178003 not runnning
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Stop I/O handling
2022.11.23 13:15:02 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:24:10 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process started for interface BidCos-RF with PID=29218
2022.11.23 13:24:10 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Initializing RPC server CB2001178100178003 for interface BidCos-RF
2022.11.23 13:24:10 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server starting
2022.11.23 13:24:10 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process started for interface HmIP-RF with PID=29219
2022.11.23 13:24:10 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Initializing RPC server CB2010178100178003 for interface HmIP-RF
2022.11.23 13:24:10 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Can't create RPC callback server CB2001178100178003. Port 7411 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:24:10 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server starting
2022.11.23 13:24:10 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Can't create RPC callback server CB2010178100178003. Port 7420 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Checking if RPC server process is running
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process not running. Cleaning up
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process CB2001178100178003 not runnning
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Stop I/O handling
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Checking if RPC server process is running
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process not running. Cleaning up
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:24:35 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process CB2010178100178003 not runnning
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Stop I/O handling
2022.11.23 13:24:35 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003VirtualDevices] Found no running processes. Cleaning up ...
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003VirtualDevices] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003VirtualDevices] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Found no running processes. Cleaning up ...
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Found no running processes. Cleaning up ...
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:27:48 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:27:48 1: HMCCU [d_ccu] Immediate shutdown
2022.11.23 13:27:48 1: HMCCU [d_ccu] No RPC device defined for interface HmIP-RF
2022.11.23 13:27:48 0: HMCCU [d_ccu] HMCCU: Can't find RPC device
2022.11.23 13:27:48 1: HMCCU [d_ccu] No RPC device defined for interface BidCos-RF
2022.11.23 13:27:48 0: HMCCU [d_ccu] HMCCU: Can't find RPC device
2022.11.23 13:27:48 1: Including fhem.cfg
2022.11.23 13:27:48 3: WEB: port 8083 opened
2022.11.23 13:27:48 2: eventTypes: loaded 21 lines from ./log/eventTypes.txt
2022.11.23 13:27:48 3: myMQTT2_SERVER: port 1883 opened
2022.11.23 13:27:48 1: HMCCU [d_ccu] CCU port 8181 is reachable
2022.11.23 13:27:48 1: HMCCU [d_ccu] Initialized version 5.0 213011850
2022.11.23 13:27:48 1: HMCCU [d_ccu] Initializing device
2022.11.23 13:27:48 2: HMCCU [d_ccu] Deleting old groups
2022.11.23 13:27:48 2: HMCCU [d_ccu] Updating device table
2022.11.23 13:27:48 1: HMCCU [d_ccu] Read 17 devices with 203 channels from CCU 192.168.178.3
2022.11.23 13:27:48 1: HMCCU [d_ccu] Read 12 programs from CCU 192.168.178.3
2022.11.23 13:27:48 1: HMCCU [d_ccu] Read 0 virtual groups from CCU 192.168.178.3
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Initialized version 5.0 212981850 for interface HmIP-RF with I/O device d_ccu
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Initialized version 5.0 212981850 for interface BidCos-RF with I/O device d_ccu
2022.11.23 13:27:48 1: HMCCURPCPROC [d_rpc178003VirtualDevices] Initialized version 5.0 212981850 for interface VirtualDevices with I/O device d_ccu
2022.11.23 13:27:48 1: Including ./log/fhem.save
2022.11.23 13:28:40 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:8181/tclrega.exe
2022.11.23 13:31:59 2: HMCCU [d_ccu] RPC device for interface HmIP-RF: d_rpc178003HmIP_RF
2022.11.23 13:31:59 2: HMCCU [d_ccu] RPC device for interface BidCos-RF: d_rpc178003BidCos_RF
2022.11.23 13:31:59 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process started for interface HmIP-RF with PID=29241
2022.11.23 13:31:59 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Initializing RPC server CB2010178100178003 for interface HmIP-RF
2022.11.23 13:31:59 4: HMCCURPCPROC [d_rpc178003HmIP_RF] Set state to busy
2022.11.23 13:31:59 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server starting
2022.11.23 13:31:59 4: HMCCURPCPROC [d_rpc178003HmIP_RF] Set rpcstate to starting
2022.11.23 13:31:59 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process started for interface BidCos-RF with PID=29242
2022.11.23 13:31:59 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Initializing RPC server CB2001178100178003 for interface BidCos-RF
2022.11.23 13:31:59 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Can't create RPC callback server CB2010178100178003. Port 7420 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:31:59 4: HMCCURPCPROC [d_rpc178003BidCos_RF] Set state to busy
2022.11.23 13:31:59 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server starting
2022.11.23 13:31:59 4: HMCCURPCPROC [d_rpc178003BidCos_RF] Set rpcstate to starting
2022.11.23 13:31:59 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Can't create RPC callback server CB2001178100178003. Port 7411 in use?
Can't use string ("0") as a HASH ref while "strict refs" in use at ./FHEM/88_HMCCURPCPROC.pm line 2086.
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Checking if RPC server process is running
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process not running. Cleaning up
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003HmIP_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server process CB2010178100178003 not runnning
2022.11.23 13:32:24 4: HMCCURPCPROC [d_rpc178003HmIP_RF] Set rpcstate to inactive
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003HmIP_RF] Stop I/O handling
2022.11.23 13:32:24 3: HMCCURPCPROC [d_rpc178003HmIP_RF] Close child socket
2022.11.23 13:32:24 3: HMCCURPCPROC [d_rpc178003HmIP_RF] Close parent socket
2022.11.23 13:32:24 4: HMCCURPCPROC [d_rpc178003HmIP_RF] Set state to OK
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003HmIP_RF] RPC server stopped. Cancel delayed shutdown.
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Checking if RPC server process is running
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process not running. Cleaning up
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003BidCos_RF] Housekeeping called. Cleaning up RPC environment
2022.11.23 13:32:24 1: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server process CB2001178100178003 not runnning
2022.11.23 13:32:24 4: HMCCURPCPROC [d_rpc178003BidCos_RF] Set rpcstate to inactive
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003BidCos_RF] Stop I/O handling
2022.11.23 13:32:24 3: HMCCURPCPROC [d_rpc178003BidCos_RF] Close child socket
2022.11.23 13:32:24 3: HMCCURPCPROC [d_rpc178003BidCos_RF] Close parent socket
2022.11.23 13:32:24 4: HMCCURPCPROC [d_rpc178003BidCos_RF] Set state to OK
2022.11.23 13:32:24 2: HMCCURPCPROC [d_rpc178003BidCos_RF] RPC server stopped. Cancel delayed shutdown.
Dies kommt mit get d_ccu ccuDevices
Name Model Interface Address Channels Supported roles
HM_RCV_50BidCoS_RF HM-RCV-50 BidCos-RF BidCoS-RF 51 VIRTUAL_KEY [50x]
_Rollo_Buero_ k_Fenster HM-LC-Bl1-FM BidCos-RF MEQ1893449 2 BLIND [1x]
4_fach_1 HM-RC-4-3 BidCos-RF NEQ1138746 5 KEY [4x]
Garage HM-LC-Sw1-Pl-CT-R1 BidCos-RF NEQ1263862 2 SWITCH [1x]
_T_oben HM-PB-4Dis-WM-2 BidCos-RF NEQ1487016 21 KEY [20x]
_unten_Taster HM-PB-4Dis-WM-2 BidCos-RF NEQ1487242 21 KEY [20x]
_Rollo_Buero HM-LC-Bl1-FM BidCos-RF NEQ1688009 2 BLIND [1x]
_Rollo_Schlafzimmer HM-LC-Bl1-FM BidCos-RF NEQ1688542 2 BLIND [1x]
_Rollo_Bad HM-LC-Bl1-FM BidCos-RF NEQ1688560 2 BLIND [1x]
_T_Garten_Tuer HM-LC-Bl1PBU-FM BidCos-RF OEQ0268274 2 BLIND [1x]
_T_Garten_Fenster HM-LC-Bl1PBU-FM BidCos-RF OEQ0268310 2 BLIND [1x]
Garage_ext1 HM-RC-Key4-3 BidCos-RF REQ0632285 5 KEY [4x]
1_Stock HmIP-FAL24-C6 HmIP-RF 000615699CED0A 11
S_Bad_Fussboden HmIP-WTH-2 HmIP-RF 000A97098ED065 8 HEATING_CLIMATECONTROL_TRANSCEIVER [1x]
S_PC HmIP-WTH-2 HmIP-RF 000A97098ED06C 8 HEATING_CLIMATECONTROL_TRANSCEIVER [1x]
S_Wohnzimmer HmIP-WTH-2 HmIP-RF 000A97098ED86C 8 HEATING_CLIMATECONTROL_TRANSCEIVER [1x]
HmIP_RCV_50HmIP_RCV_1 HmIP-RCV-50 HmIP-RF HmIP-RCV-1 51 KEY_TRANSCEIVER [50x]
und dies steht im LOG
2022.11.23 14:29:45 1: PERL WARNING: Use of uninitialized value $an in hash element at ./FHEM/88_HMCCU.pm line 6622.
wenn ich
get d_ccu createDev 1Stock aufrufe
(ps ich hatte den Namen geändert damit er nicht so lang ist!!)
alle anderen Devices lassen sich mit dieser Methode anlegen!!wie hier zu sehen ist
2022.11.23 14:25:59 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:25:59 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:25:59 2: HMCCU [d_ccu] Read 95 Paramset Descriptions for interface BidCos-RF
2022.11.23 14:25:59 2: HMCCU [d_ccu] Reading Peer Descriptions for interface BidCos-RF
2022.11.23 14:25:59 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:25:59 2: HMCCU [d_ccu] Read 28 Peer Descriptions for interface BidCos-RF
2022.11.23 14:29:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:29:45 1: PERL WARNING: Use of uninitialized value $an in hash element at ./FHEM/88_HMCCU.pm line 6622.
2022.11.23 14:34:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:39:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:44:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:49:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:54:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
2022.11.23 14:58:01 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:8181/tclrega.exe
2022.11.23 14:58:02 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 3398.
2022.11.23 14:58:02 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 3400.
2022.11.23 14:58:02 2: HMCCU [d_ccu] Attr command failed S_Bad_Fussboden ^(.+\.)?UNREACH$:activity . S_Bad_Fussboden: bad attribute name '^(.+\.)?UNREACH$:activity' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:02 2: HMCCU [d_ccu] Attr command failed S_Bad_Fussboden . S_Bad_Fussboden: bad attribute name '' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:02 2: HMCCU [d_ccu] Attr command failed S_Bad_Fussboden ^(.+\.)?LOW_?BAT$:battery . S_Bad_Fussboden: bad attribute name '^(.+\.)?LOW_?BAT$:battery' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:12 2: AttrTemplates: got 230 entries
2022.11.23 14:58:31 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:8181/tclrega.exe
2022.11.23 14:58:31 2: HMCCU [d_ccu] Attr command failed S_PC . S_PC: bad attribute name '' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:31 2: HMCCU [d_ccu] Attr command failed S_PC ^(.+\.)?UNREACH$:activity . S_PC: bad attribute name '^(.+\.)?UNREACH$:activity' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:31 2: HMCCU [d_ccu] Attr command failed S_PC ^(.+\.)?LOW_?BAT$:battery . S_PC: bad attribute name '^(.+\.)?LOW_?BAT$:battery' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:40 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:8181/tclrega.exe
2022.11.23 14:58:43 2: HMCCU [d_ccu] Attr command failed S_Wohnzimmer ^(.+\.)?LOW_?BAT$:battery . S_Wohnzimmer: bad attribute name '^(.+\.)?LOW_?BAT$:battery' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:43 2: HMCCU [d_ccu] Attr command failed S_Wohnzimmer ^(.+\.)?UNREACH$:activity . S_Wohnzimmer: bad attribute name '^(.+\.)?UNREACH$:activity' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:58:43 2: HMCCU [d_ccu] Attr command failed S_Wohnzimmer . S_Wohnzimmer: bad attribute name '' (allowed chars: A-Za-z/\d_\.-)
2022.11.23 14:59:13 4: HMCCU [d_ccu] Build URL = http://192.168.178.3:2001
Bitte mal die Ausgabe von
get d_ccu deviceInfo 1Stock
Die Rollen des Device werden momentan nicht unterstützt. Du kannst das Device aber mit einem normalen define als HMCCUDEV oder auch als ein oder mehrere HMCCUCHN anlegen.
Du scheinst auch nicht die letzte Version von HMCCU zu nutzen, da die Fehler im Log nicht zum Code passen.
Hier die Info :
HMCCU: d_ccu Invalid device/channel name or address. 1Stock
Update durchgeführt, jetzt läuft der RPCServer auch stabiler.
Danke.
Könntest Du mir sagen wo ich dazu Beispiele finde. Im moment wird der FAL durch den RaspiMaticCCU angesteuert.
Die Zustände werden aber nicht in fhem verarbeitet.
Bisher habe ich keine mir verständliche Info was den Unterschied von HMCCUDEV und HMCCUCHN ist, gefunden. Kannst Du mir da helfen?
Oder noch viel besser , was ist mit dem DEV in fhem machbar?
Lies mal die Wiki Artikel, v.a. zu HMCCU und HMCCUDEV. Da sollten die meisten Deiner Fragen beantwortet werden.
Die Doku von EQ-3 ist auch recht interessant, wenn es um das Konzept hinter Homematic geht (Geräte, Kanäle, Datenpunkte).
Hallo Zap, Danke habe ich gemacht.
Trotzdem habe ich zu der Sache noch Fragen, evtl gehören die nicht hier hin! Für mich ist es aber immer noch das Thema.
Also
1. Die Devices haben Internals,Reading, Attribute
Für mich also folgendes Problem
das Device S_AWohnZ hat folgende Daten:Internals
CFGFN
DEF
000A97098ED86C:1
FUUID
63834940-f33f-e8dd-8526-22007d6ad9c4ea3c
IODev
d_ccu
NAME
S_AWohnZ
NR
238
STATE
13.1
TYPE
HMCCUCHN
ccuaddr
000A97098ED86C:1
ccudevstate
active
ccuif
HmIP-RF
ccuname
AWohnZ_1
ccurolectrl
HEATING_CLIMATECONTROL_TRANSCEIVER
ccurolestate
HEATING_CLIMATECONTROL_TRANSCEIVER
ccusubtype
WTH-2
ccutype
HmIP-WTH-2
eventCount
75
firmware
2.8.2
readonly
no
Readings
AWohnZ_1.ACTIVE_PROFILE
1
2022-11-27 13:56:42
AWohnZ_1.ACTUAL_TEMPERATURE
13.1
2022-11-27 13:56:42
AWohnZ_1.ACTUAL_TEMPERATURE_STATUS
NORMAL
2022-11-27 13:56:42
AWohnZ_1.BOOST_MODE
false
2022-11-27 13:56:42
AWohnZ_1.BOOST_TIME
0
2022-11-27 13:56:42
AWohnZ_1.FROST_PROTECTION
false
2022-11-27 13:56:42
AWohnZ_1.HEATING_COOLING
HEATING
2022-11-27 13:56:42
AWohnZ_1.HUMIDITY
49
2022-11-27 13:56:42
AWohnZ_1.HUMIDITY_STATUS
NORMAL
2022-11-27 13:56:42
AWohnZ_1.PARTY_MODE
false
2022-11-27 13:56:42
AWohnZ_1.PARTY_SET_POINT_TEMPERATURE
0.0
2022-11-27 12:25:52
AWohnZ_1.PARTY_TIME_END
2022-11-27 12:25:52
AWohnZ_1.PARTY_TIME_START
2022-11-27 12:25:52
AWohnZ_1.QUICK_VETO_TIME
0
2022-11-27 13:56:42
AWohnZ_1.SET_POINT_MODE
auto
2022-11-27 13:56:42
AWohnZ_1.SET_POINT_TEMPERATURE
15.5
2022-11-27 13:56:42
AWohnZ_1.SWITCH_POINT_OCCURED
false
2022-11-27 13:56:42
AWohnZ_1.WINDOW_STATE
closed
2022-11-27 13:56:42
activity
alive
2022-11-27 13:56:42
battery
ok
2022-11-27 13:56:42
control
15.5
2022-11-27 13:56:42
devstate
ok
2022-11-27 13:56:42
hmstate
13.1
2022-11-27 13:56:42
rssidevice
-50
2022-11-27 13:56:42
rssipeer
-58
2022-11-27 13:10:14
state
13.1
2022-11-27 13:56:42
voltage
2.6
2022-11-27 13:56:42
Attributes
cmdIcon
auto:sani_heating_automatic manu:sani_heating_manual boost:sani_heating_boost on:general_an off:general_aus
deleteattr
room
Heizung,Homematic
deleteattr
substexcl
desired-temp
deleteattr
webCmd
desired-temp:auto:manu:boost:on:off
deleteattr
widgetOverride
desired-temp:slider,4.5,0.5,30.5,1
Dises Device lässt es zu das ich die Vorgabe Temp einstelle, es wird auch übermittelt, wenn ich aber den Client aktualisiere kommt die alte Vorgabe wieder, ohne das diese an das Device geschickt wird.
2. die Infos werden sehr sporadisch in ein Logfile geschrieben und es sind viel zu viele Infos die mit dem Befehl createlog angelegt wurden.
Wenn ich nun versuche diese zu minimieren, habe ich gar kein logfile mehr??
hier sitze ich jetzt schon 3 Tage dran und sehe wahrscheinlich den "Kleinen Fehler" nicht
Es wäre wirklich nett , wenn Du mir eine Tipp dazu geben würdest.
Sobald diese Infos da sind möchte ich mit dem Ergebnis den Kanal finden und Steuern der im FAL24 dafür vorgesehen ist.
Ich habe im Augenblick 4 der Thermostate HmIP-RF angeschlossen die Daten werden eigentlich immer nur auf dem zuletzt angelegten richtig angezeigt, weil eben auch die Logfiles der zuerst angelegte nicht mehr nachgehalten werden!
Wie gesagt ich suche seit Tagen nach dem Grund./Gründen, habe aber noch keinen wirklichen Ansatz!
Gruß
Roland
Hallo Zap, ich drehe mich immer mehr im Kreis und glaube schon fast ich mach mit Homematic nicht mehr weiter.
Die d_ccu ist angelegt und dort kann ich auch die devices die ich mit
get createdev finde auch anlegen, das dev FAL24..... ist zwar zu sehen es wird aber nicht definiert.
Die Dokus habe ich gelesen und probiert, wenn ich davon etwas anlege, stürzt mir der Service ab.
Also werde ich da wohl etwas falsch machen ich sehe aber nicht was.
Ich habe auch schon versucht Dir direkt per pm zu senden aber das ist ja nicht möglich.
Ich weiss jetzt also nicht wie ich weiter machen soll.
Ich kann mit den WTH-2 Temp um Hum lesen und die gewünschte Temp am WTH-2 einstellen, sogar die Slider funktionieren, solange ich eben keine HMCCUDEV oder CHN für das FAL24 anlege. jedoch von dem Punkt das ich das aus fhem mache und dann dort eine Steuerung aufbaue bin ich weit entfernt.
Es wäre sehr nett wenn Du einen weiteren Tipp für mich hättest.
Besten DAnk
P.S der Name ist zwar Speedy.Bear ich hab durchaus gedult. es macht nur keinen Spass Tage an dem Problem nicht weiter zu kommen und dabei zu sehen das vieles aus der Doku gar nicht mehr stimmt
Gruß
Roland