Einladung zum Beta-Test: "FHEMlazy" zur einfacheren Alexa-Integration

thoweiss · 10 August 2019, 13:36:42

Hallo zusammen,

ich habe es jetzt hinbekommen.

Aber scheinbar reicht es nicht aus das die setlist korrekt gesetzt ist.

Bei mir musste ich zusätzlich das homebridgemapping setzen.

Nur mit set-list steht im Log:

Code Auswählen

[2019-8-10 13:22:16] [FHEM] powerpi.wz.wandlampe is switch
[2019-8-10 13:22:16] [FHEM] powerpi.wz.wandlampe has

Mit aktiviertem homebridgemapping sieht das so aus:

Code Auswählen

[2019-8-10 13:25:08] [FHEM] powerpi.wz.wandlampe is switch
[2019-8-10 13:25:08] [FHEM] powerpi.wz.wandlampe has
[2019-8-10 13:25:08] [FHEM]   On [state;on,off]
  2019-08-10 13:25:08 caching: powerpi.wz.wandlampe-state:

Hier mein aktueller Dummy mit dem alexa funktioniert:

Code Auswählen


Internals:
   FUUID      5c5e94b4-f33f-bcbf-5d99-a244a1134bc78536
   NAME       powerpi.wz.wandlampe
   NR         174
   STATE      off
   TYPE       dummy
   READINGS:
     2019-08-10 13:30:31   state           off
Attributes:
   alexaName  Lampe Sofa
   alias      Wandleuchten Sofa
   genericDeviceType switch
   group      Beleuchtung
   homebridgeMapping On=state,cmdOn=on,cmdOff=off,valueOn=on,valueOff=off
   room       Wohnzimmer
   setList    state:on,off
   userattr   powerpi.wz.stehlampe powerpi.wz.stehlampe_map structexclude
   webCmd     on:off

Also muss die setlist UND das homebridgemapping gesetzt sein damit das mit den Dummys funktioniert.

Danke an alle für die tipss und Hilfe,

Gruß Thorsten

TomLee · 10 August 2019, 14:45:09

Zitat von: thoweiss am 10 August 2019, 13:36:42
Bei mir musste ich zusätzlich das homebridgemapping setzen.

Du musstest homebridgemapping setzen weil du deine setList immer noch nicht korrigiert hast, hab doch die commandref schon zitiert !?
Eine korrekte setlist reicht aus, das state: kannst ja stehen lassen, aber das Komma muss weg.

thoweiss · 10 August 2019, 14:58:59

OK sorry das habe ich überlesen.

Ich dachte das da ein Komma zwischen muss.

Gruß Thorsten

Floh22964 · 12 August 2019, 08:42:47

Hallo und guten Morgen

Mein Alexa-Fhem funktioniert nicht mehr, aber von vorne

Da ich Fhem auf einer super langsamen SD Karte installiert hatte, habe ich gestern eine Copy erstellt und genau seitdem geht Alexa und leider auch deconz nicht mehr.
Ich habe für Alexa alles mögliche kontrolliert was hier so schon besprochen wurde.

Code Auswählen

pi@FhemServer:/opt/fhem $ node -v
v8.11.3

Habe ich ja auch nichts geändert

Code Auswählen

pi@FhemServer:/opt/fhem $ ps -ef | egrep '(alexa|ssh)'
root       492     1  0 Aug11 ?        00:00:00 /usr/sbin/sshd -D
root     10931   492  0 07:58 ?        00:00:00 sshd: pi [priv]
pi       10958 10931  0 07:58 ?        00:00:00 sshd: pi@pts/0
pi       11851 10961  0 08:11 pts/0    00:00:00 grep -E --color=auto (alexa|ssh)

sollte so ja richtig sein

Code Auswählen

pi@FhemServer:/opt/fhem $ sudo ls -l /opt/fhem/.ssh
insgesamt 12
-rw------- 1 fhem dialout 1823 Aug  6 07:59 id_rsa
-rw-r--r-- 1 fhem dialout  397 Aug  6 07:59 id_rsa.pub
-rw-r--r-- 1 fhem dialout  884 Aug  6 07:59 known_hosts

