Seite drucken - HMCCU legt kein Device an

Guten Abend zusammen,

ich betreibe homatic mit pivccu und einem HMIP-RFUSB auf einem rasperry pi 4. In fhem habe ich das Modul HMCCU angelegt und auch den rpcserver konfigueriert nach Anleitung (https://wiki.fhem.de/wiki/HMCCU_Best_Practice (https://wiki.fhem.de/wiki/HMCCU_Best_Practice)), sieht für mich erstmal ok aus. In der CCU habe ich das Thermostat angelernt und kann es auch steuern (Typ: HmIP-eTRV-B)

Leider klappt der Aufruf createDev nicht, als Ergebnis wird mir immer ein leeres Fenster angezeigt. Als Device findet fhem nur ein Gateway "HM-RCV-50 BidCoS-RF", dieses anzulegen klappte auch nicht.
Unter list hmCCU3 (s.u.) finde ich aber das Thermostat und noch ein weiteres HMIP Gateway.

Meine Syntax war etwa: get hmCCU3 createDev ^HZ_OG_ARZ$ - ich habe aber auch viel ausprobiert, mit RegEx und ohne, per define Befehl in HMCCUCHN oder DEV, klappt nicht. Keinen Channel kein dev nichts gefunden.

Schonmal danke und viele Grüße,
Sebastian

Hier noch ein Auszug von list hmCCU3:

Code Auswählen


Internals:
   CCUNum     1
   Clients    :HMCCUDEV:HMCCUCHN:HMCCURPCPROC:
   DEF        192.168.1.192
   FUUID      636ab5cd-f33f-c6e7-c27e-acf53660bf85722c
   NAME       hmCCU3
   NOTIFYDEV  global
   NR         55
   NTFY_ORDER 50-hmCCU3
   RPCState   running
   STATE      running/Error
   TYPE       HMCCU
   ccuaddr    BidCoS-RF
   ccuchannels 110
   ccudevices 3
   ccuif      BidCos-RF
   ccuinterfaces BidCos-RF,VirtualDevices,HmIP-RF
   ccuip      192.168.1.192
   ccuname    HM-RCV-50 BidCoS-RF
   ccustate   active
   ccutype    CCU2/3
   config     5.0
   eventCount 16
   firmware   3.65.8
   host       192.168.1.192
   prot       http
   version    5.0 222930908
   READINGS:
     2022-12-01 19:33:16   PLATFORM        rpi3
     2022-12-01 19:33:16   PRODUCT         ccu3
     2022-12-01 19:33:16   VERSION         3.65.8
     2022-12-01 19:33:16   count_channels  110
     2022-12-01 19:33:16   count_devices   3
     2022-12-01 19:33:16   count_groups    0
     2022-12-01 19:33:16   count_interfaces 3
     2022-12-01 19:33:16   count_programs  0
     2022-11-28 20:41:17   iface_addr_1    TEQ1402262
     2022-11-28 20:41:17   iface_conn_1    1
     2022-11-28 20:41:17   iface_ducy_1    1
     2022-11-28 20:41:17   iface_type_1    CCU2
     2022-11-28 21:03:59   rpcstate        running
     2022-12-01 14:47:25   state           Error
   hmccu:
     ccuDevList "HM-RCV-50#BidCoS-RF"
     ccuSuppDevList 
     defaults   0
     evtime     0
     evtimeout  0
     postInit   0
     rcv        
     rpccount   0
     rpcports   2010,2001,9292
     snd        
     updatetime 1669919596.2398
     adr:
       HM-RCV-50 BidCoS-RF:
         address    BidCoS-RF
         addtype    dev
         valid      1
       HM-RCV-50 BidCoS-RF:0:
         address    BidCoS-RF:0
         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

## jetzt kommen die restlichen CHannels dazu dann die heizung und das hmIP Gateway:
HZ_OG_ARZ_VKN_TAST:
         address    00201F298C8316:7
         addtype    chn
         valid      1
       HZ_OG_ARZ_VK_EMPF:
         address    00201F298C8316:2
         addtype    chn
         valid      1
       HZ_OG_ARZ_VK_SEND:
         address    00201F298C8316:1
         addtype    chn
         valid      1
       HZ_OG_AZ:
         address    00201F298C8316
         addtype    dev
         valid      1
       HZ_OG_AZ:0:
         address    00201F298C8316:0
         addtype    chn
         valid      1
       HmIP-RCV-50 HmIP-RCV-1:
         address    HmIP-RCV-1
         addtype    dev
         valid      1
       HmIP-RCV-50 HmIP-RCV-1:0:
         address    HmIP-RCV-1:0
         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

# den Rest verstehe ich dann nicht mehr, was die Daten sagen

Schau mal im logfile, ob Du da feststellen kannst, warum HMCCU den Status error hat.

Probiere mal: get hmCCU3 ccuDevices, ist da dein Thermostat dann dabei?

Danke!

ich weiß nicht warum da Error steht... im fhem log steht nur:

Code Auswählen

2022.12.01 19:33:16 2: HMCCU [hmCCU3] Deleting old CCU configuration data
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Updating device table
2022.12.01 19:33:16 1: HMCCU [hmCCU3] Can't read virtual groups from CCU. Response:
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Reading Device Descriptions for interface BidCos-RF
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Read 52 Device Descriptions for interface BidCos-RF
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Reading Paramset Descriptions for interface BidCos-RF
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Read 153 Paramset Descriptions for interface BidCos-RF
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Reading Peer Descriptions for interface BidCos-RF
2022.12.01 19:33:16 2: HMCCU [hmCCU3] Read 0 Peer Descriptions for interface BidCos-RF

# aus dem Novemberlog habe ich folgende Einträge
HMCCURPCPROC [d_rpc001192BidCos_RF] RPC server process started for interface BidCos-RF with PID=1888\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] Initializing RPC server CB2001001201001192 for interface BidCos-RF\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 1: HMCCURPCPROC [d_rpc001192BidCos_RF] RPC server starting\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCU [hmCCU3] RPC server start: 1 started, 0 already running, 0 failed to start\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] Callback server CB2001001201001192 created. Listening on port 7411\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] CB2001001201001192 accepting connections. PID=1888\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] RPC server CB2001001201001192 enters server loop\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] Registering callback http://192.168.1.201:7411/fh2001 of type A with ID CB2001001201001192 at http://192.168.1.192:2001\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 1: HMCCURPCPROC [d_rpc001192BidCos_RF] RPC server CB2001001201001192 running\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 1: HMCCU [hmCCU3] All RPC servers running\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCU [hmCCU3] Found no devices to update\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 1: HMCCURPCPROC [d_rpc001192BidCos_RF] Scheduled CCU ping every 300 seconds\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:29:56 2: HMCCURPCPROC [d_rpc001192BidCos_RF] CB2001001201001192 NewDevice received 52 device and channel specifications\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:30:18 2: HMCCU [hmCCU3] RPC device for interface BidCos-RF: d_rpc001192BidCos_RF\cf1\highlight2 
\par \cf0\highlight0 2022.11.08 21:30:18 2: HMCCU [hmCCU3] RPC server start: 0 started, 1 already running, 0 failed to start\cf1\highlight2

