Firmware zu CUL, CUNX und Co. mit Timestamp Option ASKSIN tsculfw V0.43

noansi · 20 Dezember 2016, 20:14:33

Hallo Mario,

das ist es wohl.

nanoCUL: unknown message ? (T01 is unknown) Use one of A B C E F G J K M R U V W X Y Z e f i l m t x

Der nanoCUL hat kein FHT in der Firmware, um RAM zu sparen. Und in der 00_TSCUL.pm war das nicht abgefangen.

Hier https://forum.fhem.de/index.php/topic,24436.msg529649.html#msg529649 liegt ene neue zip. Daraus musst Du die 00_TSCUL.pm in Deinem FHEM Verzeichis aktualisieren. Nur die ist geändert.

Gruß, Ansgar.

noansi · 20 Dezember 2016, 20:59:00

Hallo scr3tchy,

die Reihenfolge des Sendens passt jetzt.

Und das Timing sieht auch gut aus.

Code Auswählen

As 0A 61 8002 2A4CC9 4E62E2 00
zu dem 4E62E2 klappt das Senden und Empfangen eigentlich gut.
Ich habe nur den Eindruck, das obiger ACK den einschlafen läßt und es dann nicht mehr weiter geht. Das wäre eine Frage an Martin, ob das an der Stelle im Protkoll stört.
Das gehört dann ins Homematic Forum.

Die Befehlabsetz und Knopfchendrücksequenz kann auch noch fehlerhaft sein. Kann ich mangels Hardware nicht testen.

Ansonsten bräuchte ich mal ein WM55 Log, wo es funktioniert, um die Unterschiede zu sehen. Für das vollständige Protokollverständniss fehlt mir leider die Zeit.

Beim 4E5E9A ist der Empfang vielleicht nicht so gut.
Versuch mal hmFreqOffs (unter set) auf 0 zu stellen. Und von da aus +/- 50 kHz in 10kHz Schritten und beobachte insbesondere auch den RSSI zu und von den Geräten, ob es besser wird. Mein default Wert kann auch Serienstreuungsbeeinflusst sein.

Gruß, Ansgar.

kaihs · 20 Dezember 2016, 21:42:19

Hallo Ansgar,

ich überlege diese culfw auf einem rpiaddon Device einzusetzen.
Es sieht erst mal so aus, als sei die board.h schon angepasst worden. Ist das eher Zufall, oder sind die Einstellungen schon auf den atmega644 abgestimmt der bei dem Device zum Einsatz kommt?

Gruß,

Kai

noansi · 20 Dezember 2016, 22:03:10

Hallo Kai,

zum rapiaddon liegen mir weder Daten noch Erfahrungen vor. In sofern auch nicht, ob der Prozessor passt, aber Deine Augen werden es Dir verraten (haben).
Ich habe nur mal von Zeit zu Zeit die völlig ungestesteten im Source versucht nach zu ziehen. Ansonsten basieren sie auf der culfw Basis auf der ich mal aufgesetzt habe.

In der board.h ist bezüglich Hardware

SPI_CC1101_READ_SPECIAL_PIN
IRRX_SPECIAL_PIN

stets ein Fragezeichen ob die Pins wirklich ungenutzt sind (und in diesem Falle, ob IRRX relevant ist).
Ich benutze diese Pins jeweils als schnelles Speicherbit. Daher darf nichts angeschlossen sein, was damit nicht klar kommt.

Ansonsten bezüglich Konfiguration und rapiaddon.c im Zweifel mal mit SCC, COC, CUNO2, CUL und nanoCUL vergleichen. Zu den ersten 4 kann ich selbst was testen und zu nanoCUL gibt es schon Tester. Die Initialisierung und main loop müssen halt zur Hardware und auch zur gewählten Softwarekonfiguration passen (wo kein "Task", da passiert auch nichts).

Beim Compilieren immer darauf achten, dass es auch zuzüglich Bootloader (normalerweise wohl 4kB) in den Flash Speicher passt und bezüglich RAM, dass noch gut was für den Stack übrig bleibt.
Wo genau die Grenze beim Stack liegt erfährt man wohl erst, wenn man sie gefunden hat.

Viel Erfolg beim Testen!

Gruß, Ansgar.

kaihs · 20 Dezember 2016, 22:08:17

Danke, für die Info.
Der atmega644 hat ja im Vergleich zu den anderen Devices reichlich Flash und RAM, da wird es wohl keine Probleme geben.

Ich werde aber nochmal alle Einstellungen mit dem Datenblatt des Prozessors und dem Schaltplan des Board abgleichen.

noansi · 20 Dezember 2016, 22:21:08

Hallo Kai,

wenn Du Deine Ergebnisse hier postest, dann kann ich sie in den Source einfließen lassen.

Danke!

Ansgar.

kaihs · 20 Dezember 2016, 22:22:46

Ja, wenn ich fertig bin werde ich die Ergebnisse posten.

Die Einstellungen der Pins passen schon mal.
Allerdings ist

Code Auswählen


#define HAS_ASKSIN_FUP

nicht aktiviert. Wird OTA Firmwareupdate von deiner culfw unterstützt?

Ich habe zwei von den Boards. Eines direkt im Haupt-FHEM, ein zweites ist über WLAN per ser2net angebunden.
Beide sind einer vccu zugeordnet.
Verursachen die damit wahrscheinlich einhergehenden Latenzen wohl Probleme oder werden die durch die Timestamps eher verringert?

noansi · 21 Dezember 2016, 01:23:09

Hallo Kai,

Zitatnicht aktiviert. Wird OTA Firmwareupdate von deiner culfw unterstützt?]nicht aktiviert. Wird OTA Firmwareupdate von deiner culfw unterstützt?

Das ist richtig so, weil man es bei mir gar nicht weglassen kann!

Nun, theoretisch läuft es, also es wird auf 100kbit/s hochgeschaltet und das Timing wird angepasst.
Testen kann ich es leider nicht, mangels Hardware die sich updaten ließe. Beschwert hat sich auch noch keiner, dass es nicht ginge oder ginge.
Ich habe die Preamble für den FUP Modus von 10ms auf 1ms runtergesetzt und hoffe das reicht aus. Außerdem sind die Sendeabstände veringert.
Wenn Du testen möchtest, gerne. Da ich aber auch mit credits in der Firmware arbeite (mit Subaufösung eben wegen FUP) macht ein FUP Versuch nur Sinn, wenn Du vorher die Credits auf 1800 "aufgeladen" hast, sprich ggf. erst mal sendearm wartest.

ZitatIch habe zwei von den Boards. Eines direkt im Haupt-FHEM, ein zweites ist über WLAN per ser2net angebunden.
Beide sind einer vccu zugeordnet.
Verursachen die damit wahrscheinlich einhergehenden Latenzen wohl Probleme oder werden die durch die Timestamps eher verringert?

Wenn die Latenzen zo groß werden, dann gibt es nur eventuell Probleme bei Antworten auf messages vom Device. Die müssen schnell genug von FHEM, bzw. CUL_HM kommen. Ich habe nur eine "Unterhaltung" eingeführt, sprich wenn tsculfw eine message empfängt, die das Antwortflag gesetzt hat, dann werden andere Sendeaktionen für eine gewisse Zeit (etwa 400ms) nicht ausgeführt, sondern auf die Sendeantwort von FHEM gewartet. Wenn allerdings schon eine "Unterhaltung" läuft, wird diese nicht unterbrochen, warum auch, wenn einer dazwischen quasselt. Wenn natürlich ein Paket mit Antwortflag für ein device reinkommt, dem nicht über dieses IO geantwortet wird, kann das andere Unterhaltungen aufhalten. Das ist der kleine Haken an der Sache für einen Mehrempfänger/-sender Betrieb.
In die andere Richtung, also Sendetiming und ggf. AES Signing zum device ausführen ist in der Firmware.
So lange die Sendedaten rechtzeitig vorliegen, kümmert sich die Firmware um die (nach bisheriger Erfahrung) korrekte Antwortzeit und versucht 3 Wiederholungen, wenn eine Antwort erwartet wird. Das entschärft wiederum Timingengpässe.

Ich habe das Timing in die Firmware gebracht, weil ich einen COC (HM) auf einem SCC 433MHz sitzen habe. Und da spielt das schon etwas rein, weil die Kommunikation durch den SCC durch muss, sprich über dessen beide serielle Schnittstellen. Und wenn SCC einen dickeren packen an RasPi schickt, dann kann COC so lange nur in den Puffer auf SCC schreiben und es gibt extra Verzögerungen zur ohnehin schon doppelten Übertragungszeit. Die andere Richtung habe ich noch optimieren können, da in dieser Richtung zu SCC nicht viel los ist. Dann ist die Latenz nur 1 Byte + ein bischen zu COC (oder allgemein für jedes zwischengeschaltete SCC).

Nutzung der FHEM Module nicht vergessen! Mit den Standart Modulen geht es nicht.

Gruß, Ansgar.

Maxl · 21 Dezember 2016, 18:58:40

Hallo Ansgar,

mir ist aufgefallen, das ich keine Aktoren mehr mit der neuen V0.5 pairen kann, unter V0.3 gab es noch keine Probleme. Evtl. stimmen auch ein paar Einstellungen unter der board.h nicht, die habe ich so genommen wie im zip-File. Könntest du das prüfen?

so sah es unter V0.3 aus:

Code Auswählen

