Autor Thema: ungewünschtes Delay bei Ausführung von Schaltbefehlen  (Gelesen 11335 mal)

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Hallo,
ich habe seit einigen Wochen Probleme mit massivem Delay zwischen dem Betätigen des Lichtschalters und dem schalten des Aktors.
Konkret geht es dabei um Homematic Wired. Wenn ich auf einen Taster drücke, der am 12/7 angeschlossen ist, schaltet das licht irgendwann zwischen sofort und nie. Oft liegt der Zeitbereich zwischen 2 und 5 sekunden, aber viel zu oft auch darüber. Ich habe schon folgende Dinge versucht:

- fhem update: erfolgreich, tagesaktuell
- ubuntu update: erfolgreich, tagesaktuell ( Intel Atom, 4 GB RAM)
- neue fhem.cfg ( alte umbenannt, neue angelegt): gleicher Fehler
- owserver upgedated( selbst kompiliert, auf version 3.1): gleicher Fehler
- dabei über die ausgabe von apptime gewundert:https://forum.fhem.de/index.php/topic,51854.0.html
- owserver wieder downgegraded : gleicher Fehler
- Homematic-Komponenten stromlos gemacht, 30sek gewartet, wieder eingeschaltet: gleicher Fehler
- Homematic-Komponenten bis auf einen 12/7 vom Gateway getrennt ( Bus-Leitungen (beide) abgeklemmt): gleicher Fehler
- festgestellt, dass die Festplatte vollgelaufen ist: die Updates haben die sqlite-Datenbank gesichert. Festplatte vergrößert: gleiches Fehlerbild.
- festgestellt, dass von den 4 eingebauten GB nur 768 verwendet werden: im BIOS die RAM-Zuweisung verändert.
- SQLite verdächtigt, LOG deaktiviert ( in der fhem.cfg): gleiches Fehlerbild.
- managbarer Switch(Netgear GS724T): STP deaktiviert: neues Fehlerbild:
##einmal drücken: schaltet sofort
##zweites mal drücken: schaltet sofort
##3. mal drücken: es tut sich nichts.
##Nach 5 Sekunden, in denen ich drücken kann, sooft ich will, fängt das spiel wieder von vorne an.
zur Zeit reproduzierbar.
Umstecken der Verbindung HM-Gateway - FHEM vom Switch auf die Fritzbox:  gleiches Fehlerbild
- event-Monitor:
Ich habe einen Taster genommen und von 13:24:09 bis 13:24:20 ca 2-3 mal pro Sekunde gedrückt:
2016-04-06 13:24:01.537 HM485 HMW02.I07 leistung: 2139
2016-04-06 13:24:09.232 HM485 HMW02.I07 literpromin: 17.5179784629291
2016-04-06 13:24:09.703 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:09.786 HM485 HMW01.I01 press_short: 34
2016-04-06 13:24:09.786 HM485 HMW01.I01 press_short_34
2016-04-06 13:24:09.825 HM485 HMW01.O04 set_toggle
2016-04-06 13:24:09.875 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:09.914 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:09.997 HM485 HMW01.O04 off
2016-04-06 13:24:09.997 HM485 HMW01.O04 working: off
2016-04-06 13:24:12.643 HM485 HMW02.I07 leistung: 2130
2016-04-06 13:24:15.004 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:15.075 HM485 HMW01.I01 press_short: 35
2016-04-06 13:24:15.075 HM485 HMW01.I01 press_short_35
2016-04-06 13:24:15.823 HM485 HMW01.O04 set_toggle
2016-04-06 13:24:15.865 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:15.906 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:15.976 HM485 HMW01.I01 press_short: 36
2016-04-06 13:24:15.976 HM485 HMW01.I01 press_short_36
2016-04-06 13:24:16.009 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.043 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.113 HM485 HMW01.I01 press_short: 37
2016-04-06 13:24:16.113 HM485 HMW01.I01 press_short_37
2016-04-06 13:24:16.154 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.187 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.234 HM485 HMW01.O04 working: off
2016-04-06 13:24:16.234 HM485 HMW01.O04 on
2016-04-06 13:24:16.276 HM485 HMW01.O04 set_toggle
2016-04-06 13:24:16.309 HM485 HMW01.O04 set_toggle
2016-04-06 13:24:16.343 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.413 HM485 HMW01.I01 press_short: 38
2016-04-06 13:24:16.413 HM485 HMW01.I01 press_short_38
2016-04-06 13:24:16.443 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.480 HM485 HMW01.O04 set_toggle
2016-04-06 13:24:16.520 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 13:24:16.568 HM485 HMW01.O04 off

Als Gegenprobe habe ich einen FS20-S4U verwendet:
2016-04-06 13:26:56.227 FS20 FS20_Garage on
2016-04-06 13:26:56.702 FS20 FS20_Garage on
2016-04-06 13:26:57.175 FS20 FS20_Garage on
2016-04-06 13:26:57.767 FS20 FS20_Garage on
2016-04-06 13:26:58.288 FS20 FS20_Garage on
2016-04-06 13:26:58.669 FS20 FS20_Garage on
2016-04-06 13:26:59.193 FS20 FS20_Garage on
2016-04-06 13:26:59.789 FS20 FS20_Garage on
2016-04-06 13:27:00.220 FS20 FS20_Garage on
2016-04-06 13:27:00.726 FS20 FS20_Garage on
2016-04-06 13:27:01.216 FS20 FS20_Garage on
2016-04-06 13:27:01.712 FS20 FS20_Garage on
2016-04-06 13:27:02.272 FS20 FS20_Garage on
2016-04-06 13:27:02.784 FS20 FS20_Garage on
2016-04-06 13:27:03.315 FS20 FS20_Garage on
2016-04-06 13:27:03.757 FS20 FS20_Garage on
2016-04-06 13:27:04.242 FS20 FS20_Garage on
2016-04-06 13:27:04.817 FS20 FS20_Garage on
2016-04-06 13:27:05.750 FS20 FS20_Garage on
2016-04-06 13:27:05.797 FS20 FS20_Garage on
2016-04-06 13:27:06.159 FS20 FS20_Garage on
2016-04-06 13:27:06.853 FS20 FS20_Garage on
2016-04-06 13:27:08.815 FS20 FS20_Garage on

Also liegts doch vermutlich nicht an fhem...

also hab ich nen tcpdump gemacht, um herauszufinden, obs am LAN liegt:
 13:30:51.375884 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 2044516721:2044516739, ack 2882156965, win 4380, length 18
13:30:51.375916 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 18, win 29200, length 0
13:30:54.767453 ARP, Request who-has 192.168.0.5 tell 192.168.0.30, length 28
13:30:54.767551 ARP, Reply 192.168.0.5 is-at 00:1a:22:04:0a:c1, length 46
13:30:56.604983 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 18:36, ack 1, win 4380, length 18
13:30:56.605029 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 36, win 29200, length 0
13:31:00.035066 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 36:53, ack 1, win 4380, length 17
13:31:00.035111 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 53, win 29200, length 0
13:31:00.060057 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 53:82, ack 1, win 4380, length 29
13:31:00.060103 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 82, win 29200, length 0
13:31:00.164680 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [P.], seq 1:18, ack 82, win 29200, length 17
13:31:00.170002 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [.], ack 18, win 4380, length 0
13:31:00.202093 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 82:91, ack 18, win 4380, length 9
13:31:00.202138 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 91, win 29200, length 0
13:31:00.436080 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 91:108, ack 18, win 4380, length 17
13:31:00.436138 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 108, win 29200, length 0
13:31:00.461211 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 108:137, ack 18, win 4380, length 29
13:31:00.461258 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 137, win 29200, length 0
13:31:00.589294 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [P.], seq 18:35, ack 137, win 29200, length 17
13:31:00.594623 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [.], ack 35, win 4380, length 0
13:31:00.626112 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 137:146, ack 35, win 4380, length 9
13:31:00.626157 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 146, win 29200, length 0
13:31:01.238115 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 146:163, ack 35, win 4380, length 17
13:31:01.238170 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 163, win 29200, length 0
13:31:01.262892 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 163:192, ack 35, win 4380, length 29
13:31:01.262938 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 192, win 29200, length 0
13:31:01.413241 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [P.], seq 35:52, ack 192, win 29200, length 17
13:31:01.418567 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [.], ack 52, win 4380, length 0
13:31:01.450130 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 192:201, ack 52, win 4380, length 9
13:31:01.450176 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 201, win 29200, length 0
13:31:01.955962 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 201:218, ack 52, win 4380, length 17
13:31:01.956019 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 218, win 29200, length 0
13:31:01.981108 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 218:247, ack 52, win 4380, length 29
13:31:01.981156 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 247, win 29200, length 0
13:31:02.100376 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [P.], seq 52:69, ack 247, win 29200, length 17
13:31:02.105710 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [.], ack 69, win 4380, length 0
13:31:02.136152 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 247:256, ack 69, win 4380, length 9
13:31:02.136197 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 256, win 29200, length 0
13:31:03.944193 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 256:274, ack 69, win 4380, length 18
13:31:03.944253 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 274, win 29200, length 0
13:31:07.132271 IP 192.168.0.5.1000 > 192.168.0.30.50442: Flags [P.], seq 274:292, ack 69, win 4380, length 18
13:31:07.132308 IP 192.168.0.30.50442 > 192.168.0.5.1000: Flags [.], ack 292, win 29200, length 0
das waren 10 mal drücken, die ersten vier haben einen Aktor ausgelöst, die folgenden 6 sind "verloren gegangen". Ich hab aber zu wenig Ahnung vom Protokoll, um da was rein interpretieren zu können...

bliebe noch, einen Reset vom LAN-Gateway zu machen.. aber ich habe sorge, dass mir das mein System dann komplett zerschießt ( momentan gehts ja noch halbwegs)... Ich such mal nach ner Anleitung, ggf muss ich Ersatz kaufen.
was mir grade noch einfällt: ich hab nen Raspi, da installiere ich gleich mal fhem..


Ja, und da werde ich jetzt echt ratlos. Ich hab sonst keine Idee mehr... Kann jemand helfen?
Wenn noch Informationen gewünscht werden, sagt Bescheid, vielleicht hab ich was vergessen. Oben steht soweit alles, was ich bisher versucht habe.

Danke!
Stephan
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #1 am: 06 April 2016, 15:12:14 »
Hi,
wie sind denn die Taster mit den Aktoren verbunden? Sind die Dinger direkt gepeert oder geht da was über notify oder so?
Wahrscheinlich wäre es das beste, wenn Du das hier in den Homematic-Bereich verschiebst.
Dann bitte auch gleich die Ausgabe von "version" hinzufügen.
Gruß,
   Thorsten
FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #2 am: 06 April 2016, 15:24:09 »
Hi Thorsten,

Das geht ausschließlich über notify, habe keinerlei direkte peerings drin.