get ccuDevices liefert mir leider nur das Interface.. Keine Thermostate dabei, die sehe ich nur mit list hmCCU3. Dachte auch ich muss das Interface als Gerät anlegen, aber das klappt ja auch nicht

Danke und Grüße,
Sebastian

@sebr:
Gib bitte erst mal ein vollständiges List von deinem CCU3-Device.

Villeicht hilft aber auch schon in deiner CCU§-Definition das Anhängen von "ccudelay=180" und dann ein Neustart.

Gruß
eurofinder

Okay, hier das Modul:
Ist natürlich jede menge Zeug. Ich weiß auch noch nicht warumda State Error steht.

CCU-Delay 180 ist doch Standard? Ich versuche mal den höher zu setzen.
[code]Internals:
CCUNum 1
Clients :HMCCUDEV:HMCCUCHN:HMCCURPCPROC:
DEF 192.168.1.192
FUUID 636ab5cd-f33f-c6e7-c27e-acf53660bf85722c
NAME hmCCU3
NOTIFYDEV global
NR 55
NTFY_ORDER 50-hmCCU3
RPCState running
STATE running/Error
TYPE HMCCU
ccuaddr BidCoS-RF
ccuchannels 110
ccudevices 3
ccuif BidCos-RF
ccuinterfaces BidCos-RF,VirtualDevices,HmIP-RF
ccuip 192.168.1.192
ccuname HM-RCV-50 BidCoS-RF
ccustate active
ccutype CCU2/3
config 5.0
eventCount 16
firmware 3.65.8
host 192.168.1.192
prot http
version 5.0 222930908
READINGS:
2022-12-01 19:33:16 PLATFORM rpi3
2022-12-01 19:33:16 PRODUCT ccu3
2022-12-01 19:33:16 VERSION 3.65.8
2022-12-01 19:33:16 count_channels 110
2022-12-01 19:33:16 count_devices 3
2022-12-01 19:33:16 count_groups 0
2022-12-01 19:33:16 count_interfaces 3
2022-12-01 19:33:16 count_programs 0
2022-11-28 20:41:17 iface_addr_1 TEQ1402262
2022-11-28 20:41:17 iface_conn_1 1
2022-11-28 20:41:17 iface_ducy_1 1
2022-11-28 20:41:17 iface_type_1 CCU2
2022-11-28 21:03:59 rpcstate running
2022-12-01 14:47:25 state Error
hmccu:
ccuDevList "HM-RCV-50#BidCoS-RF"
ccuSuppDevList
defaults 0
evtime 0
evtimeout 0
postInit 0
rcv
rpccount 0
rpcports 2010,2001,9292
snd
updatetime 1669919596.2398
adr:
HM-RCV-50 BidCoS-RF:
address BidCoS-RF
addtype dev
valid 1
HM-RCV-50 BidCoS-RF:0:
address BidCoS-RF:0
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
HZ_OG_ARZ_VKN_TAST:
address 00201F298C8316:7
addtype chn
valid 1
HZ_OG_ARZ_VK_EMPF:
address 00201F298C8316:2
addtype chn
valid 1
HZ_OG_ARZ_VK_SEND:
address 00201F298C8316:1
addtype chn
valid 1
HZ_OG_AZ:
address 00201F298C8316
addtype dev
valid 1
HZ_OG_AZ:0:
address 00201F298C8316:0
addtype chn
valid 1
HmIP-RCV-50 HmIP-RCV-1:
address HmIP-RCV-1
addtype dev
valid 1
HmIP-RCV-50 HmIP-RCV-1:0:
address HmIP-RCV-1:0
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-eTRV-B 00201F298C8316:3:
address 00201F298C8316:3
addtype chn
valid 1
HmIP-eTRV-B 00201F298C8316:4:
address 00201F298C8316:4
addtype chn
valid 1
HmIP-eTRV-B 00201F298C8316:5:
address 00201F298C8316:5
addtype chn
valid 1
HmIP-eTRV-B 00201F298C8316:6:
address 00201F298C8316:6
addtype chn
valid 1
ccu:
chncount 110
delay 180
delayed 0
devcount 3
gcount 0
ifcount 3
prgcount 0
sync 1
timeout 1
ccuTypes:
supported
unsupported HM-RCV-50
dev:
00201F298C8316:
addtype dev
channels 8
direction 0
interface HmIP-RF
name HZ_OG_AZ
type HmIP-eTRV-B
valid 1
00201F298C8316:0:
addtype chn
channels 1
direction 0
name HZ_OG_AZ:0
valid 1
00201F298C8316:1:
addtype chn
channels 1
direction 1
name HZ_OG_ARZ_VK_SEND
valid 1
00201F298C8316:2:
addtype chn
channels 1
direction 2
name HZ_OG_ARZ_VK_EMPF
valid 1
00201F298C8316:3:
addtype chn
channels 1
direction 2
name HmIP-eTRV-B 00201F298C8316:3
valid 1
00201F298C8316:4:
addtype chn
channels 1
direction 2
name HmIP-eTRV-B 00201F298C8316:4
valid 1
00201F298C8316:5:
addtype chn
channels 1
direction 1
name HmIP-eTRV-B 00201F298C8316:5
valid 1
00201F298C8316:6:
addtype chn
channels 1
direction 2
name HmIP-eTRV-B 00201F298C8316:6
valid 1
00201F298C8316:7:
addtype chn
channels 1
direction 2
name HZ_OG_ARZ_VKN_TAST
valid 1
BidCoS-RF:
addtype dev
channels 51
direction 0
interface BidCos-RF
name HM-RCV-50 BidCoS-RF
type HM-RCV-50
valid 1
BidCoS-RF:0:
addtype chn
channels 1
direction 0
name HM-RCV-50 BidCoS-RF:0
valid 1
BidCoS-RF:1:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:1
valid 1
BidCoS-RF:10:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:10
valid 1
BidCoS-RF:11:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:11
valid 1
BidCoS-RF:12:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:12
valid 1
BidCoS-RF:13:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:13
valid 1
BidCoS-RF:14:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:14
valid 1
BidCoS-RF:15:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:15
valid 1
BidCoS-RF:16:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:16
valid 1
BidCoS-RF:17:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:17
valid 1
BidCoS-RF:18:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:18
valid 1
BidCoS-RF:19:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:19
valid 1
BidCoS-RF:2:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:2
valid 1
BidCoS-RF:20:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:20
valid 1
BidCoS-RF:21:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:21
valid 1
BidCoS-RF:22:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:22
valid 1
BidCoS-RF:23:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:23
valid 1
BidCoS-RF:24:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:24
valid 1
BidCoS-RF:25:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:25
valid 1
BidCoS-RF:26:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:26
valid 1
BidCoS-RF:27:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:27
valid 1
BidCoS-RF:28:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:28
valid 1
BidCoS-RF:29:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:29
valid 1
BidCoS-RF:3:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:3
valid 1
BidCoS-RF:30:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:30
valid 1
BidCoS-RF:31:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:31
valid 1
BidCoS-RF:32:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:32
valid 1
BidCoS-RF:33:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:33
valid 1
BidCoS-RF:34:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:34
valid 1
BidCoS-RF:35:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:35
valid 1
BidCoS-RF:36:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:36
valid 1
BidCoS-RF:37:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:37
valid 1
BidCoS-RF:38:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:38
valid 1
BidCoS-RF:39:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:39
valid 1
BidCoS-RF:4:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:4
valid 1
BidCoS-RF:40:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:40
valid 1
BidCoS-RF:41:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:41
valid 1
BidCoS-RF:42:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:42
valid 1
BidCoS-RF:43:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:43
valid 1
BidCoS-RF:44:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:44
valid 1
BidCoS-RF:45:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:45
valid 1
BidCoS-RF:46:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:46
valid 1
BidCoS-RF:47:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:47
valid 1
BidCoS-RF:48:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:48
valid 1
BidCoS-RF:49:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:49
valid 1
BidCoS-RF:5:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:5
valid 1
BidCoS-RF:50:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:50
valid 1
BidCoS-RF:6:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:6
valid 1
BidCoS-RF:7:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:7
valid 1
BidCoS-RF:8:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:8
valid 1
BidCoS-RF:9:
addtype chn
channels 1
direction 1
name HM-RCV-50 BidCoS-RF:9
valid 1
HmIP-RCV-1:
addtype dev
channels 51
direction 0
interface HmIP-RF
name HmIP-RCV-50 HmIP-RCV-1
type HmIP-RCV-50
valid 1
HmIP-RCV-1:0:
addtype chn
channels 1
direction 0
name HmIP-RCV-50 HmIP-RCV-1:0
valid 1
HmIP-RCV-1:1:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:1
valid 1
HmIP-RCV-1:10:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:10
valid 1
HmIP-RCV-1:11:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:11
valid 1
HmIP-RCV-1:12:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:12
valid 1
HmIP-RCV-1:13:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:13
valid 1
HmIP-RCV-1:14:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:14
valid 1
HmIP-RCV-1:15:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:15
valid 1
HmIP-RCV-1:16:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:16
valid 1
HmIP-RCV-1:17:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:17
valid 1
HmIP-RCV-1:18:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:18
valid 1
HmIP-RCV-1:19:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:19
valid 1
HmIP-RCV-1:2:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:2
valid 1
HmIP-RCV-1:20:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:20
valid 1
HmIP-RCV-1:21:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:21
valid 1
HmIP-RCV-1:22:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:22
valid 1
HmIP-RCV-1:23:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:23
valid 1
HmIP-RCV-1:24:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:24
valid 1
HmIP-RCV-1:25:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:25
valid 1
HmIP-RCV-1:26:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:26
valid 1
HmIP-RCV-1:27:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:27
valid 1
HmIP-RCV-1:28:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:28
valid 1
HmIP-RCV-1:29:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:29
valid 1
HmIP-RCV-1:3:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:3
valid 1
HmIP-RCV-1:30:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:30
valid 1
HmIP-RCV-1:31:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:31
valid 1
HmIP-RCV-1:32:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:32
valid 1
HmIP-RCV-1:33:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:33
valid 1
HmIP-RCV-1:34:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:34
valid 1
HmIP-RCV-1:35:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:35
valid 1
HmIP-RCV-1:36:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:36
valid 1
HmIP-RCV-1:37:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:37
valid 1
HmIP-RCV-1:38:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:38
valid 1
HmIP-RCV-1:39:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:39
valid 1
HmIP-RCV-1:4:
addtype chn
channels 1
direction 1
name HmIP-RCV-50 HmIP-RCV-1:4
valid 1
HmIP-RCV-1:40:
addtype chn
channels 1