2016.12.21 18:52:49.187 4: TSCUL_Parse: nanoCUL  238095 A FF51 00047868 00 1A 06 8400 461413 000000 16005D4E45513031313830363481110100 -78
2016.12.21 18:52:49.196 3: Device Bewegungsmelder_EG added to ActionDetector with 024:00 time
2016.12.21 18:52:49.201 4: Device CUL_HM_HM_CC_RT_DN_3549E1 is alive
2016.12.21 18:52:49.202 4: Device Bewegungsmelder_EG is alive
2016.12.21 18:52:49.204 3: CUL_HM pair: Bewegungsmelder_EG motionDetector, model HM-Sen-MDIR-O serialNr NEQ0118064
2016.12.21 18:52:49.224 4: TSCUL_send:  nanoCUL                         As 10 2E A001 F11234 461413 00050000000000
2016.12.21 18:52:49.224 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:62 toms:73
2016.12.21 18:52:49.327 4: TSCUL_Parse: nanoCUL  238243 A FF53 00047988 00 10 2E A001 F11234 461413 00 _dhmSt:120 -138
2016.12.21 18:52:49.445 4: TSCUL_Parse: nanoCUL  238362 A FF51 00048136 00 0A 2E 8002 461413 F11234 00 -74
2016.12.21 18:52:49.461 4: TSCUL_send:  nanoCUL                         As 13 2F A001 F11234 461413 000802010AF10B120C34
2016.12.21 18:52:49.462 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:91 toms:74
2016.12.21 18:52:49.597 4: TSCUL_Parse: nanoCUL  238514 A FF53 00048256 00 13 2F A001 F11234 461413 00 _dhmSt:120 -138
2016.12.21 18:52:49.713 4: TSCUL_Parse: nanoCUL  238630 A FF51 00048404 00 0A 2F 8002 461413 F11234 00 -71.5
2016.12.21 18:52:49.730 4: TSCUL_send:  nanoCUL                         As 0B 30 A001 F11234 461413 0006
2016.12.21 18:52:49.730 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:95 toms:72
2016.12.21 18:52:49.859 4: TSCUL_Parse: nanoCUL  238775 A FF53 00048524 00 0B 30 A001 F11234 461413 00 _dhmSt:120 -138
2016.12.21 18:52:49.982 4: TSCUL_Parse: nanoCUL  238898 A FF51 00048672 00 0A 30 8002 461413 F11234 00 -69.5
2016.12.21 18:52:53.772 4: dummy set Test2 toggle
2016.12.21 18:52:53.786 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.21 18:52:53.792 4: dummy set Test off
2016.12.21 18:52:53.795 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.21 18:52:55.808 4: TSCUL_Parse: nanoCUL  244719 A FF52 00054496 00 15 AABBCCDDAABBCCDDAABBCCDDAABBCCDDAABBCCDDAA _ping -138
2016.12.21 18:53:00.587 4: Connection closed for WEB_192.168.1.28_63455: EOF
2016.12.21 18:53:00.591 4: WEB_192.168.1.28_63456 GET /fhem/FileLog_logWrapper?dev=Logfile&type=text&file=fhem-2016-12.log; BUFLEN:0

Gruß
Mario

noansi · 22 Dezember 2016, 01:56:27

Hallo Mario,

Zitatso sah es unter V0.3 aus:

Und jetzt?

Bei mir läuft das mit meinen devices absolut sauber durch, sofern Autocreate aktiviert ist.

Du nutzt noch die 10_CUL_HM.pm aus der zip und hast Dich nicht etwa zu einem update von FHEM verleiten lassen, ohne die vor update zu schützen?

Gruß,

Ansgar.

Maxl · 22 Dezember 2016, 13:23:12

Hallo Ansgar,

anbei nochmals das Log nach dem Neustart mit der V0.5, habe sicherheitshalber nochmals alle pm-Files nach FHEM kopiert. Zum Schluß hätte ich versucht einen HM-SEN-MDIR-O zu pairen, dieser blinkt gelb mit dieser Version und geht dann in das Timeout, blinkt rot. Bei den anderen hat es noch funktioniert, weiß leider nicht genau was der Unterschied zwischen den Versionen ist. Mir fiel nur auf, das sich das board.h zw. V3, V4 und V5 geändert hat.
Das das Pairen seit V4 bei mir nicht mehr geht fiel nicht auf, da alles passte.

define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log

steht in der cfg.

Code Auswählen

