Heating Control: not recognized as heating

ToKa · 25 Dezember 2016, 20:34:59

Hallo zusammen,

da ich gerade ein paar Dinge teste, hatte ich beim Neustart von fhem verbose 5 gesetzt. Dabei ist mir im Log folgendes aufgefallen:

Code Auswählen

2016.12.25 17:21:09.284 4: [E2.ku.ZS.Heizung.tim] no switch in the yesterdays because of the devices type(E2.ku.HR.Heizung is not recognized as heating) - use attr switchInThePast

Es handelt sich hierbei um ein Heating Control, das einen Eurotronic COMET Z steuert. Das funktioniert soweit auch gut und mir ist grundsätzlich auch klar, was die Meldung und das attr switchInThePast bedeuten.

Was mich nun interessiert ist, hat es weitere Auswirkungen, dass mein COMET Z nicht als "Heizung" erkannt wird? Was sind die Vorraussetzungen, dass der COMET als "Heizung" erkannt wird?

Hier noch das List des COMET:

Code Auswählen

Internals: 
   DEF        d14c12e6 31 
   IODev      ZWAVE1 
   LASTInputDev ZWAVE1 
   MSGCNT     56 
   NAME       E2.ku.HR.Heizung 
   NR         145 
   STATE      <strong>Ist: </strong>21.5 °C<strong> / Soll: </strong>20.5 °C</br><strong>Ventil: </strong>7 % 
   STILLDONETIME 0 
   TYPE       ZWave 
   ZWAVE1_MSGCNT 56 
   ZWAVE1_RAWMSG 0004001f03260307 
   ZWAVE1_TIME 2016-12-25 20:23:12 
   ZWaveSubDevice no 
   homeId     d14c12e6 
   isWakeUp   1 
   lastMsgSent 1482693794.00722 
   nodeIdHex  1f 
   Helper: 
     Dblog: 
       Reportedstate: 
         Logdb: 
           TIME       1482693792.14497 
           VALUE      7 
       Setpointtemp: 
         Logdb: 
           TIME       1482693791.57661 
           VALUE      20.5 
       Temperature: 
         Logdb: 
           TIME       1482693791.97432 
           VALUE      21.5 
       Wakeup: 
         Logdb: 
           TIME       1482693791.45415 
           VALUE      notification 
   Readings: 
     2016-12-24 17:11:38   SEND_DATA       failed:00 
     2016-12-24 03:20:23   UNPARSED        SWITCH_MULTILEVEL 022603 
     2016-12-25 17:01:56   WunschTemp      00 
     2016-12-25 04:46:26   battery         100 % 
     2016-12-08 12:42:23   model           EUROtronic EUR_COMETZ Wall Radiator Thermostat Valve Control 
     2016-12-08 12:42:23   modelConfig     eurotronic/eur_cometz.xml 
     2016-12-08 12:42:23   modelId         0148-0002-0001 
     2016-12-09 21:18:25   neighborList    EG.ga.ZS.Glasbausteine E2.ku.ZS.Tischleuchte 
     2016-12-09 21:17:41   neighborUpdate  done 
     2016-12-25 20:23:12   reportedState   7 
     2016-12-25 20:23:11   setpointTemp    20.5 
     2016-12-25 20:23:12   state           dim 7 
     2016-12-25 20:23:11   temperature     21.5 
     2016-12-25 20:23:14   timeToAck       0.052 
     2016-12-25 20:23:14   transmit        OK 
     2016-12-25 20:23:11   wakeup          notification 