Im Log kann ich kein Problem erkennen, bin aber auch kein Experte.
Ich habe mal HMCCU gestoppt, das Log geleert und dann HMCCU wieder gestartet. Das steht dann bei mir im Log (zum vergleichen):

Code Auswählen

2022.12.02 15:58:39 0: Logfile gelöscht
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] RPC server process started for interface VirtualDevices with PID=30745
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] Initializing RPC server CB9292066004066006 for interface VirtualDevices
2022.12.02 15:58:46 1: HMCCURPCPROC [d_rpc066006VirtualDevices] RPC server starting
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006HmIP_RF] RPC server process started for interface HmIP-RF with PID=30746
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006HmIP_RF] Initializing RPC server CB2010066004066006 for interface HmIP-RF
2022.12.02 15:58:46 1: HMCCURPCPROC [d_rpc066006HmIP_RF] RPC server starting
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] Callback server CB9292066004066006 created. Listening on port 14702
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] CB9292066004066006 accepting connections. PID=30745
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] RPC server CB9292066004066006 enters server loop
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] Registering callback http://192.168.xxx.xxx:14702/fh9292 of type A with ID CB9292066004066006 at http://192.168.xxx.xxx:9292/groups
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006HmIP_RF] Callback server CB2010066004066006 created. Listening on port 7420
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006HmIP_RF] CB2010066004066006 accepting connections. PID=30746
2022.12.02 15:58:46 2: HMCCURPCPROC [d_rpc066006VirtualDevices] CB9292066004066006 NewDevice received 48 device and channel specifications
2022.12.02 15:58:56 1: HMCCURPCPROC [d_rpc066006VirtualDevices] RPC server CB9292066004066006 running
2022.12.02 15:58:57 2: HMCCURPCPROC [d_rpc066006HmIP_RF] RPC server CB2010066004066006 enters server loop
2022.12.02 15:58:57 2: HMCCURPCPROC [d_rpc066006HmIP_RF] Registering callback http://192.168.xxx.xxx:7420/fh2010 of type A with ID CB2010066004066006 at http://192.168.xxx.xxx:2010
2022.12.02 15:58:57 1: HMCCURPCPROC [d_rpc066006HmIP_RF] RPC server CB2010066004066006 running
2022.12.02 15:58:57 2: HMCCURPCPROC [d_rpc066006HmIP_RF] CB2010066004066006 NewDevice received 355 device and channel specifications