Code Auswählen

pi@FhemServer:/opt/fhem $ sudo -u fhem ssh -p 58824 fhem-va.fhem.de status
Unregistered.
Your SSH key ist not registered.

Ich habe versucht Alexa-fhem zu löschen oder neu zu installieren und da kam dann diese Meldung

Code Auswählen

pi@FhemServer:~ $ sudo npm install -g alexa-fhem
Speicherzugriffsfehler

Leider schreibt Alexa nichts in das Log File
Im Fhem Log File steht das

Code Auswählen

2019.08.12 08:06:02 3: alexa: starting
2019.08.12 08:06:02 3: alexa: using logfile: ./log/alexa-2019-08-12.log
2019.08.12 08:06:03 3: alexa: read: end of file reached while sysread
2019.08.12 08:06:03 3: alexa: stopped

Ich weis nicht weiter und hoffe das einer von Euch noch eine Idee hat.

Auf der anderen SD Karte ist das selbe Problem zu Wechseln hatte ich bereits versucht.

Kay

CatWeazle · 08 September 2019, 21:07:22

Hi Leutz,

da bin ich doch heute erst über Alexa FHEMlazy gestolpert und auch nur weil die HA Bridge mich mal wieder im Stich gelassen hat

Ich hätte da mal ein Problem .....

Mein Vorgehen:

1. Raspberry update und upgrade
2. sudo npm install -g alexa-fhem
3. FHEM update
4. nach Wiki: "FHEM Connector für Amazon Alexa" vorgegangen
5. define alexa alexa

sieht immer noch gut aus .... ..... aber !
es wurde kein "alexaFHEM.skillRegKey" angelegt ?

Dann lese ich:
Falls noch kein SSH-Key für den Benutzer, unter dem FHEM läuft, existiert, wird einer generiert.

Hmmm, das war aber nicht passiert also lege ich selber einen an.
define telnetPort telnet 7072 global
dann im Telnet-Modul per attr ein Passwort vergeben

gespeichert neu gestartet , hat nicht geholfen, weiter kein "alexaFHEM.skillRegKey"

Wo ist der Fehler ?

EDIT:
Da war ich ein wenig neben der Frequenz SSH ist nicht Telnet

*

amenomade · 08 September 2019, 21:13:14

Was sagt

Code Auswählen

ls -la /opt/fhem/.ssh
und was sagt die Log?

CatWeazle · 08 September 2019, 21:24:25

Hi,

pi@raspberrypi:~ $ sudo ls -la /opt/fhem/.ssh
insgesamt 20
drwx------ 2 fhem dialout 4096 Sep 8 20:07 .
drwxr-xr-x 12 fhem dialout 4096 Sep 8 21:12 ..
-rw------- 1 fhem dialout 1679 Sep 8 20:07 id_rsa
-rw-r--r-- 1 fhem dialout 398 Sep 8 20:07 id_rsa.pub
-rw-r--r-- 1 fhem dialout 884 Sep 8 20:07 known_hosts
pi@raspberrypi:~ $

Die Log hat einiges gesagt ....

Code Auswählen

jump to the end

