Installationsprobleme

Begonnen von kblc, 04 Dezember 2014, 16:26:20

Vorheriges Thema - Nächstes Thema

kblc

Hallo an Alle,

ich habe soeben meinen RFXTRX installieren wollen, ich habe FHEM noch auf der Fritzbox 7390. Ich hatte zuvor ein CUL 868 angeschlossen, woran erkenne ich, dass mein neues Gerät erfolgreich angeschlossen/erkannt wurde?
Es tut nichts. Es blinkt nichts und ich finde keine Informationen dazu.

In der Log steht:
2014.12.04 14:19:15 1: usb create starting
2014.12.04 14:19:16 3: Opening TCM310 device /dev/ttyUSB0
2014.12.04 14:19:16 3: Setting TCM310 baudrate to 57600
2014.12.04 14:19:17 3: TCM310 device opened
2014.12.04 14:19:17 3: Opening TCM120 device /dev/ttyUSB0
2014.12.04 14:19:17 3: Setting TCM120 baudrate to 9600
2014.12.04 14:19:17 3: TCM120 device opened
2014.12.04 14:19:17 3: Opening FHZ device /dev/ttyUSB0
2014.12.04 14:19:17 3: Setting FHZ baudrate to 9600
2014.12.04 14:19:17 3: FHZ device opened
2014.12.04 14:19:18 3: Opening TRX device /dev/ttyUSB0
2014.12.04 14:19:18 3: Setting TRX baudrate to 38400
2014.12.04 14:19:18 3: TRX device opened
2014.12.04 14:19:19 1: define TRX_0 TRX /dev/ttyUSB0@38400
2014.12.04 14:19:19 3: Opening TRX_0 device /dev/ttyUSB0
2014.12.04 14:19:19 3: Setting TRX_0 baudrate to 38400
2014.12.04 14:19:19 3: TRX_0 device opened
2014.12.04 14:19:19 1: TRX: Init OK
2014.12.04 14:19:19 1: TRX: Init status: '433.92MHz transceiver, firmware=231, protocols enabled: LaCrosse Hideki OREGON AC ARC X10 '
2014.12.04 14:19:20 1: usb create end
2014.12.04 14:19:20 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart fhem for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.12.04 14:19:20 0: Server started with 338 defined entities (version $Id: fhem.pl 3872 2013-09-07 11:58:33Z rudolfkoenig $, os linux, user boxusr99, pid 2926)
2014.12.04 14:20:26 1: usb create starting
2014.12.04 14:20:27 1: usb create end
2014.12.04 14:23:51 1: usb create starting
2014.12.04 14:23:52 1: usb create end
2014.12.04 14:26:28 1: usb create starting
2014.12.04 14:26:29 1: usb create end
2014.12.04 14:27:42 1: Including fhem.cfg
2014.12.04 14:27:42 3: telnetPort: port 7072 opened
2014.12.04 14:27:42 3: WEB: port 8083 opened
2014.12.04 14:27:42 3: WEBphone: port 8084 opened
2014.12.04 14:27:42 3: WEBtablet: port 8085 opened
2014.12.04 14:27:42 3: Opening FritzBox1 device 192.168.78.6:1012
2014.12.04 14:27:42 3: FritzBox1 device opened
2014.12.04 14:27:42 2: FB_CALLMONITOR: FritzBox1 found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:27:42 2: FB_CALLMONITOR: FritzBox1 read 254 contacts from FritzBox phonebook
2014.12.04 14:27:42 3: Opening FritzBox device 192.168.78.1:1012
2014.12.04 14:27:42 3: FritzBox device opened
2014.12.04 14:27:42 2: FB_CALLMONITOR: FritzBox found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:27:43 2: FB_CALLMONITOR: FritzBox read 254 contacts from FritzBox phonebook
2014.12.04 14:27:43 3: Opening FritzBox2 device 192.168.78.2:1012
2014.12.04 14:27:43 3: FritzBox2 device opened
2014.12.04 14:27:43 2: FB_CALLMONITOR: FritzBox2 found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:27:43 2: FB_CALLMONITOR: FritzBox2 read 254 contacts from FritzBox phonebook
2014.12.04 14:27:43 3: Opening FritzBoxLS device 192.168.79.9:1012
2014.12.04 14:27:43 3: FritzBoxLS device opened
2014.12.04 14:27:43 2: FB_CALLMONITOR: FritzBoxLS found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:27:44 2: FB_CALLMONITOR: FritzBoxLS read 254 contacts from FritzBox phonebook
2014.12.04 14:27:44 3: Opening FritzBoxKS device 192.168.178.1:1012
2014.12.04 14:27:44 3: FritzBoxKS device opened
2014.12.04 14:27:44 2: FB_CALLMONITOR: FritzBoxKS found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:27:44 2: FB_CALLMONITOR: FritzBoxKS read 254 contacts from FritzBox phonebook
2014.12.04 14:27:44 3: Opening CUL_0 device /dev/ttyACM0
2014.12.04 14:27:44 3: Can't open /dev/ttyACM0: No such file or directory
2014.12.04 14:27:44 1: Including ./FHEM/wetter.cfg
2014.12.04 14:27:45 1: Including ./FHEM/test.cfg
2014.12.04 14:27:48 1: Including ./FHEM/Anruferkennung.cfg
2014.12.04 14:27:48 1: Including ./FHEM/Testensteuuerung.cfg
2014.12.04 14:27:48 3: Opening TRX_0 device /dev/ttyUSB0
2014.12.04 14:27:48 3: Setting TRX_0 baudrate to 38400
2014.12.04 14:27:48 3: TRX_0 device opened
2014.12.04 14:27:49 1: TRX: Init OK
2014.12.04 14:27:49 1: TRX: Init status: '433.92MHz transceiver, firmware=231, protocols enabled: LaCrosse Hideki OREGON AC ARC X10 '
2014.12.04 14:27:49 1: Including ./log/fhem.save
2014.12.04 14:29:05 1: usb create starting
2014.12.04 14:29:06 1: usb create end
2014.12.04 14:36:03 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.12.04 14:36:14 3: Setting TRX_0 baudrate to 38400
2014.12.04 14:36:14 1: /dev/ttyUSB0 reappeared (TRX_0)
2014.12.04 14:36:22 1: usb create starting
2014.12.04 14:36:24 1: usb create end
2014.12.04 14:37:22 0: Server shutdown
2014.12.04 14:37:26 1: Including fhem.cfg
2014.12.04 14:37:27 3: telnetPort: port 7072 opened
2014.12.04 14:37:28 3: WEB: port 8083 opened
2014.12.04 14:37:28 3: WEBphone: port 8084 opened
2014.12.04 14:37:28 3: WEBtablet: port 8085 opened
2014.12.04 14:37:28 3: Opening FritzBox1 device 192.168.78.6:1012
2014.12.04 14:37:28 3: FritzBox1 device opened
2014.12.04 14:37:28 2: FB_CALLMONITOR: FritzBox1 found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBox1 read 254 contacts from FritzBox phonebook
2014.12.04 14:37:29 3: Opening FritzBox device 192.168.78.1:1012
2014.12.04 14:37:29 3: FritzBox device opened
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBox found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBox read 254 contacts from FritzBox phonebook
2014.12.04 14:37:29 3: Opening FritzBox2 device 192.168.78.2:1012
2014.12.04 14:37:29 3: FritzBox2 device opened
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBox2 found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBox2 read 254 contacts from FritzBox phonebook
2014.12.04 14:37:29 3: Opening FritzBoxLS device 192.168.79.9:1012
2014.12.04 14:37:29 3: FritzBoxLS device opened
2014.12.04 14:37:29 2: FB_CALLMONITOR: FritzBoxLS found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:37:30 2: FB_CALLMONITOR: FritzBoxLS read 254 contacts from FritzBox phonebook
2014.12.04 14:37:30 3: Opening FritzBoxKS device 192.168.178.1:1012
2014.12.04 14:37:30 3: FritzBoxKS device opened
2014.12.04 14:37:30 2: FB_CALLMONITOR: FritzBoxKS found FritzBox phonebook /var/flash/phonebook
2014.12.04 14:37:30 2: FB_CALLMONITOR: FritzBoxKS read 254 contacts from FritzBox phonebook
2014.12.04 14:37:30 3: Opening CUL_0 device /dev/ttyACM0
2014.12.04 14:37:31 3: Can't open /dev/ttyACM0: No such file or directory
2014.12.04 14:37:31 1: Including ./FHEM/wetter.cfg
2014.12.04 14:37:32 1: Including ./FHEM/test.cfg
2014.12.04 14:37:34 1: Including ./FHEM/Anruferkennung.cfg
2014.12.04 14:37:35 1: Including ./FHEM/Testensteuuerung.cfg
2014.12.04 14:37:36 3: Opening TRX_0 device /dev/ttyUSB0
2014.12.04 14:37:36 3: Setting TRX_0 baudrate to 38400
2014.12.04 14:37:36 3: TRX_0 device opened
2014.12.04 14:37:37 1: TRX: Init OK
2014.12.04 14:37:37 1: TRX: Init status: '433.92MHz transceiver, firmware=231, protocols enabled: LaCrosse Hideki OREGON AC ARC X10 '
2014.12.04 14:37:37 1: Including ./log/fhem.save
2014.12.04 14:37:40 1: usb create starting
2014.12.04 14:37:41 1: usb create end
2014.12.04 14:37:41 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart fhem for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.12.04 14:37:41 0: Server started with 338 defined entities (version $Id: fhem.pl 3872 2013-09-07 11:58:33Z rudolfkoenig $, os linux, user boxusr99, pid 3887)
2014.12.04 14:40:12 1: usb create starting
2014.12.04 14:40:13 1: usb create end
2014.12.04 14:52:18 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.12.04 14:52:26 3: Setting TRX_0 baudrate to 38400
2014.12.04 14:52:26 1: /dev/ttyUSB0 reappeared (TRX_0)
2014.12.04 14:53:50 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.12.04 15:07:06 3: FS20 set Licht2_an on
2014.12.04 15:27:36 3: Setting TRX_0 baudrate to 38400
2014.12.04 15:27:36 1: /dev/ttyUSB0 reappeared (TRX_0)
2014.12.04 15:36:18 3: update get http://fhem.de/fhemupdate4/svn/controls_fhem.txt
2014.12.04 15:37:20 3: update get http://fhem.de/fhemupdate4/svn/controls_fhem.txt
2014.12.04 15:37:28 1: update Action required: please run 'notice view update-20130127-001'
2014.12.04 15:38:12 0: Server shutdown
2014.12.04 15:38:16 1: Including fhem.cfg
2014.12.04 15:38:17 3: telnetPort: port 7072 opened
2014.12.04 15:38:19 3: WEB: port 8083 opened
2014.12.04 15:38:19 3: WEBphone: port 8084 opened
2014.12.04 15:38:19 3: WEBtablet: port 8085 opened
2014.12.04 15:38:20 3: Opening FritzBox1 device 192.168.78.6:1012
2014.12.04 15:38:20 3: FritzBox1 device opened
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox1 found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox1 read 254 contacts from FritzBox phonebook
2014.12.04 15:38:20 3: Opening FritzBox device 192.168.78.1:1012
2014.12.04 15:38:20 3: FritzBox device opened
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox read 254 contacts from FritzBox phonebook
2014.12.04 15:38:20 3: Opening FritzBox2 device 192.168.78.2:1012
2014.12.04 15:38:20 3: FritzBox2 device opened
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox2 found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:38:20 2: FB_CALLMONITOR: FritzBox2 read 254 contacts from FritzBox phonebook
2014.12.04 15:38:21 3: Opening FritzBoxLS device 192.168.79.9:1012
2014.12.04 15:38:21 3: FritzBoxLS device opened
2014.12.04 15:38:21 2: FB_CALLMONITOR: FritzBoxLS found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:38:21 2: FB_CALLMONITOR: FritzBoxLS read 254 contacts from FritzBox phonebook
2014.12.04 15:38:21 3: Opening FritzBoxKS device 192.168.178.1:1012
2014.12.04 15:38:21 3: FritzBoxKS device opened
2014.12.04 15:38:21 2: FB_CALLMONITOR: FritzBoxKS found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:38:21 2: FB_CALLMONITOR: FritzBoxKS read 254 contacts from FritzBox phonebook
2014.12.04 15:38:21 3: Opening CUL_0 device /dev/ttyACM0
2014.12.04 15:38:22 3: Can't open /dev/ttyACM0: No such file or directory
2014.12.04 15:38:22 1: Including ./FHEM/wetter.cfg
2014.12.04 15:38:23 1: Including ./FHEM/test.cfg
2014.12.04 15:38:28 1: Including ./FHEM/Anruferkennung.cfg
2014.12.04 15:38:29 1: Including ./FHEM/Testensteuuerung.cfg
2014.12.04 15:38:29 3: Opening TRX_0 device /dev/ttyUSB0
2014.12.04 15:38:29 3: Setting TRX_0 baudrate to 38400
2014.12.04 15:38:29 3: TRX_0 device opened
2014.12.04 15:38:30 1: TRX: Init OK
2014.12.04 15:38:30 1: TRX: Init status: '433.92MHz transceiver, firmware=231, protocols enabled: LaCrosse Hideki OREGON AC ARC X10 '
2014.12.04 15:38:30 1: Including ./log/fhem.save
2014.12.04 15:38:31 1: usb create starting
2014.12.04 15:38:32 1: usb create end
2014.12.04 15:38:32 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart fhem for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.12.04 15:38:32 0: Server started with 338 defined entities (version $Id: fhem.pl 3872 2013-09-07 11:58:33Z rudolfkoenig $, os linux, user boxusr99, pid 5730)
2014.12.04 15:40:37 3: FS20 set LichtW34_an off
2014.12.04 15:40:37 3: LichtWM34AUS return value: <xml><exec>/fhem2ccu.exe</exec><sessionId></sessionId><httpUserAgent></httpUserAgent><Status>false</Status></xml>
2014.12.04 15:46:39 3: set CUL_0 raw is0F00FFFF0FFF
2014.12.04 15:46:54 1: Including fhem.cfg
2014.12.04 15:46:54 3: telnetPort: port 7072 opened
2014.12.04 15:46:54 3: WEB: port 8083 opened
2014.12.04 15:46:54 3: WEBphone: port 8084 opened
2014.12.04 15:46:54 3: WEBtablet: port 8085 opened
2014.12.04 15:46:54 3: Opening FritzBox1 device 192.168.78.6:1012
2014.12.04 15:46:54 3: FritzBox1 device opened
2014.12.04 15:46:54 2: FB_CALLMONITOR: FritzBox1 found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:46:54 2: FB_CALLMONITOR: FritzBox1 read 254 contacts from FritzBox phonebook
2014.12.04 15:46:54 3: Opening FritzBox device 192.168.78.1:1012
2014.12.04 15:46:54 3: FritzBox device opened
2014.12.04 15:46:54 2: FB_CALLMONITOR: FritzBox found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:46:55 2: FB_CALLMONITOR: FritzBox read 254 contacts from FritzBox phonebook
2014.12.04 15:46:55 3: Opening FritzBox2 device 192.168.78.2:1012
2014.12.04 15:46:55 3: FritzBox2 device opened
2014.12.04 15:46:55 2: FB_CALLMONITOR: FritzBox2 found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:46:55 2: FB_CALLMONITOR: FritzBox2 read 254 contacts from FritzBox phonebook
2014.12.04 15:46:55 3: Opening FritzBoxLS device 192.168.79.9:1012
2014.12.04 15:46:55 3: FritzBoxLS device opened
2014.12.04 15:46:55 2: FB_CALLMONITOR: FritzBoxLS found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:46:56 2: FB_CALLMONITOR: FritzBoxLS read 254 contacts from FritzBox phonebook
2014.12.04 15:46:56 3: Opening FritzBoxKS device 192.168.178.1:1012
2014.12.04 15:46:56 3: FritzBoxKS device opened
2014.12.04 15:46:56 2: FB_CALLMONITOR: FritzBoxKS found FritzBox phonebook /var/flash/phonebook
2014.12.04 15:46:56 2: FB_CALLMONITOR: FritzBoxKS read 254 contacts from FritzBox phonebook
2014.12.04 15:46:56 3: Opening CUL_0 device /dev/ttyACM0
2014.12.04 15:46:56 3: Can't open /dev/ttyACM0: No such file or directory
2014.12.04 15:46:56 1: Including ./FHEM/wetter.cfg
2014.12.04 15:46:57 1: Including ./FHEM/test.cfg
2014.12.04 15:47:00 1: Including ./FHEM/Anruferkennung.cfg
2014.12.04 15:47:00 1: Including ./FHEM/Testensteuuerung.cfg
2014.12.04 15:47:00 3: Opening TRX_0 device /dev/ttyUSB0
2014.12.04 15:47:00 3: Setting TRX_0 baudrate to 38400
2014.12.04 15:47:00 3: TRX_0 device opened
2014.12.04 15:47:01 1: TRX: Init OK
2014.12.04 15:47:01 1: TRX: Init status: '433.92MHz transceiver, firmware=231, protocols enabled: LaCrosse Hideki OREGON AC ARC X10 '
2014.12.04 15:47:01 1: Including ./log/fhem.save
2014.12.04 16:08:07 1: usb create starting
2014.12.04 16:08:08 1: usb create end


