Hallo,
wird für das Wandthermostat HmIP-BWTH der Schaltzustand für 230v Fussbodenheizungen in FHEM angezeigen?
In der CCU3 steht Schaltzustand: ON oder OFF.
Auf Kanal 8 wird der Schaltzustand angezeigt.
In den FHEM Readings sehe ich nix?
Danke.
Hallo,
ich würde sagen das state den zustand anzeigt.
Versuch doch mal eine Lampe daran hängen und dann state beobachten.
Gruß Rolf
Danke für die Antwort.
Bei State wird die gemessene Temperatur angegeben, wenn das Thermostat auf 2 Punkt Regelung für Fussbodenheizung eingestellt ist.
Wenn das Wandthermostat die Ventile schaltet bei Unterschreitung der Solltemperatur, dann zeigt er das auch in der CCU3 an mit "Schaltzustand: ON".
Nur in FHEM fehlt mir ein Rückgabeattribut
hallo,
also bei mir zeigt Fhem on/off in State an. Ich habe es zwar mit einem Heizkörperthermostat gekoppelt will aber umrüsten.
gruß Rolf
Seltsam, bei mir steht bei allen Wandthermostaten die IST-Temperatur drin,
liegt wahrscheinlich an Current state datapoint = 1.ACTUAL_TEMPERATURE
Device channels and datapoints
DEV WT__DG__Kueche_Flur 000CBAC9AF35E9 interface=HmIP-RF type=HmIP-BWTH
CHN 000CBAC9AF35E9:0 WT__DG__Kueche_Flur:0
0.CONFIG_PENDING = false {b} [RE]
0.DUTY_CYCLE = false {b} [RE]
0.INSTALL_TEST = true {b} [RW]
0.OPERATING_VOLTAGE = 0.000000 {f} [RE]
0.OPERATING_VOLTAGE_STATUS = 0 {i} [RE]
0.RSSI_DEVICE = -75 {i} [RE]
0.RSSI_PEER = -66 {i} [RE]
0.UNREACH = false {b} [RE]
0.UPDATE_PENDING = false {b} [RE]
CHN 000CBAC9AF35E9:1 WT__DG__Kueche_Flur: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 = 49 {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 = 0 {i} [RWE]
1.SET_POINT_TEMPERATURE = 21.000000 {f} [RWE]
1.SWITCH_POINT_OCCURED = false {b} [RE]
1.WINDOW_STATE = 0 {i} [RWE]
CHN 000CBAC9AF35E9:8 WT__DG__Kueche_Flur:8
8.EMERGENCY_OPERATION = false {b} [RE]
8.FROST_PROTECTION = false {b} [RE]
8.HUMIDITY_ALARM = false {b} [RE]
8.STATE = false {b} [RE]
CHN 000CBAC9AF35E9:9 WT__DG__Kueche_Flur:9
9.STATE = false {b} [RE]
CHN 000CBAC9AF35E9:10 WT__DG__Kueche_Flur:10
10.STATE = false {b} [RE]
CHN 000CBAC9AF35E9:11 WT__DG__Kueche_Flur:11
11.STATE = false {b} [RE]
CHN 000CBAC9AF35E9:12 WT__DG__Kueche_Flur:12
12.STATE = false {b} [RE]
Device detection:
StateDatapoint = 1.ACTUAL_TEMPERATURE [HEATING_CLIMATECONTROL_TRANSCEIVER]
StateDatapoint = 10.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 11.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 12.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 9.STATE [SWITCH_TRANSMITTER]
ControlDatapoint = 1.SET_POINT_TEMPERATURE [HEATING_CLIMATECONTROL_TRANSCEIVER]
Recommended module for device definition: HMCCUDEV
Current state datapoint = 1.ACTUAL_TEMPERATURE
Current control datapoint = 1.SET_POINT_TEMPERATURE
Device description
hallo,
ja bei mir sieht es da so aus:
Device channels and datapoints
DEV WT_Wohnzimmer 000CA0C99D2FEE interface=HmIP-RF type=HmIP-BWTH
CHN 000CA0C99D2FEE:0 WT_Wohnzimmer:0
0.CONFIG_PENDING = false {b} [RE]
0.DUTY_CYCLE = false {b} [RE]
0.INSTALL_TEST = true {b} [RW]
0.OPERATING_VOLTAGE = 0.000000 {f} [RE]
0.OPERATING_VOLTAGE_STATUS = 0 {i} [RE]
0.RSSI_DEVICE = -38 {i} [RE]
0.RSSI_PEER = -34 {i} [RE]
0.UNREACH = false {b} [RE]
0.UPDATE_PENDING = false {b} [RE]
CHN 000CA0C99D2FEE:1 WT_Wohnzimmer:1
1.ACTIVE_PROFILE = 1 {i} [RWE]
1.ACTUAL_TEMPERATURE = 21.500000 {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 = 0 {i} [RWE]
1.SET_POINT_TEMPERATURE = 21.000000 {f} [RWE]
1.SWITCH_POINT_OCCURED = false {b} [RE]
1.WINDOW_STATE = 0 {i} [RWE]
CHN 000CA0C99D2FEE:8 WT_Wohnzimmer:8
8.EMERGENCY_OPERATION = false {b} [RE]
8.FROST_PROTECTION = false {b} [RE]
8.HUMIDITY_ALARM = false {b} [RE]
8.STATE = false {b} [RE]
CHN 000CA0C99D2FEE:9 WT_Wohnzimmer:9
9.STATE = false {b} [RE]
CHN 000CA0C99D2FEE:10 WT_Wohnzimmer:10
10.STATE = false {b} [RE]
CHN 000CA0C99D2FEE:11 WT_Wohnzimmer:11
11.STATE = false {b} [RE]
CHN 000CA0C99D2FEE:12 WT_Wohnzimmer:12
12.STATE = false {b} [RE]
Device detection:
StateDatapoint = 1.ACTUAL_TEMPERATURE [HEATING_CLIMATECONTROL_TRANSCEIVER]
StateDatapoint = 10.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 11.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 12.STATE [SWITCH_VIRTUAL_RECEIVER]
StateDatapoint = 9.STATE [SWITCH_TRANSMITTER]
ControlDatapoint = 1.SET_POINT_TEMPERATURE [HEATING_CLIMATECONTROL_TRANSCEIVER]
Recommended module for device definition: HMCCUDEV
Current state datapoint = 9.STATE
Current control datapoint = 1.SET_POINT_TEMPERATURE
gruß Rolf
Kanal 8 ist es, da wird der Schaltzustand angezeigt im
8.STATE = false {b} [RE]
CHN 000CA0C99D2FEE:8 WT_Wohnzimmer:8
8.EMERGENCY_OPERATION = false {b} [RE]
8.FROST_PROTECTION = false {b} [RE]
8.HUMIDITY_ALARM = false {b} [RE]
8.STATE = false {b} [RE]
Schaltzustand_CCU3.JPG
Habs gerade getestet, wenn die Ventile geöffnet werden, geht der
8.STATE = true {b} [RE]
auf TRUE.
Leider sieht man das Attribut nicht im Device.
Kann man das einblenden?
Gruß und Dank.
Wer definiert denn hier, welche Attribute in so eine Homematic Device Definition reinkommen?
Heute habe ich auch einen HmIP-BWTH bekommen und in debmatic angelernt.
Danach das Gerät in FHEM einfach mit "get ... createDev ..." erzeugt und ohne weiteres Zutun liefert der Thermostat alle Werte, die ich haben möchte, in readings.
defmod wz_FuBo HMCCUDEV 000CA0C9AF1A67 sd=9.STATE
attr wz_FuBo ccureadingfilter 1,9..*
attr wz_FuBo substexcl desired-temp
attr wz_FuBo webCmd desired-temp
attr wz_FuBo widgetOverride desired-temp:slider,15,0.5,24,1
setstate wz_FuBo off
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTIVE_PROFILE 1
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTUAL_TEMPERATURE 23.3
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTUAL_TEMPERATURE_STATUS NORMAL
setstate wz_FuBo 2024-11-29 20:04:54 1.BOOST_MODE off
setstate wz_FuBo 2024-11-29 20:04:54 1.BOOST_TIME 0
setstate wz_FuBo 2024-11-29 20:04:54 1.FROST_PROTECTION false
setstate wz_FuBo 2024-11-29 20:04:54 1.HEATING_COOLING HEATING
setstate wz_FuBo 2024-11-29 20:04:54 1.HUMIDITY 56
setstate wz_FuBo 2024-11-29 20:04:54 1.HUMIDITY_STATUS NORMAL
setstate wz_FuBo 2024-11-29 20:04:54 1.PARTY_MODE false
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_SET_POINT_TEMPERATURE 0.0
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_TIME_END
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_TIME_START
setstate wz_FuBo 2024-11-29 20:04:54 1.QUICK_VETO_TIME 0
setstate wz_FuBo 2024-11-29 20:04:54 1.SET_POINT_MODE manual
setstate wz_FuBo 2024-11-29 20:04:54 1.SET_POINT_TEMPERATURE 22.0
setstate wz_FuBo 2024-11-29 20:04:54 1.SWITCH_POINT_OCCURED false
setstate wz_FuBo 2024-11-29 20:04:54 1.WINDOW_STATE closed
setstate wz_FuBo 2024-11-29 20:04:55 9.STATE off
setstate wz_FuBo 2024-11-29 20:04:55 activity alive
setstate wz_FuBo 2024-11-29 20:04:54 boost off
setstate wz_FuBo 2024-11-29 20:04:54 control 22.0
setstate wz_FuBo 2024-11-29 20:04:54 desired-temp 22.0
setstate wz_FuBo 2024-11-29 20:04:55 devstate ok
setstate wz_FuBo 2024-11-29 20:04:55 hmstate off
setstate wz_FuBo 2024-11-29 20:04:54 humidity 56
setstate wz_FuBo 2024-11-29 20:04:54 measured-temp 23.3
setstate wz_FuBo 2024-11-29 20:04:55 rssidevice -69
setstate wz_FuBo 2024-11-29 19:12:53 rssipeer -63
setstate wz_FuBo 2024-11-29 20:04:55 state off
setstate wz_FuBo 2024-11-29 18:01:27 voltage 0.0
setstate wz_FuBo 2024-11-29 20:04:54 week-program 1
9.STATE liefert den Schaltzustand, der taucht dann auch in state und in hmstate auf.
Mit HmIP habe ich mich noch nicht sonderlich viel beschäftigt, bisher haben alle devices, die ich mit diesem Protokoll nutze, immer nach dem gleichen Anlege-Prinzip in FHEM funktioniert.
Zitat von: betateilchen am 29 November 2024, 20:15:22Heute habe ich auch einen HmIP-BWTH bekommen und in debmatic angelernt.
Danach das Gerät in FHEM einfach mit "get ... createDev ..." erzeugt und ohne weiteres Zutun liefert der Thermostat alle Werte, die ich haben möchte, in readings.
defmod wz_FuBo HMCCUDEV 000CA0C9AF1A67 sd=9.STATE
attr wz_FuBo ccureadingfilter 1,9..*
attr wz_FuBo substexcl desired-temp
attr wz_FuBo webCmd desired-temp
attr wz_FuBo widgetOverride desired-temp:slider,15,0.5,24,1
setstate wz_FuBo off
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTIVE_PROFILE 1
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTUAL_TEMPERATURE 23.3
setstate wz_FuBo 2024-11-29 20:04:54 1.ACTUAL_TEMPERATURE_STATUS NORMAL
setstate wz_FuBo 2024-11-29 20:04:54 1.BOOST_MODE off
setstate wz_FuBo 2024-11-29 20:04:54 1.BOOST_TIME 0
setstate wz_FuBo 2024-11-29 20:04:54 1.FROST_PROTECTION false
setstate wz_FuBo 2024-11-29 20:04:54 1.HEATING_COOLING HEATING
setstate wz_FuBo 2024-11-29 20:04:54 1.HUMIDITY 56
setstate wz_FuBo 2024-11-29 20:04:54 1.HUMIDITY_STATUS NORMAL
setstate wz_FuBo 2024-11-29 20:04:54 1.PARTY_MODE false
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_SET_POINT_TEMPERATURE 0.0
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_TIME_END
setstate wz_FuBo 2024-11-29 18:01:27 1.PARTY_TIME_START
setstate wz_FuBo 2024-11-29 20:04:54 1.QUICK_VETO_TIME 0
setstate wz_FuBo 2024-11-29 20:04:54 1.SET_POINT_MODE manual
setstate wz_FuBo 2024-11-29 20:04:54 1.SET_POINT_TEMPERATURE 22.0
setstate wz_FuBo 2024-11-29 20:04:54 1.SWITCH_POINT_OCCURED false
setstate wz_FuBo 2024-11-29 20:04:54 1.WINDOW_STATE closed
setstate wz_FuBo 2024-11-29 20:04:55 9.STATE off
setstate wz_FuBo 2024-11-29 20:04:55 activity alive
setstate wz_FuBo 2024-11-29 20:04:54 boost off
setstate wz_FuBo 2024-11-29 20:04:54 control 22.0
setstate wz_FuBo 2024-11-29 20:04:54 desired-temp 22.0
setstate wz_FuBo 2024-11-29 20:04:55 devstate ok
setstate wz_FuBo 2024-11-29 20:04:55 hmstate off
setstate wz_FuBo 2024-11-29 20:04:54 humidity 56
setstate wz_FuBo 2024-11-29 20:04:54 measured-temp 23.3
setstate wz_FuBo 2024-11-29 20:04:55 rssidevice -69
setstate wz_FuBo 2024-11-29 19:12:53 rssipeer -63
setstate wz_FuBo 2024-11-29 20:04:55 state off
setstate wz_FuBo 2024-11-29 18:01:27 voltage 0.0
setstate wz_FuBo 2024-11-29 20:04:54 week-program 1
9.STATE liefert den Schaltzustand, der taucht dann auch in state und in hmstate auf.
Mit HmIP habe ich mich noch nicht sonderlich viel beschäftigt, bisher haben alle devices, die ich mit diesem Protokoll nutze, immer nach dem gleichen Anlege-Prinzip in FHEM funktioniert.
Super, Danke das wars, ich habs per HMCCUCHN definiert, ich kannte die get Createdev gar nicht. Jetzt läufts.
Dann noch alsUserreading
| attr WT__DG__Buero_Gaeste_9 userReadings actuator:9.STATE.* { ReadingsVal("$name","9.STATE",999) eq "on" ? 100 : 0 } |
und schon reiht es sich in die anderen ein...