[2019-9-8 20:07:23] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-8 20:07:23] os.homedir()=/opt/fhem
[2019-9-8 20:07:23] this is alexa-fhem 0.5.28
[2019-9-8 20:07:23] connecting to FHEM ...
[2019-9-8 20:07:24] [FHEM] trying longpoll to listen for fhem events
[2019-9-8 20:07:24] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1567966044780
[2019-9-8 20:07:24] [FHEM] got csrfToken: 
[2019-9-8 20:07:24] [FHEM] Checking devices and attributes...
[2019-9-8 20:07:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-9-8 20:07:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-9-8 20:07:24] [FHEM] waiting for events ...
[2019-9-8 20:07:24] [FHEM] Fetching FHEM devices...
[2019-9-8 20:07:24] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-9-8 20:07:24] [FHEM] alexa device is alexa
[2019-9-8 20:07:25] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:25] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:25] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:25] Server listening on: http://127.0.0.1:39211 for proxy connections
[2019-9-8 20:07:25] *** SSH: checking proxy configuration
[2019-9-8 20:07:25] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-9-8 20:07:25] sshautoconf: env={"OLDPWD":"/","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","LANG":"de_DE.UTF-8","PWD":"/opt/fhem"}
[2019-9-8 20:07:25] sshautoconf: Creating directory /opt/fhem/.alexa
[2019-9-8 20:07:25] Passed config: {"connections":[{"port":"8083","filter":"alexaName=..*","server":"127.0.0.1","uid":999,"name":"FHEM","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":39211}}
[2019-9-8 20:07:25] sshautoconf: No SSH public key found, we have to generate one.
[2019-9-8 20:07:26] sshautoconf: Generating public/private rsa key pair.
Created directory '/opt/fhem/.ssh'.
Your identification has been saved in /opt/fhem/.ssh/id_rsa.
Your public key has been saved in /opt/fhem/.ssh/id_rsa.pub.
The key fingerprint is:
5c:af:f6:60:8a:ec:56:4f:5c:af:f6:60:8a:ec:56:4f fhem@raspberrypi
The key's randomart image is:
+---[RSA 2048]----+
|        E        |
|         .       |
|        . o      |
|       o + .     |
|      . S.  .    |
|       oo +.     |
|      .oo==      |
|     .o* +.o     |
|     +*.o   .    |
+-----------------+

[2019-9-8 20:07:27] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:27] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%20addToAttrList(%20%22homebridgeMapping%3AtextField-long%22%20)%20%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:27] [FHEM] homebridgeMapping attribute created.
[2019-9-8 20:07:27] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BaddToAttrList(%20%22genericDeviceType%3Asecurity%2Cignore%2Cswitch%2Coutlet%2Clight%2Cblind%2Cthermometer%2Cthermostat%2Ccontact%2Cgarage%2Cwindow%2Clock%2Cscene%22%20)%20%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-8 20:07:27] [FHEM] got: 0 results
[2019-9-8 20:07:27] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-9-8 20:07:27] 39_alexa.pm is new version: true
[2019-9-8 20:07:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bset%20alexa%20proxyToken%205DA5E545D11364AC%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:28] [FHEM] genericDeviceType attribute was not known. please restart.
[2019-9-8 20:07:48] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-8 20:07:48] os.homedir()=/opt/fhem
[2019-9-8 20:07:48] this is alexa-fhem 0.5.28
[2019-9-8 20:07:48] connecting to FHEM ...
[2019-9-8 20:07:49] [FHEM] trying longpoll to listen for fhem events
[2019-9-8 20:07:49] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1567966069337
[2019-9-8 20:07:49] [FHEM] got csrfToken: 
[2019-9-8 20:07:49] [FHEM] Checking devices and attributes...
[2019-9-8 20:07:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-9-8 20:07:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-9-8 20:07:49] [FHEM] waiting for events ...
[2019-9-8 20:07:49] [FHEM] Fetching FHEM devices...
[2019-9-8 20:07:49] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-9-8 20:07:49] [FHEM] alexa device is alexa
[2019-9-8 20:07:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:49] Server listening on: http://127.0.0.1:42385 for proxy connections
[2019-9-8 20:07:49] *** SSH: checking proxy configuration
[2019-9-8 20:07:49] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-9-8 20:07:49] Passed config: {"connections":[{"port":"8083","filter":"alexaName=..*","server":"127.0.0.1","uid":999,"name":"FHEM","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":42385}}
[2019-9-8 20:07:49] sshautoconf: SSH key seems to exist
[2019-9-8 20:07:50] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-9-8 20:07:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-8 20:07:50] [FHEM] got: 0 results
[2019-9-8 20:07:50] BearerToken '...364AC' read from alexa
[2019-9-8 20:07:50] 39_alexa.pm is new version: true
[2019-9-8 20:07:50] sshautoconf: completed successfully
[2019-9-8 20:07:50] *** SSH: proxy configuration set up done
[2019-9-8 20:07:50] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-9-8 20:07:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:50] Starting SSH with -R 1234:127.0.0.1:42385 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-9-8 20:07:50] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-9-8 20:07:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:07:50] *** SSH: proxy connection established
[2019-9-8 20:07:50] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated.  
[2019-9-8 20:20:29] Got SIGTERM, shutting down alexa-fhem...
[2019-9-8 20:20:29] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-9-8 20:20:29] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:29] Stopping SSH ...
[2019-9-8 20:20:29] Reading alexaFHEM.ProxyConnection set to stopped
[2019-9-8 20:20:29] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:29] *** SSH: exited with 143
[2019-9-8 20:20:49] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-8 20:20:49] os.homedir()=/opt/fhem
[2019-9-8 20:20:49] this is alexa-fhem 0.5.28
[2019-9-8 20:20:49] connecting to FHEM ...
[2019-9-8 20:20:50] [FHEM] trying longpoll to listen for fhem events
[2019-9-8 20:20:50] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1567966850368
[2019-9-8 20:20:57] [FHEM] got csrfToken: 
[2019-9-8 20:20:57] [FHEM] Checking devices and attributes...
[2019-9-8 20:20:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-9-8 20:20:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-9-8 20:20:57] [FHEM] waiting for events ...
[2019-9-8 20:20:57] [FHEM] Fetching FHEM devices...
[2019-9-8 20:20:57] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-9-8 20:20:57] [FHEM] alexa device is alexa
[2019-9-8 20:20:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:57] Server listening on: http://127.0.0.1:44161 for proxy connections
[2019-9-8 20:20:57] *** SSH: checking proxy configuration
[2019-9-8 20:20:57] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-9-8 20:20:57] Passed config: {"connections":[{"port":"8083","filter":"alexaName=..*","server":"127.0.0.1","uid":999,"name":"FHEM","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":44161}}
[2019-9-8 20:20:57] sshautoconf: SSH key seems to exist
[2019-9-8 20:20:58] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-9-8 20:20:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-8 20:20:58] [FHEM] got: 0 results
[2019-9-8 20:20:58] 39_alexa.pm is new version: true
[2019-9-8 20:20:58] sshautoconf: completed successfully
[2019-9-8 20:20:58] *** SSH: proxy configuration set up done
[2019-9-8 20:20:58] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-9-8 20:20:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:58] Starting SSH with -R 1234:127.0.0.1:44161 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-9-8 20:20:58] BearerToken '...364AC' read from alexa
[2019-9-8 20:20:59] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-9-8 20:20:59] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:20:59] *** SSH: proxy connection established
[2019-9-8 20:20:59] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated.  
[2019-9-8 20:46:15] Got SIGTERM, shutting down alexa-fhem...
[2019-9-8 20:46:15] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-9-8 20:46:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:15] Stopping SSH ...
[2019-9-8 20:46:15] Reading alexaFHEM.ProxyConnection set to stopped
[2019-9-8 20:46:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:15] *** SSH: exited with 143
[2019-9-8 20:46:37] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-8 20:46:37] os.homedir()=/opt/fhem
[2019-9-8 20:46:37] this is alexa-fhem 0.5.28
[2019-9-8 20:46:37] connecting to FHEM ...
[2019-9-8 20:46:38] [FHEM] trying longpoll to listen for fhem events
[2019-9-8 20:46:38] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1567968398034
[2019-9-8 20:46:46] [FHEM] got csrfToken: 
[2019-9-8 20:46:46] [FHEM] Checking devices and attributes...
[2019-9-8 20:46:46] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-9-8 20:46:46] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-9-8 20:46:46] [FHEM] waiting for events ...
[2019-9-8 20:46:46] [FHEM] Fetching FHEM devices...
[2019-9-8 20:46:46] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-9-8 20:46:46] [FHEM] alexa device is alexa
[2019-9-8 20:46:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:47] Server listening on: http://127.0.0.1:43983 for proxy connections
[2019-9-8 20:46:47] *** SSH: checking proxy configuration
[2019-9-8 20:46:47] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-9-8 20:46:47] Passed config: {"connections":[{"port":"8083","filter":"alexaName=..*","server":"127.0.0.1","uid":999,"name":"FHEM","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":43983}}
[2019-9-8 20:46:47] sshautoconf: SSH key seems to exist
[2019-9-8 20:46:47] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-9-8 20:46:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-8 20:46:47] [FHEM] got: 0 results
[2019-9-8 20:46:47] BearerToken '...364AC' read from alexa
[2019-9-8 20:46:47] 39_alexa.pm is new version: true
[2019-9-8 20:46:47] sshautoconf: completed successfully
[2019-9-8 20:46:47] *** SSH: proxy configuration set up done
[2019-9-8 20:46:47] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-9-8 20:46:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:47] Starting SSH with -R 1234:127.0.0.1:43983 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-9-8 20:46:49] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-9-8 20:46:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 20:46:49] *** SSH: proxy connection established
[2019-9-8 20:46:49] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated.  
[2019-9-8 21:11:02] reloading http://127.0.0.1:8083/fhem
[2019-9-8 21:11:02] [FHEM] Fetching FHEM devices...
[2019-9-8 21:11:02] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2019-9-8 21:11:02] [FHEM] got: 0 results
[2019-9-8 21:11:33] reloading http://127.0.0.1:8083/fhem
[2019-9-8 21:11:33] [FHEM] Fetching FHEM devices...
[2019-9-8 21:11:33] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2019-9-8 21:11:33] [FHEM] got: 0 results
[2019-9-8 21:20:44] Got SIGTERM, shutting down alexa-fhem...
[2019-9-8 21:20:44] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-9-8 21:20:44] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:44] Stopping SSH ...
[2019-9-8 21:20:44] Reading alexaFHEM.ProxyConnection set to stopped
[2019-9-8 21:20:44] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:44] *** SSH: exited with 143
[2019-9-8 21:20:47] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-8 21:20:47] os.homedir()=/opt/fhem
[2019-9-8 21:20:47] this is alexa-fhem 0.5.28
[2019-9-8 21:20:47] connecting to FHEM ...
[2019-9-8 21:20:47] [FHEM] trying longpoll to listen for fhem events
[2019-9-8 21:20:47] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1567970447883
[2019-9-8 21:20:47] [FHEM] got csrfToken: 
[2019-9-8 21:20:47] [FHEM] Checking devices and attributes...
[2019-9-8 21:20:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-9-8 21:20:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-9-8 21:20:47] [FHEM] waiting for events ...
[2019-9-8 21:20:47] [FHEM] Fetching FHEM devices...
[2019-9-8 21:20:47] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-9-8 21:20:48] [FHEM] alexa device is alexa
[2019-9-8 21:20:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:48] Server listening on: http://127.0.0.1:41505 for proxy connections
[2019-9-8 21:20:48] *** SSH: checking proxy configuration
[2019-9-8 21:20:48] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-9-8 21:20:48] Passed config: {"sshproxy":{"description":"FHEM Connector","ssh":"/usr/bin/ssh","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":41505},"connections":[{"uid":999,"name":"FHEM","filter":"alexaName=..*","server":"127.0.0.1","webname":"fhem","port":"8083"}]}
[2019-9-8 21:20:48] sshautoconf: SSH key seems to exist
[2019-9-8 21:20:49] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-9-8 21:20:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-8 21:20:49] [FHEM] got: 0 results
[2019-9-8 21:20:50] BearerToken '...364AC' read from alexa
[2019-9-8 21:20:50] 39_alexa.pm is new version: true
[2019-9-8 21:20:50] sshautoconf: completed successfully
[2019-9-8 21:20:50] *** SSH: proxy configuration set up done
[2019-9-8 21:20:50] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-9-8 21:20:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:50] Starting SSH with -R 1234:127.0.0.1:41505 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-9-8 21:20:50] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-9-8 21:20:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-9-8 21:20:50] *** SSH: proxy connection established
[2019-9-8 21:20:50] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated.  