in der fhem.cfg wurde auch was angelgt, wobei ich mir nicht sicher bin, ob es nicht vom CUL Stick stammt:


define CUL_TX_55 CUL_TX 55
attr CUL_TX_55 room CUL_TX
define FileLog_CUL_TX_55 FileLog ./log/CUL_TX_55-%Y.log CUL_TX_55
attr FileLog_CUL_TX_55 logtype temp4hum4:Temp/Hum,text
attr FileLog_CUL_TX_55 room CUL_TX
define SVG_CUL_TX_55 SVG FileLog_CUL_TX_55:temp4hum4:CURRENT
attr SVG_CUL_TX_55 label "CUL_TX_55 Min $data{min1}, Max $data{max1}, Last $data{currval1}"
attr SVG_CUL_TX_55 room Plots
define TRX_0 TRX /dev/ttyUSB0@38400


Der CUL Stick hat nämlich von mir in fhem.cfg folgenden Eintrag erhalten:

define CUL_0 CUL /dev/ttyACM0@9600 1034


Es sind keine neues "rooms" Räume angelegt. Ich finde das Ding nicht.

Wenn ich in Everything schaue, dann finde ich folgenden Eintrag:


TRX
TRX_0    Initialized


Aber wenn ich den Befehl

set TRX_0 raw is0F00FFFF0FFF
eingebe, tut sich bei meiner Lampe nichts. Beim CUL 433 (den ich testweise hatte) schaltete sich die Steckdose immer ein.