Hier das erste notify als Beispiel:
HMW01.I01:press_long:.* set FS20_Garage onHMW01.I01:press_short:.* set FS20_Garage offSo habe ich das für jeden Eingang meines Homematic angelegt, mit verschiedenen set-Befehlen natürlich.

#version:
Latest Revision: 11184

File                     Rev   Last Change

fhem.pl                  11191 2016-04-05 11:55:05Z rudolfkoenig
96_allowed.pm            11184 2016-04-04 08:24:33Z rudolfkoenig
98_apptime.pm             8074 2015-02-22 19:31:19Z betateilchen
90_at.pm                 11183 2016-04-04 08:22:42Z rudolfkoenig
98_autocreate.pm         11094 2016-03-20 09:41:03Z rudolfkoenig
00_CUL.pm                10855 2016-02-15 11:30:02Z rudolfkoenig
15_CUL_EM.pm              6825 2014-10-28 09:25:24Z arnoaugustin
09_CUL_FHTTK.pm           7529 2015-01-11 18:52:43Z matscher
14_CUL_WS.pm             10794 2016-02-11 06:26:06Z rudolfkoenig
93_DbLog.pm              10796 2016-02-11 09:11:41Z rapster
98_DOIF.pm               10985 2016-03-03 17:25:24Z damian-s
98_dummy.pm              10530 2016-01-16 19:27:21Z rudolfkoenig
91_eventTypes.pm         10530 2016-01-16 19:27:21Z rudolfkoenig
01_FHEMWEB.pm            11178 2016-04-03 14:20:32Z rudolfkoenig
92_FileLog.pm            10530 2016-01-16 19:27:21Z rudolfkoenig
10_FS20.pm               10984 2016-03-03 08:59:47Z rudolfkoenig
98_help.pm               10809 2016-02-13 09:51:16Z betateilchen
# $Id: 10_HM485.pm 0743 2016-02-26 09:02:00Z Thorsten Pferdekaemper $
No Id found for 00_HM485_LAN.pm
12_HMS.pm                 5097 2014-03-02 15:25:08Z rudolfkoenig
No Id found for hmw_io12_fm.pm
No Id found for hmw_io12_sw14_dr.pm
No Id found for hmw_io12_sw7_dr.pm
No Id found for hmw_io12_sw7_dr_v3_02.pm
No Id found for hmw_io12_sw7_dr_V3_02.pm
No Id found for hmw_io_12_fm.pm
No Id found for hmw_sen_sc_12_dr.pm
98_JsonList2.pm          10530 2016-01-16 19:27:21Z rudolfkoenig
No Id found for 99_MyUtils.pm
91_notify.pm             11178 2016-04-03 14:20:32Z rudolfkoenig
11_OWDevice.pm           11137 2016-03-28 14:07:20Z borisneubert
10_OWServer.pm           11137 2016-03-28 14:07:20Z borisneubert
No Id found for 99_perfmon.pm
98_PID20.pm              10722 2016-02-04 17:12:18Z john99sr
99_SUNRISE_EL.pm         10569 2016-01-19 06:30:28Z rudolfkoenig
98_SVG.pm                10792 2016-02-10 20:20:49Z rudolfkoenig
50_TelegramBot.pm        11090 2016-03-19 21:38:31Z viegener
98_telnet.pm             10551 2016-01-17 11:03:44Z rudolfkoenig
99_Utils.pm              10570 2016-01-19 06:39:23Z rudolfkoenig
98_version.pm            11026 2016-03-08 07:25:45Z markusbloch

No Id found for ConfigurationManager.pm
No Id found for Constants.pm
DevIo.pm                 11020 2016-03-07 12:01:43Z rudolfkoenig
No Id found for FhemWebHelper.pm
No Id found for hmw-sen-sc-12.pm
No Id found for hmw_central.pm
No Id found for hmw_generic.pm
No Id found for hmw_io_4_fm.pm
No Id found for hmw_io_4_fm_v3_02.pm
No Id found for hmw_io_4_fm_V3_02.pm
No Id found for hmw_io_sr_fm.pm
No Id found for hmw_lc_bl1_dr.pm
No Id found for hmw_lc_bl1_dr_v3_02.pm
No Id found for hmw_lc_bl1_dr_V3_02.pm
No Id found for hmw_lc_dim1l_dr.pm
No Id found for hmw_lc_sw2_dr.pm
No Id found for hmw_lc_sw2_dr_v3_02.pm
No Id found for hmw_lc_sw2_dr_V3_02.pm
No Id found for hmw_virtual.pm
HttpUtils.pm             11154 2016-03-30 08:57:41Z rudolfkoenig
# $Id: OWNet.pm,v 1.24 2013/02/02 11:41:28 alfille Exp $
No Id found for PeeringManager.pm
RTypes.pm                10476 2016-01-12 21:03:33Z borisneubert
SetExtensions.pm         10858 2016-02-15 17:42:13Z rudolfkoenig
TcpServerUtils.pm        10346 2016-01-03 12:34:27Z rudolfkoenig
TimeSeries.pm            10907 2016-02-21 17:38:02Z borisneubert
No Id found for Util.pm

Leider habe ich keinen blassen Dunst, wie ich den Beitrag verschiebe ... ??
Danke
Stephan


PS: wenn ich im Web-Frontend die Ausgänge schalte, scheint es, als würde alles einwandfrei funktionieren...
Deutet mit den fehlenden Events auf Probleme mit dem Eingang hin. Möchtest du auch noch einen Auszug aus dem Log haben?


« Letzte Änderung: 06 April 2016, 15:27:44 von abc2006 »
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #3 am: 06 April 2016, 15:37:01 »
Loglevel 5, habe umm 15:27:50 mehrfach den Taster gedrückt, Licht hat auch geschaltet, aber nicht so oft, wie ich gedrückt habe:

[code]
2016.04.06 15:27:47.599 4: Connection closed for WEB_192.168.0.29_57516: EOF
2016.04.06 15:27:47.756 4: WEB_192.168.0.29_57614 GET /fhem?XHR=1&inform=type=status;filter=;since=1459949266;fmt=JSON&fw_id=561&timestamp=1459949267752; BUFLEN:0
2016.04.06 15:27:48.655 4: Connection accepted from WEB_192.168.0.29_57616
2016.04.06 15:27:48.656 4: WEB_192.168.0.29_57616 GET /fhem?XHR=1&inform=type=raw;withLog=0;filter=.*&timestamp=1459949268650; BUFLEN:0
2016.04.06 15:27:48.732 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 82 Cmd: 101
2016.04.06 15:27:48.733 4: MyHMLAN: Event:HASH(0x58ae780)
2016.04.06 15:27:48.733 5: MyHMLAN dispatch \FDRe\00\00\00^\00\00\9A+i\00:\F6
2016.04.06 15:27:48.733 5: MyHMLAN: HM485_Parse: MsgId: 82
2016.04.06 15:27:48.733 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:48.733 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003AF6
2016.04.06 15:27:48.736 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:48.737 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:48.740 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:48.742 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:48.742 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15094
2016.04.06 15:27:48.743 5: HM485: HM485:Device:dataConversion: retVal = 15094.00
2016.04.06 15:27:48.743 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15094.00
2016.04.06 15:27:48.743 5: HM485: Device:valueToControl: valName = frequency = 15094.00
2016.04.06 15:27:48.743 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003AF6 actionType = frame
2016.04.06 15:27:48.745 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:48.745 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15094.00 Alter Wert = 15384.00
2016.04.06 15:27:48.745 4: HMW02.I07: frequency -> 15094.00
2016.04.06 15:27:49.007 4: Connection closed for WEB_192.168.0.29_57616: EOF
2016.04.06 15:27:49.008 4: Connection accepted from WEB_192.168.0.29_57618
2016.04.06 15:27:49.010 4: WEB_192.168.0.29_57618 GET /fhem?XHR=1&inform=type=raw;withLog=1;filter=.*&timestamp=1459949269003; BUFLEN:0
2016.04.06 15:27:50.114 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 83 Cmd: 101
2016.04.06 15:27:50.115 4: MyHMLAN: Event:HASH(0x58a89e8)
2016.04.06 15:27:50.115 5: MyHMLAN dispatch \FDSe\00\00\00X\00\00\9A+i\00;\CF
2016.04.06 15:27:50.115 5: MyHMLAN: HM485_Parse: MsgId: 83
2016.04.06 15:27:50.116 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:50.116 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003BCF
2016.04.06 15:27:50.118 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:50.120 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:50.123 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:50.124 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:50.125 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15311
2016.04.06 15:27:50.125 5: HM485: HM485:Device:dataConversion: retVal = 15311.00
2016.04.06 15:27:50.126 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15311.00
2016.04.06 15:27:50.126 5: HM485: Device:valueToControl: valName = frequency = 15311.00
2016.04.06 15:27:50.126 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003BCF actionType = frame
2016.04.06 15:27:50.128 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:50.128 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15311.00 Alter Wert = 15094.00
2016.04.06 15:27:50.128 4: HMW02.I07: frequency -> 15311.00
2016.04.06 15:27:50.242 5: CUL/RAW: /K016561631D