jump to the top

*

EDIT:

Zum Zeitpunkt als ich Define alexa alexa ausgeführt habe, war der Skill noch nicht aktiviert!
Aber ich denke das war richtig ..... oder

*

amenomade · 08 September 2019, 22:01:16

Die Log sieht gut aus (bis auf dem Fakt, dass Du regelmässig fhem neu startest)

Passiert was bei

Code Auswählen

get alexa proxyKey(bitte die Key nicht hier kopieren...)

CatWeazle · 08 September 2019, 22:06:37

get alexa proxyKey hatte ich auch schon in der Wiki: "FHEM Connector für Amazon Alexa" gefunden und versucht.
Leider kommt darauf nur ein kleines Fenster mit nix drin und einem OK Button.

amenomade · 08 September 2019, 22:16:26

Und was sagt die Log?

CatWeazle · 08 September 2019, 22:31:56

Hallo amenomade,

die Log sagt:

Code Auswählen

2019.09.08 22:26:16 4 : Connection accepted from WEB_192.168.0.149_56505
2019.09.08 22:26:16 4 : WEB_192.168.0.149_56505 POST /fhem?cmd=get%20alexa%20proxyKey&XHR=1&fw_id=1234; BUFLEN:0
2019.09.08 22:26:16 5 : Cmd: >get alexa proxyKey<
2019.09.08 22:26:16 4 : WEB: /fhem?cmd=get%20alexa%20proxyKey&XHR=1&fw_id=1234 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip / Cache-Control: no-cache, no-store, must-revalidate
2019.09.08 22:26:16 4 : Connection closed for WEB_192.168.0.149_56505: EOF