Attributes: 
   DbLogInclude temperature,setpointTemp,reportedState,thermostatMode,battery,wakeup 
   IODev      ZWAVE1 
   alias      Küche 
   classes    BASIC SWITCH_MULTILEVEL SENSOR_MULTILEVEL THERMOSTAT_MODE THERMOSTAT_SETPOINT NODE_NAMING BATTERY WAKE_UP MANUFACTURER_SPECIFIC VERSION 
   group      Heizung 
   icon       sani_heating 
   room       Übersicht 
   sortby     3 
   stateFormat {"<strong>Ist: </strong>".ReadingsVal('E2.ku.HR.Heizung','temperature','')." °C<strong> / Soll: </strong>".ReadingsVal('E2.ku.HR.Heizung','setpointTemp','')." °C</br><strong>Ventil: </strong>".ReadingsVal('E2.ku.HR.Heizung','reportedState','')." %"} 
   vclasses   BASIC:1 BATTERY:1 MANUFACTURER_SPECIFIC:1 NODE_NAMING:1 SENSOR_MULTILEVEL:4 SWITCH_MULTILEVEL:3 THERMOSTAT_MODE:3 THERMOSTAT_SETPOINT:3 VERSION:1 WAKE_UP:2 
   webCmd     ::

Beste Grüße
Torsten

Dietmar63 · 25 Dezember 2016, 21:33:56

Bei Heizungen wird switchinthepast automatisch gesetzt, und außerdem kennt HC das jeweilige Kommando zum Einstellen der Temperatur : desiredTemp oder so.

Demnächst gebe ich eine Version frei, die Comet automatisch erkennt.
Die Erkennung habe ich vereinfacht - kann aber nicht selbst testen, weil ich die verschiedenen Heizungen nicht habe.

ToKa · 25 Dezember 2016, 21:44:15

Hallo Dietmar,

ok verstanden, das mit der neuen Version klingt gut. Beim COMET wird die Temperatur über thermostatSetpointSet gesetzt.

Wenn Du soweit bist, kann ich dann gerne für die COMET testen.

Gruß
Torsten

Dietmar63 · 27 Dezember 2016, 23:34:03

probier mal ob COMET jetzt automatisch erkannt wird.
Übrigens wird jezt auch desired-temp unterstützt.

ToKa · 30 Dezember 2016, 13:51:15

Hallo Dietmar,

leider wird der COMET noch nicht erkannt (auch nach fhem update und Neustart). Im Log habe ich wieder die entsprechende Meldung.

Code Auswählen