Mich wundert, dass bei Dir nur BidCoS-RF-Einträge im Log sind. Prüfe mal das Attribut rpcinterfaces, ob da auch HmIP-RF ausgewählt ist..
Hier mal mein Ausschnitt der fhem.cfg (da ich kein HM habe, ist bei mir BidCos-RF nicht aktiv):

Code Auswählen

define CCU HMCCU 192.168.xxx.xxx nosync
attr CCU ccudef-attributes room=Homematic
attr CCU ccuflags nonBlocking
attr CCU cmdIcon on:general_an off:general_aus
attr CCU room Homematic
attr CCU rpcinterfaces VirtualDevices,HmIP-RF
attr CCU rpcserver on
attr CCU stateFormat rpcstate/state
attr CCU verbose 0

@sebr:
Was sagt den

Code Auswählen

sudo pivccu-info
Wird der HmIP-RFUSB korrekt erkannt?
Gruß
eurofinder

Guten Morgen,

yeehawww, da ist das Ding :)! Eure Vermutung mit dem Attribut rpcinterfaces war richtig. Im Attribut rpcinterfaces stand nur das Bidcos-Interface, da habe ich den Wert aus ccuinterfaces (HmIP-RF,VirtualDevices,BidCos-RF) eingetragen.
Bisschen rumprobiert, neugestartet und peng, ccuDevices liefert das Thermostat und das Homatic IP Interface. Gerät anlegen klappt jetzt.

Danke, ihr habt mich auf die richtige Spur gebracht :)

Jetzt kann es endlich weitergehen 8)

Schönes Wochenende,
Sebastian

"BidCoS" ist die Adresse der CCU selbst, nicht zu verwechseln mit dem Interface "BidCos". Man beachte "S" vs. "s" ;)

FHEM Forum

FHEM - Hausautomations-Systeme => Homematic => Thema gestartet von: sebr am 01 Dezember 2022, 19:41:35