149 ist mein Mac

amenomade · 08 September 2019, 22:40:34

Zitat von: wikiIm Logfile (über den link Logfile in der Detail-Ansicht über set, oder über den Namen bei <it>currentlogfile</it> in den Internals) findest Du idealerweise selber Hinweise, wo es hakt, oder kannst im Forum nachfragen.

CatWeazle · 08 September 2019, 23:02:47

Okay,

bin einen Schritt weiter!
Ich habe ....
pi@raspberrypi:~# sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister
Your registration has been removed

danach FHEM neu gestartet und Alexa hat jetzt einen "alexaFHEM.skillRegKey"

Mals sehen wie es weiter geht ...

*

masterpete23 · 09 September 2019, 17:36:07

Hallo,

ich hoffe, ich bin hier richtig.
Ich habe npm auf meinem raspberry pi mit wheezy über https://github.com/audstanley/NodeJs-Raspberry-Pi/ auf eine aktuelle Version gebracht :

Code Auswählen

root@raspi3:~# node -v
v8.16.1
root@raspi3:~# npm -v
6.4.1

Nach einem set alexa alexa steht nun folgendes im state:

Code Auswählen

stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
Ich hatte früher eine alte Version aber davon hoffe ich alles gelöscht zu haben.
beim

Code Auswählen