2016.04.06 15:27:50.242 4: CUL_Parse: CUL_0 K016561631D -59.5
2016.04.06 15:27:50.243 5: CUL_0 dispatch K01656163
2016.04.06 15:27:50.244 4: CUL_WS S300TH S300TH: T: 16.5  H: 63.6
2016.04.06 15:27:50.248 5: Triggering S300TH (4 changes)
2016.04.06 15:27:50.248 5: Starting notify loop for S300TH, first event T: 16.5  H: 63.6
2016.04.06 15:27:50.253 5: Notify from Device: S300TH recieved
2016.04.06 15:27:50.254 5: DbLog: logging of Device: S300TH , Type: CUL_WS , Event: T: 16.5  H: 63.6 , Reading: data , Value: T: 16.5  H: 63.6 , Unit: 63.6
2016.04.06 15:27:50.281 5: DbLog: logging of Device: S300TH , Type: CUL_WS , Event: temperature: 16.5 , Reading: temperature , Value: 16.5 , Unit: °C
2016.04.06 15:27:50.332 5: DbLog: logging of Device: S300TH , Type: CUL_WS , Event: taupunkt: 9.5 , Reading: taupunkt , Value: 9.5 , Unit:
2016.04.06 15:27:50.369 5: DbLog: logging of Device: S300TH , Type: CUL_WS , Event: avgTemp: 15.5605263157895 , Reading: avgTemp , Value: 15.5605263157895 , Unit:
2016.04.06 15:27:51.254 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 84 Cmd: 101
2016.04.06 15:27:51.255 4: MyHMLAN: Event:HASH(0x5931c08)
2016.04.06 15:27:51.255 5: MyHMLAN dispatch \FDTe\00\00\00Z\00\00\9A+i\00:\F6
2016.04.06 15:27:51.255 5: MyHMLAN: HM485_Parse: MsgId: 84
2016.04.06 15:27:51.256 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:51.256 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003AF6
2016.04.06 15:27:51.258 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:51.260 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:51.263 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:51.264 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:51.265 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15094
2016.04.06 15:27:51.265 5: HM485: HM485:Device:dataConversion: retVal = 15094.00
2016.04.06 15:27:51.266 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15094.00
2016.04.06 15:27:51.266 5: HM485: Device:valueToControl: valName = frequency = 15094.00
2016.04.06 15:27:51.266 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003AF6 actionType = frame
2016.04.06 15:27:51.268 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:51.268 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15094.00 Alter Wert = 15311.00
2016.04.06 15:27:51.268 4: HMW02.I07: frequency -> 15094.00
2016.04.06 15:27:51.272 5: Triggering HMW02.I07 (1 changes)
2016.04.06 15:27:51.273 5: Starting notify loop for HMW02.I07, first event leistung: 2754.2
2016.04.06 15:27:51.274 5: Notify from Device: HMW02.I07 recieved
2016.04.06 15:27:51.275 5: DbLog: logging of Device: HMW02.I07 , Type: HM485 , Event: leistung: 2754.2 , Reading: leistung , Value: 2754.2 , Unit:
2016.04.06 15:27:52.277 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 85 Cmd: 101
2016.04.06 15:27:52.277 4: MyHMLAN: Event:HASH(0x5931bf0)
2016.04.06 15:27:52.278 5: MyHMLAN dispatch \FDUe\00\00\00\\00\00\9A+i\00<
2016.04.06 15:27:52.278 5: MyHMLAN: HM485_Parse: MsgId: 85
2016.04.06 15:27:52.278 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:52.279 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003C18
2016.04.06 15:27:52.281 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:52.282 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:52.286 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:52.287 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:52.288 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15384
2016.04.06 15:27:52.288 5: HM485: HM485:Device:dataConversion: retVal = 15384.00
2016.04.06 15:27:52.288 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15384.00
2016.04.06 15:27:52.289 5: HM485: Device:valueToControl: valName = frequency = 15384.00
2016.04.06 15:27:52.289 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003C18 actionType = frame
2016.04.06 15:27:52.290 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:52.291 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15384.00 Alter Wert = 15094.00
2016.04.06 15:27:52.291 4: HMW02.I07: frequency -> 15384.00
2016.04.06 15:27:53.421 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 86 Cmd: 101
2016.04.06 15:27:53.421 4: MyHMLAN: Event:HASH(0x5932908)
2016.04.06 15:27:53.421 5: MyHMLAN dispatch \FDVe\00\00\00^\00\00\9A+i\00;=
2016.04.06 15:27:53.422 5: MyHMLAN: HM485_Parse: MsgId: 86
2016.04.06 15:27:53.422 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:53.422 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B3D
2016.04.06 15:27:53.425 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:53.426 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:53.429 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:53.431 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:53.432 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15165
2016.04.06 15:27:53.432 5: HM485: HM485:Device:dataConversion: retVal = 15165.00
2016.04.06 15:27:53.432 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15165.00
2016.04.06 15:27:53.432 5: HM485: Device:valueToControl: valName = frequency = 15165.00
2016.04.06 15:27:53.433 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003B3D actionType = frame
2016.04.06 15:27:53.434 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:53.435 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15165.00 Alter Wert = 15384.00
2016.04.06 15:27:53.435 4: HMW02.I07: frequency -> 15165.00
2016.04.06 15:27:54.029 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 87 Cmd: 101
2016.04.06 15:27:54.029 4: MyHMLAN: Event:HASH(0x58e9f10)
2016.04.06 15:27:54.030 5: MyHMLAN dispatch \FDWe\FF\FF\FF\FF\DA\00\00\B8\C5K\00\00\C2
2016.04.06 15:27:54.030 5: MyHMLAN: HM485_Parse: MsgId: 87
2016.04.06 15:27:54.031 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:54.031 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4B0000C2
2016.04.06 15:27:54.034 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 48
2016.04.06 15:27:54.034 5: HM485: HM485:Device:dataConversion: retVal = 48
2016.04.06 15:27:54.035 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 48
2016.04.06 15:27:54.035 5: HM485: Device:valueToControl: valName = press_short = 48
2016.04.06 15:27:54.035 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B0000C2 actionType = frame
2016.04.06 15:27:54.037 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:27:54.037 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:27:54.038 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:27:54.040 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:27:54.080 4: HMW01.I01: HM485_ChannelDoUpdate
2016.04.06 15:27:54.080 5: HMW01.I01: HM485_ChannelDoUpdate: valueKey = press_short value = 48 Alter Wert = 47
2016.04.06 15:27:54.080 4: HMW01.I01: press_short -> 48
2016.04.06 15:27:54.081 5: Triggering HMW01.I01 (2 changes)
2016.04.06 15:27:54.081 5: Starting notify loop for HMW01.I01, first event press_short: 48
2016.04.06 15:27:54.082 5: Triggering N_1.I01_short
2016.04.06 15:27:54.082 4: N_1.I01_short exec set HMW01.O04 toggle
2016.04.06 15:27:54.083 5: Cmd: >set HMW01.O04 toggle<
2016.04.06 15:27:54.086 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_SendCommand: 780FFF
2016.04.06 15:27:54.088 5: Notify from Device: HMW01.I01 recieved
2016.04.06 15:27:54.089 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short: 48 , Reading: press_short , Value: 48 , Unit:
2016.04.06 15:27:54.127 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short_48 , Reading: state , Value: press_short_48 , Unit:
2016.04.06 15:27:54.160 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 88 Cmd: 101
2016.04.06 15:27:54.160 4: MyHMLAN: Event:HASH(0x58c0200)
2016.04.06 15:27:54.160 5: MyHMLAN dispatch \FDXe\FF\FF\FF\FF\DC\00\00\B8\C5A\00\00LEQ0016352
2016.04.06 15:27:54.161 5: MyHMLAN: HM485_Parse: MsgId: 88
2016.04.06 15:27:54.161 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:54.161 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4100120003064C455130303136333532
2016.04.06 15:27:54.162 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 15:27:54.164 5: Triggering HMW01.O04 (1 changes)
2016.04.06 15:27:54.164 5: Starting notify loop for HMW01.O04, first event set_toggle
2016.04.06 15:27:54.165 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:27:54.167 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: set_toggle , Reading: state , Value: set_toggle , Unit:
2016.04.06 15:27:54.192 5: MyHMLAN: HM485_LAN_Write TX: 100
2016.04.06 15:27:54.193 5: MyHMLAN: HM485_LAN_SendQueueNextItem: QID: 00000191
2016.04.06 15:27:54.193 5: SW: fd0f6453c80000b8c51e00000001780fff
2016.04.06 15:27:54.194 4: MyHMLAN: MyHMLAN: TX: (100) I[3](0,F,B)(1E) 00000001 -> 0000B8C5 [5] 78(x) 0FFF
2016.04.06 15:27:54.195 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_DoSendCommand: hmwId = 0000B8C5 data = 780FFF requestId = 100
2016.04.06 15:27:54.196 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:27:54.196 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:27:54.197 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:27:54.199 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:27:54.228 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 100 Cmd: 114
2016.04.06 15:27:54.228 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Response: (100) 690F0000
2016.04.06 15:27:54.229 5: MyHMLAN dispatch \FDdr~i\00\00
2016.04.06 15:27:54.229 5: MyHMLAN: HM485_Parse: MsgId: 100
2016.04.06 15:27:54.229 5: MyHMLAN: HM485_Parse: ProcessResponse
2016.04.06 15:27:54.229 5: MyHMLAN: HM485_ProcessResponse: msgData = 690F0000
2016.04.06 15:27:54.230 5: MyHMLAN: HM485_ProcessResponse: deviceKey =  requestType = 78 requestData = 0FFF msgData = 690F0000
2016.04.06 15:27:54.232 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state_flags value1 = 0
2016.04.06 15:27:54.232 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:54.233 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:27:54.233 5: HM485: Device:valueToControl: valName = working = 0
2016.04.06 15:27:54.234 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state value1 = 0
2016.04.06 15:27:54.234 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:54.235 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:27:54.235 5: HM485: Device:valueToControl: valName = state = 0
2016.04.06 15:27:54.235 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 16 msgData = 690F0000 actionType = response
2016.04.06 15:27:54.236 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Removing Queue 00000191
2016.04.06 15:27:54.236 5: MyHMLAN: HM485_LAN_CheckResendQueueItems: QID: 00000191
2016.04.06 15:27:54.237 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:27:54.237 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:27:54.239 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:27:54.240 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:27:54.284 4: HMW01.O04: HM485_ChannelDoUpdate
2016.04.06 15:27:54.284 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = working value = off Alter Wert = off
2016.04.06 15:27:54.284 4: HMW01.O04: working -> off
2016.04.06 15:27:54.285 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = state value = off Alter Wert = set_toggle
2016.04.06 15:27:54.285 4: HMW01.O04: state -> off
2016.04.06 15:27:54.285 5: Triggering HMW01.O04 (2 changes)
2016.04.06 15:27:54.285 5: Starting notify loop for HMW01.O04, first event working: off
2016.04.06 15:27:54.287 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:27:54.288 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: working: off , Reading: working , Value: off , Unit:
2016.04.06 15:27:54.314 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: off , Reading: state , Value: off , Unit:
2016.04.06 15:27:56.309 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 89 Cmd: 101
2016.04.06 15:27:56.309 4: MyHMLAN: Event:HASH(0x5943970)
2016.04.06 15:27:56.309 5: MyHMLAN dispatch \FDYe\00\00\00X\00\00\9A+i\00;\86
2016.04.06 15:27:56.309 5: MyHMLAN: HM485_Parse: MsgId: 89
2016.04.06 15:27:56.310 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:27:56.310 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B86
2016.04.06 15:27:56.312 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:56.314 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:56.317 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:56.318 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:27:56.319 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15238
2016.04.06 15:27:56.320 5: HM485: HM485:Device:dataConversion: retVal = 15238.00
2016.04.06 15:27:56.320 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15238.00
2016.04.06 15:27:56.320 5: HM485: Device:valueToControl: valName = frequency = 15238.00
2016.04.06 15:27:56.320 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003B86 actionType = frame
2016.04.06 15:27:56.322 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:27:56.322 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15238.00 Alter Wert = 15165.00
2016.04.06 15:27:56.323 4: HMW02.I07: frequency -> 15238.00
2016.04.06 15:27:57.006 5: OWServer child ID for reading '/28.615050070000/temperature10' is 25803
2016.04.06 15:27:58.121 5: OWServer child read /28.615050070000/temperature10: 85
2016.04.06 15:27:58.598 5: OWServer child ID for reading '/28.FF8EE6A41503/temperature10' is 25807
2016.04.06 15:27:58.853 5: OWServer child read /28.FF8EE6A41503/temperature10: 23.25
2016.04.06 15:27:59.324 1: Perfmon: possible freeze starting at 15:27:58, delay is 1.324
2016.04.06 15:27:59.331 5: OWServer child ID for reading '/28.95CD51070000/temperature10' is 25811
2016.04.06 15:27:59.651 5: OWServer child read /28.95CD51070000/temperature10: 36.5
2016.04.06 15:28:00.127 5: OWServer child ID for reading '/28.2B308A060000/temperature10' is 25815
2016.04.06 15:28:00.382 5: OWServer child read /28.2B308A060000/temperature10: 26.5
2016.04.06 15:28:00.860 5: OWServer child ID for reading '/28.FF9BA5A41503/temperature10' is 25819
2016.04.06 15:28:01.179 5: OWServer child read /28.FF9BA5A41503/temperature10: 22.5
2016.04.06 15:28:01.651 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 90 Cmd: 101
2016.04.06 15:28:01.651 4: MyHMLAN: Event:HASH(0x59442a0)
2016.04.06 15:28:01.652 5: MyHMLAN dispatch \FDZe\00\00\00Z\00\00\9A+i\00;=
2016.04.06 15:28:01.652 5: MyHMLAN: HM485_Parse: MsgId: 90
2016.04.06 15:28:01.652 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:01.653 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B3D
2016.04.06 15:28:01.656 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:01.657 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:01.661 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:01.662 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:01.663 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15165
2016.04.06 15:28:01.663 5: HM485: HM485:Device:dataConversion: retVal = 15165.00
2016.04.06 15:28:01.664 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15165.00
2016.04.06 15:28:01.664 5: HM485: Device:valueToControl: valName = frequency = 15165.00
2016.04.06 15:28:01.664 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003B3D actionType = frame
2016.04.06 15:28:01.670 5: OWServer child ID for reading '/28.3BC952070000/temperature10' is 25823
2016.04.06 15:28:01.923 5: OWServer child read /28.3BC952070000/temperature10: 22.75
2016.04.06 15:28:02.394 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:02.395 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15165.00 Alter Wert = 15238.00
2016.04.06 15:28:02.395 4: HMW02.I07: frequency -> 15165.00
2016.04.06 15:28:02.400 5: Triggering HMW02.I07 (1 changes)
2016.04.06 15:28:02.400 5: Starting notify loop for HMW02.I07, first event leistung: 2751.75
2016.04.06 15:28:02.402 5: Notify from Device: HMW02.I07 recieved
2016.04.06 15:28:02.403 5: DbLog: logging of Device: HMW02.I07 , Type: HM485 , Event: leistung: 2751.75 , Reading: leistung , Value: 2751.75 , Unit:
2016.04.06 15:28:02.434 5: OWServer child ID for reading '/28.6A568A060000/temperature10' is 25827
2016.04.06 15:28:02.689 5: OWServer child read /28.6A568A060000/temperature10: 28.5
2016.04.06 15:28:03.166 5: OWServer child ID for reading '/28.AE7720070000/temperature10' is 25831
2016.04.06 15:28:03.419 5: OWServer child read /28.AE7720070000/temperature10: 25.25
2016.04.06 15:28:03.894 5: OWServer child ID for reading '/28.058A50070000/temperature10' is 25835
2016.04.06 15:28:04.213 5: OWServer child read /28.058A50070000/temperature10: 28.25
2016.04.06 15:28:04.684 1: Perfmon: possible freeze starting at 15:28:03, delay is 1.684
2016.04.06 15:28:04.686 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 91 Cmd: 101
2016.04.06 15:28:04.686 4: MyHMLAN: Event:HASH(0x588bc40)
2016.04.06 15:28:04.686 5: MyHMLAN dispatch \FD[e\00\00\00\\00\00\9A+i\00<
2016.04.06 15:28:04.687 5: MyHMLAN: HM485_Parse: MsgId: 91
2016.04.06 15:28:04.687 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:04.688 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003C18
2016.04.06 15:28:04.690 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.692 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.695 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.697 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.698 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15384
2016.04.06 15:28:04.698 5: HM485: HM485:Device:dataConversion: retVal = 15384.00
2016.04.06 15:28:04.698 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15384.00
2016.04.06 15:28:04.698 5: HM485: Device:valueToControl: valName = frequency = 15384.00
2016.04.06 15:28:04.699 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003C18 actionType = frame
2016.04.06 15:28:04.699 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 92 Cmd: 101
2016.04.06 15:28:04.700 4: MyHMLAN: Event:HASH(0x5930f48)
2016.04.06 15:28:04.700 5: MyHMLAN dispatch \FD\e\00\00\00^\00\00\9A+i\00:\AF
2016.04.06 15:28:04.700 5: MyHMLAN: HM485_Parse: MsgId: 92
2016.04.06 15:28:04.701 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:04.701 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003AAF
2016.04.06 15:28:04.703 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.705 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.708 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.709 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:04.710 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15023
2016.04.06 15:28:04.710 5: HM485: HM485:Device:dataConversion: retVal = 15023.00
2016.04.06 15:28:04.711 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15023.00
2016.04.06 15:28:04.711 5: HM485: Device:valueToControl: valName = frequency = 15023.00
2016.04.06 15:28:04.711 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003AAF actionType = frame
2016.04.06 15:28:04.712 5: CUL/RAW: /E03093E65B6000065B60F

2016.04.06 15:28:04.712 4: CUL_Parse: CUL_0 E03093E65B6000065B60F -66.5
2016.04.06 15:28:04.713 5: CUL_0 dispatch E03093E65B6000065B6
2016.04.06 15:28:04.714 5: Mi Apr  6 15:28:04 2016
2016.04.06 15:28:04.714 5: CUL_EM Gaszaehler: seqno: 62 total_cnt: 46693  current_cnt: 0  peak_cnt: 46693
2016.04.06 15:28:04.715 4: CUL_EM Gaszaehler: CNT: 62 CUM: 15196.992  5MIN: 0.000  TOP: 0.000
2016.04.06 15:28:04.717 5: Triggering Gaszaehler (1 changes)
2016.04.06 15:28:04.717 5: Starting notify loop for Gaszaehler, first event CNT: 62 CUM: 15196.992  5MIN: 0.000  TOP: 0.000
2016.04.06 15:28:04.719 5: Notify from Device: Gaszaehler recieved
2016.04.06 15:28:04.721 5: DbLog: logging of Device: Gaszaehler , Type: CUL_EM , Event: CNT: 62 CUM: 15196.992  5MIN: 0.000  TOP: 0.000 , Reading: CNT , Value: 62 CUM: 15196.992  5MIN: 0.000  TOP: 0.000 , Unit:
2016.04.06 15:28:04.752 5: OWServer child ID for reading '/28.36FE4F070000/temperature10' is 25839
2016.04.06 15:28:05.007 5: OWServer child read /28.36FE4F070000/temperature10: 24.5
2016.04.06 15:28:05.479 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:05.480 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15384.00 Alter Wert = 15165.00
2016.04.06 15:28:05.480 4: HMW02.I07: frequency -> 15384.00
2016.04.06 15:28:05.485 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:05.486 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15023.00 Alter Wert = 15384.00
2016.04.06 15:28:05.486 4: HMW02.I07: frequency -> 15023.00
2016.04.06 15:28:05.491 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 93 Cmd: 101
2016.04.06 15:28:05.492 4: MyHMLAN: Event:HASH(0x5946a18)
2016.04.06 15:28:05.492 5: MyHMLAN dispatch \FD]e\00\00\00X\00\00\9A+i\00<
2016.04.06 15:28:05.492 5: MyHMLAN: HM485_Parse: MsgId: 93
2016.04.06 15:28:05.493 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:05.493 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003C18
2016.04.06 15:28:05.496 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:05.497 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:05.501 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:05.502 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:05.503 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15384
2016.04.06 15:28:05.503 5: HM485: HM485:Device:dataConversion: retVal = 15384.00
2016.04.06 15:28:05.503 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15384.00
2016.04.06 15:28:05.504 5: HM485: Device:valueToControl: valName = frequency = 15384.00
2016.04.06 15:28:05.504 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003C18 actionType = frame
2016.04.06 15:28:05.510 5: OWServer child ID for reading '/28.6B878A060000/temperature10' is 25843
2016.04.06 15:28:05.831 5: OWServer child read /28.6B878A060000/temperature10: 28.75
2016.04.06 15:28:06.302 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:06.303 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15384.00 Alter Wert = 15023.00
2016.04.06 15:28:06.303 4: HMW02.I07: frequency -> 15384.00
2016.04.06 15:28:06.313 5: OWServer child ID for reading '/28.59F550070000/temperature10' is 25847
2016.04.06 15:28:06.569 5: OWServer child read /28.59F550070000/temperature10: 22.5
2016.04.06 15:28:07.040 1: Perfmon: possible freeze starting at 15:28:06, delay is 1.04
2016.04.06 15:28:07.041 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 94 Cmd: 101
2016.04.06 15:28:07.042 4: MyHMLAN: Event:HASH(0x5946688)
2016.04.06 15:28:07.042 5: MyHMLAN dispatch \FD^e\00\00\00Z\00\00\9A+i\00:\F6
2016.04.06 15:28:07.043 5: MyHMLAN: HM485_Parse: MsgId: 94
2016.04.06 15:28:07.043 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:07.043 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003AF6
2016.04.06 15:28:07.046 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:07.048 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:07.051 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:07.053 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:07.053 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15094
2016.04.06 15:28:07.054 5: HM485: HM485:Device:dataConversion: retVal = 15094.00
2016.04.06 15:28:07.054 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15094.00
2016.04.06 15:28:07.054 5: HM485: Device:valueToControl: valName = frequency = 15094.00
2016.04.06 15:28:07.054 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003AF6 actionType = frame
2016.04.06 15:28:07.060 5: OWServer child ID for reading '/28.AF6551070000/temperature10' is 25851
2016.04.06 15:28:07.380 5: OWServer child read /28.AF6551070000/temperature10: 32.5
2016.04.06 15:28:07.856 5: OWServer child ID for reading '/28.F4C58A060000/temperature10' is 25855
2016.04.06 15:28:08.109 5: OWServer child read /28.F4C58A060000/temperature10: 33.25
2016.04.06 15:28:08.580 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:08.581 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15094.00 Alter Wert = 15384.00
2016.04.06 15:28:08.581 4: HMW02.I07: frequency -> 15094.00
2016.04.06 15:28:08.585 5: Triggering HMW02.I07 (1 changes)
2016.04.06 15:28:08.586 5: Starting notify loop for HMW02.I07, first event leistung: 2755.75
2016.04.06 15:28:08.588 5: Notify from Device: HMW02.I07 recieved
2016.04.06 15:28:08.589 5: DbLog: logging of Device: HMW02.I07 , Type: HM485 , Event: leistung: 2755.75 , Reading: leistung , Value: 2755.75 , Unit:
2016.04.06 15:28:08.616 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 95 Cmd: 101
2016.04.06 15:28:08.617 4: MyHMLAN: Event:HASH(0x5946d90)
2016.04.06 15:28:08.617 5: MyHMLAN dispatch \FD_e\00\00\00\\00\00\9A+i\00;\86
2016.04.06 15:28:08.617 5: MyHMLAN: HM485_Parse: MsgId: 95
2016.04.06 15:28:08.618 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:08.618 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B86
2016.04.06 15:28:08.621 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:08.622 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:08.626 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:08.627 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:08.628 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15238
2016.04.06 15:28:08.628 5: HM485: HM485:Device:dataConversion: retVal = 15238.00
2016.04.06 15:28:08.628 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15238.00
2016.04.06 15:28:08.629 5: HM485: Device:valueToControl: valName = frequency = 15238.00
2016.04.06 15:28:08.629 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003B86 actionType = frame
2016.04.06 15:28:08.635 5: OWServer child ID for reading '/28.FF7DE5A41503/temperature10' is 25859
2016.04.06 15:28:08.888 5: OWServer child read /28.FF7DE5A41503/temperature10: 22.75
2016.04.06 15:28:09.359 1: Perfmon: possible freeze starting at 15:28:08, delay is 1.359
2016.04.06 15:28:09.360 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:09.360 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15238.00 Alter Wert = 15094.00
2016.04.06 15:28:09.361 4: HMW02.I07: frequency -> 15238.00
2016.04.06 15:28:09.369 4: <hidden>: HTTP response code 200
2016.04.06 15:28:09.369 4: HttpUtils <hidden>: Got data, length: 23
2016.04.06 15:28:09.369 5: TelegramBot_Callback remotebot: called from Polling
2016.04.06 15:28:09.369 5: TelegramBot_ParseUpdate remotebot: data returned :{"ok":true,"result":[]}:
2016.04.06 15:28:09.370 5: UpdatePoll remotebot: number of results 0
2016.04.06 15:28:09.370 5: TelegramBot_UpdatePoll remotebot: called
2016.04.06 15:28:09.370 4: TelegramBot_UpdatePoll remotebot: initiate polling with nonblockingGet with 30s
2016.04.06 15:28:09.371 4: HttpUtils url=<hidden>
2016.04.06 15:28:09.374 4: TelegramBot_Callback remotebot: resulted in :SUCCESS: from Polling
2016.04.06 15:28:10.772 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 96 Cmd: 101
2016.04.06 15:28:10.772 4: MyHMLAN: Event:HASH(0x58d38e8)
2016.04.06 15:28:10.772 5: MyHMLAN dispatch \FD`e\FF\FF\FF\FF\F8\00\00\B8\C5K\00\00\C6
2016.04.06 15:28:10.773 5: MyHMLAN: HM485_Parse: MsgId: 96
2016.04.06 15:28:10.773 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:10.773 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4B0000C6
2016.04.06 15:28:10.777 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 49
2016.04.06 15:28:10.777 5: HM485: HM485:Device:dataConversion: retVal = 49
2016.04.06 15:28:10.777 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 49
2016.04.06 15:28:10.778 5: HM485: Device:valueToControl: valName = press_short = 49
2016.04.06 15:28:10.778 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B0000C6 actionType = frame
2016.04.06 15:28:10.779 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:10.780 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:10.782 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:10.783 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:10.810 4: HMW01.I01: HM485_ChannelDoUpdate
2016.04.06 15:28:10.810 5: HMW01.I01: HM485_ChannelDoUpdate: valueKey = press_short value = 49 Alter Wert = 48
2016.04.06 15:28:10.810 4: HMW01.I01: press_short -> 49
2016.04.06 15:28:10.811 5: Triggering HMW01.I01 (2 changes)
2016.04.06 15:28:10.811 5: Starting notify loop for HMW01.I01, first event press_short: 49
2016.04.06 15:28:10.812 5: Triggering N_1.I01_short
2016.04.06 15:28:10.813 4: N_1.I01_short exec set HMW01.O04 toggle
2016.04.06 15:28:10.813 5: Cmd: >set HMW01.O04 toggle<
2016.04.06 15:28:10.817 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_SendCommand: 780FFF
2016.04.06 15:28:10.819 5: Notify from Device: HMW01.I01 recieved
2016.04.06 15:28:10.820 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short: 49 , Reading: press_short , Value: 49 , Unit:
2016.04.06 15:28:10.859 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short_49 , Reading: state , Value: press_short_49 , Unit:
2016.04.06 15:28:10.905 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 97 Cmd: 101
2016.04.06 15:28:10.905 4: MyHMLAN: Event:HASH(0x58d4798)
2016.04.06 15:28:10.905 5: MyHMLAN dispatch \FDae\FF\FF\FF\FF\FA\00\00\B8\C5A\00\00LEQ0016352
2016.04.06 15:28:10.906 5: MyHMLAN: HM485_Parse: MsgId: 97
2016.04.06 15:28:10.906 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:10.906 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4100120003064C455130303136333532
2016.04.06 15:28:10.907 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 15:28:10.909 5: Triggering HMW01.O04 (1 changes)
2016.04.06 15:28:10.909 5: Starting notify loop for HMW01.O04, first event set_toggle
2016.04.06 15:28:10.911 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:10.912 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: set_toggle , Reading: state , Value: set_toggle , Unit:
2016.04.06 15:28:10.939 5: MyHMLAN: HM485_LAN_Write TX: 101
2016.04.06 15:28:10.939 5: MyHMLAN: HM485_LAN_SendQueueNextItem: QID: 00000192
2016.04.06 15:28:10.940 5: SW: fd0f6553c80000b8c51800000001780fff
2016.04.06 15:28:10.941 4: MyHMLAN: MyHMLAN: TX: (101) I[0](0,F,B)(18) 00000001 -> 0000B8C5 [5] 78(x) 0FFF
2016.04.06 15:28:10.941 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_DoSendCommand: hmwId = 0000B8C5 data = 780FFF requestId = 101
2016.04.06 15:28:10.942 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:10.942 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:10.944 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:10.945 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:10.984 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 101 Cmd: 114
2016.04.06 15:28:10.984 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Response: (101) 690FC800
2016.04.06 15:28:10.984 5: MyHMLAN dispatch \FDeri\C8\00
2016.04.06 15:28:10.985 5: MyHMLAN: HM485_Parse: MsgId: 101
2016.04.06 15:28:10.985 5: MyHMLAN: HM485_Parse: ProcessResponse
2016.04.06 15:28:10.985 5: MyHMLAN: HM485_ProcessResponse: msgData = 690FC800
2016.04.06 15:28:10.985 5: MyHMLAN: HM485_ProcessResponse: deviceKey =  requestType = 78 requestData = 0FFF msgData = 690FC800
2016.04.06 15:28:10.988 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state_flags value1 = 0
2016.04.06 15:28:10.988 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:10.988 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:28:10.988 5: HM485: Device:valueToControl: valName = working = 0
2016.04.06 15:28:10.990 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state value1 = 200
2016.04.06 15:28:10.990 5: HM485: HM485:Device:dataConversion: retVal = 1
2016.04.06 15:28:10.990 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 1
2016.04.06 15:28:10.990 5: HM485: Device:valueToControl: valName = state = 1
2016.04.06 15:28:10.991 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 16 msgData = 690FC800 actionType = response
2016.04.06 15:28:10.991 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Removing Queue 00000192
2016.04.06 15:28:10.992 5: MyHMLAN: HM485_LAN_CheckResendQueueItems: QID: 00000192
2016.04.06 15:28:10.993 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:10.993 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:10.995 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:10.996 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:11.028 4: HMW01.O04: HM485_ChannelDoUpdate
2016.04.06 15:28:11.028 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = state value = on Alter Wert = set_toggle
2016.04.06 15:28:11.028 4: HMW01.O04: state -> on
2016.04.06 15:28:11.028 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = working value = off Alter Wert = off
2016.04.06 15:28:11.029 4: HMW01.O04: working -> off
2016.04.06 15:28:11.029 5: Triggering HMW01.O04 (2 changes)
2016.04.06 15:28:11.029 5: Starting notify loop for HMW01.O04, first event on
2016.04.06 15:28:11.031 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:11.032 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: on , Reading: state , Value: on , Unit:
2016.04.06 15:28:11.072 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: working: off , Reading: working , Value: off , Unit:
2016.04.06 15:28:15.187 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 98 Cmd: 101
2016.04.06 15:28:15.187 4: MyHMLAN: Event:HASH(0x592ccb0)
2016.04.06 15:28:15.188 5: MyHMLAN dispatch \FDbe\00\00\00^\00\00\9A+i\00;\CF
2016.04.06 15:28:15.188 5: MyHMLAN: HM485_Parse: MsgId: 98
2016.04.06 15:28:15.188 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:15.189 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003BCF
2016.04.06 15:28:15.191 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:15.193 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:15.196 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:15.197 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:15.198 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15311
2016.04.06 15:28:15.198 5: HM485: HM485:Device:dataConversion: retVal = 15311.00
2016.04.06 15:28:15.199 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15311.00
2016.04.06 15:28:15.199 5: HM485: Device:valueToControl: valName = frequency = 15311.00
2016.04.06 15:28:15.199 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003BCF actionType = frame
2016.04.06 15:28:15.201 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:15.201 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15311.00 Alter Wert = 15238.00
2016.04.06 15:28:15.201 4: HMW02.I07: frequency -> 15311.00
2016.04.06 15:28:15.205 5: Triggering HMW02.I07 (1 changes)
2016.04.06 15:28:15.205 5: Starting notify loop for HMW02.I07, first event literpromin: 17.5874093179897
2016.04.06 15:28:15.207 5: Notify from Device: HMW02.I07 recieved
2016.04.06 15:28:15.208 5: DbLog: logging of Device: HMW02.I07 , Type: HM485 , Event: literpromin: 17.5874093179897 , Reading: literpromin , Value: 17.5874093179897 , Unit:
2016.04.06 15:28:17.411 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 99 Cmd: 101
2016.04.06 15:28:17.412 4: MyHMLAN: Event:HASH(0x5936418)
2016.04.06 15:28:17.412 5: MyHMLAN dispatch \FDce\00\00\00X\00\00\9A+i\00;=
2016.04.06 15:28:17.412 5: MyHMLAN: HM485_Parse: MsgId: 99
2016.04.06 15:28:17.412 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:17.413 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B3D
2016.04.06 15:28:17.415 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:17.416 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:17.420 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:17.421 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:17.422 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15165
2016.04.06 15:28:17.422 5: HM485: HM485:Device:dataConversion: retVal = 15165.00
2016.04.06 15:28:17.422 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15165.00
2016.04.06 15:28:17.423 5: HM485: Device:valueToControl: valName = frequency = 15165.00
2016.04.06 15:28:17.423 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003B3D actionType = frame
2016.04.06 15:28:17.424 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:17.425 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15165.00 Alter Wert = 15311.00
2016.04.06 15:28:17.425 4: HMW02.I07: frequency -> 15165.00
2016.04.06 15:28:17.429 5: Triggering HMW02.I07 (1 changes)
2016.04.06 15:28:17.429 5: Starting notify loop for HMW02.I07, first event leistung: 2744.66666666667
2016.04.06 15:28:17.431 5: Notify from Device: HMW02.I07 recieved
2016.04.06 15:28:17.432 5: DbLog: logging of Device: HMW02.I07 , Type: HM485 , Event: leistung: 2744.66666666667 , Reading: leistung , Value: 2744.66666666667 , Unit:
2016.04.06 15:28:19.193 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 100 Cmd: 101
2016.04.06 15:28:19.193 4: MyHMLAN: Event:HASH(0x5936838)
2016.04.06 15:28:19.193 5: MyHMLAN dispatch \FDde\FF\FF\FF\FF\9E\00\00\B8\C5K\00\00\CA
2016.04.06 15:28:19.194 5: MyHMLAN: HM485_Parse: MsgId: 100
2016.04.06 15:28:19.194 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:19.194 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4B0000CA
2016.04.06 15:28:19.197 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 50
2016.04.06 15:28:19.198 5: HM485: HM485:Device:dataConversion: retVal = 50
2016.04.06 15:28:19.198 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 50
2016.04.06 15:28:19.198 5: HM485: Device:valueToControl: valName = press_short = 50
2016.04.06 15:28:19.198 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B0000CA actionType = frame
2016.04.06 15:28:19.200 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.200 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.202 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.203 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.216 4: HMW01.I01: HM485_ChannelDoUpdate
2016.04.06 15:28:19.216 5: HMW01.I01: HM485_ChannelDoUpdate: valueKey = press_short value = 50 Alter Wert = 49
2016.04.06 15:28:19.217 4: HMW01.I01: press_short -> 50
2016.04.06 15:28:19.217 5: Triggering HMW01.I01 (2 changes)
2016.04.06 15:28:19.217 5: Starting notify loop for HMW01.I01, first event press_short: 50
2016.04.06 15:28:19.218 5: Triggering N_1.I01_short
2016.04.06 15:28:19.219 4: N_1.I01_short exec set HMW01.O04 toggle
2016.04.06 15:28:19.219 5: Cmd: >set HMW01.O04 toggle<
2016.04.06 15:28:19.223 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_SendCommand: 780FFF
2016.04.06 15:28:19.224 5: Notify from Device: HMW01.I01 recieved
2016.04.06 15:28:19.226 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short: 50 , Reading: press_short , Value: 50 , Unit:
2016.04.06 15:28:19.253 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short_50 , Reading: state , Value: press_short_50 , Unit:
2016.04.06 15:28:19.286 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 101 Cmd: 101
2016.04.06 15:28:19.287 4: MyHMLAN: Event:HASH(0x5936aa8)
2016.04.06 15:28:19.287 5: MyHMLAN dispatch \FDee\FF\FF\FF\FF\98\00\00\B8\C5A\00\00LEQ0016352
2016.04.06 15:28:19.287 5: MyHMLAN: HM485_Parse: MsgId: 101
2016.04.06 15:28:19.288 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:19.288 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4100120003064C455130303136333532
2016.04.06 15:28:19.289 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 15:28:19.290 5: Triggering HMW01.O04 (1 changes)
2016.04.06 15:28:19.291 5: Starting notify loop for HMW01.O04, first event set_toggle
2016.04.06 15:28:19.292 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:19.293 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: set_toggle , Reading: state , Value: set_toggle , Unit:
2016.04.06 15:28:19.330 5: MyHMLAN: HM485_LAN_Write TX: 102
2016.04.06 15:28:19.331 5: MyHMLAN: HM485_LAN_SendQueueNextItem: QID: 00000193
2016.04.06 15:28:19.331 5: SW: fd0f6653c80000b8c51a00000001780fff
2016.04.06 15:28:19.332 4: MyHMLAN: MyHMLAN: TX: (102) I[1](0,F,B)(1A) 00000001 -> 0000B8C5 [5] 78(x) 0FFF
2016.04.06 15:28:19.333 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_DoSendCommand: hmwId = 0000B8C5 data = 780FFF requestId = 102
2016.04.06 15:28:19.333 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.334 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.335 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.337 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.375 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 102 Cmd: 114
2016.04.06 15:28:19.376 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Response: (102) 690F0000
2016.04.06 15:28:19.376 5: MyHMLAN dispatch \FDfr:i\00\00
2016.04.06 15:28:19.376 5: MyHMLAN: HM485_Parse: MsgId: 102
2016.04.06 15:28:19.376 5: MyHMLAN: HM485_Parse: ProcessResponse
2016.04.06 15:28:19.377 5: MyHMLAN: HM485_ProcessResponse: msgData = 690F0000
2016.04.06 15:28:19.377 5: MyHMLAN: HM485_ProcessResponse: deviceKey =  requestType = 78 requestData = 0FFF msgData = 690F0000
2016.04.06 15:28:19.379 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state value1 = 0
2016.04.06 15:28:19.379 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:19.380 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:28:19.380 5: HM485: Device:valueToControl: valName = state = 0
2016.04.06 15:28:19.381 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state_flags value1 = 0
2016.04.06 15:28:19.381 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:19.381 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:28:19.382 5: HM485: Device:valueToControl: valName = working = 0
2016.04.06 15:28:19.382 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 16 msgData = 690F0000 actionType = response
2016.04.06 15:28:19.382 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Removing Queue 00000193
2016.04.06 15:28:19.383 5: MyHMLAN: HM485_LAN_CheckResendQueueItems: QID: 00000193
2016.04.06 15:28:19.384 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.384 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.386 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.387 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.419 4: HMW01.O04: HM485_ChannelDoUpdate
2016.04.06 15:28:19.419 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = working value = off Alter Wert = off
2016.04.06 15:28:19.420 4: HMW01.O04: working -> off
2016.04.06 15:28:19.420 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = state value = off Alter Wert = set_toggle
2016.04.06 15:28:19.420 4: HMW01.O04: state -> off
2016.04.06 15:28:19.420 5: Triggering HMW01.O04 (2 changes)
2016.04.06 15:28:19.421 5: Starting notify loop for HMW01.O04, first event working: off
2016.04.06 15:28:19.422 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:19.423 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: working: off , Reading: working , Value: off , Unit:
2016.04.06 15:28:19.463 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: off , Reading: state , Value: off , Unit:
2016.04.06 15:28:19.695 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 102 Cmd: 101
2016.04.06 15:28:19.695 4: MyHMLAN: Event:HASH(0x5936ce8)
2016.04.06 15:28:19.696 5: MyHMLAN dispatch \FDfe\FF\FF\FF\FF\BC\00\00\B8\C5K\00\00\CE
2016.04.06 15:28:19.696 5: MyHMLAN: HM485_Parse: MsgId: 102
2016.04.06 15:28:19.696 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:19.697 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4B0000CE
2016.04.06 15:28:19.700 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 51
2016.04.06 15:28:19.700 5: HM485: HM485:Device:dataConversion: retVal = 51
2016.04.06 15:28:19.700 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 51
2016.04.06 15:28:19.700 5: HM485: Device:valueToControl: valName = press_short = 51
2016.04.06 15:28:19.701 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B0000CE actionType = frame
2016.04.06 15:28:19.702 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.702 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.704 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.705 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.717 4: HMW01.I01: HM485_ChannelDoUpdate
2016.04.06 15:28:19.717 5: HMW01.I01: HM485_ChannelDoUpdate: valueKey = press_short value = 51 Alter Wert = 50
2016.04.06 15:28:19.718 4: HMW01.I01: press_short -> 51
2016.04.06 15:28:19.718 5: Triggering HMW01.I01 (2 changes)
2016.04.06 15:28:19.718 5: Starting notify loop for HMW01.I01, first event press_short: 51
2016.04.06 15:28:19.720 5: Triggering N_1.I01_short
2016.04.06 15:28:19.720 4: N_1.I01_short exec set HMW01.O04 toggle
2016.04.06 15:28:19.720 5: Cmd: >set HMW01.O04 toggle<
2016.04.06 15:28:19.724 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_SendCommand: 780FFF
2016.04.06 15:28:19.726 5: Notify from Device: HMW01.I01 recieved
2016.04.06 15:28:19.727 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short: 51 , Reading: press_short , Value: 51 , Unit:
2016.04.06 15:28:19.762 5: DbLog: logging of Device: HMW01.I01 , Type: HM485 , Event: press_short_51 , Reading: state , Value: press_short_51 , Unit:
2016.04.06 15:28:19.776 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 103 Cmd: 101
2016.04.06 15:28:19.777 4: MyHMLAN: Event:HASH(0x5936f28)
2016.04.06 15:28:19.777 5: MyHMLAN dispatch \FDge\FF\FF\FF\FF\BE\00\00\B8\C5A\00\00LEQ0016352
2016.04.06 15:28:19.777 5: MyHMLAN: HM485_Parse: MsgId: 103
2016.04.06 15:28:19.778 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:19.778 5: MyHMLAN: HM485_ProcessEvent: hmwId = 0000B8C5 msgData = 4100120003064C455130303136333532
2016.04.06 15:28:19.779 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 15:28:19.780 5: Triggering HMW01.O04 (1 changes)
2016.04.06 15:28:19.781 5: Starting notify loop for HMW01.O04, first event set_toggle
2016.04.06 15:28:19.782 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:19.784 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: set_toggle , Reading: state , Value: set_toggle , Unit:
2016.04.06 15:28:19.814 5: MyHMLAN: HM485_LAN_Write TX: 103
2016.04.06 15:28:19.815 5: MyHMLAN: HM485_LAN_SendQueueNextItem: QID: 00000194
2016.04.06 15:28:19.815 5: SW: fd0f6753c80000b8c51c00000001780fff
2016.04.06 15:28:19.817 4: MyHMLAN: MyHMLAN: TX: (103) I[2](0,F,B)(1C) 00000001 -> 0000B8C5 [5] 78(x) 0FFF
2016.04.06 15:28:19.817 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_DoSendCommand: hmwId = 0000B8C5 data = 780FFF requestId = 103
2016.04.06 15:28:19.818 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.818 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.820 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.821 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.862 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 103 Cmd: 114
2016.04.06 15:28:19.863 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Response: (103) 690FC800
2016.04.06 15:28:19.863 5: MyHMLAN dispatch \FDgrXi\C8\00
2016.04.06 15:28:19.863 5: MyHMLAN: HM485_Parse: MsgId: 103
2016.04.06 15:28:19.864 5: MyHMLAN: HM485_Parse: ProcessResponse
2016.04.06 15:28:19.864 5: MyHMLAN: HM485_ProcessResponse: msgData = 690FC800
2016.04.06 15:28:19.864 5: MyHMLAN: HM485_ProcessResponse: deviceKey =  requestType = 78 requestData = 0FFF msgData = 690FC800
2016.04.06 15:28:19.866 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state value1 = 200
2016.04.06 15:28:19.867 5: HM485: HM485:Device:dataConversion: retVal = 1
2016.04.06 15:28:19.867 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 1
2016.04.06 15:28:19.867 5: HM485: Device:valueToControl: valName = state = 1
2016.04.06 15:28:19.868 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = state_flags value1 = 0
2016.04.06 15:28:19.869 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:19.869 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 0
2016.04.06 15:28:19.869 5: HM485: Device:valueToControl: valName = working = 0
2016.04.06 15:28:19.869 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 16 msgData = 690FC800 actionType = response
2016.04.06 15:28:19.870 5: MyHMLAN: HM485_LAN_parseIncommingCommand: Removing Queue 00000194
2016.04.06 15:28:19.870 5: MyHMLAN: HM485_LAN_CheckResendQueueItems: QID: 00000194
2016.04.06 15:28:19.871 5: Triggering HMW_IO_12_Sw7_DR_LEQ0016352 (1 changes)
2016.04.06 15:28:19.872 5: Starting notify loop for HMW_IO_12_Sw7_DR_LEQ0016352, first event ACK
2016.04.06 15:28:19.873 5: Notify from Device: HMW_IO_12_Sw7_DR_LEQ0016352 recieved
2016.04.06 15:28:19.874 5: DbLog: logging of Device: HMW_IO_12_Sw7_DR_LEQ0016352 , Type: HM485 , Event: ACK , Reading: state , Value: ACK , Unit:
2016.04.06 15:28:19.906 4: HMW01.O04: HM485_ChannelDoUpdate
2016.04.06 15:28:19.906 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = working value = off Alter Wert = off
2016.04.06 15:28:19.907 4: HMW01.O04: working -> off
2016.04.06 15:28:19.907 5: HMW01.O04: HM485_ChannelDoUpdate: valueKey = state value = on Alter Wert = set_toggle
2016.04.06 15:28:19.907 4: HMW01.O04: state -> on
2016.04.06 15:28:19.908 5: Triggering HMW01.O04 (2 changes)
2016.04.06 15:28:19.908 5: Starting notify loop for HMW01.O04, first event working: off
2016.04.06 15:28:19.909 5: Notify from Device: HMW01.O04 recieved
2016.04.06 15:28:19.911 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: working: off , Reading: working , Value: off , Unit:
2016.04.06 15:28:19.950 5: DbLog: logging of Device: HMW01.O04 , Type: HM485 , Event: on , Reading: state , Value: on , Unit:
2016.04.06 15:28:22.101 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 104 Cmd: 101
2016.04.06 15:28:22.102 4: MyHMLAN: Event:HASH(0x5938610)
2016.04.06 15:28:22.102 5: MyHMLAN dispatch \FDhe\00\00\00Z\00\00\9A+i\00;\CF
2016.04.06 15:28:22.102 5: MyHMLAN: HM485_Parse: MsgId: 104
2016.04.06 15:28:22.102 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:22.103 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003BCF
2016.04.06 15:28:22.105 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:22.106 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:22.110 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:22.111 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:22.112 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15311
2016.04.06 15:28:22.112 5: HM485: HM485:Device:dataConversion: retVal = 15311.00
2016.04.06 15:28:22.112 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: value2 = 15311.00
2016.04.06 15:28:22.113 5: HM485: Device:valueToControl: valName = frequency = 15311.00
2016.04.06 15:28:22.113 5: HMW_IO_12_Sw14_DR_JEQ0459634: HM485_ProcessChannelState: hmwId = 00009A2B Channel = 15 msgData = 690E003BCF actionType = frame
2016.04.06 15:28:22.114 4: HMW02.I07: HM485_ChannelDoUpdate
2016.04.06 15:28:22.115 5: HMW02.I07: HM485_ChannelDoUpdate: valueKey = frequency value = 15311.00 Alter Wert = 15165.00
2016.04.06 15:28:22.115 4: HMW02.I07: frequency -> 15311.00
2016.04.06 15:28:23.603 5: MyHMLAN: HM485_LAN_parseIncommingCommand: MsgId: 105 Cmd: 101
2016.04.06 15:28:23.604 4: MyHMLAN: Event:HASH(0x59474e0)
2016.04.06 15:28:23.604 5: MyHMLAN dispatch \FDie\00\00\00\\00\00\9A+i\00;\86
2016.04.06 15:28:23.604 5: MyHMLAN: HM485_Parse: MsgId: 105
2016.04.06 15:28:23.605 5: MyHMLAN: HM485_Parse: ProcessEvent
2016.04.06 15:28:23.605 5: MyHMLAN: HM485_ProcessEvent: hmwId = 00009A2B msgData = 690E003B86
2016.04.06 15:28:23.607 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:23.609 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:23.612 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:23.613 5: HM485: HM485:Device:dataConversion: retVal = 0
2016.04.06 15:28:23.614 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW14_DR valId = state value1 = 15238
2016.04.06 15:28:23.614 5: HM485: HM485:Device:dataConversion: retVal = 15238.00
2016.04.06 15:28:23.614 5: HMW_IO_12_Sw14_DR_JEQ0459634: Device:con
« Letzte Änderung: 06 April 2016, 15:43:45 von abc2006 »
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #4 am: 06 April 2016, 15:41:39 »
Hi,
wie sehen denn Deine notifys aus?
Gruß,
   Thorsten
FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #5 am: 06 April 2016, 15:48:11 »
Hi Thorsten, bezüglich der notifies:

Hier das erste notify als Beispiel:
HMW01.I01:press_long:.* set FS20_Garage onHMW01.I01:press_short:.* set FS20_Garage offSo habe ich das für jeden Eingang meines Homematic angelegt, mit verschiedenen set-Befehlen natürlich.
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #6 am: 06 April 2016, 15:50:15 »
Hi,
hab die notifys grade gefunden. Allerdings wundere ich mich, wo dann das hier im Event-Monitor herkommt:
2016-04-06 13:24:09.825 HM485 HMW01.O04 set_toggle
Anyway...
Erst einmal sollten wir rausfinden, ob da tatsächlich Events verloren gehen. Ist es tatsächlich so, dass etwas im Event-Monitor fehlt?
Ansonsten: Taucht das Problem nur für HMW-Aktoren auf oder auch für FS20-Aktoren?
Das Problem ist: Das Toggle-Kommando ist für manche Aktoren in FHEM implementiert, da es der Aktor selbst nicht kann. Das Problem dabei ist, dass erst einmal die Rückmeldung vom Aktor kommen muss, bis man wieder korrekt "toggeln" kann.
Gruß,
   Thorsten

 
FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #7 am: 06 April 2016, 16:03:18 »
Hi,
hab die notifys grade gefunden. Allerdings wundere ich mich, wo dann das hier im Event-Monitor herkommt:
2016-04-06 13:24:09.825 HM485 HMW01.O04 set_toggle
Anyway...
define N_1.I01_short notify HMW01.I01:press_short:.* set HMW01.O04 toggle
attr N_1.I01_short group n_short
attr N_1.I01_short room _notify
define N_1.I01_long notify HMW01.I01:press_long:.* set FS20_Garage toggle
attr N_1.I01_long group n_long
attr N_1.I01_long room _notify

Hi Thorsten,
da ist mir wohl beim testen eine asynchronität unterlaufen.. vorher hat das drin gestanden, habs jetzt mal aus der fhem.cfg rausgeklaubt...

Ansonsten: Taucht das Problem nur für HMW-Aktoren auf oder auch für FS20-Aktoren?
Das Problem ist: Das Toggle-Kommando ist für manche Aktoren in FHEM implementiert, da es der Aktor selbst nicht kann. Das Problem dabei ist, dass erst einmal die Rückmeldung vom Aktor kommen muss, bis man wieder korrekt "toggeln" kann.

Das Problem taucht nicht nur für HMW-Aktoren auf.
Ich habe grade mal getestet:

define N_1.I01_short notify HMW01.I01:press_short:.* set HMW01.O04 off
attr N_1.I01_short group n_short
attr N_1.I01_short room _notify
define N_1.I01_long notify HMW01.I01:press_long:.* set HMW01.O04 on
attr N_1.I01_long group n_long
attr N_1.I01_long room _notify

auch hierbei treten die Probleme wie beschrieben auf.

dann habe ich getestet:
 
define N_1.I01_short notify HMW01.I01:press_short:.* set FS20_TEST off
attr N_1.I01_short group n_short
attr N_1.I01_short room _notify
define N_1.I01_long notify HMW01.I01:press_long:.* set FS20_TEST on
attr N_1.I01_long group n_long
attr N_1.I01_long room _notify

Hierbei treten die Verzögerungen im Schalten des FS20ST4 genauso auf, d.h. ich habe ein vergleichbares delay. Jetzt könnte ich noch HMW und FS20 gleichzeitig schalten lassen und schauen ob das synchron ist ...

Ob im Event-Monitor Events *fehlen*, weiss ich nicht. Die nummerierung ist durchgehend. Allerdings ist es tatsächlich so, dass Tastendrücke, die ich ausgeführt habe, nicht aufgelistet, nummeriert und bearbeitet werden.

Grüße
Stephan
« Letzte Änderung: 06 April 2016, 17:10:38 von abc2006 »
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #8 am: 06 April 2016, 17:37:29 »
Okay, nochmal ne Info von mir. Gerade habe ich den Taster im Bad ca. 60 Sekunden festgehalten. Vielleicht auch mehr, hatte mein Handy mit dem Event-Monitor nicht so schnell zur Hand. Habe auf jeden Fall nicht losgelassen. Taster siehe unten(Badezimmer.png). Dazu gehört das notify long, siehe notify_long.png
Im Eventmonitor sind folgende Zeilen aufgetaucht:

2016-04-06 17:31:06.858 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:06.905 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:06.949 HM485 HMW02.I07 leistung: 607.5
2016-04-06 17:31:06.994 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:08.816 OWDevice DS18B20_Ruecklauf_WT_EG temperature: 26.75
2016-04-06 17:31:09.784 HM485 HMW02.I07 leistung: 305.5
2016-04-06 17:31:12.800 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:13.089 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:13.391 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:13.690 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:13.991 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:14.292 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:14.593 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:14.916 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:15.195 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:18.178 HM485 HMW02.I07 leistung: 303.5
2016-04-06 17:31:20.333 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:20.610 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:20.910 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:21.210 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:21.511 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:21.814 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e temperature: 21.3
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e humidity: 43.8
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e battery: ok
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e type: HMS100TF
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e T: 21.3  H: 43.8  Bat: ok
2016-04-06 17:31:21.964 HMS HMS100TF_5f5e taupunkt: 8.49547065340043
2016-04-06 17:31:27.543 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:27.829 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:28.130 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:28.186 HM485 HMW02.I07 literpromin: 17.5442810364209
2016-04-06 17:31:28.186 HM485 HMW02.I07 leistung: 306
2016-04-06 17:31:28.432 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:28.731 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:29.033 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:29.334 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:29.634 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:29.934 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:30.334 HM485 HMW02.I07 leistung: 305
2016-04-06 17:31:32.190 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:32.220 HM485 HMW_IO_12_Sw7_DR_LEQ0016352 ACK
2016-04-06 17:31:38.516 HM485 HMW02.I07 leistung: 305.666666666667
2016-04-06 17:31:42.043 HM485 HMW02.I07 spreizung: 0.338235294117647
2016-04-06 17:31:44.457 CUL_WS S300TH T: 16.6  H: 64.9
2016-04-06 17:31:44.457 CUL_WS S300TH humidity: 64.9
2016-04-06 17:31:44.457 CUL_WS S300TH taupunkt: 9.9
2016-04-06 17:31:45.231 TelegramBot remotebot PollingLastError: NonBlockingGet timed out on read from  after 65s
2016-04-06 17:31:45.264 TelegramBot remotebot PollingErrCount: 46
2016-04-06 17:31:45.303 HM485 HMW02.I07 leistung: 339.666666666667
2016-04-06 17:31:48.972 HM485 HMW02.I07 literpromin: 17.5092420339057
2016-04-06 17:31:50.870 OWDevice DS18B20_RuecklaufHK temperature: 26.5
2016-04-06 17:31:51.754 OWDevice DS18B20_Ruecklauf_Zirkulation temperature: 37.5
2016-04-06 17:31:52.758 OWDevice DS18B20_Mischer_unten temperature: 25.25
2016-04-06 17:31:53.754 OWDevice DS18B20_Vorlauf_WW temperature: 45
2016-04-06 17:31:58.804 OWDevice DS18B20_Vorlauf_EG_Boden temperature: 24.5
2016-04-06 17:31:58.840 HM485 HMW02.I07 leistung: 364.6
2016-04-06 17:32:02.821 HM485 HMW02.I07 leistung: 611.5
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #9 am: 06 April 2016, 17:39:01 »
Hi,
hmm... Also erst sagst Du, dass es nur bei HMW-Aktoren auftritt und dann, dass es auch bei FS20-Aktoren passiert. Ja was denn nun?
Gruß,
   Thorsten
FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #10 am: 06 April 2016, 17:53:29 »
Hi,
da habe ich mich wohl nicht ganz korrekt artikuliert, davon abgesehen, dass ich bei FHEM gerade nicht mehr weiss, wo mir der Kopf steht... ich teste was, stelle fest dass es geht, und ne Stunde später geht das was vorher nicht ging und umgekehrt... Sorry wenn ich dich da durcheinandergebracht habe...

Was ich oben eigentlich sagen wollte ist, dass der S4(FS20-Taster) events produziert, und diese (vermutlich) alle im Eventlog protokolliert werden. Aber das hat ja wiederum nichts mit den Aktoren zu tun ...

Ist es jetzt klarer?   :-\ ::)

Grüße
Stephan
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #11 am: 06 April 2016, 19:37:48 »
Hi,

Du scheinst mit event-on-change-reading zu arbeiten. Dann ist es schonmal kein Wunder, das bei den long_press nicht wie erwartet alle 300ms ein Event kommt. Komisch ist allerdings, dass auch der erste long_press nicht erscheint. Komisch ist dabei, dass das Device selbst anscheinend alle 300ms ein ACK schickt, d.h. es muss was empfangen haben. Es wird also irgendwas geschaltet, obwohl kein Event im Monitor angezeigt wird???

Ich würde mal sagen, dass wir jetzt aus den ganzen Problemen erst einmal genau eins herauspicken sollten. Könntest Du mal folgendes probieren:
Schalte mal das Log Level nur für das eine Device mit einem Taster (wahrscheinlich HMW_IO_12_Sw7_DR_LEQ0016352) auf 5. Das globale Log Level bitte maximal auf 3. Dann einen Taster ungefähr im Takt von 1 Mal pro Sekunde 10 Mal kurz drücken.
Am besten wäre es, wenn alle zugehörigen Notifys inaktiv wären.
Das Log würde ich gerne sehen.

Gruß,
   Thorsten


FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #12 am: 06 April 2016, 22:24:27 »
attr HMW_IO_12_Sw7_DR_LEQ0016352 verbose 5 - check and set.
attr global loglevel 3 - check and set.
attr N_1.I01_long disable 1 - check and set
attr N_1.I01_short disable 1 - check and set



2016.04.06 22:20:08.432 1: Perfmon: possible freeze starting at 22:20:07, delay is 1.432
2016.04.06 22:21:01.769 1: Perfmon: possible freeze starting at 22:20:59, delay is 2.768
2016.04.06 22:21:03.266 1: Perfmon: possible freeze starting at 22:21:02, delay is 1.266
2016.04.06 22:21:05.004 1: Perfmon: possible freeze starting at 22:21:04, delay is 1.004
2016.04.06 22:21:07.275 1: Perfmon: possible freeze starting at 22:21:06, delay is 1.275
2016.04.06 22:21:13.833 3: backupCfg return value: Can't modify single ref constructor in scalar assignment at (eval 82241) line 1, at EOF
syntax error at (eval 82241) line 1, at EOF

2016.04.06 22:21:37.737 3: PID20 PID.FUBO: Calc.709 <set D_MischerPID  70>
2016.04.06 22:22:02.590 1: Perfmon: possible freeze starting at 22:22:01, delay is 1.59
2016.04.06 22:22:38.706 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 6
2016.04.06 22:22:38.706 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 6
2016.04.06 22:22:38.708 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B00001A actionType = frame
2016.04.06 22:22:38.809 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 22:22:40.347 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 7
2016.04.06 22:22:40.348 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 7
2016.04.06 22:22:40.348 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B00001E actionType = frame
2016.04.06 22:22:40.445 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 22:22:45.735 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 8
2016.04.06 22:22:45.735 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 8
2016.04.06 22:22:45.737 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B000022 actionType = frame
2016.04.06 22:22:45.739 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 22:22:46.123 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 9
2016.04.06 22:22:46.124 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 9
2016.04.06 22:22:46.124 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B000026 actionType = frame
2016.04.06 22:22:46.195 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 22:22:51.841 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 10
2016.04.06 22:22:51.842 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 10
2016.04.06 22:22:51.842 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B00002A actionType = frame
2016.04.06 22:22:51.917 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
2016.04.06 22:22:53.260 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: deviceKey = HMW_IO12_SW7_DR_V3_02 valId = counter value1 = 11
2016.04.06 22:22:53.260 5: HMW_IO_12_Sw7_DR_LEQ0016352: Device:convertFrameDataToValue: value2 = 11
2016.04.06 22:22:53.261 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 Channel = 01 msgData = 4B00002E actionType = frame
2016.04.06 22:22:53.347 5: HMW_IO_12_Sw7_DR_LEQ0016352: HM485_ProcessChannelState: hmwId = 0000B8C5 No channel
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX

Offline Thorsten Pferdekaemper

  • Developer
  • Hero Member
  • ****
  • Beiträge: 6433
  • Finger weg von der fhem.cfg
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #13 am: 06 April 2016, 22:38:08 »
Hi,
für mich sieht das so aus, als ob das Device die Tastendrücke erst gar nicht rausschickt. Man sieht z.B. zwischen 22:22:40 und 22:22:45, dass hier eine Lücke von 5 Sekunden ist, aber der Counter der Tastendrücke springt von 7 nach 8. Hätte das Device dazwischen Deine Tastendrücke (im Sekundentakt) erfasst und rausgeschickt, dann würde man einen Sprung von 7 nach 12 oder so sehen.
Ich kann mir folgendes vorstellen:
  • Wackelkontakt am Taster
  • Der HMW_IO_12_Sw7_DR_LEQ0016352 ist kaputt
  • Der Wired-Bus ist vollgemüllt und das Device kann daher nichts senden.

Beim letzten Punkt kann ich mir vorstellen, dass das Device in dem Fall einfach wartet und daher auch die Tastendrücke nicht mitbekommt.
Hast Du den so genannten Abschlußwiderstand eingebaut? Ansonsten könnten irgendwelche Zufalls-Signale auf dem Bus für Chaos sorgen.
Ansonsten könnte ich mir noch vorstellen, dass der Lan-Adapter Probleme macht. Du hast doch das Original eq3-Teil, oder?
Gruß,
   Thorsten
FUIP

Offline abc2006

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1035
Antw:ungewünschtes Delay bei Ausführung von Schaltbefehlen
« Antwort #14 am: 08 April 2016, 16:12:53 »
Hi Thorsten,
sorry dass die Antwort dieses mal so lange gedauert hat.
Ich dreh mich echt im Kreis: jedes mal, wenn ich irgendwas teste, ist es nicht so wie vorher, sondern verhält sich anders... *verzweifel*

also:

Wackelkontakt am Taster: ich habe folgendes gemacht:
Als erstes habe ich das event-on-change gelöscht.
Einen Draht an I1 und Masse geklemmt -> kein Wackelkontakt. Die Events haben Aussetzer. Meistens so 5-10 Sekunden, aber auch alle anderen Werte sind mal vertreten.
Der 12/7 ist kaputt:
Also habe ich den Draht an I1 von meinem anderen 12/7 geklemmt: Ergebnis: die Events haben deutlich weniger und kürzere Aussetzer, ABER: es gibt immer noch welche. Sporadisch, nicht nachvollziehbar.

Also kanns noch am Bus liegen. Einen Endwiderstand habe ich bestellt, aber irgendwie ist Prime heute nicht so eilig ... naja, kommts halt morgen - vielleicht.
Aber: Wenns am Bus liegt: warum dann nur bei einem Device?

An den LAN-Adapter habe ich auch schon gedacht, selbe Frage wie oben: warum nur bei einem Device?

Kann man die Devices resetten? eigentlich ist ja nichts drauf gespeichert ( bei mir, keine direkten peerings). Und der LAN-Gateway hat auch einen RESET. Weisst du, was passiert, wenn ich den drücke?

Viele Grüße
Stephan
FHEM nightly auf Intel Atom (lubuntu) mit VDSL 50000 ;-)
Nutze zur Zeit OneWire und KNX