Hallo,
ich habe versucht, alles wie in https://wiki.fhem.de/wiki/HMCCU (https://wiki.fhem.de/wiki/HMCCU) beschrieben, umzusetzen.
Ich bekomme wohl eine Verbindung zur CCU3, aber das Erzeugen von Devices in FHEM scheitert
mit einer nichtssagenden Fehlermeldung:
get d_ccu createDev HmIPThermostatBuero
Results of create command:
Not detected CCU devices:
HmIPThermostatBuero = 00392409930634 [HmIPThermostatBuero]
In Log steht noch:
2025.11.04 17:30:44 5: HMCCU [d_ccu] No roles detected for device 00392409930634
defmod d_ccu HMCCU 192.168.188.190
attr d_ccu ccudef-attributes room=Homematic
attr d_ccu room Homematic
attr d_ccu rpcinterfaces VirtualDevices,BidCos-RF,HmIP-RF
attr d_ccu stateFormat rpcstate/state
attr d_ccu verbose 5
setstate d_ccu running/OK
setstate d_ccu 2025-11-04 17:18:50 PLATFORM rpi3
setstate d_ccu 2025-11-04 17:18:50 PRODUCT ccu3
setstate d_ccu 2025-11-04 17:18:50 VERSION 3.83.6
setstate d_ccu 2025-11-04 17:18:50 count_channels 111
setstate d_ccu 2025-11-04 17:18:50 count_devices 4
setstate d_ccu 2025-11-04 17:18:50 count_groups 0
setstate d_ccu 2025-11-04 17:18:50 count_interfaces 3
setstate d_ccu 2025-11-04 17:18:50 count_programs 1
setstate d_ccu 2025-11-04 17:18:47 rpcstate running
setstate d_ccu 2025-11-04 17:23:32 state OK
Das Gerät HmIPThermostatBuero ist in der CCU3 aktiv, und funktioniert auch soweit.
Wo kann ich noch schauen, wieso es nicht geht?
Hallo,
nachdem zwischenzeitlich der RPC-Server sich nicht mehr starten lies,
hier noch ein paar Logzeilen, nach dem Neustart des FHEM und dem Befehl
set d_ccu on
2025.11.04 22:39:21 1: PERL WARNING: Subroutine myUtils_Initialize redefined at ./FHEM/99_myUtilsTemplate.pm line 14.
2025.11.04 22:39:21 1: PERL WARNING: Subroutine SplitReading redefined at ./FHEM/99_myUtilsTemplate.pm line 19.
Die obigen Zeilen gehören nicht zum Problem, aber wo befindet sich die andere Definition? Ich habe alle Dateien durchsucht und nichts gefunden...
Hier jetzt das Log vom HMCCU-Device d_ccu:
2025.11.04 22:39:30 1: HMCCU [d_ccu] CCU port 8181 is reachable
2025.11.04 22:39:30 1: HMCCU [d_ccu] Initialized version 2024-12
2025.11.04 22:39:30 1: HMCCU [d_ccu] Initializing device
2025.11.04 22:39:30 1: HMCCU [d_ccu] Read 4 devices with 111 channels, 3 programs, 0 virtual groups from CCU 192.168.188.190
2025.11.04 22:39:31 0: HMCCU [d_ccu] Scheduling post FHEM initialization tasks in 12 seconds
2025.11.04 22:39:31 0: Featurelevel: 6.4
2025.11.04 22:39:31 0: Server started with 214 defined entities (fhem.pl:30177/2025-08-06 perl:5.036000 os:linux user:fhem pid:12938)
2025.11.04 22:39:43 1: HMCCU [d_ccu] Reading device config from CCU. This may take a couple of seconds ...
2025.11.04 22:39:43 1: HMCCU [d_ccu] No RPC device defined for interface BidCos-RF
2025.11.04 22:39:43 1: HMCCU [d_ccu] Creating new RPC device d_rpc188190BidCos_RF for interface BidCos-RF
2025.11.04 22:39:43 1: HMCCURPCPROC [d_rpc188190BidCos_RF] Initialized version 2024-12 for interface BidCos-RF with I/O device d_ccu
2025.11.04 22:39:44 1: HMCCU [d_ccu] No RPC device defined for interface HmIP-RF
2025.11.04 22:39:44 1: HMCCU [d_ccu] Creating new RPC device d_rpc188190HmIP_RF for interface HmIP-RF
2025.11.04 22:39:44 1: HMCCURPCPROC [d_rpc188190HmIP_RF] Initialized version 2024-12 for interface HmIP-RF with I/O device d_ccu
2025.11.04 22:40:17 2: HMCCURPCPROC [d_rpc188190HmIP_RF] RPC request getParamsetDescription failed: RPC::XML::Client::simple_request:
no element found at line 1, column 0, byte -1:
3^
68599071360
at /usr/share/perl5/RPC/XML/Client.pm line 436.
2025.11.04 22:40:17 2: HMCCURPCPROC [d_rpc188190HmIP_RF] Retrying request getParamsetDescription
2025.11.04 22:40:47 2: HMCCURPCPROC [d_rpc188190HmIP_RF] RPC request getParamsetDescription failed: RPC::XML::Client::simple_request:
no element found at line 1, column 0, byte -1:
3^
68599071360
at /usr/share/perl5/RPC/XML/Client.pm line 436.
2025.11.04 22:40:47 2: HMCCURPCPROC [d_rpc188190HmIP_RF] Retrying request getParamsetDescription
2025.11.04 22:40:47 2: HMCCURPCPROC [d_rpc188190HmIP_RF] Error(s) while fetching parameter set descriptions 00392409930634. Error while executing RPC multicall request: RPC request getParamsetDescription failed: RPC::XML::Client::simple_request:
no element found at line 1, column 0, byte -1:
3^
68599071360
at /usr/share/perl5/RPC/XML/Client.pm line 436.
2025.11.04 22:40:47 1: HMCCU [d_ccu] No RPC device defined for interface VirtualDevices
2025.11.04 22:40:47 1: HMCCU [d_ccu] Creating new RPC device d_rpc188190VirtualDevices for interface VirtualDevices
2025.11.04 22:40:47 1: HMCCURPCPROC [d_rpc188190VirtualDevices] Initialized version 2024-12 for interface VirtualDevices with I/O device d_ccu
Die "raw definition":
defmod d_ccu HMCCU 192.168.188.190
attr d_ccu room Homematic
attr d_ccu stateFormat rpcstate/state
setstate d_ccu inactive/OK
setstate d_ccu 2025-11-04 22:39:30 PLATFORM rpi3
setstate d_ccu 2025-11-04 22:39:30 PRODUCT ccu3
setstate d_ccu 2025-11-04 22:39:30 VERSION 3.83.6
setstate d_ccu 2025-11-04 22:39:30 count_channels 111
setstate d_ccu 2025-11-04 22:39:30 count_devices 4
setstate d_ccu 2025-11-04 22:39:30 count_groups 0
setstate d_ccu 2025-11-04 22:39:30 count_interfaces 3
setstate d_ccu 2025-11-04 22:39:30 count_programs 3
setstate d_ccu 2025-11-04 22:39:30 rpcstate inactive
setstate d_ccu 2025-11-04 22:39:43 state OK
das define ist einfach:
define d_ccu HMCCU 192.168.188.190
Im Anhang das komplette list des devices...
Ich hoffe, mir kann jemand erklären, wieso ich das Thermostat nicht als Device in FHEM bekomme...
Oder was ich eingeben muss, um es manuell einzubinden...
Viele Grüße
Wolfgang
Habe das Device jetzt manuell erzeugt.
Aber wie hier (https://forum.fhem.de/index.php?topic=134050.0) angegeben:
ich versuche nun den statedatapoint zu setzen:
attr HmIPThermostatBuero statadatapoint 1.ACTUAL_TEMPERATURE
Laut
get HmIPThermostatBuero deviceInfo
Device channels and datapoints
DEV HmIPThermostatBuero 00392409930634 interface=HmIP-RF type=HmIP-WTH-1
CHN 00392409930634:0 HmIPThermostatBuero:0
0.CONFIG_PENDING = false {b} [RE]
0.DUTY_CYCLE = false {b} [RE]
0.INSTALL_TEST = true {b} [RW]
0.LOW_BAT = false {b} [RE]
0.OPERATING_VOLTAGE = 3.100000 {f} [RE]
0.OPERATING_VOLTAGE_STATUS = 0 {i} [RE]
0.RSSI_DEVICE = -45 {i} [RE]
0.RSSI_PEER = -46 {i} [RE]
0.UNREACH = false {b} [RE]
0.UPDATE_PENDING = false {b} [RE]
CHN 00392409930634:1 HmIP-WTH-1 00392409930634:1
1.ACTIVE_PROFILE = 1 {i} [RWE]
1.ACTUAL_TEMPERATURE = 22.200000 {f} [RE]
1.ACTUAL_TEMPERATURE_STATUS = 0 {i} [RE]
1.BOOST_MODE = false {b} [WE]
1.BOOST_TIME = 0 {i} [RE]
1.CONTROL_DIFFERENTIAL_TEMPERATURE = {f} [W]
1.CONTROL_MODE = {i} [W]
1.DURATION_UNIT = {i} [W]
1.DURATION_VALUE = {i} [W]
1.FROST_PROTECTION = false {b} [RE]
1.HEATING_COOLING = 0 {i} [RWE]
1.HUMIDITY = 52 {i} [RE]
1.HUMIDITY_STATUS = 0 {i} [RE]
1.PARTY_MODE = false {b} [RE]
1.PARTY_SET_POINT_TEMPERATURE = 0.000000 {f} [RE]
1.PARTY_TIME_END = {s} [RWE]
1.PARTY_TIME_START = {s} [RWE]
1.QUICK_VETO_TIME = 0 {i} [RE]
1.SET_POINT_MODE = 1 {i} [RWE]
1.SET_POINT_TEMPERATURE = 20.500000 {f} [RWE]
1.SWITCH_POINT_OCCURED = false {b} [RE]
1.WINDOW_STATE = 0 {i} [RWE]
Device description
Device 00392409930634 HmIPThermostatBuero [HmIP-WTH-1]
AES_ACTIVE: 1
AVAILABLE_FIRMWARE: 0.0.0
CHILDREN: 00392409930634:0,00392409930634:1,00392409930634:2,00392409930634:3,00392409930634:4,00392409930634:5,00392409930634:6,00392409930634:7
DIRECTION: NONE
FIRMWARE: 1.2.8
FIRMWARE_UPDATE_STATE: UP_TO_DATE
FLAGS: Visible
PARAMSETS: MASTER,SERVICE
RF_ADDRESS: 6110729
ROAMING: 0
RX_MODE: ALWAYS,LAZY_CONFIG,BURST
SUBTYPE: WTH-2
UPDATABLE: 1
Channel 00392409930634:0 HmIPThermostatBuero:0 [MAINTENANCE]
AES_ACTIVE: 1
DIRECTION: NONE
FLAGS: Visible
PARAMSETS: MASTER,VALUES,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:1 HmIP-WTH-1 00392409930634:1 [HEATING_CLIMATECONTROL_TRANSCEIVER] known
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CLIMATE_CONTROL_WTH_TRV
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:2 HmIP-WTH-1 00392409930634:2 [HEATING_CLIMATECONTROL_RECEIVER]
AES_ACTIVE: 1
DIRECTION: RECEIVER
FLAGS: Visible
LINK_TARGET_ROLES: CLIMATE_CONTROL_WGD_WTH,CLIMATE_CONTROL_TRV_WTH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:3 HmIP-WTH-1 00392409930634:3 [HEATING_CLIMATECONTROL_CL_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CLIMATE_CONTROL_CL
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:4 HmIP-WTH-1 00392409930634:4 [HEATING_SHUTTER_CONTACT_RECEIVER]
AES_ACTIVE: 1
DIRECTION: RECEIVER
FLAGS: Visible
LINK_TARGET_ROLES: WINDOW_SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:5 HmIP-WTH-1 00392409930634:5 [HEATING_CLIMATECONTROL_SWITCH_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:6 HmIP-WTH-1 00392409930634:6 [HEATING_KEY_RECEIVER]
AES_ACTIVE: 1
DIRECTION: RECEIVER
FLAGS: Visible
LINK_TARGET_ROLES: REMOTE_CONTROL
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00392409930634:7 HmIP-WTH-1 00392409930634:7 [CLIMATECONTROL_FLOOR_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CLIMATE_CONTROL_FLOOR
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00392409930634
PARENT_TYPE: HmIP-WTH-1
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Defaults
Support for role(s) HEATING_CLIMATECONTROL_TRANSCEIVER of device type HmIP-WTH-1 is built in.
Sollte das ja funktionieren...