sudo npm install -g alexa-fhem

kommt immer

Code Auswählen

root@raspi3:~# sudo npm install -g alexa-fhem
/opt/nodejs/bin/alexa-fhem -> /opt/nodejs/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.28
updated 1 package in 13.829s

Zeit variiert.
Aber ich bekomm es nicht lauffähig.
Hat jemand eine Idee? Braucht ihr mehr Infos oder reicht es so?

EDIT:
root@raspi3:~# cd /opt/node-v8.16.1-linux-armv7l/lib/node_modules/alexa-fhem/bin/
root@raspi3:/opt/node-v8.16.1-linux-armv7l/lib/node_modules/alexa-fhem/bin# ./alexa
[2019-9-9 17:56:11] os.homedir()=/root
[2019-9-9 17:56:11] using config from /root/.alexa/config.json
[2019-9-9 17:56:11] Couldn't find a config file at '/root/.alexa/config.json'. Look at config-sample.json for an example.

CatWeazle · 09 September 2019, 21:59:02

Hi Leutz,

ERFOLG, nachdem ich die Wiki: "FHEM Connector für Amazon Alexa" nochmal durchgegangen bin.

Der Schlüssel war: fhem-va.fhem.de unregister mit anschließendem FHEM Neustart.

Danach war es nur noch die Wiki Step by Step abarbeiten und es funktioniert.

Schade das ich im ersten Versuch nicht den alexaFHEM.skillRegKey erhalten halbe, sonst hätte die Wiki Anleitung auf Annhieb funktioniert.

By the way, die Anleitung inklusive der Beschreibung möglicher Fehlermeldungen ist echt gut gemacht!
Besten Dank für Wiki und Forenhilfe.

*