Was mache ich falsch? Was muss ich ändern? Ich habe versucht, das so zu installieren, wie im wiki beschrieben.

Ich bitte um Hilfe.

Danke.

liebe Grüße aus Oberfranken.

Kai 
SPS, Arduino, Controllino, Sensortechnik, Elektronik

Doggiebert

vom Logfile sieht's wunderbar aus, der TRX sagt Init OK und liest auch aus, welche Protokolle aktiviert sind. Wie kommst du drauf, dass das TRX device ein "raw" Kommando kennt? Das device ist nur das Rohdevice, das von den Protokolldevices (z.B. TRX_LIGHT) angesprochen wird.

Ohne das Lampendingens zu kennen: mach Dich mal schlau, was das Teil für ein Protokoll spricht, und probiers mal über den RFXmngr ...
SW: FHEM 5.5, Raspian, XBMC, Testinstallation auf Win7
HW: Raspi B, 32GB SD, enocean Pi, RFXTRX433E, BSC - MwC-32, Onkyo TX-NR709, Samsung UE55F8090, Jung LS-Eno, permundo SmartPlug, KDG-FB 6490cable (ohne FHEM)

kblc

Danke für die schnelle Antwort.

Das hat mir geholfen.
SPS, Arduino, Controllino, Sensortechnik, Elektronik