Autor Thema: Keine Initialisierung von Enocean Pi at Raspberry Pi  (Gelesen 486 mal)

Offline pelle2011

  • Newbie
  • Beiträge: 1
Hi Leute,

ich wollte heute mal die Enocean Steuerung mit einem Raspberry Pi3 und Enocean Pi anfangen.

der Raspberry ist mit der aktuellen Software aufgesetzt und der Serial Port entsprechend der Anleitung https://wiki.fhem.de/wiki/Raspberry_Pi_3:_GPIO-Port_Module_und_Bluetooth umgebogen.

Der Enocean Pi wird weder vom System noch von FHEM erkannt:

Bootlog:
[ESC[32m  OK  ESC[0m] Started Load/Save Random Seed.
[ESC[32m  OK  ESC[0m] Created slice system-systemd\x2drfkill.slice.
         Starting Load/Save RF Kill Switch Status of rfkill0...
[ESC[32m  OK  ESC[0m] Started Show Plymouth Boot Screen.
[ESC[32m  OK  ESC[0m] Reached target Paths.
[ESC[32m  OK  ESC[0m] Started Load/Save RF Kill Switch Status of rfkill0.
[ESC[32m  OK  ESC[0m] Created slice system-ifup.slice.
[    2.907789] systemd-fsck[244]: fsck.fat 3.0.27 (2014-11-12)
[    2.908761] systemd-fsck[244]: /dev/mmcblk0p1: 137 files, 42778/82644 clusters
[ESC[32m  OK  ESC[0m] Started File System Check on /dev/disk/by-partuuid/aad276d5-01.
         Mounting /boot...
[ESC[32m  OK  ESC[0m] Mounted /boot.
[ESC[32m  OK  ESC[0m] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Tell Plymouth To Write Out Runtime Data...
[ESC[32m  OK  ESC[0m] Reached target Remote File Systems.
         Starting Trigger Flushing of Journal to Persistent Storage...
         Starting LSB: Prepare console...
         Starting LSB: Switch to ondemand cpu governor (unless ... is pressed)...
         Starting LSB: Raise network interfaces....
[ESC[32m  OK  ESC[0m] Started Tell Plymouth To Write Out Runtime Data.
[ESC[32m  OK  ESC[0m] Started Trigger Flushing of Journal to Persistent Storage.
[ESC[32m  OK  ESC[0m] Started Create Volatile Files and Directories.
[ESC[32m  OK  ESC[0m] Started LSB: Switch to ondemand cpu governor (unless s...ey is pressed).
         Starting Update UTMP about System Boot/Shutdown...
[ESC[32m  OK  ESC[0m] Started Update UTMP about System Boot/Shutdown.
[ESC[32m  OK  ESC[0m] Started LSB: Prepare console.
         Starting LSB: Set console font and keymap...
[ESC[32m  OK  ESC[0m] Started LSB: Set console font and keymap.
[ESC[32m  OK  ESC[0m] Started LSB: Raise network interfaces..
         Starting ifup for wlan0...
[ESC[32m  OK  ESC[0m] Started ifup for wlan0.
[ESC[32m  OK  ESC[0m] Reached target System Initialization.
[ESC[32m  OK  ESC[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ESC[32m  OK  ESC[0m] Listening on D-Bus System Message Bus Socket.
[ESC[32m  OK  ESC[0m] Reached target Sockets.
[ESC[32m  OK  ESC[0m] Reached target Timers.
         Starting Restore Sound Card State...
[ESC[32m  OK  ESC[0m] Reached target Basic System.
         Starting Regular background program processing daemon...
[ESC[32m  OK  ESC[0m] Started Regular background program processing daemon.
         Starting Configure Bluetooth Modems connected by UART...
         Starting dhcpcd on all interfaces...
         Starting Login Service...
         Starting LSB: Autogenerate and use a swap file...
         Starting LSB: triggerhappy hotkey daemon...
         Starting LSB: FHEM server...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting D-Bus System Message Bus...

FHEM-Log:
2017.05.19 09:25:04 0: Server shutdown
2017.05.19 09:25:16 1: Including fhem.cfg
2017.05.19 09:25:17 3: WEB: port 8083 opened
2017.05.19 09:25:17 3: WEBphone: port 8084 opened
2017.05.19 09:25:17 3: WEBtablet: port 8085 opened
2017.05.19 09:25:17 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2017.05.19 09:25:17 1: Including ./log/fhem.save
2017.05.19 09:25:17 1: usb create starting
2017.05.19 09:25:17 3: Probing CUL device /dev/ttyAMA0
2017.05.19 09:25:17 3: Probing TCM_ESP3 device /dev/ttyAMA0
2017.05.19 09:25:17 3: Probing FRM device /dev/ttyAMA0
2017.05.19 09:25:29 1: usb create end
2017.05.19 09:25:29 0: Featurelevel: 5.8
2017.05.19 09:25:29 0: Server started with 11 defined entities (fhem.pl:13447/2017-02-19 perl:5.020002 os:linux user:fhem pid:840)
2017.05.19 09:37:49 1: Including fhem.cfg
2017.05.19 09:37:49 3: WEB: port 8083 opened
2017.05.19 09:37:49 3: WEBphone: port 8084 opened
2017.05.19 09:37:49 3: WEBtablet: port 8085 opened
2017.05.19 09:37:49 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2017.05.19 09:37:49 3: Opening TCM310_0 device /dev/ttyAMA0
2017.05.19 09:37:49 3: Setting TCM310_0 serial parameters to 57600,8,N,1
2017.05.19 09:37:49 3: TCM310_0 device opened
2017.05.19 09:37:49 1: Including ./log/fhem.save
2017.05.19 09:37:49 3: TCM set TCM310_0 reset
2017.05.19 09:37:51 2: TCM TCM310_0 Timeout reading response for set reset
2017.05.19 09:37:51 2: TCM TCM310_0 Attribute sendInterval 0 initialized
2017.05.19 09:37:52 3: TCM get TCM310_0 baseID
2017.05.19 09:37:54 2: TCM TCM310_0 Timeout reading response for get baseID
2017.05.19 09:37:54 3: TCM get TCM310_0 version
2017.05.19 09:37:56 2: TCM TCM310_0 Timeout reading response for get version
2017.05.19 09:37:56 3: TCM set TCM310_0 mode 00
2017.05.19 09:37:58 2: TCM TCM310_0 Timeout reading response for set mode
2017.05.19 09:37:58 3: TCM set TCM310_0 maturity 01
2017.05.19 09:38:00 2: TCM TCM310_0 Timeout reading response for set maturity
2017.05.19 09:38:00 3: TCM set TCM310_0 repeater 0000
2017.05.19 09:38:02 2: TCM TCM310_0 Timeout reading response for set repeater
2017.05.19 09:38:02 3: TCM set TCM310_0 smartAckMailboxMax 0
2017.05.19 09:38:04 2: TCM TCM310_0 Timeout reading response for set smartAckMailboxMax
2017.05.19 09:38:04 2: TCM TCM310_0 initialized
2017.05.19 09:38:09 3: FHEMWEB WEB CSRF error: fhem_961570092883950 ne fhem_67421220599561.1. For detals see the csrfToken FHEMWEB attribute
2017.05.19 09:38:12 3: FHEMWEB WEB CSRF error: fhem_961570092883950 ne fhem_67421220599561.1. For detals see the csrfToken FHEMWEB attribute
2017.05.19 09:38:15 3: FHEMWEB WEB CSRF error: fhem_961570092883950 ne fhem_67421220599561.1. For detals see the csrfToken FHEMWEB attribute
2017.05.19 09:38:38 0: Server shutdown
2017.05.19 09:38:50 1: Including fhem.cfg
2017.05.19 09:38:51 3: WEB: port 8083 opened
2017.05.19 09:38:51 3: WEBphone: port 8084 opened
2017.05.19 09:38:51 3: WEBtablet: port 8085 opened
2017.05.19 09:38:51 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2017.05.19 09:38:51 3: Opening TCM310_0 device /dev/ttyAMA0
2017.05.19 09:38:51 3: Setting TCM310_0 serial parameters to 57600,8,N,1
2017.05.19 09:38:51 3: TCM310_0 device opened
2017.05.19 09:38:51 1: Including ./log/fhem.save
2017.05.19 09:38:51 3: TCM set TCM310_0 reset
2017.05.19 09:38:53 2: TCM TCM310_0 Timeout reading response for set reset
2017.05.19 09:38:53 2: TCM TCM310_0 Attribute sendInterval 0 initialized
2017.05.19 09:38:53 3: TCM get TCM310_0 baseID
2017.05.19 09:39:02 2: TCM TCM310_0 Timeout reading response for get baseID
2017.05.19 09:39:02 3: TCM get TCM310_0 version
2017.05.19 09:39:04 2: TCM TCM310_0 Timeout reading response for get version
2017.05.19 09:39:04 3: TCM set TCM310_0 smartAckMailboxMax 0
2017.05.19 09:39:06 2: TCM TCM310_0 Timeout reading response for set smartAckMailboxMax
2017.05.19 09:39:06 3: TCM set TCM310_0 maturity 01
2017.05.19 09:39:08 2: TCM TCM310_0 Timeout reading response for set maturity
2017.05.19 09:39:08 3: TCM set TCM310_0 repeater 0000
2017.05.19 09:39:10 2: TCM TCM310_0 Timeout reading response for set repeater
2017.05.19 09:39:10 3: TCM set TCM310_0 mode 00
2017.05.19 09:39:12 2: TCM TCM310_0 Timeout reading response for set mode
2017.05.19 09:39:12 2: TCM TCM310_0 initialized
2017.05.19 09:39:12 1: usb create starting
2017.05.19 09:39:12 1: usb create end
2017.05.19 09:39:12 0: Featurelevel: 5.8
2017.05.19 09:39:12 0: Server started with 12 defined entities (fhem.pl:13447/2017-02-19 perl:5.020002 os:linux user:fhem pid:846)
2017.05.19 09:39:58 3: FHEMWEB WEB CSRF error: fhem_961570092883950 ne fhem_584470464599172. For detals see the csrfToken FHEMWEB attribute

FHEM-config:
attr global userattr cmdIcon devStateIcon devStateStyle icon sortby webCmd widgetOverride
attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global backup_before_update 1
attr global verbose 3

# define telnetPort telnet 7072 global

define WEB FHEMWEB 8083 global
attr WEB longpoll 1
attr WEB stylesheetPrefix dark
define allowed_WEB allowed
attr allowed_WEB basicAuth { "user:pass"}
attr allowed_WEB validFor WEB

define WEBphone FHEMWEB 8084 global
attr WEBphone longpoll 1
attr WEBphone stylesheetPrefix dark
define allowed_WEBphone allowed
attr allowed_WEBphone basicAuth { "user:pass"}
attr allowed_WEBphone validFor WEBphone


define WEBtablet FHEMWEB 8085 global
attr WEBtablet longpoll 1
attr WEBtablet stylesheetPrefix dark
define allowed_WEBtablet allowed
attr allowed_WEBtablet basicAuth { "user:pass"}
attr allowed_WEBtablet validFor WEBtablet


# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog

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

define eventTypes eventTypes ./log/eventTypes.txt

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create

#added by myself
define TCM310_0 TCM 310 /dev/ttyAMA0@57600


Offline mbr89

  • Newbie
  • Beiträge: 1
Antw:Keine Initialisierung von Enocean Pi at Raspberry Pi
« Antwort #1 am: 18 Juni 2017, 16:19:36 »
Hi,

glaub ich hab das gleiche Problem

2017.06.18 16:12:10 1: Including fhem.cfg
2017.06.18 16:12:11 3: telnetPort: port 7072 opened
2017.06.18 16:12:11 3: WEB: port 8083 opened
2017.06.18 16:12:11 3: WEBphone: port 8084 opened
2017.06.18 16:12:11 3: WEBtablet: port 8085 opened
2017.06.18 16:12:11 2: eventTypes: loaded 2 events from ./log/eventTypes.txt
2017.06.18 16:12:11 3: Opening TCM310_0 device /dev/ttyAMA0
2017.06.18 16:12:11 3: Setting TCM310_0 serial parameters to 57600,8,N,1
2017.06.18 16:12:11 3: TCM310_0 device opened
2017.06.18 16:12:11 1: Including ./log/fhem.save
2017.06.18 16:12:11 3: TCM set TCM310_0 reset
2017.06.18 16:12:13 2: TCM TCM310_0 Timeout reading response for set reset
2017.06.18 16:12:14 3: TCM get TCM310_0 baseID
2017.06.18 16:12:16 2: TCM TCM310_0 Timeout reading response for get baseID
2017.06.18 16:12:16 3: TCM get TCM310_0 version
2017.06.18 16:12:18 2: TCM TCM310_0 Timeout reading response for get version
2017.06.18 16:12:18 3: TCM set TCM310_0 mode 00
2017.06.18 16:12:20 2: TCM TCM310_0 Timeout reading response for set mode
2017.06.18 16:12:20 3: TCM set TCM310_0 maturity 01
2017.06.18 16:12:22 2: TCM TCM310_0 Timeout reading response for set maturity
2017.06.18 16:12:22 3: TCM set TCM310_0 repeater 0000
2017.06.18 16:12:24 2: TCM TCM310_0 Timeout reading response for set repeater
2017.06.18 16:12:24 3: TCM set TCM310_0 smartAckMailboxMax 0
2017.06.18 16:12:27 2: TCM TCM310_0 Timeout reading response for set smartAckMailboxMax
2017.06.18 16:12:27 2: TCM TCM310_0 initialized
2017.06.18 16:12:27 0: Server shutdown
2017.06.18 16:13:06 1: Including fhem.cfg
2017.06.18 16:13:07 3: telnetPort: port 7072 opened
2017.06.18 16:13:09 3: WEB: port 8083 opened
2017.06.18 16:13:09 3: WEBphone: port 8084 opened
2017.06.18 16:13:09 3: WEBtablet: port 8085 opened
2017.06.18 16:13:09 2: eventTypes: loaded 2 events from ./log/eventTypes.txt
2017.06.18 16:13:10 3: Opening TCM310_0 device /dev/ttyAMA0
2017.06.18 16:13:10 3: Setting TCM310_0 serial parameters to 57600,8,N,1
2017.06.18 16:13:10 3: TCM310_0 device opened
2017.06.18 16:13:10 1: Including ./log/fhem.save
2017.06.18 16:13:10 3: TCM set TCM310_0 reset
2017.06.18 16:13:13 2: TCM TCM310_0 Timeout reading response for set reset
2017.06.18 16:13:13 3: TCM get TCM310_0 baseID
2017.06.18 16:13:15 2: TCM TCM310_0 Timeout reading response for get baseID
2017.06.18 16:13:15 3: TCM get TCM310_0 version
2017.06.18 16:13:17 2: TCM TCM310_0 Timeout reading response for get version
2017.06.18 16:13:17 3: TCM set TCM310_0 maturity 01
2017.06.18 16:13:19 2: TCM TCM310_0 Timeout reading response for set maturity
2017.06.18 16:13:19 3: TCM set TCM310_0 smartAckMailboxMax 0
2017.06.18 16:13:22 2: TCM TCM310_0 Timeout reading response for set smartAckMailboxMax
2017.06.18 16:13:22 3: TCM set TCM310_0 mode 00
2017.06.18 16:13:24 2: TCM TCM310_0 Timeout reading response for set mode
2017.06.18 16:13:24 3: TCM set TCM310_0 repeater 0000
2017.06.18 16:13:26 2: TCM TCM310_0 Timeout reading response for set repeater
2017.06.18 16:13:26 2: TCM TCM310_0 initialized
2017.06.18 16:13:26 1: usb create starting
2017.06.18 16:13:28 1: usb create end
2017.06.18 16:13:28 2: SecurityCheck:  WEB,WEBphone,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.
2017.06.18 16:13:28 0: Featurelevel: 5.8
2017.06.18 16:13:28 0: Server started with 10 defined entities (fhem.pl:14348/2017-05-22 perl:5.020002 os:linux user:fhem pid:853)
« Letzte Änderung: 18 Juni 2017, 16:29:25 von mbr89 »

Offline Otto123

  • Hero Member
  • *****
  • Beiträge: 6248
    • Otto's Technik Blog
Antw:Keine Initialisierung von Enocean Pi at Raspberry Pi
« Antwort #2 am: 18 Juni 2017, 16:45:05 »
Hi,

versuch mal bitte meinen Hinweis von hier -> https://forum.fhem.de/index.php/topic,73295.msg649431.html#msg649431

Ich glaube die serielle Schnittstelle ttyAMA0 ist nicht "frei", das Modul wird nicht richtig erkannt.

Ich habe auch von diesem Modul keine Ahnung, nur von der Schnittstelle.

Gruß Otto
Viele Grüße aus Leipzig
RaspberryPi,HMLAN,HMUART,Homematic,Fritz!Box 7490,Sonos,ET9200,Arduino nano,ESP8266

 

decade-submarginal