FHEM Forum

FHEM => Anfängerfragen => Thema gestartet von: siltalai am 12 August 2016, 12:54:08

Titel: Jeelink v3c und TX 29 DTH - IT kein pairing trotz neuem sketch
Beitrag von: siltalai am 12 August 2016, 12:54:08
Hallo ich habe:
Jeelink v3c 868 MHz Version an windows server 2012.
und 2 x Technoline Außensender TX 29 DTH - IT

Nach
http://www.fhemwiki.de/wiki/JeeLink (http://www.fhemwiki.de/wiki/JeeLink)
habe ich die Treiber installiert und dann den Jeelink unter Windows mit der arduino IDE geflasht mit folgendem Sketch:
36_LaCrosse-LaCrosseITPlusReader.zip: Version 10.1q: Hotfix for WS 1080
Klappte.

STATE opened
Clients:PCA301:EC3000:RoomNode:LaCrosse:ETH200comfort:CUL_IR:HX2272:FS20:AliRF:Level:EMT7110:KeyValueProtoco


Das Log sieht bei mir, wenn ich das Pairing aktiviert und die Batterie einsetze so aus:
Pairing findet nicht statt (wenn ich  das richtig sehe)

2016.08.12 12:24:07 4: WEB_192.168.23.16_58680 GET /fhem?XHR=1&inform=type=status;filter=room=all;since=1470997444;fmt=JSON&fw_id=83×tamp=1470997447262; BUFLEN:0
2016.08.12 12:24:09 4: Connection closed for WEB_192.168.23.16_58680: EOF
2016.08.12 12:24:09 4: WEB_192.168.23.16_58678 GET /fhem?detail=myJeeLink; BUFLEN:0
2016.08.12 12:24:09 4: name: /fhem?detail=myJeeLink / RL:2953 / text/html; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:10 4: WEB_192.168.23.16_58678 GET /fhem?cmd={ReadingsVal(%22myJeeLink%22,%22LaCrossePairForSec%22,%22%22)}&XHR=1; BUFLEN:0
2016.08.12 12:24:10 5: Cmd: >{ReadingsVal("myJeeLink","LaCrossePairForSec","")}<
2016.08.12 12:24:10 4: name: /fhem?cmd={ReadingsVal(%22myJeeLink%22,%22LaCrossePairForSec%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:10 4: WEB_192.168.23.16_58676 GET /fhem?cmd={AttrVal(%22myJeeLink%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.08.12 12:24:10 5: Cmd: >{AttrVal("myJeeLink","room","")}<
2016.08.12 12:24:10 4: name: /fhem?cmd={AttrVal(%22myJeeLink%22,%22room%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:10 4: WEB_192.168.23.16_58678 GET /fhem?XHR=1&inform=type=status;filter=myJeeLink;since=1470997448;fmt=JSON&fw_id=81×tamp=1470997450443; BUFLEN:0
2016.08.12 12:24:18 4: Connection closed for WEB_192.168.23.16_58678: EOF
2016.08.12 12:24:18 4: WEB_192.168.23.16_58676 POST /fhem&detail=myJeeLink&dev.setmyJeeLink=myJeeLink&cmd.setmyJeeLink=set&arg.setmyJeeLink=LaCrossePairForSec&val.setmyJeeLink=60; BUFLEN:0
2016.08.12 12:24:18 5: Cmd: >set myJeeLink LaCrossePairForSec 60<
2016.08.12 12:24:18 5: Triggering myJeeLink (1 changes)
2016.08.12 12:24:18 5: Starting notify loop for myJeeLink, first event LaCrossePairForSec 60
2016.08.12 12:24:18 4: WEB_192.168.23.16_58676 GET /fhem?detail=myJeeLink&fw_id=; BUFLEN:0
2016.08.12 12:24:18 4: name: /fhem?detail=myJeeLink&fw_id= / RL:2969 / text/html; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:19 4: WEB_192.168.23.16_58676 GET /fhem?cmd={ReadingsVal(%22myJeeLink%22,%22LaCrossePairForSec%22,%22%22)}&XHR=1; BUFLEN:0
2016.08.12 12:24:19 5: Cmd: >{ReadingsVal("myJeeLink","LaCrossePairForSec","")}<
2016.08.12 12:24:19 4: name: /fhem?cmd={ReadingsVal(%22myJeeLink%22,%22LaCrossePairForSec%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:19 4: WEB_192.168.23.16_58679 GET /fhem?cmd={AttrVal(%22myJeeLink%22,%22room%22,%22%22)}&XHR=1; BUFLEN:0
2016.08.12 12:24:19 5: Cmd: >{AttrVal("myJeeLink","room","")}<
2016.08.12 12:24:19 4: name: /fhem?cmd={AttrVal(%22myJeeLink%22,%22room%22,%22%22)}&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2016.08.12 12:24:19 4: WEB_192.168.23.16_58676 GET /fhem?XHR=1&inform=type=status;filter=myJeeLink;since=1470997457;fmt=JSON&fw_id=79×tamp=1470997459218; BUFLEN:0
2016.08.12 12:25:07 5: FBAHA/RAW: /0703001c00000011001000000000000c000000140004000000000000
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c000000140004000000000000
2016.08.12 12:25:07 4: Payload: 000000140004000000000000 -> power: 0.00 W
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event power: 0.00 W
2016.08.12 12:25:07 5: FBAHA/RAW: /0703001c00000011001000000000000c0000000f0004000000000000070300200000001100100000000000100000001700080000000000ff000000000703001c00000011001000000000000c0000001300040000000395d00703001c00000011001000000000000c00000012000400000000000a0703001c00000011001000000000000c00000015000400000000017e0703001c00000011001000000000000c000000160004000000000000
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c0000000f0004000000000000
2016.08.12 12:25:07 4: Payload: 0000000f0004000000000000 -> state: off
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event off
2016.08.12 12:25:07 5: Fritzbox dispatch 070300200000001100100000000000100000001700080000000000ff00000000
2016.08.12 12:25:07 4: Payload: 0000001700080000000000ff00000000 -> temperature: 25.5 C (measured)
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event temperature: 25.5 C (measured)
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c0000001300040000000395d0
2016.08.12 12:25:07 4: Payload: 0000001300040000000395d0 -> voltage: 234.960 V
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event voltage: 234.960 V
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c00000012000400000000000a
2016.08.12 12:25:07 4: Payload: 00000012000400000000000a -> current: 0.0010 A
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event current: 0.0010 A
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c00000015000400000000017e
2016.08.12 12:25:07 4: Payload: 00000015000400000000017e -> energy: 382 Wh
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event energy: 382 Wh
2016.08.12 12:25:07 5: Fritzbox dispatch 0703001c00000011001000000000000c000000160004000000000000
2016.08.12 12:25:07 4: Payload: 000000160004000000000000 -> powerFactor: 0.000
2016.08.12 12:25:07 5: FBDECT_Parse for device FBDECT_Fritzbox_16 done
2016.08.12 12:25:07 5: Triggering FBDECT_Fritzbox_16 (1 changes)
2016.08.12 12:25:07 5: Starting notify loop for FBDECT_Fritzbox_16, first event powerFactor: 0.000


Kann mir jemand weiterhelfen?
Vielen Dank!
Michael
Titel: Antw:Jeelink v3c und TX 29 DTH - IT kein pairing trotz neuem sketch
Beitrag von: siltalai am 02 September 2016, 13:12:51
Ich habe das dämliche Ding mit dem gleichen Sketch nochmals geflasht und jetzt gehts. ::)..............