2016.12.22 13:16:20.311 1: Including fhem.cfg
2016.12.22 13:16:20.410 3: telnetPort: port 7072 opened
2016.12.22 13:16:20.821 3: WEB: port 8083 opened
2016.12.22 13:16:20.825 3: WEBphone: port 8084 opened
2016.12.22 13:16:20.850 3: WEBtablet: port 8085 opened
2016.12.22 13:16:21.802 2: eventTypes: loaded 995 events from ./log/eventTypes.txt
2016.12.22 13:16:23.224 2: TSCUL_Parse: nanoCUL new condition disconnected
2016.12.22 13:16:23.225 3: Opening nanoCUL device /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
2016.12.22 13:16:23.357 3: DevIoTS_OpenDev: Setting nanoCUL serial parameters to 38400,8,N,1
2016.12.22 13:16:24.174 1: nanoCUL is VERSION_TS, VTS 0.05 nanoCUL868, nanoCUL_V1.x
2016.12.22 13:16:25.072 3: nanoCUL: Possible commands: ABCEFGJKMRUVWXYZefilmtx
2016.12.22 13:16:25.104 2: TSCUL_Parse: nanoCUL new condition init
2016.12.22 13:16:25.106 3: DevIoTS_OpenDev: nanoCUL device opened
2016.12.22 13:16:25.162 2: TSCUL_Parse: nanoCUL new condition init
2016.12.22 13:16:25.163 2: Switched nanoCUL rfmode to HomeMatic
2016.12.22 13:16:25.449 3: HM485: HM485: Loading available device files
2016.12.22 13:16:25.449 3: HM485: =====================================
2016.12.22 13:16:25.450 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw-sen-sc-12.pm
2016.12.22 13:16:25.456 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2016.12.22 13:16:25.460 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2016.12.22 13:16:25.462 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_fm.pm
2016.12.22 13:16:25.493 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2016.12.22 13:16:25.512 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2016.12.22 13:16:25.552 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2016.12.22 13:16:25.592 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_v3_02.pm
2016.12.22 13:16:25.622 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2016.12.22 13:16:25.669 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2016.12.22 13:16:25.713 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2016.12.22 13:16:25.755 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_v3_02.pm
2016.12.22 13:16:25.786 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2016.12.22 13:16:25.828 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2016.12.22 13:16:25.889 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2016.12.22 13:16:25.948 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_v3_02.pm
2016.12.22 13:16:25.990 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2016.12.22 13:16:26.051 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2016.12.22 13:16:26.095 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2016.12.22 13:16:26.137 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_v3_02.pm
2016.12.22 13:16:26.168 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2016.12.22 13:16:26.176 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_virtual.pm
2016.12.22 13:16:26.288 3: Opening NETIO1 device 192.168.1.98:2701
2016.12.22 13:16:26.304 3: NETIO1 device opened
2016.12.22 13:16:26.379 3: Opening NETIO2 device 192.168.1.99:2701
2016.12.22 13:16:26.383 3: NETIO2 device opened
2016.12.22 13:16:26.637 2: HM_LAN_WIRED: Assigned 00011169 as HMW_IO_12_Sw14_DR_LEQ1322965
2016.12.22 13:16:27.475 2: HM_LAN_WIRED: Assigned 00012465 as HMW_IO_12_Sw14_DR_MEQ0370281
2016.12.22 13:16:28.241 1: Including ./log/fhem.save
2016.12.22 13:16:29.187 3: Device Bewegungsmelder_EG added to ActionDetector with 024:00 time
2016.12.22 13:16:29.200 4: Device Bewegungsmelder_EG is alive
2016.12.22 13:16:29.222 3: Device Bewegungsmelder_UG added to ActionDetector with 024:00 time
2016.12.22 13:16:29.233 4: Device Bewegungsmelder_UG is alive
2016.12.22 13:16:29.256 3: Device CUL_HM_HM_CC_RT_DN_354555 added to ActionDetector with 000:10 time
2016.12.22 13:16:29.265 4: Device CUL_HM_HM_CC_RT_DN_354555 is alive
2016.12.22 13:16:29.337 3: Device CUL_HM_HM_CC_RT_DN_3547B5 added to ActionDetector with 000:10 time
2016.12.22 13:16:29.347 4: Device CUL_HM_HM_CC_RT_DN_3547B5 is alive
2016.12.22 13:16:29.420 3: Device CUL_HM_HM_CC_RT_DN_3547BA added to ActionDetector with 000:10 time
2016.12.22 13:16:29.431 4: Device CUL_HM_HM_CC_RT_DN_3547BA is alive
2016.12.22 13:16:29.503 3: Device CUL_HM_HM_CC_RT_DN_3547BB added to ActionDetector with 000:10 time
2016.12.22 13:16:29.513 4: Device CUL_HM_HM_CC_RT_DN_3547BB is alive
2016.12.22 13:16:29.586 3: Device CUL_HM_HM_CC_RT_DN_3547BF added to ActionDetector with 000:10 time
2016.12.22 13:16:29.597 4: Device CUL_HM_HM_CC_RT_DN_3547BF is alive
2016.12.22 13:16:29.669 3: Device CUL_HM_HM_CC_RT_DN_3549DB added to ActionDetector with 000:10 time
2016.12.22 13:16:29.680 4: Device CUL_HM_HM_CC_RT_DN_3549DB is alive
2016.12.22 13:16:29.752 3: Device CUL_HM_HM_CC_RT_DN_3549DE added to ActionDetector with 000:10 time
2016.12.22 13:16:29.764 4: Device CUL_HM_HM_CC_RT_DN_3549DE is alive
2016.12.22 13:16:29.838 3: Device CUL_HM_HM_CC_RT_DN_3549E1 added to ActionDetector with 000:10 time
2016.12.22 13:16:29.849 4: Device CUL_HM_HM_CC_RT_DN_3549E1 is alive
2016.12.22 13:16:30.039 3: Device CUL_HM_HM_SEC_SD_2F361B added to ActionDetector with 099:00 time
2016.12.22 13:16:30.049 4: Device CUL_HM_HM_SEC_SD_2F361B is alive
2016.12.22 13:16:30.076 3: Device CUL_HM_HM_SEC_SD_2F3665 added to ActionDetector with 099:00 time
2016.12.22 13:16:30.086 4: Device CUL_HM_HM_SEC_SD_2F3665 is alive
2016.12.22 13:16:30.115 3: Device CUL_HM_HM_SEC_SD_2F36E2 added to ActionDetector with 099:00 time
2016.12.22 13:16:30.125 4: Device CUL_HM_HM_SEC_SD_2F36E2 is alive
2016.12.22 13:16:30.158 3: Device CUL_HM_HM_SEC_SD_2F387B added to ActionDetector with 099:00 time
2016.12.22 13:16:30.168 4: Device CUL_HM_HM_SEC_SD_2F387B is alive
2016.12.22 13:16:30.198 3: Device CUL_HM_HM_SEC_SD_2F387C added to ActionDetector with 099:00 time
2016.12.22 13:16:30.209 4: Device CUL_HM_HM_SEC_SD_2F387C is alive
2016.12.22 13:16:30.237 3: Device CUL_HM_HM_SEC_SD_2F389B added to ActionDetector with 099:00 time
2016.12.22 13:16:30.249 4: Device CUL_HM_HM_SEC_SD_2F389B is alive
2016.12.22 13:16:30.630 4: initialUsbCheck exec usb create
2016.12.22 13:16:30.631 1: usb create starting
2016.12.22 13:16:31.216 4: ### ttyAMA0: checking if it is a CUL
2016.12.22 13:16:31.220 3: Probing CUL device /dev/ttyAMA0
2016.12.22 13:16:31.431 4: got wrong answer for a CUL
2016.12.22 13:16:31.432 4: ### ttyAMA0: checking if it is a TCM_ESP3
2016.12.22 13:16:31.434 3: Probing TCM_ESP3 device /dev/ttyAMA0
2016.12.22 13:16:31.643 4: got wrong answer for a TCM_ESP3
2016.12.22 13:16:31.645 4: ### ttyAMA0: checking if it is a FRM
2016.12.22 13:16:31.647 3: Probing FRM device /dev/ttyAMA0
2016.12.22 13:16:36.863 4: got wrong answer for a FRM
2016.12.22 13:16:36.864 4: ### ttyUSB0: checking if it is a TCM_ESP3
2016.12.22 13:16:36.865 4: ttyUSB0 is already used by the fhem device nanoCUL
2016.12.22 13:16:36.866 4: ### ttyUSB1: checking if it is a TCM_ESP3
2016.12.22 13:16:36.868 3: Probing TCM_ESP3 device /dev/ttyUSB1
2016.12.22 13:16:37.086 4: got wrong answer for a TCM_ESP3
2016.12.22 13:16:37.087 4: ### ttyUSB1: checking if it is a TCM_ESP2
2016.12.22 13:16:37.089 3: Probing TCM_ESP2 device /dev/ttyUSB1
2016.12.22 13:16:37.306 4: got wrong answer for a TCM_ESP2
2016.12.22 13:16:37.307 4: ### ttyUSB1: checking if it is a FHZ
2016.12.22 13:16:37.309 3: Probing FHZ device /dev/ttyUSB1
2016.12.22 13:16:37.526 4: got wrong answer for a FHZ
2016.12.22 13:16:37.527 4: ### ttyUSB1: checking if it is a TRX
2016.12.22 13:16:37.529 3: Probing TRX device /dev/ttyUSB1
2016.12.22 13:16:38.255 4: got wrong answer for a TRX
2016.12.22 13:16:38.256 4: ### ttyUSB1: checking if it is a ZWDongle
2016.12.22 13:16:38.259 3: Probing ZWDongle device /dev/ttyUSB1
2016.12.22 13:16:38.479 4: got wrong answer for a ZWDongle
2016.12.22 13:16:38.480 4: ### ttyUSB1: checking if it is a FRM
2016.12.22 13:16:38.482 3: Probing FRM device /dev/ttyUSB1
2016.12.22 13:16:45.158 4: got wrong answer for a FRM
2016.12.22 13:16:45.191 1: usb create end
2016.12.22 13:16:45.221 2: SecurityCheck:  WEB,WEBtablet has no associated allowed device with basicAuth. telnetPort has no associated allowed device with password/globalpassword.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message. 
2016.12.22 13:16:45.223 0: Featurelevel: 5.7
2016.12.22 13:16:45.223 0: Server started with 245 defined entities (fhem.pl:12463/2016-10-29 perl:5.014002 os:linux user:fhem pid:26829)
2016.12.22 13:16:45.378 3: HM_LAN_WIRED: Start HM485d with command line: ./FHEM/lib/HM485/HM485d/HM485d.pl --hmwId 00000001 --serialNumber SGW0123456 --device 192.168.1.97:5000 --localPort 2000 --verbose 1
2016.12.22 13:16:45.462 3: HM_LAN_WIRED: HM485d was started with PID: 26840
2016.12.22 13:16:45.463 3: HM_LAN_WIRED: Connect to HM485d delayed for 4 seconds
2016.12.22 13:16:45.476 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 13:16:45.488 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 13:16:45.512 4: dummy set Test2 toggle
2016.12.22 13:16:45.523 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:16:45.594 4: dummy set Test off
2016.12.22 13:16:45.596 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 13:16:45.647 4: Connection accepted from WEB_192.168.1.20_51302
2016.12.22 13:16:45.651 2: TSCUL_Parse: nanoCUL new condition ok
2016.12.22 13:16:45.661 4: TSCUL_Parse: nanoCUL  414283 A FF52 00021824 00 01 C3 _ping -138
2016.12.22 13:16:45.663 4: TSCUL_Parse: nanoCUL  414286 A FF52 00021844 00 15 AABBCCDDAABBCCDDAABBCCDDAABBCCDDAABBCCDDAA _ping -138
2016.12.22 13:16:46.086 4: WEB_192.168.1.20_51302 GET /fhem?XHR=1&inform=type=status;filter=;since=1482408907.932;fmt=JSON&fw_id=513×tamp=1482408977144; BUFLEN:0
2016.12.22 13:16:46.094 4: Connection accepted from WEB_192.168.1.20_51303
2016.12.22 13:16:46.099 4: Connection closed for WEB_192.168.1.20_51302: EOF
2016.12.22 13:16:46.101 4: Connection accepted from WEB_192.168.1.20_51313
2016.12.22 13:16:46.103 4: Connection closed for WEB_192.168.1.20_51303: EOF
2016.12.22 13:16:46.106 4: WEB_192.168.1.20_51313 GET /fhem/FileLog_logWrapper?dev=Logfile&type=text&file=fhem-2016-12.log; BUFLEN:0
2016.12.22 13:16:46.298 4: WEB_192.168.1.20_51313 GET /fhem/pgm2/style.css?v=1482408980; BUFLEN:0
2016.12.22 13:16:46.427 4: WEB_192.168.1.20_51313 GET /fhem/pgm2/hm485.js?1482408986.21393; BUFLEN:0
2016.12.22 13:16:46.653 1: HM485d: Server started ...
2016.12.22 13:16:46.937 4: WEB_192.168.1.20_51313 GET /fhem/FileLog_logWrapper?XHR=1&inform=type=status;filter=;since=1482409005;fmt=JSON&fw_id=491×tamp=1482409005173; BUFLEN:0
2016.12.22 13:16:47.022 4: dummy set Test2 toggle
2016.12.22 13:16:47.073 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:16:47.079 4: dummy set Test on
2016.12.22 13:16:47.081 4: Dummy_Ein exec { fhem "set Relais9 on";; fhem "set HMW_IO_12_Sw14_DR_LEQ1322965_01 toggle" }
2016.12.22 13:16:47.728 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (1) I[0](0,Y,F,B)(98) 00000001 -> 00011169 [6] 73(s) 000000
2016.12.22 13:16:48.793 3: HMW_IO_12_Sw14_DR_LEQ1322965: RESPONSE TIMEOUT for 00011169
2016.12.22 13:16:49.566 3: Opening HM_LAN_WIRED device localhost:2000
2016.12.22 13:16:49.573 3: HM_LAN_WIRED: connected to device localhost:2000
2016.12.22 13:16:49.574 3: HM_LAN_WIRED device opened
2016.12.22 13:16:49.576 3: HM_LAN_WIRED: Lan Device Information
2016.12.22 13:16:49.576 3: HM_LAN_WIRED: Protocol-Version: 01
2016.12.22 13:16:49.577 3: HM_LAN_WIRED: Interface-Type: HMW-SOFT-GW
2016.12.22 13:16:49.577 3: HM_LAN_WIRED: Firmware-Version: 0.2.2
2016.12.22 13:16:49.577 3: HM_LAN_WIRED: Serial-Number: SGW0123456
2016.12.22 13:16:49.578 3: HM_LAN_WIRED: Initialize the interface
2016.12.22 13:16:50.480 3: HM_LAN_WIRED: Initialisierung von Modul 00011169
2016.12.22 13:16:50.482 3: HM_LAN_WIRED: Initialisierung von Modul 00012465
2016.12.22 13:16:50.510 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (2) I[1](0,F,B)(1A) 00000001 -> 00011169 [3] 68(h) 
2016.12.22 13:16:50.572 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (3) I[2](0,F,B)(1C) 00000001 -> 00011169 [3] 6E(n) 
2016.12.22 13:16:50.637 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (4) I[3](0,F,B)(1E) 00000001 -> 00011169 [3] 76(v) 
2016.12.22 13:16:50.680 3: HMW_IO_12_Sw14_DR_LEQ1322965: Request config for device 00011169
2016.12.22 13:16:50.696 3: HMW_IO_12_Sw14_DR_LEQ1322965: Lese Eeprom 00011169
2016.12.22 13:16:50.713 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (5) I[0](0,Y,F,B)(98) 00000001 -> 00012465 [3] 68(h) 
2016.12.22 13:16:50.776 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (6) I[1](0,F,B)(1A) 00000001 -> 00012465 [3] 6E(n) 
2016.12.22 13:16:50.841 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (7) I[2](0,F,B)(1C) 00000001 -> 00012465 [3] 76(v) 
2016.12.22 13:16:50.884 3: HMW_IO_12_Sw14_DR_MEQ0370281: Request config for device 00012465
2016.12.22 13:16:50.898 3: HMW_IO_12_Sw14_DR_MEQ0370281: Lese Eeprom 00012465
2016.12.22 13:16:50.913 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (8) I[0](0,F,B)(18) 00000001 -> 00011169 [6] 52(R) 000010
2016.12.22 13:16:50.969 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (9) I[1](0,F,B)(1A) 00000001 -> 00011169 [6] 52(R) 001010
2016.12.22 13:16:51.016 4: HMW_IO_12_Sw14_DR_LEQ1322965: Channels initialisieren 00011169
2016.12.22 13:16:51.736 4: HMW_IO_12_Sw14_DR_LEQ1322965: HM485_UpdateConfigReadings called
2016.12.22 13:16:51.902 4: HMW_IO_12_Sw14_DR_LEQ1322965: State der Channels ermitteln 00011169
2016.12.22 13:16:51.923 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (10) I[3](0,F,B)(1E) 00000001 -> 00012465 [6] 52(R) 000010
2016.12.22 13:16:52.148 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (11) I[0](0,F,B)(18) 00000001 -> 00012465 [6] 52(R) 001010
2016.12.22 13:16:52.193 4: HMW_IO_12_Sw14_DR_MEQ0370281: Channels initialisieren 00012465
2016.12.22 13:16:52.918 4: HMW_IO_12_Sw14_DR_MEQ0370281: HM485_UpdateConfigReadings called
2016.12.22 13:16:53.086 4: HMW_IO_12_Sw14_DR_MEQ0370281: State der Channels ermitteln 00012465
2016.12.22 13:16:53.105 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (12) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 00
2016.12.22 13:16:53.328 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: HM485_ChannelDoUpdate
2016.12.22 13:16:53.329 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: state -> on
2016.12.22 13:16:53.341 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (13) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 01
2016.12.22 13:16:53.390 4: HMW_IO_12_Sw14_DR_LEQ1322965_02: HM485_ChannelDoUpdate
2016.12.22 13:16:53.391 4: HMW_IO_12_Sw14_DR_LEQ1322965_02: state -> off
2016.12.22 13:16:53.403 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (14) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 02
2016.12.22 13:16:53.452 4: HMW_IO_12_Sw14_DR_LEQ1322965_03: HM485_ChannelDoUpdate
2016.12.22 13:16:53.454 4: HMW_IO_12_Sw14_DR_LEQ1322965_03: state -> off
2016.12.22 13:16:53.466 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (15) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 03
2016.12.22 13:16:53.515 4: HMW_IO_12_Sw14_DR_LEQ1322965_04: HM485_ChannelDoUpdate
2016.12.22 13:16:53.516 4: HMW_IO_12_Sw14_DR_LEQ1322965_04: state -> off
2016.12.22 13:16:53.530 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (16) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 04
2016.12.22 13:16:53.575 4: HMW_IO_12_Sw14_DR_LEQ1322965_05: HM485_ChannelDoUpdate
2016.12.22 13:16:53.576 4: HMW_IO_12_Sw14_DR_LEQ1322965_05: state -> off
2016.12.22 13:16:53.588 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (17) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 05
2016.12.22 13:16:53.638 4: HMW_IO_12_Sw14_DR_LEQ1322965_06: HM485_ChannelDoUpdate
2016.12.22 13:16:53.640 4: HMW_IO_12_Sw14_DR_LEQ1322965_06: state -> off
2016.12.22 13:16:53.652 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (18) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 06
2016.12.22 13:16:53.679 4: TSCUL_Parse: nanoCUL  422312 A FF52 00030004 00 01 C3 _ping -138
2016.12.22 13:16:53.714 4: HMW_IO_12_Sw14_DR_LEQ1322965_07: HM485_ChannelDoUpdate
2016.12.22 13:16:53.715 4: HMW_IO_12_Sw14_DR_LEQ1322965_07: state -> off
2016.12.22 13:16:53.726 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (19) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 07
2016.12.22 13:16:53.789 4: HMW_IO_12_Sw14_DR_LEQ1322965_08: HM485_ChannelDoUpdate
2016.12.22 13:16:53.790 4: HMW_IO_12_Sw14_DR_LEQ1322965_08: state -> off
2016.12.22 13:16:53.801 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (20) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 08
2016.12.22 13:16:53.867 4: HMW_IO_12_Sw14_DR_LEQ1322965_09: HM485_ChannelDoUpdate
2016.12.22 13:16:53.869 4: HMW_IO_12_Sw14_DR_LEQ1322965_09: state -> off
2016.12.22 13:16:53.881 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (21) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 09
2016.12.22 13:16:53.946 4: HMW_IO_12_Sw14_DR_LEQ1322965_10: HM485_ChannelDoUpdate
2016.12.22 13:16:53.947 4: HMW_IO_12_Sw14_DR_LEQ1322965_10: state -> off
2016.12.22 13:16:53.963 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (22) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 0A
2016.12.22 13:16:54.027 4: HMW_IO_12_Sw14_DR_LEQ1322965_11: HM485_ChannelDoUpdate
2016.12.22 13:16:54.028 4: HMW_IO_12_Sw14_DR_LEQ1322965_11: state -> off
2016.12.22 13:16:54.040 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (23) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 0B
2016.12.22 13:16:54.103 4: HMW_IO_12_Sw14_DR_LEQ1322965_12: HM485_ChannelDoUpdate
2016.12.22 13:16:54.104 4: HMW_IO_12_Sw14_DR_LEQ1322965_12: state -> off
2016.12.22 13:16:54.115 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (24) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 0C
2016.12.22 13:16:54.182 4: HMW_IO_12_Sw14_DR_LEQ1322965_13: HM485_ChannelDoUpdate
2016.12.22 13:16:54.183 4: HMW_IO_12_Sw14_DR_LEQ1322965_13: state -> off
2016.12.22 13:16:54.195 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (25) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 0D
2016.12.22 13:16:54.258 4: HMW_IO_12_Sw14_DR_LEQ1322965_14: HM485_ChannelDoUpdate
2016.12.22 13:16:54.260 4: HMW_IO_12_Sw14_DR_LEQ1322965_14: state -> off
2016.12.22 13:16:54.271 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (26) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 0E
2016.12.22 13:16:54.338 4: HMW_IO_12_Sw14_DR_LEQ1322965_15: HM485_ChannelDoUpdate
2016.12.22 13:16:54.339 4: HMW_IO_12_Sw14_DR_LEQ1322965_15: frequency -> 0.00
2016.12.22 13:16:54.353 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (27) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 0F
2016.12.22 13:16:54.416 4: HMW_IO_12_Sw14_DR_LEQ1322965_16: HM485_ChannelDoUpdate
2016.12.22 13:16:54.417 4: HMW_IO_12_Sw14_DR_LEQ1322965_16: state -> on
2016.12.22 13:16:54.432 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (28) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 10
2016.12.22 13:16:54.491 4: HMW_IO_12_Sw14_DR_LEQ1322965_17: HM485_ChannelDoUpdate
2016.12.22 13:16:54.492 4: HMW_IO_12_Sw14_DR_LEQ1322965_17: state -> on
2016.12.22 13:16:54.504 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (29) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 11
2016.12.22 13:16:54.570 4: HMW_IO_12_Sw14_DR_LEQ1322965_18: HM485_ChannelDoUpdate
2016.12.22 13:16:54.571 4: HMW_IO_12_Sw14_DR_LEQ1322965_18: state -> on
2016.12.22 13:16:54.583 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (30) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 12
2016.12.22 13:16:54.646 4: HMW_IO_12_Sw14_DR_LEQ1322965_19: HM485_ChannelDoUpdate
2016.12.22 13:16:54.647 4: HMW_IO_12_Sw14_DR_LEQ1322965_19: state -> on
2016.12.22 13:16:54.658 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (31) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 13
2016.12.22 13:16:54.725 4: HMW_IO_12_Sw14_DR_LEQ1322965_20: HM485_ChannelDoUpdate
2016.12.22 13:16:54.726 4: HMW_IO_12_Sw14_DR_LEQ1322965_20: state -> on
2016.12.22 13:16:54.742 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (32) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 14
2016.12.22 13:16:54.805 4: HMW_IO_12_Sw14_DR_LEQ1322965_21: HM485_ChannelDoUpdate
2016.12.22 13:16:54.806 4: HMW_IO_12_Sw14_DR_LEQ1322965_21: state -> off
2016.12.22 13:16:54.822 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (33) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 15
2016.12.22 13:16:54.884 4: HMW_IO_12_Sw14_DR_LEQ1322965_22: HM485_ChannelDoUpdate
2016.12.22 13:16:54.885 4: HMW_IO_12_Sw14_DR_LEQ1322965_22: state -> off
2016.12.22 13:16:54.901 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (34) I[0](0,F,B)(18) 00000001 -> 00011169 [4] 53(S) 16
2016.12.22 13:16:54.964 4: HMW_IO_12_Sw14_DR_LEQ1322965_23: HM485_ChannelDoUpdate
2016.12.22 13:16:54.965 4: HMW_IO_12_Sw14_DR_LEQ1322965_23: state -> off
2016.12.22 13:16:54.981 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (35) I[1](0,F,B)(1A) 00000001 -> 00011169 [4] 53(S) 17
2016.12.22 13:16:55.046 4: HMW_IO_12_Sw14_DR_LEQ1322965_24: HM485_ChannelDoUpdate
2016.12.22 13:16:55.047 4: HMW_IO_12_Sw14_DR_LEQ1322965_24: state -> off
2016.12.22 13:16:55.063 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (36) I[2](0,F,B)(1C) 00000001 -> 00011169 [4] 53(S) 18
2016.12.22 13:16:55.126 4: HMW_IO_12_Sw14_DR_LEQ1322965_25: HM485_ChannelDoUpdate
2016.12.22 13:16:55.127 4: HMW_IO_12_Sw14_DR_LEQ1322965_25: state -> off
2016.12.22 13:16:55.143 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (37) I[3](0,F,B)(1E) 00000001 -> 00011169 [4] 53(S) 19
2016.12.22 13:16:55.207 4: HMW_IO_12_Sw14_DR_LEQ1322965_26: HM485_ChannelDoUpdate
2016.12.22 13:16:55.208 4: HMW_IO_12_Sw14_DR_LEQ1322965_26: state -> off
2016.12.22 13:16:55.223 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (38) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 00
2016.12.22 13:16:55.269 4: HMW_IO_12_Sw14_DR_MEQ0370281_01: HM485_ChannelDoUpdate
2016.12.22 13:16:55.270 4: HMW_IO_12_Sw14_DR_MEQ0370281_01: state -> off
2016.12.22 13:16:55.283 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (39) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 01
2016.12.22 13:16:55.331 4: HMW_IO_12_Sw14_DR_MEQ0370281_02: HM485_ChannelDoUpdate
2016.12.22 13:16:55.333 4: HMW_IO_12_Sw14_DR_MEQ0370281_02: state -> off
2016.12.22 13:16:55.347 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (40) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 02
2016.12.22 13:16:55.396 4: HMW_IO_12_Sw14_DR_MEQ0370281_03: HM485_ChannelDoUpdate
2016.12.22 13:16:55.397 4: HMW_IO_12_Sw14_DR_MEQ0370281_03: state -> off
2016.12.22 13:16:55.413 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (41) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 03
2016.12.22 13:16:55.460 4: HMW_IO_12_Sw14_DR_MEQ0370281_04: HM485_ChannelDoUpdate
2016.12.22 13:16:55.461 4: HMW_IO_12_Sw14_DR_MEQ0370281_04: state -> off
2016.12.22 13:16:55.473 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (42) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 04
2016.12.22 13:16:55.521 4: HMW_IO_12_Sw14_DR_MEQ0370281_05: HM485_ChannelDoUpdate
2016.12.22 13:16:55.522 4: HMW_IO_12_Sw14_DR_MEQ0370281_05: state -> off
2016.12.22 13:16:55.533 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (43) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 05
2016.12.22 13:16:55.585 4: HMW_IO_12_Sw14_DR_MEQ0370281_06: HM485_ChannelDoUpdate
2016.12.22 13:16:55.586 4: HMW_IO_12_Sw14_DR_MEQ0370281_06: state -> off
2016.12.22 13:16:55.598 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (44) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 06
2016.12.22 13:16:55.661 4: HMW_IO_12_Sw14_DR_MEQ0370281_07: HM485_ChannelDoUpdate
2016.12.22 13:16:55.662 4: HMW_IO_12_Sw14_DR_MEQ0370281_07: state -> off
2016.12.22 13:16:55.673 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (45) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 07
2016.12.22 13:16:55.741 4: HMW_IO_12_Sw14_DR_MEQ0370281_08: HM485_ChannelDoUpdate
2016.12.22 13:16:55.742 4: HMW_IO_12_Sw14_DR_MEQ0370281_08: state -> off
2016.12.22 13:16:55.756 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (46) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 08
2016.12.22 13:16:55.820 4: HMW_IO_12_Sw14_DR_MEQ0370281_09: HM485_ChannelDoUpdate
2016.12.22 13:16:55.821 4: HMW_IO_12_Sw14_DR_MEQ0370281_09: state -> off
2016.12.22 13:16:55.836 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (47) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 09
2016.12.22 13:16:55.900 4: HMW_IO_12_Sw14_DR_MEQ0370281_10: HM485_ChannelDoUpdate
2016.12.22 13:16:55.901 4: HMW_IO_12_Sw14_DR_MEQ0370281_10: state -> off
2016.12.22 13:16:55.916 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (48) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 0A
2016.12.22 13:16:55.981 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: HM485_ChannelDoUpdate
2016.12.22 13:16:55.982 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: state -> off
2016.12.22 13:16:55.996 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (49) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 0B
2016.12.22 13:16:56.062 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: HM485_ChannelDoUpdate
2016.12.22 13:16:56.064 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: state -> off
2016.12.22 13:16:56.080 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (50) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 0C
2016.12.22 13:16:56.142 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: HM485_ChannelDoUpdate
2016.12.22 13:16:56.143 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: state -> off
2016.12.22 13:16:56.157 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (51) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 0D
2016.12.22 13:16:56.222 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: HM485_ChannelDoUpdate
2016.12.22 13:16:56.224 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: state -> off
2016.12.22 13:16:56.240 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (52) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 0E
2016.12.22 13:16:56.302 4: HMW_IO_12_Sw14_DR_MEQ0370281_15: HM485_ChannelDoUpdate
2016.12.22 13:16:56.303 4: HMW_IO_12_Sw14_DR_MEQ0370281_15: state -> on
2016.12.22 13:16:56.316 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (53) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 0F
2016.12.22 13:16:56.379 4: HMW_IO_12_Sw14_DR_MEQ0370281_16: HM485_ChannelDoUpdate
2016.12.22 13:16:56.380 4: HMW_IO_12_Sw14_DR_MEQ0370281_16: state -> on
2016.12.22 13:16:56.384 4: Rollo_stopp_Zimmer2 exec {
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_11 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_12 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_13 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_14 off";; }
2016.12.22 13:16:57.011 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (54) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 10
2016.12.22 13:16:57.068 4: dummy set Test2 toggle
2016.12.22 13:16:57.077 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:16:57.082 4: dummy set Test off
2016.12.22 13:16:57.084 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 13:16:57.152 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (55) I[2](0,F,B)(1C) 00000001 -> 00012465 [6] 73(s) 0A0000
2016.12.22 13:16:57.164 4: HMW_IO_12_Sw14_DR_MEQ0370281_17: HM485_ChannelDoUpdate
2016.12.22 13:16:57.165 4: HMW_IO_12_Sw14_DR_MEQ0370281_17: state -> on
2016.12.22 13:16:57.216 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (56) I[3](0,F,B)(1E) 00000001 -> 00012465 [6] 73(s) 0B0000
2016.12.22 13:16:57.228 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: HM485_ChannelDoUpdate
2016.12.22 13:16:57.229 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: state -> off
2016.12.22 13:16:57.273 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (57) I[0](0,F,B)(18) 00000001 -> 00012465 [6] 73(s) 0C0000
2016.12.22 13:16:57.284 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: HM485_ChannelDoUpdate
2016.12.22 13:16:57.285 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: state -> off
2016.12.22 13:16:57.332 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (58) I[1](0,F,B)(1A) 00000001 -> 00012465 [6] 73(s) 0D0000
2016.12.22 13:16:57.343 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: HM485_ChannelDoUpdate
2016.12.22 13:16:57.345 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: state -> off
2016.12.22 13:16:57.399 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (59) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 11
2016.12.22 13:16:57.410 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: HM485_ChannelDoUpdate
2016.12.22 13:16:57.412 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: state -> off
2016.12.22 13:16:57.466 4: HMW_IO_12_Sw14_DR_MEQ0370281_18: HM485_ChannelDoUpdate
2016.12.22 13:16:57.467 4: HMW_IO_12_Sw14_DR_MEQ0370281_18: state -> on
2016.12.22 13:16:57.472 4: Rollo_stopp_Zimmer2 exec {
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_11 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_12 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_13 off";;
  fhem "set HMW_IO_12_Sw14_DR_MEQ0370281_14 off";; }
2016.12.22 13:16:57.576 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (60) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 12
2016.12.22 13:16:57.665 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (61) I[0](0,F,B)(18) 00000001 -> 00012465 [6] 73(s) 0A0000
2016.12.22 13:16:57.676 4: HMW_IO_12_Sw14_DR_MEQ0370281_19: HM485_ChannelDoUpdate
2016.12.22 13:16:57.678 4: HMW_IO_12_Sw14_DR_MEQ0370281_19: state -> on
2016.12.22 13:16:57.720 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (62) I[1](0,F,B)(1A) 00000001 -> 00012465 [6] 73(s) 0B0000
2016.12.22 13:16:57.731 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: HM485_ChannelDoUpdate
2016.12.22 13:16:57.732 4: HMW_IO_12_Sw14_DR_MEQ0370281_11: state -> off
2016.12.22 13:16:57.784 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (63) I[2](0,F,B)(1C) 00000001 -> 00012465 [6] 73(s) 0C0000
2016.12.22 13:16:57.795 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: HM485_ChannelDoUpdate
2016.12.22 13:16:57.796 4: HMW_IO_12_Sw14_DR_MEQ0370281_12: state -> off
2016.12.22 13:16:57.852 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (64) I[3](0,F,B)(1E) 00000001 -> 00012465 [6] 73(s) 0D0000
2016.12.22 13:16:57.863 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: HM485_ChannelDoUpdate
2016.12.22 13:16:57.865 4: HMW_IO_12_Sw14_DR_MEQ0370281_13: state -> off
2016.12.22 13:16:57.906 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (65) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 13
2016.12.22 13:16:57.917 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: HM485_ChannelDoUpdate
2016.12.22 13:16:57.918 4: HMW_IO_12_Sw14_DR_MEQ0370281_14: state -> off
2016.12.22 13:16:57.967 4: HMW_IO_12_Sw14_DR_MEQ0370281_20: HM485_ChannelDoUpdate
2016.12.22 13:16:57.969 4: HMW_IO_12_Sw14_DR_MEQ0370281_20: state -> on
2016.12.22 13:16:57.983 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (66) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 14
2016.12.22 13:16:58.043 4: HMW_IO_12_Sw14_DR_MEQ0370281_21: HM485_ChannelDoUpdate
2016.12.22 13:16:58.045 4: HMW_IO_12_Sw14_DR_MEQ0370281_21: state -> off
2016.12.22 13:16:58.059 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (67) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 15
2016.12.22 13:16:58.119 4: HMW_IO_12_Sw14_DR_MEQ0370281_22: HM485_ChannelDoUpdate
2016.12.22 13:16:58.120 4: HMW_IO_12_Sw14_DR_MEQ0370281_22: state -> off
2016.12.22 13:16:58.131 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (68) I[3](0,F,B)(1E) 00000001 -> 00012465 [4] 53(S) 16
2016.12.22 13:16:58.199 4: HMW_IO_12_Sw14_DR_MEQ0370281_23: HM485_ChannelDoUpdate
2016.12.22 13:16:58.200 4: HMW_IO_12_Sw14_DR_MEQ0370281_23: state -> off
2016.12.22 13:16:58.216 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (69) I[0](0,F,B)(18) 00000001 -> 00012465 [4] 53(S) 17
2016.12.22 13:16:58.279 4: HMW_IO_12_Sw14_DR_MEQ0370281_24: HM485_ChannelDoUpdate
2016.12.22 13:16:58.280 4: HMW_IO_12_Sw14_DR_MEQ0370281_24: state -> off
2016.12.22 13:16:58.293 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (70) I[1](0,F,B)(1A) 00000001 -> 00012465 [4] 53(S) 18
2016.12.22 13:16:58.360 4: HMW_IO_12_Sw14_DR_MEQ0370281_25: HM485_ChannelDoUpdate
2016.12.22 13:16:58.361 4: HMW_IO_12_Sw14_DR_MEQ0370281_25: state -> off
2016.12.22 13:16:58.377 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (71) I[2](0,F,B)(1C) 00000001 -> 00012465 [4] 53(S) 19
2016.12.22 13:16:58.440 4: HMW_IO_12_Sw14_DR_MEQ0370281_26: HM485_ChannelDoUpdate
2016.12.22 13:16:58.441 4: HMW_IO_12_Sw14_DR_MEQ0370281_26: state -> off
2016.12.22 13:16:59.216 4: Connection closed for WEB_192.168.1.20_51313: EOF
2016.12.22 13:16:59.245 4: Connection accepted from WEB_192.168.1.20_51340
2016.12.22 13:16:59.249 4: WEB_192.168.1.20_51340 GET /fhem?room=CUL%5fHM; BUFLEN:0
2016.12.22 13:16:59.414 4: name: /fhem?room=CUL%5fHM / RL:3025 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:16:59.699 4: WEB_192.168.1.20_51340 GET /fhem/images/default/off.png; BUFLEN:0
2016.12.22 13:16:59.701 4: WEB_192.168.1.20_51340 => 304 Not Modified
2016.12.22 13:16:59.710 4: WEB_192.168.1.20_51340 GET /fhem/images/default/on.png; BUFLEN:0
2016.12.22 13:16:59.712 4: WEB_192.168.1.20_51340 => 304 Not Modified
2016.12.22 13:17:00.495 4: WEB_192.168.1.20_51340 GET /fhem?XHR=1&inform=type=status;filter=room=CUL%5fHM;since=1482409018;fmt=JSON&fw_id=492×tamp=1482409018737; BUFLEN:0
2016.12.22 13:17:01.944 4: Connection closed for WEB_192.168.1.20_51340: EOF
2016.12.22 13:17:01.976 4: Connection accepted from WEB_192.168.1.20_51343
2016.12.22 13:17:01.979 4: WEB_192.168.1.20_51343 GET /fhem?detail=nanoCUL; BUFLEN:0
2016.12.22 13:17:02.035 4: name: /fhem?detail=nanoCUL / RL:4170 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:02.766 4: WEB_192.168.1.20_51343 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 13:17:02.777 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:02.780 4: Connection accepted from WEB_192.168.1.20_51345
2016.12.22 13:17:02.783 4: WEB_192.168.1.20_51345 GET /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 13:17:02.793 4: name: /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1 / RL:27 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:02.864 4: WEB_192.168.1.20_51343 GET /fhem?XHR=1&inform=type=status;filter=nanoCUL;since=1482409020;fmt=JSON&fw_id=493×tamp=1482409021092; BUFLEN:0
2016.12.22 13:17:06.758 4: WEB_192.168.1.20_51345 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22hmPairForSec%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 13:17:06.768 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22hmPairForSec%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:07.022 4: dummy set Test2 toggle
2016.12.22 13:17:07.075 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:17:07.081 4: dummy set Test on
2016.12.22 13:17:07.083 4: Dummy_Ein exec { fhem "set Relais9 on";; fhem "set HMW_IO_12_Sw14_DR_LEQ1322965_01 toggle" }
2016.12.22 13:17:07.163 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (72) I[0](0,F,B)(18) 00000001 -> 00011169 [6] 73(s) 000000
2016.12.22 13:17:07.211 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: HM485_ChannelDoUpdate
2016.12.22 13:17:07.212 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: state -> off
2016.12.22 13:17:10.455 4: Connection closed for WEB_192.168.1.20_51343: EOF
2016.12.22 13:17:10.465 4: WEB_192.168.1.20_51345 POST /fhem&detail=nanoCUL&dev.setnanoCUL=nanoCUL&cmd.setnanoCUL=set&arg.setnanoCUL=hmPairForSec&val.setnanoCUL=30; BUFLEN:0
2016.12.22 13:17:10.495 4: WEB_192.168.1.20_51345 GET /fhem?detail=nanoCUL&fw_id=; BUFLEN:0
2016.12.22 13:17:10.550 4: name: /fhem?detail=nanoCUL&fw_id= / RL:4186 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:11.223 4: WEB_192.168.1.20_51345 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 13:17:11.233 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:11.249 4: WEB_192.168.1.20_51345 GET /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 13:17:11.259 4: name: /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1 / RL:27 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 13:17:11.307 4: WEB_192.168.1.20_51345 GET /fhem?XHR=1&inform=type=status;filter=nanoCUL;since=1482409029;fmt=JSON&fw_id=494×tamp=1482409029552; BUFLEN:0
2016.12.22 13:17:16.731 4: TSCUL_Parse: nanoCUL  445354 A FF52 00053064 00 15 AABBCCDDAABBCCDDAABBCCDDAABBCCDDAABBCCDDAA _ping -138
2016.12.22 13:17:17.022 4: dummy set Test2 toggle
2016.12.22 13:17:17.031 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:17:17.036 4: dummy set Test off
2016.12.22 13:17:17.038 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 13:17:27.029 4: dummy set Test2 toggle
2016.12.22 13:17:27.038 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:17:27.044 4: dummy set Test on
2016.12.22 13:17:27.047 4: Dummy_Ein exec { fhem "set Relais9 on";; fhem "set HMW_IO_12_Sw14_DR_LEQ1322965_01 toggle" }
2016.12.22 13:17:27.126 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (73) I[1](0,F,B)(1A) 00000001 -> 00011169 [6] 73(s) 0003FF
2016.12.22 13:17:27.176 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: HM485_ChannelDoUpdate
2016.12.22 13:17:27.177 4: HMW_IO_12_Sw14_DR_LEQ1322965_01: state -> on
2016.12.22 13:17:35.911 4: TSCUL_Parse: nanoCUL  464537 A FF51 00072260 00 0F AE 8610 3547BB 000000 0AA0D5080D40 -50
2016.12.22 13:17:37.023 4: dummy set Test2 toggle
2016.12.22 13:17:37.032 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 13:17:37.038 4: dummy set Test off
2016.12.22 13:17:37.040 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 13:17:38.015 4: Connection closed for WEB_192.168.1.20_51345: EOF
2016.12.22 13:17:38.840 4: Connection accepted from WEB_192.168.1.20_51382
2016.12.22 13:17:38.844 4: WEB_192.168.1.20_51382 GET /fhem/FileLog_logWrapper?dev=Logfile&type=text&file=fhem-2016-12.log; BUFLEN:0

noansi · 22 Dezember 2016, 13:41:57

Hallo Mario,

ich sehe in Deinem Log, keinen einzigen Versuch eines Anlernvorgangs mit TSCUL.
Es wird kein entsprechendes Paket empfangen.

Falls es ein Empfangsproblem ist, stell mal hmFreqOffs mit set auf 0.
Kontrolle ist über get ccconf möglich.

Wenn es dann geht, dann weicht Dein cc1101 Empfänger eher in Richtung 0+ ab, denke ich.

Gruß, Ansgar.

Maxl · 22 Dezember 2016, 14:29:15

Hi,

anbei das config des nanoCUL

Code Auswählen

nanoCUL ccconf => freq:868.300MHz bWidth:101kHz rAmpl:33dB sens:8dB drate:9.993kBit/s agcprio:1 agcwait:16 agchyst:2 dcBlockingoff:0 IF:152.34kHz agcMaxLNA:0.0dB agcMaxDVGA:1 AGC_FREEZE:0 freq_offs:0.000kHz CCAmode:3 csRelThr:dis csAbsThr:0dB

und das Logfile

Code Auswählen

2016.12.22 14:26:53.162 1: Including fhem.cfg
2016.12.22 14:26:53.259 3: telnetPort: port 7072 opened
2016.12.22 14:26:53.675 3: WEB: port 8083 opened
2016.12.22 14:26:53.679 3: WEBphone: port 8084 opened
2016.12.22 14:26:53.706 3: WEBtablet: port 8085 opened
2016.12.22 14:26:54.637 2: eventTypes: loaded 1000 events from ./log/eventTypes.txt
2016.12.22 14:26:56.039 2: TSCUL_Parse: nanoCUL new condition disconnected
2016.12.22 14:26:56.040 3: Opening nanoCUL device /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
2016.12.22 14:26:56.170 3: DevIoTS_OpenDev: Setting nanoCUL serial parameters to 38400,8,N,1
2016.12.22 14:26:56.986 1: nanoCUL is VERSION_TS, VTS 0.05 nanoCUL868, nanoCUL_V1.x
2016.12.22 14:26:57.014 3: nanoCUL: Possible commands: ABCEFGJKMRUVWXYZefilmtx
2016.12.22 14:26:57.046 2: TSCUL_Parse: nanoCUL new condition init
2016.12.22 14:26:57.047 3: DevIoTS_OpenDev: nanoCUL device opened
2016.12.22 14:26:57.104 2: TSCUL_Parse: nanoCUL new condition init
2016.12.22 14:26:57.106 2: Switched nanoCUL rfmode to HomeMatic
2016.12.22 14:26:57.414 3: HM485: HM485: Loading available device files
2016.12.22 14:26:57.415 3: HM485: =====================================
2016.12.22 14:26:57.416 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw-sen-sc-12.pm
2016.12.22 14:26:57.422 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2016.12.22 14:26:57.427 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2016.12.22 14:26:57.429 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_fm.pm
2016.12.22 14:26:57.462 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2016.12.22 14:26:57.483 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2016.12.22 14:26:57.528 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2016.12.22 14:26:57.570 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_v3_02.pm
2016.12.22 14:26:57.602 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2016.12.22 14:26:57.648 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2016.12.22 14:26:57.695 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2016.12.22 14:26:57.739 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_v3_02.pm
2016.12.22 14:26:57.774 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2016.12.22 14:26:57.820 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2016.12.22 14:26:57.885 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2016.12.22 14:26:57.950 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_v3_02.pm
2016.12.22 14:26:57.995 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2016.12.22 14:26:58.061 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2016.12.22 14:26:58.108 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2016.12.22 14:26:58.150 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_v3_02.pm
2016.12.22 14:26:58.182 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2016.12.22 14:26:58.190 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_virtual.pm
2016.12.22 14:26:58.326 3: Opening NETIO1 device 192.168.1.98:2701
2016.12.22 14:26:58.343 3: NETIO1 device opened
2016.12.22 14:26:58.417 3: Opening NETIO2 device 192.168.1.99:2701
2016.12.22 14:26:58.421 3: NETIO2 device opened
2016.12.22 14:26:58.676 2: HM_LAN_WIRED: Assigned 00011169 as HMW_IO_12_Sw14_DR_LEQ1322965
2016.12.22 14:26:59.508 2: HM_LAN_WIRED: Assigned 00012465 as HMW_IO_12_Sw14_DR_MEQ0370281
2016.12.22 14:27:00.269 1: Including ./log/fhem.save
2016.12.22 14:27:01.217 3: Device Bewegungsmelder_EG added to ActionDetector with 024:00 time
2016.12.22 14:27:01.228 4: Device Bewegungsmelder_EG is alive
2016.12.22 14:27:01.250 3: Device Bewegungsmelder_UG added to ActionDetector with 024:00 time
2016.12.22 14:27:01.260 4: Device Bewegungsmelder_UG is alive
2016.12.22 14:27:01.283 3: Device CUL_HM_HM_CC_RT_DN_354555 added to ActionDetector with 000:10 time
2016.12.22 14:27:01.293 4: Device CUL_HM_HM_CC_RT_DN_354555 is alive
2016.12.22 14:27:01.365 3: Device CUL_HM_HM_CC_RT_DN_3547B5 added to ActionDetector with 000:10 time
2016.12.22 14:27:01.375 4: Device CUL_HM_HM_CC_RT_DN_3547B5 is alive
2016.12.22 14:27:01.448 3: Device CUL_HM_HM_CC_RT_DN_3547BA added to ActionDetector with 000:10 time
2016.12.22 14:27:01.458 4: Device CUL_HM_HM_CC_RT_DN_3547BA is alive
2016.12.22 14:27:01.530 3: Device CUL_HM_HM_CC_RT_DN_3547BB added to ActionDetector with 000:10 time
2016.12.22 14:27:01.541 4: Device CUL_HM_HM_CC_RT_DN_3547BB is alive
2016.12.22 14:27:01.614 3: Device CUL_HM_HM_CC_RT_DN_3547BF added to ActionDetector with 000:10 time
2016.12.22 14:27:01.625 4: Device CUL_HM_HM_CC_RT_DN_3547BF is alive
2016.12.22 14:27:01.697 3: Device CUL_HM_HM_CC_RT_DN_3549DB added to ActionDetector with 000:10 time
2016.12.22 14:27:01.708 4: Device CUL_HM_HM_CC_RT_DN_3549DB is alive
2016.12.22 14:27:01.781 3: Device CUL_HM_HM_CC_RT_DN_3549DE added to ActionDetector with 000:10 time
2016.12.22 14:27:01.793 4: Device CUL_HM_HM_CC_RT_DN_3549DE is alive
2016.12.22 14:27:01.866 3: Device CUL_HM_HM_CC_RT_DN_3549E1 added to ActionDetector with 000:10 time
2016.12.22 14:27:01.878 4: Device CUL_HM_HM_CC_RT_DN_3549E1 is alive
2016.12.22 14:27:02.067 3: Device CUL_HM_HM_SEC_SD_2F361B added to ActionDetector with 099:00 time
2016.12.22 14:27:02.077 4: Device CUL_HM_HM_SEC_SD_2F361B is alive
2016.12.22 14:27:02.105 3: Device CUL_HM_HM_SEC_SD_2F3665 added to ActionDetector with 099:00 time
2016.12.22 14:27:02.115 4: Device CUL_HM_HM_SEC_SD_2F3665 is alive
2016.12.22 14:27:02.142 3: Device CUL_HM_HM_SEC_SD_2F36E2 added to ActionDetector with 099:00 time
2016.12.22 14:27:02.153 4: Device CUL_HM_HM_SEC_SD_2F36E2 is alive
2016.12.22 14:27:02.181 3: Device CUL_HM_HM_SEC_SD_2F387B added to ActionDetector with 099:00 time
2016.12.22 14:27:02.192 4: Device CUL_HM_HM_SEC_SD_2F387B is alive
2016.12.22 14:27:02.220 3: Device CUL_HM_HM_SEC_SD_2F387C added to ActionDetector with 099:00 time
2016.12.22 14:27:02.231 4: Device CUL_HM_HM_SEC_SD_2F387C is alive
2016.12.22 14:27:02.259 3: Device CUL_HM_HM_SEC_SD_2F389B added to ActionDetector with 099:00 time
2016.12.22 14:27:02.271 4: Device CUL_HM_HM_SEC_SD_2F389B is alive
2016.12.22 14:27:02.655 4: initialUsbCheck exec usb create
2016.12.22 14:27:02.656 1: usb create starting
2016.12.22 14:27:03.249 4: ### ttyAMA0: checking if it is a CUL
2016.12.22 14:27:03.252 3: Probing CUL device /dev/ttyAMA0
2016.12.22 14:27:03.467 4: got wrong answer for a CUL
2016.12.22 14:27:03.468 4: ### ttyAMA0: checking if it is a TCM_ESP3
2016.12.22 14:27:03.470 3: Probing TCM_ESP3 device /dev/ttyAMA0
2016.12.22 14:27:03.679 4: got wrong answer for a TCM_ESP3
2016.12.22 14:27:03.680 4: ### ttyAMA0: checking if it is a FRM
2016.12.22 14:27:03.683 3: Probing FRM device /dev/ttyAMA0
2016.12.22 14:27:08.895 4: got wrong answer for a FRM
2016.12.22 14:27:08.896 4: ### ttyUSB0: checking if it is a TCM_ESP3
2016.12.22 14:27:08.899 4: ttyUSB0 is already used by the fhem device nanoCUL
2016.12.22 14:27:08.900 4: ### ttyUSB1: checking if it is a TCM_ESP3
2016.12.22 14:27:08.902 3: Probing TCM_ESP3 device /dev/ttyUSB1
2016.12.22 14:27:09.121 4: got wrong answer for a TCM_ESP3
2016.12.22 14:27:09.122 4: ### ttyUSB1: checking if it is a TCM_ESP2
2016.12.22 14:27:09.124 3: Probing TCM_ESP2 device /dev/ttyUSB1
2016.12.22 14:27:09.344 4: got wrong answer for a TCM_ESP2
2016.12.22 14:27:09.345 4: ### ttyUSB1: checking if it is a FHZ
2016.12.22 14:27:09.347 3: Probing FHZ device /dev/ttyUSB1
2016.12.22 14:27:09.566 4: got wrong answer for a FHZ
2016.12.22 14:27:09.567 4: ### ttyUSB1: checking if it is a TRX
2016.12.22 14:27:09.569 3: Probing TRX device /dev/ttyUSB1
2016.12.22 14:27:10.300 4: got wrong answer for a TRX
2016.12.22 14:27:10.301 4: ### ttyUSB1: checking if it is a ZWDongle
2016.12.22 14:27:10.304 3: Probing ZWDongle device /dev/ttyUSB1
2016.12.22 14:27:10.524 4: got wrong answer for a ZWDongle
2016.12.22 14:27:10.525 4: ### ttyUSB1: checking if it is a FRM
2016.12.22 14:27:10.527 3: Probing FRM device /dev/ttyUSB1
2016.12.22 14:27:17.202 4: got wrong answer for a FRM
2016.12.22 14:27:17.234 1: usb create end
2016.12.22 14:27:17.264 2: SecurityCheck:  WEB,WEBtablet has no associated allowed device with basicAuth. telnetPort has no associated allowed device with password/globalpassword.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message. 
2016.12.22 14:27:17.265 0: Featurelevel: 5.7
2016.12.22 14:27:17.265 0: Server started with 245 defined entities (fhem.pl:12463/2016-10-29 perl:5.014002 os:linux user:fhem pid:27914)
2016.12.22 14:27:17.405 1: HM_LAN_WIRED: HM485d already running with PID 27719. We are using this process.
2016.12.22 14:27:17.418 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:17.428 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:17.452 4: dummy set Test2 toggle
2016.12.22 14:27:17.461 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 14:27:17.530 4: dummy set Test off
2016.12.22 14:27:17.533 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 14:27:17.580 4: Connection accepted from WEB_192.168.1.20_54754
2016.12.22 14:27:17.583 2: TSCUL_Parse: nanoCUL new condition ok
2016.12.22 14:27:17.593 4: TSCUL_Parse: nanoCUL  451904 A FF51 00006384 00 0F FB 8610 3549E1 000000 0A24C70B0040 -72.5
2016.12.22 14:27:17.775 4: TSCUL_Parse: nanoCUL  452097 A FF51 00008092 00 0F 64 8610 354555 000000 0A28A80A0040 -59
2016.12.22 14:27:17.837 4: TSCUL_Parse: nanoCUL  452160 A FF51 00010552 00 0D DC A641 4F9EC9 F11234 012AB240 -84.5
2016.12.22 14:27:17.854 4: TSCUL_send:  nanoCUL                         As 0D DC 8002 F11234 4F9EC9 0101B200
2016.12.22 14:27:17.855 3: TSCUL_XmitDlyHM:  nanoCUL  id:4F9EC9 dDly:91 toms:72
2016.12.22 14:27:17.884 4: TSCUL_Parse: nanoCUL  452207 A FF51 00011220 00 0D DC A641 4F9EC9 F11234 012AB240 -84.5
2016.12.22 14:27:17.887 4: CUL_HM Bewegungsmelder_UG dupe: dont process
2016.12.22 14:27:17.890 4: TSCUL_Parse: nanoCUL  452213 A FF51 00011520 00 0D DC A641 4F9EC9 F11234 012AB240 -84
2016.12.22 14:27:17.893 4: CUL_HM Bewegungsmelder_UG dupe: dont process
2016.12.22 14:27:17.896 3: Opening HM_LAN_WIRED device localhost:2000
2016.12.22 14:27:17.904 3: Can't connect to localhost:2000: Connection reset by peer
2016.12.22 14:27:17.908 4: Connection accepted from WEB_192.168.1.20_54753
2016.12.22 14:27:17.911 4: TSCUL_Parse: nanoCUL  452233 A FF51 00016136 00 0D AB A641 461413 F11234 01176C40 -73
2016.12.22 14:27:17.928 4: TSCUL_send:  nanoCUL                         As 0D AB 8002 F11234 461413 01016C00
2016.12.22 14:27:17.928 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:91 toms:72
2016.12.22 14:27:17.955 4: TSCUL_Parse: nanoCUL  452278 A FF51 00016360 00 0D AB A641 461413 F11234 01176C40 -73
2016.12.22 14:27:17.958 4: CUL_HM Bewegungsmelder_EG dupe: dont process
2016.12.22 14:27:17.960 4: TSCUL_Parse: nanoCUL  452284 A FF51 00016848 00 0D AB A641 461413 F11234 01176C40 -73
2016.12.22 14:27:17.963 4: CUL_HM Bewegungsmelder_EG dupe: dont process
2016.12.22 14:27:17.966 4: TSCUL_Parse: nanoCUL  452295 A FF52 00020952 00 01 C3 _ping -138
2016.12.22 14:27:17.967 4: TSCUL_Parse: nanoCUL  452287 A FF52 00020972 00 15 AABBCCDDAABBCCDDAABBCCDDAABBCCDDAABBCCDDAA _ping -138
2016.12.22 14:27:18.341 4: WEB_192.168.1.20_54754 GET /fhem?XHR=1&inform=type=status;filter=nanoCUL;since=1482413146.362;fmt=JSON&fw_id=507×tamp=1482413211317; BUFLEN:0
2016.12.22 14:27:18.522 3: HM_LAN_WIRED: Start HM485d with command line: ./FHEM/lib/HM485/HM485d/HM485d.pl --hmwId 00000001 --serialNumber SGW0123456 --device 192.168.1.97:5000 --localPort 2000 --verbose 1
2016.12.22 14:27:18.613 3: HM_LAN_WIRED: HM485d was started with PID: 27930
2016.12.22 14:27:18.614 3: HM_LAN_WIRED: Connect to HM485d delayed for 4 seconds
2016.12.22 14:27:18.626 4: TSCUL_send:  nanoCUL                         As 0A DC 8002 F11234 4F9EC9 00
2016.12.22 14:27:18.638 4: TSCUL_send:  nanoCUL                         As 0A AB 8002 F11234 461413 00
2016.12.22 14:27:18.642 4: Connection accepted from WEB_192.168.1.20_54771
2016.12.22 14:27:18.643 4: Connection closed for WEB_192.168.1.20_54753: EOF
2016.12.22 14:27:18.646 4: TSCUL_Parse: nanoCUL  452970 A FF53 00021380 02 0D DC 8002 F11234 4F9EC9 01 _CCAdly:8 -138
2016.12.22 14:27:18.648 4: TSCUL_Parse: nanoCUL  452972 A FF53 00021472 01 0D AB 8002 F11234 461413 01 _CCAdly:4 -138
2016.12.22 14:27:18.652 4: Connection closed for WEB_192.168.1.20_54754: EOF
2016.12.22 14:27:18.743 4: WEB_192.168.1.20_54771 GET /fhem?room=CUL%5fHM; BUFLEN:0
2016.12.22 14:27:18.939 4: name: /fhem?room=CUL%5fHM / RL:3017 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:18.942 4: TSCUL_Parse: nanoCUL  453266 A FF53 00022152 02 0A DC 8002 F11234 4F9EC9 00 _CCAdly:8 -138
2016.12.22 14:27:18.944 4: TSCUL_Parse: nanoCUL  453269 A FF53 00022240 01 0A AB 8002 F11234 461413 00 _CCAdly:4 -138
2016.12.22 14:27:19.118 4: dummy set Test2 toggle
2016.12.22 14:27:19.170 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 14:27:19.176 4: dummy set Test on
2016.12.22 14:27:19.178 4: Dummy_Ein exec { fhem "set Relais9 on";; fhem "set HMW_IO_12_Sw14_DR_LEQ1322965_01 toggle" }
2016.12.22 14:27:19.827 4: Connection accepted from WEB_192.168.1.20_54779
2016.12.22 14:27:19.829 4: WEB_192.168.1.20_54771 GET /fhem/pgm2/style.css?v=1482413213; BUFLEN:0
2016.12.22 14:27:19.830 1: HM485d: Server started ...
2016.12.22 14:27:19.928 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (1) I[0](0,Y,F,B)(98) 00000001 -> 00011169 [6] 73(s) 0003FF
2016.12.22 14:27:19.932 4: WEB_192.168.1.20_54779 GET /fhem/pgm2/hm485.js?1482413218.25254; BUFLEN:0
2016.12.22 14:27:20.021 4: Connection accepted from WEB_192.168.1.20_54780
2016.12.22 14:27:20.104 4: WEB_192.168.1.20_54771 GET /fhem/images/default/off.png; BUFLEN:0
2016.12.22 14:27:20.106 4: WEB_192.168.1.20_54771 => 304 Not Modified
2016.12.22 14:27:20.109 4: WEB_192.168.1.20_54779 GET /fhem/images/default/on.png; BUFLEN:0
2016.12.22 14:27:20.110 4: WEB_192.168.1.20_54779 => 304 Not Modified
2016.12.22 14:27:20.679 4: WEB_192.168.1.20_54771 GET /fhem?XHR=1&inform=type=status;filter=room=CUL%5fHM;since=1482413237;fmt=JSON&fw_id=491×tamp=1482413238526; BUFLEN:0
2016.12.22 14:27:21.075 3: HMW_IO_12_Sw14_DR_LEQ1322965: RESPONSE TIMEOUT for 00011169
2016.12.22 14:27:22.501 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:22.502 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:22.801 3: Opening HM_LAN_WIRED device localhost:2000
2016.12.22 14:27:22.894 4: Connection closed for WEB_192.168.1.20_54771: EOF
2016.12.22 14:27:22.983 4: WEB_192.168.1.20_54779 GET /fhem?detail=nanoCUL; BUFLEN:0
2016.12.22 14:27:23.037 4: name: /fhem?detail=nanoCUL / RL:4270 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:23.787 4: WEB_192.168.1.20_54779 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 14:27:23.798 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:23.888 4: WEB_192.168.1.20_54780 GET /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 14:27:23.899 4: name: /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1 / RL:27 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:24.010 4: WEB_192.168.1.20_54779 GET /fhem?XHR=1&inform=type=status;filter=nanoCUL;since=1482413241;fmt=JSON&fw_id=492×tamp=1482413241756; BUFLEN:0
2016.12.22 14:27:26.069 4: TSCUL_Parse: nanoCUL  460398 A FF52 00029584 00 01 C3 _ping -138
2016.12.22 14:27:27.243 4: WEB_192.168.1.20_54780 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22hmPairForSec%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 14:27:27.254 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22hmPairForSec%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:27.585 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:27.588 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:28.498 4: TSCUL_Parse: nanoCUL  462819 A FF51 00031932 00 0F 1E 8610 3547B5 000000 0A4CBD0A0040 -90
2016.12.22 14:27:29.142 4: dummy set Test2 toggle
2016.12.22 14:27:29.153 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 14:27:29.159 4: dummy set Test off
2016.12.22 14:27:29.161 4: Dummy_Aus exec { fhem "set Relais9 off" }
2016.12.22 14:27:29.506 4: TSCUL_Parse: nanoCUL  463829 A FF51 00032940 00 0D AC A641 461413 F11234 01186C40 -73
2016.12.22 14:27:29.525 4: TSCUL_send:  nanoCUL                         As 0D AC 8002 F11234 461413 01016C00
2016.12.22 14:27:29.525 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:13 toms:72
2016.12.22 14:27:29.648 4: TSCUL_send:  nanoCUL                         As 0A AC 8002 F11234 461413 00
2016.12.22 14:27:29.649 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:11 toms:72
2016.12.22 14:27:29.653 4: TSCUL_Parse: nanoCUL  463977 A FF53 00033060 01 0D AC 8002 F11234 461413 01 _CCAdly:4 _dhmSt:120 -138
2016.12.22 14:27:29.739 4: TSCUL_Parse: nanoCUL  464063 A FF53 00033180 01 0A AC 8002 F11234 461413 00 _CCAdly:4 _dhmSt:240 -138
2016.12.22 14:27:31.019 4: Connection closed for WEB_192.168.1.20_54779: EOF
2016.12.22 14:27:31.104 4: WEB_192.168.1.20_54780 POST /fhem&detail=nanoCUL&dev.setnanoCUL=nanoCUL&cmd.setnanoCUL=set&arg.setnanoCUL=hmPairForSec&val.setnanoCUL=30; BUFLEN:0
2016.12.22 14:27:31.207 4: WEB_192.168.1.20_54780 GET /fhem?detail=nanoCUL&fw_id=; BUFLEN:0
2016.12.22 14:27:31.267 4: name: /fhem?detail=nanoCUL&fw_id= / RL:4283 / text/html; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:32.045 4: WEB_192.168.1.20_54780 GET /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 14:27:32.058 4: name: /fhem?cmd={ReadingsVal(%22nanoCUL%22,%22CCAmode%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:32.142 4: Connection accepted from WEB_192.168.1.20_54791
2016.12.22 14:27:32.228 4: WEB_192.168.1.20_54791 GET /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.12.22 14:27:32.240 4: name: /fhem?cmd={AttrVal(%22nanoCUL%22,%22room%22,%22%22)}&XHR=1 / RL:27 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / 
2016.12.22 14:27:32.243 4: WEB_192.168.1.20_54780 GET /fhem?XHR=1&inform=type=status;filter=nanoCUL;since=1482413250;fmt=JSON&fw_id=493×tamp=1482413250025; BUFLEN:0
2016.12.22 14:27:32.672 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:32.673 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:34.732 4: TSCUL_Parse: nanoCUL  469048 A FF51 00038168 00 1A AD 8400 461413 000000 16005D4E45513031313830363481110100 -77
2016.12.22 14:27:34.738 3: Device Bewegungsmelder_EG added to ActionDetector with 024:00 time
2016.12.22 14:27:34.744 4: Device Bewegungsmelder_EG is alive
2016.12.22 14:27:34.745 3: CUL_HM pair: Bewegungsmelder_EG motionDetector, model HM-Sen-MDIR-O serialNr NEQ0118064
2016.12.22 14:27:34.764 4: TSCUL_send:  nanoCUL                         As 10 D5 A001 F11234 461413 00050000000000
2016.12.22 14:27:34.938 4: TSCUL_Parse: nanoCUL  469263 A FF53 00038304 02 10 D5 A001 F11234 461413 00 _CCAdly:8 _dhmSt:136 -138
2016.12.22 14:27:34.941 4: TSCUL_Parse: nanoCUL  469265 A FF51 00038452 00 0A D5 8002 461413 F11234 00 -78
2016.12.22 14:27:34.958 4: TSCUL_send:  nanoCUL                         As 13 D6 A001 F11234 461413 000802010AF10B120C34
2016.12.22 14:27:34.958 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:85 toms:74
2016.12.22 14:27:35.165 4: TSCUL_Parse: nanoCUL  469489 A FF53 00038572 01 13 D6 A001 F11234 461413 00 _CCAdly:4 _dhmSt:120 -138
2016.12.22 14:27:35.251 4: TSCUL_Parse: nanoCUL  469575 A FF51 00038720 00 0A D6 8002 461413 F11234 00 -76.5
2016.12.22 14:27:35.269 4: TSCUL_send:  nanoCUL                         As 0B D7 A001 F11234 461413 0006
2016.12.22 14:27:35.270 3: TSCUL_XmitDlyHM:  nanoCUL  id:461413 dDly:46 toms:72
2016.12.22 14:27:35.358 4: TSCUL_Parse: nanoCUL  469682 A FF53 00038840 01 0B D7 A001 F11234 461413 00 _CCAdly:4 _dhmSt:120 -138
2016.12.22 14:27:35.549 4: TSCUL_Parse: nanoCUL  469873 A FF51 00038988 00 0A D7 8002 461413 F11234 00 -71.5
2016.12.22 14:27:37.760 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:37.761 3: HM_LAN_WIRED: Warte auf Initialisierung Gateway
2016.12.22 14:27:39.142 4: dummy set Test2 toggle
2016.12.22 14:27:39.153 4: nty_Test exec IF ([Test:&STATE] eq "on") (set Test off) ELSE (set Test on)
2016.12.22 14:27:39.159 4: dummy set Test on
2016.12.22 14:27:39.162 4: Dummy_Ein exec { fhem "set Relais9 on";; fhem "set HMW_IO_12_Sw14_DR_LEQ1322965_01 toggle" }
2016.12.22 14:27:39.323 4: HM_LAN_WIRED: HM_LAN_WIRED: TX: (1) I[1](0,F,B)(1A) 00000001 -> 00011169 [6] 73(s) 000000
2016.12.22 14:27:39.957 4: Connection closed for WEB_192.168.1.20_54780: EOF
2016.12.22 14:27:40.043 4: WEB_192.168.1.20_54791 GET /fhem/FileLog_logWrapper?dev=Logfile&type=text&file=fhem-2016-12.log; BUFLEN:0

sieht aus als hätte es jetzt funktioniert, zumindest hat der Melder OK gemeldet. Welche Frequenz haben die Aktoren genau und warum ist ein OFFSET defaultmäßig von 300kHz eingestellt?

noansi · 22 Dezember 2016, 15:47:02

Hallo Mario,

seltsam, ein Offset auf 300kHz kann eingentlich nicht sein, weil der Range gar nicht ganz so groß ist.

Wenn Du neu compiliert hast und HAS_NO_VERSION_CHANGE_FACTORY_RESET in der board.h aktiviert hast, dann wird kein "factory_reset" des EEPROMs mit Versionsänderung ausgeführt und dann kann ziemlicher Quatsch drin stehen. Bei leerem EEPROM Speicherplatz müste es eigentlich FF sein als -1.6x kHz oder so was.
Ein set raw e führt den factory_reset auch aus.

Mein default mit factory Reset Wert ist -22.217kHz, weil es bei mir so gut passt und bei allen CULs die ich testen kann recht ähnlich ist.

Gruß, Ansgar.

Maxl · 22 Dezember 2016, 16:47:51

Hallo Ansgar,

nach dem Reset hatte ich deine erwähnten Werte, mal schaun wie sich nun alles verhält.

Danke