2016.12.30 13:46:05.172 5: [E2.ku.ZS.Heizung.tim] removing Timer: E2.ku.ZS.Heizung.tim_3
2016.12.30 13:46:05.176 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|05:45|20.5  - trying to accept as a switchtime
2016.12.30 13:46:05.178 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|05:45|20.5 - accepted
2016.12.30 13:46:05.178 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|06:45|19.5  - trying to accept as a switchtime
2016.12.30 13:46:05.180 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|06:45|19.5 - accepted
2016.12.30 13:46:05.181 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|15:30|20.5  - trying to accept as a switchtime
2016.12.30 13:46:05.182 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|15:30|20.5 - accepted
2016.12.30 13:46:05.183 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|00:30|19.5  - trying to accept as a switchtime
2016.12.30 13:46:05.184 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|00:30|19.5 - accepted
2016.12.30 13:46:05.185 5: [E2.ku.ZS.Heizung.tim] Sa-So|08:00|20.5  - trying to accept as a switchtime
2016.12.30 13:46:05.186 4: [E2.ku.ZS.Heizung.tim] Sa-So|08:00|20.5 - accepted
2016.12.30 13:46:05.187 5: [E2.ku.ZS.Heizung.tim] Sa-So|01:00|19.5  - trying to accept as a switchtime
2016.12.30 13:46:05.189 4: [E2.ku.ZS.Heizung.tim] Sa-So|01:00|19.5 - accepted
2016.12.30 13:46:05.189 5: [E2.ku.ZS.Heizung.tim] {fhem  - trying to accept as a switchtime
2016.12.30 13:46:05.190 5: [E2.ku.ZS.Heizung.tim] {fhem  - unbalanced brackets {}:1
2016.12.30 13:46:05.191 5: [E2.ku.ZS.Heizung.tim] {fhem "set  - trying to accept as a switchtime
2016.12.30 13:46:05.191 5: [E2.ku.ZS.Heizung.tim] {fhem "set  - unbalanced quotes: 1 " found
2016.12.30 13:46:05.192 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME  - trying to accept as a switchtime
2016.12.30 13:46:05.192 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME  - unbalanced quotes: 1 " found
2016.12.30 13:46:05.193 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet  - trying to accept as a switchtime
2016.12.30 13:46:05.193 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet  - unbalanced quotes: 1 " found
2016.12.30 13:46:05.194 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT"  - trying to accept as a switchtime
2016.12.30 13:46:05.195 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT"  - unbalanced brackets {}:1
2016.12.30 13:46:05.195 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT" }  - trying to accept as a switchtime
2016.12.30 13:46:05.197 4: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT" } - NOT accepted, must be command or condition
2016.12.30 13:46:05.225 4: [E2.ku.ZS.Heizung.tim] 07:43:56 17:13:40 Freitag
2016.12.30 13:46:05.226 4: [E2.ku.ZS.Heizung.tim] 01:00:00 19.5, 08:00:00 20.5 (Profil 0: Sonntag)
2016.12.30 13:46:05.226 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 1: Montag)
2016.12.30 13:46:05.227 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 2: Dienstag)
2016.12.30 13:46:05.227 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 3: Mittwoch)
2016.12.30 13:46:05.228 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 4: Donnerstag)
2016.12.30 13:46:05.228 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 5: Freitag)
2016.12.30 13:46:05.229 4: [E2.ku.ZS.Heizung.tim] 01:00:00 19.5, 08:00:00 20.5 (Profil 6: Samstag)
2016.12.30 13:46:05.229 5: [E2.ku.ZS.Heizung.tim] removing Timer: E2.ku.ZS.Heizung.tim_SetTimerOfDay
2016.12.30 13:46:05.230 5: [E2.ku.ZS.Heizung.tim] setting  Timer: E2.ku.ZS.Heizung.tim_SetTimerOfDay 2016-12-31 00:00:05
2016.12.30 13:46:05.278 4: [E2.ku.ZS.Heizung.tim] device type ZWave: recognized, setModifier:
2016.12.30 13:46:05.279 4: [E2.ku.ZS.Heizung.tim] no switch in the yesterdays because of the devices type(E2.ku.HR.Heizung is not recognized as heating) - use attr switchInThePast
2016.12.30 13:46:05.299 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2016.12.30 13:46:05.300 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.302 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2016.12.30 13:46:05.323 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2016.12.30 13:46:05.324 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.326 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2016.12.30 13:46:05.346 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2016.12.30 13:46:05.347 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.349 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2016.12.30 13:46:05.369 4: [E2.ku.ZS.Heizung.tim] setTimer - timer seems to be active today: 12345|15:30|20.5
2016.12.30 13:46:05.369 5: [E2.ku.ZS.Heizung.tim] setting  Timer: E2.ku.ZS.Heizung.tim_3 2016-12-30 15:30:00
2016.12.30 13:46:05.370 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2016.12.30 13:46:05.370 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.372 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2016.12.30 13:46:05.392 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:0,6
2016.12.30 13:46:05.393 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(0,6);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.395 5: [E2.ku.ZS.Heizung.tim] result of condition:
2016.12.30 13:46:05.395 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:0,6
2016.12.30 13:46:05.396 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(0,6);;;;( 1 && (defined $days->{$wday}))}
2016.12.30 13:46:05.398 5: [E2.ku.ZS.Heizung.tim] result of condition:

desired-temp gibt es jetzt auch beim COMET bei den SET Befehlen, das kann ich bestätigen.

Benötigst Du weitere Informationen, um herauszufinden, warum der COMET nicht erkannt wird?

Beste Grüße
Torsten

Dietmar63 · 30 Dezember 2016, 14:49:14

Ich musste die Änderung wieder zurück nehmen.

Dietmar63 · 02 Januar 2017, 18:39:27

98_WeekdayTimer, 98_Heating_Contorl: a new try to use a new method to check if a device is a heating - the new method is very easy, it checks if a device understand desired-temp ....

The first version, that was checked in, was causing errors.

Zwave, Devolo + FBDECT sollten nun erkannt werden. Bitte prüfen. Mangels Hardware kann ich nicht wirklich testen

ToKa · 02 Januar 2017, 20:49:50

Hallo Dietmar,

werde mit dem COMET testen, sobald das Update verfügbar ist.

Gruß
Torsten

ToKa · 03 Januar 2017, 18:26:08

Hallo Dietmar,

prima, vielen Dank für die Erweiterung. Der COMET Z wird als "Heating Contol" erkannt, aber im Log irritiert mich die Zeile

Code Auswählen

2017.01.03 18:17:47.412 4: [E2.ku.ZS.Heizung.tim] list of window sensors found: 'E2.ku.ZS.Heizung.tim'

Ist das nur ein falscher Text oder was hat es damit auf sich?

Code Auswählen

2017.01.03 18:16:56.299 3: ZWave set ST.sz.HR.Heizung thermostatSetpointSet 19.5
2017.01.03 18:16:56.300 3: set ST.sz.HR.Heizung thermostatSetpointSet 19.5 : Scheduled for sending after WAKEUP
2017.01.03 18:16:56.300 3: Scheduled for sending after WAKEUP
2017.01.03 18:16:56.325 3: ST.bz.HR.Steuerung.tim: ST.bz.HR.Heizung 22.0
2017.01.03 18:16:56.326 3: ZWave set ST.bz.HR.Heizung thermostatSetpointSet 22.0
2017.01.03 18:16:56.327 3: set ST.bz.HR.Heizung thermostatSetpointSet 22.0 : Scheduled for sending after WAKEUP
2017.01.03 18:16:56.327 3: Scheduled for sending after WAKEUP
2017.01.03 18:16:56.348 3: EG.fl.HR.Steuerung.tim: EG.fl.HR.Heizung 20.5
2017.01.03 18:16:56.350 3: ZWave set EG.fl.HR.Heizung thermostatSetpointSet 20.5
2017.01.03 18:16:56.351 3: set EG.fl.HR.Heizung thermostatSetpointSet 20.5 : Scheduled for sending after WAKEUP
2017.01.03 18:16:56.351 3: Scheduled for sending after WAKEUP
2017.01.03 18:16:56.375 3: ZWave set E2.ku.HR.Heizung thermostatSetpointSet 20.5
2017.01.03 18:16:56.375 3: set E2.ku.HR.Heizung thermostatSetpointSet 20.5 : Scheduled for sending after WAKEUP
2017.01.03 18:16:56.376 3: Scheduled for sending after WAKEUP
2017.01.03 18:16:59.004 0: HourCounter KG.hz.BZ.Zirkulationspumpe Run.598 first run done countsOverall:109
2017.01.03 18:17:02.417 3: WeatherAtHome: 0 result(s) retrieved
2017.01.03 18:17:11.151 3: ZWave got config for fibaro/fgwpe.xml from ./FHEM/lib/openzwave_deviceconfig.xml.gz
2017.01.03 18:17:47.277 5: [E2.ku.ZS.Heizung.tim] removing Timer: E2.ku.ZS.Heizung.tim_3
2017.01.03 18:17:47.278 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|05:45|20.5  - trying to accept as a switchtime
2017.01.03 18:17:47.279 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|05:45|20.5 - accepted
2017.01.03 18:17:47.279 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|06:45|19.5  - trying to accept as a switchtime
2017.01.03 18:17:47.279 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|06:45|19.5 - accepted
2017.01.03 18:17:47.279 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|15:30|20.5  - trying to accept as a switchtime
2017.01.03 18:17:47.280 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|15:30|20.5 - accepted
2017.01.03 18:17:47.280 5: [E2.ku.ZS.Heizung.tim] Mo-Fr|00:30|19.5  - trying to accept as a switchtime
2017.01.03 18:17:47.280 4: [E2.ku.ZS.Heizung.tim] Mo-Fr|00:30|19.5 - accepted
2017.01.03 18:17:47.280 5: [E2.ku.ZS.Heizung.tim] Sa-So|08:00|20.5  - trying to accept as a switchtime
2017.01.03 18:17:47.281 4: [E2.ku.ZS.Heizung.tim] Sa-So|08:00|20.5 - accepted
2017.01.03 18:17:47.281 5: [E2.ku.ZS.Heizung.tim] Sa-So|01:00|19.5  - trying to accept as a switchtime
2017.01.03 18:17:47.282 4: [E2.ku.ZS.Heizung.tim] Sa-So|01:00|19.5 - accepted
2017.01.03 18:17:47.282 5: [E2.ku.ZS.Heizung.tim] {fhem  - trying to accept as a switchtime
2017.01.03 18:17:47.282 5: [E2.ku.ZS.Heizung.tim] {fhem  - unbalanced brackets {}:1
2017.01.03 18:17:47.282 5: [E2.ku.ZS.Heizung.tim] {fhem "set  - trying to accept as a switchtime
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set  - unbalanced quotes: 1 " found
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME  - trying to accept as a switchtime
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME  - unbalanced quotes: 1 " found
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet  - trying to accept as a switchtime
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet  - unbalanced quotes: 1 " found
2017.01.03 18:17:47.283 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT"  - trying to accept as a switchtime
2017.01.03 18:17:47.284 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT"  - unbalanced brackets {}:1
2017.01.03 18:17:47.284 5: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT" }  - trying to accept as a switchtime
2017.01.03 18:17:47.284 4: [E2.ku.ZS.Heizung.tim] {fhem "set $NAME thermostatSetpointSet $EVENT" } - NOT accepted, must be command or condition
2017.01.03 18:17:47.293 4: [E2.ku.ZS.Heizung.tim] 07:43:57 17:16:30 Dienstag
2017.01.03 18:17:47.293 4: [E2.ku.ZS.Heizung.tim] 01:00:00 19.5, 08:00:00 20.5 (Profil 0: Sonntag)
2017.01.03 18:17:47.293 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 1: Montag)
2017.01.03 18:17:47.293 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 2: Dienstag)
2017.01.03 18:17:47.294 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 3: Mittwoch)
2017.01.03 18:17:47.294 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 4: Donnerstag)
2017.01.03 18:17:47.294 4: [E2.ku.ZS.Heizung.tim] 00:30:00 19.5, 05:45:00 20.5, 06:45:00 19.5, 15:30:00 20.5 (Profil 5: Freitag)
2017.01.03 18:17:47.294 4: [E2.ku.ZS.Heizung.tim] 01:00:00 19.5, 08:00:00 20.5 (Profil 6: Samstag)
2017.01.03 18:17:47.294 5: [E2.ku.ZS.Heizung.tim] removing Timer: E2.ku.ZS.Heizung.tim_SetTimerOfDay
2017.01.03 18:17:47.295 5: [E2.ku.ZS.Heizung.tim] setting  Timer: E2.ku.ZS.Heizung.tim_SetTimerOfDay 2017-01-04 00:00:05
2017.01.03 18:17:47.320 4: [E2.ku.ZS.Heizung.tim] device type heating recognized, setModifier:desired-temp
2017.01.03 18:17:47.320 4: [E2.ku.ZS.Heizung.tim] Heating recognized - switch in the past activated
2017.01.03 18:17:47.331 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2017.01.03 18:17:47.331 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.332 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:47.342 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2017.01.03 18:17:47.342 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.343 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:47.353 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2017.01.03 18:17:47.353 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.354 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:47.364 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2017.01.03 18:17:47.365 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.365 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:47.375 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:0,6
2017.01.03 18:17:47.376 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(0,6);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.377 5: [E2.ku.ZS.Heizung.tim] result of condition:
2017.01.03 18:17:47.377 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:0,6
2017.01.03 18:17:47.377 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(0,6);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:47.378 5: [E2.ku.ZS.Heizung.tim] result of condition:
2017.01.03 18:17:47.411 4: [E2.ku.ZS.Heizung.tim] time=15:30/1483453800 delay=10067, nextDelay=10140, nextRetry=1483463940
2017.01.03 18:17:47.412 4: [E2.ku.ZS.Heizung.tim] delayedExecutionCond:0
2017.01.03 18:17:47.412 4: [E2.ku.ZS.Heizung.tim] result of delayedExecutionCond:0
2017.01.03 18:17:47.412 4: [E2.ku.ZS.Heizung.tim] list of window sensors found: 'E2.ku.ZS.Heizung.tim'
2017.01.03 18:17:47.412 4: [E2.ku.ZS.Heizung.tim] past timer on E2.ku.HR.Heizung at 2017-01-03 15:30:00 with  20.5 activated
2017.01.03 18:17:47.413 5: [E2.ku.ZS.Heizung.tim] setting  Timer: E2.ku.ZS.Heizung.tim_delayed 2017-01-03 18:17:52
2017.01.03 18:17:52.003 4: E2.ku.HR.Heizung 2017-01-03 15:30:00 10072s 
2017.01.03 18:17:52.003 5: [E2.ku.ZS.Heizung.tim] setting  Timer: E2.ku.ZS.Heizung.tim_3 2017-01-03 15:30:00
2017.01.03 18:17:52.016 4: [E2.ku.ZS.Heizung.tim] device type heating recognized, setModifier:desired-temp
2017.01.03 18:17:52.016 4: [E2.ku.ZS.Heizung.tim] time=15:30/1483453800 delay=10072, nextDelay=10140, nextRetry=1483463940
2017.01.03 18:17:52.017 4: [E2.ku.ZS.Heizung.tim] delayedExecutionCond:0
2017.01.03 18:17:52.017 4: [E2.ku.ZS.Heizung.tim] result of delayedExecutionCond:0
2017.01.03 18:17:52.017 4: [E2.ku.ZS.Heizung.tim] list of window sensors found: 'E2.ku.ZS.Heizung.tim'
2017.01.03 18:17:52.017 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:7,8
2017.01.03 18:17:52.018 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}();;;;( 1 && (defined $days->{$wday} ||  $we || !$we))}
2017.01.03 18:17:52.018 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:52.019 4: [E2.ku.ZS.Heizung.tim] condition: - Tage:1,2,3,4,5
2017.01.03 18:17:52.019 5: [E2.ku.ZS.Heizung.tim] condition: {my $days={};;map{$days->{$_}=1}(1,2,3,4,5);;;;( 1 && (defined $days->{$wday}))}
2017.01.03 18:17:52.020 5: [E2.ku.ZS.Heizung.tim] result of condition:1
2017.01.03 18:17:52.020 4: [E2.ku.ZS.Heizung.tim] Update   - past timer activated
2017.01.03 18:17:52.026 4: [E2.ku.ZS.Heizung.tim] device type heating recognized, setModifier:desired-temp
2017.01.03 18:17:52.026 4: [E2.ku.ZS.Heizung.tim] aktParam: newParam:20.5 - is  not disabled
2017.01.03 18:17:52.026 4: [E2.ku.ZS.Heizung.tim] command: '{fhem "set $NAME thermostatSetpointSet $EVENT" }' executed with %NAME=>E2.ku.HR.Heizung,%EVENT=>20.5
2017.01.03 18:17:52.028 3: ZWave set E2.ku.HR.Heizung thermostatSetpointSet 20.5
2017.01.03 18:17:52.029 3: set E2.ku.HR.Heizung thermostatSetpointSet 20.5 : Scheduled for sending after WAKEUP
2017.01.03 18:17:52.029 3: Scheduled for sending after WAKEUP

Gruß
Torsten

Dietmar63 · 04 Januar 2017, 00:14:45

Nein ist kein Fehler, man HC selbst so definieren dass innerhalb von HC ein Logischer Fensterkontakt definiert ist