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

Begonnen von gvzdus, 23 Dezember 2018, 15:30:36

Vorheriges Thema - Nächstes Thema

sash.sc


pi@raspi:~ $ ls -ld /opt/fhem
drwxrwxrwx 12 fhem dialout 4096 Jan 15 22:42 /opt/fhem



Also total reset ?!?!

Danke
Sascha

Raspi 4B+ Bullseye ;LaCrosse; HomeMatic; MapleCUL; ZigBee; Signalduino ESP32 ; Shellys; MQTT2; Grafana mit Influxdb

gvzdus

Bah! Das ist der Grund! SSH mag nicht, wenn andere in Deinem (seinem) FHEM-HomeDir rumpfuschen könnten!

sudo chmod 755 /opt/fhem


zum Fixen,
... und dann bitte einmal Start aus dem Alexa-Device heraus. Ggf. ändert sich der Reg-Key.

gvzdus

Weil ich gleich vom Computer weg bin: Wenn Du das gemacht hast, kann es sein, dass der Reg-Key im Alexa-Device vom User "pi" stammt, während Dein SSH-Tunnel jetzt richtig vom User "fhem" kommt. Dann wäre das Ergebnis: Beim Verknüpfen sagt er "Key prima, aber kein SSH-Tunnel".
Um Anzustoßen, dass der Reg-Key neu erzeugt wird, würde ich

sudo rm -rf /opt/fhem/.ssh/*

vorschlagen, und dann einen Restart im Alexa-Frontend. Dann sollte ein neuer, passender Reg-Key erzeugt werden.

sash.sc

Habe die Rechte wie vorher geschrieben. Reset durchgeführt. Neustart über alexa device. Key wurde geändert.
Im Skill eingegeben und es läuft

Alles grün !!!!!!!!!!!!!!!!!!!!


Besten Dank !!!!

Schönes WE

Wenn noch probleme sind, melde mich dann !!!  ;)
Raspi 4B+ Bullseye ;LaCrosse; HomeMatic; MapleCUL; ZigBee; Signalduino ESP32 ; Shellys; MQTT2; Grafana mit Influxdb

gvzdus

Super. Dann Christian72D:

Möglicherweise ähnliche Gründe. Kannst Du bitte die 5 "ls"-Kommandos durchführen? Das wäre auch bei Dir ein möglicher Grund. Den Fix für "ls -ld /opt/fhem" zeigt mehr als ein "w" an, habe ich ja schon geschrieben.

Falls das bei Dir nichts nützt, bitte auch der Abschnitt zwischen den "*** SSH .... proxy configuration" -Abschnitten.

bergadler

#305
Hallo, ich habe auch ein Problem, daß meine Linux (immer noch) Grundkenntnisse stark übersteigt.

Die Installation ist eigentlich (nach Updates) fehlerfrei durchgelaufen,aber

in den Readings gibt es kein "alexaFHEM.skillRegKey".

list alexa:
Internals:
   FD         4
   LAST_START 2019-01-19 14:52:54
   NAME       alexa
   NOTIFYDEV  global
   NR         97
   NTFY_ORDER 50-alexa
   PID        1118
   STARTS     1
   STATE      running /usr/local/bin/alexa-fhem
   TYPE       alexa
   active     0
   alexa-fhem version 0.5.11
   currentlogfile /media/usbstick/fhemlog/alexa-2019-01-19.log
   logfile    %L/alexa-%Y-%m-%d.log
   READINGS:
     2019-01-19 14:52:54   alexaFHEM       running /usr/local/bin/alexa-fhem
     2019-01-19 14:52:57   alexaFHEM.ProxyConnection running; SSH connected
     2019-01-19 14:45:53   alexaFHEM.bearerToken crypt:570xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Attributes:
   alexaFHEM-config ./alexa-fhem.cfg
   alexaFHEM-log %L/alexa-%Y-%m-%d.log
   alexaMapping #Characteristic=<name>=<value>,...


Und im Logfile steht ein:

*** SSH: stderr: Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.

[2019-1-19 15:20:06] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-1-19 15:20:06] this is alexa-fhem 0.5.11
[2019-1-19 15:20:06] connecting to FHEM ...
[2019-1-19 15:20:07] [FHEM] trying longpoll to listen for fhem events
[2019-1-19 15:20:07] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547907607621
[2019-1-19 15:20:07] [FHEM] got csrfToken:
[2019-1-19 15:20:07] [FHEM] Checking devices and attributes...
[2019-1-19 15:20:07] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-1-19 15:20:07] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-1-19 15:20:07] [FHEM] waiting for events ...
[2019-1-19 15:20:07] [FHEM] Fetching FHEM devices...
[2019-1-19 15:20:07] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2019-1-19 15:20:07] [FHEM] got: 0 results
[2019-1-19 15:20:07] [FHEM] alexa device is alexa
[2019-1-19 15:20:07] [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.11%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 15:20:07] [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-1-19 15:20:07] [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-1-19 15:20:07] Server listening on: http://127.0.0.1:43621 for proxy connections
[2019-1-19 15:20:07] *** SSH: checking proxy configuration
[2019-1-19 15:20:07] os.homedir()=/opt/fhem
[2019-1-19 15:20:07] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":43621},"connections":[{"filter":"alexaName=..*","uid":999,"server":"127.0.0.1","webname":"fhem","name":"FHEM","port":"8083"}]}
[2019-1-19 15:20:07] sshautoconf: SSH key seems to exist
[2019-1-19 15:20:08] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-1-19 15:20:08] [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-1-19 15:20:08] BearerToken '...E5367' read from alexa
[2019-1-19 15:20:08] 39_alexa.pm is new version: true
[2019-1-19 15:20:08] sshautoconf: completed successfully
[2019-1-19 15:20:08] *** SSH: proxy configuration set up done
[2019-1-19 15:20:08] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-1-19 15:20:08] [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-1-19 15:20:08] Reading alexaFHEM.ProxyConnection set to running;; stderr=Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 15:20:08] [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%20stderr%3DWarning%3A%20Identity%20file%20~%2F.ssh%2Fid_rsa%20not%20accessible%3A%20No%20such%20file%20or%20directory.%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 15:20:08] *** SSH: stderr: Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 15:20:09] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-1-19 15:20:09] [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-1-19 15:20:09] *** SSH: proxy connection established
[2019-1-19 15:20:09] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 


Bin für jede Hilfe dankbar


aktuelles FHEM auf Raspberry B+, FHEM von fhem.de V.5.7, CUL868 V1.57, (6x FHT80B+ FHTTK, div. IT,div. FS20,Harmony Hub)

gvzdus

Du hast vermutlich aus FHEM raus über das Alexa-Device gestartet, wie es sein soll, oder? Wie wird fhem gestartet?

Das mit dem ~/.ssh/id_rsa war wohl echt keine gute Idee. Ich gehe heute abend in die Bütt...

bergadler

Die Installation habe ich gemäß Wiki gemacht.
Bis nach "define alexa alexa" das erwähnte Reading fehlt.

Und dann eben, egal ob
- Device alexa manuell set stop/start
-oder FHEM shutdown restart
oder einen Raspi reboot

das Ergebnis ist jeweils gleich.

Zumindest bei einem kompletten Raspi Reboot sollte doch alles automatisch starten?.

Oder habe ich vielleicht durch die vielen (unprofessionellen) Start/Stop Versuche, irgend etwas versaubeutelt und
es wäre leichter und schneller, die alexa Installation noch einmal drüber zu bügeln/platt machen?
aktuelles FHEM auf Raspberry B+, FHEM von fhem.de V.5.7, CUL868 V1.57, (6x FHT80B+ FHTTK, div. IT,div. FS20,Harmony Hub)

gvzdus

So, Andre hat vor 30 Sekunden 0.5.12 rausgebracht. Die sollte eventuell auf Anhieb für Dich Hilfe bringen, sonst aber hoffentlich wenigstens Hinweise direkt in der GUI.

Wenn Du bitte einmal updatest (0.5.12 sollte geladen werden) und restartest...

bergadler

So nach dem Update und shutdown restart verrät das Logfile etwas mehr:

[2019-1-19 20:35:38] Got SIGTERM, shutting down alexa-fhem...
[2019-1-19 20:35:38] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-1-19 20:35:38] [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-1-19 20:35:38] Stopping SSH ...
[2019-1-19 20:35:38] Reading alexaFHEM.ProxyConnection set to stopped;; Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 20:35:38] [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%3B%20Warning%3A%20Identity%20file%20~%2F.ssh%2Fid_rsa%20not%20accessible%3A%20No%20such%20file%20or%20directory.%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 20:35:38] *** SSH: exited with Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 20:35:46] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-1-19 20:35:46] this is alexa-fhem 0.5.11
[2019-1-19 20:35:46] connecting to FHEM ...
[2019-1-19 20:35:47] [FHEM] trying longpoll to listen for fhem events
[2019-1-19 20:35:47] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547926547072
[2019-1-19 20:35:47] [FHEM] got csrfToken:
[2019-1-19 20:35:47] [FHEM] Checking devices and attributes...
[2019-1-19 20:35:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-1-19 20:35:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-1-19 20:35:47] [FHEM] waiting for events ...
[2019-1-19 20:35:47] [FHEM] Fetching FHEM devices...
[2019-1-19 20:35:47] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2019-1-19 20:35:47] [FHEM] got: 0 results
[2019-1-19 20:35:47] [FHEM] alexa device is alexa
[2019-1-19 20:35: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.11%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 20:35: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-1-19 20:35: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-1-19 20:35:47] Server listening on: http://127.0.0.1:37313 for proxy connections
[2019-1-19 20:35:47] *** SSH: checking proxy configuration
[2019-1-19 20:35:47] os.homedir()=/opt/fhem
[2019-1-19 20:35:47] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":37313},"connections":[{"filter":"alexaName=..*","uid":999,"server":"127.0.0.1","webname":"fhem","name":"FHEM","port":"8083"}]}
[2019-1-19 20:35:47] sshautoconf: SSH key seems to exist
[2019-1-19 20:35:48] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-1-19 20:35: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%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 20:35:48] BearerToken '...E5367' read from alexa
[2019-1-19 20:35:48] 39_alexa.pm is new version: true
[2019-1-19 20:35:48] sshautoconf: completed successfully
[2019-1-19 20:35:48] *** SSH: proxy configuration set up done
[2019-1-19 20:35:48] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-1-19 20:35: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%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-1-19 20:35:48] Reading alexaFHEM.ProxyConnection set to running;; stderr=Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 20:35: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20stderr%3DWarning%3A%20Identity%20file%20~%2F.ssh%2Fid_rsa%20not%20accessible%3A%20No%20such%20file%20or%20directory.%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 20:35:48] *** SSH: stderr: Warning: Identity file ~/.ssh/id_rsa not accessible: No such file or directory.
[2019-1-19 20:35:48] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-1-19 20:35: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%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-1-19 20:35:48] *** SSH: proxy connection established
[2019-1-19 20:35:48] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 

aktuelles FHEM auf Raspberry B+, FHEM von fhem.de V.5.7, CUL868 V1.57, (6x FHT80B+ FHTTK, div. IT,div. FS20,Harmony Hub)

gvzdus

[2019-1-19 20:35:46] this is alexa-fhem 0.5.11

Hmmh, ist aber noch 0.5.11 - da würde ich jetzt nichts Neues erwarten...

bergadler

Also Update habe ich gemacht, die  39_alexa.pm war auch  mit dabei, aber wenn ich sie mir betrachte:

$Id: 39_alexa.pm 18283 2019-01-16 16:58:23Z justme1968

Wo gibt es die neue?
Ein update check bringt "nothing to do"
aktuelles FHEM auf Raspberry B+, FHEM von fhem.de V.5.7, CUL868 V1.57, (6x FHT80B+ FHTTK, div. IT,div. FS20,Harmony Hub)

gvzdus


bergadler

#313
Nö, noch nicht,
sorry, habe gedacht update vom Modul. ???
Aber gleich...

So, jetzt habe ich die 0.5.12

An den readings vom Alexa Device hat sich noch nichts geändert.

Hier der  alexa log nach dem Update und Reboot vom Raspi:

[2019-1-19 21:06:09] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-1-19 21:06:09] os.homedir()=/opt/fhem
[2019-1-19 21:06:09] this is alexa-fhem 0.5.12
[2019-1-19 21:06:09] connecting to FHEM ...
[2019-1-19 21:06:11] [FHEM] trying longpoll to listen for fhem events
[2019-1-19 21:06:11] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547928371343
[2019-1-19 21:06:11] [FHEM] got csrfToken:
[2019-1-19 21:06:11] [FHEM] Checking devices and attributes...
[2019-1-19 21:06:11] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-1-19 21:06:11] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-1-19 21:06:11] [FHEM] waiting for events ...
[2019-1-19 21:06:11] [FHEM] Fetching FHEM devices...
[2019-1-19 21:06:11] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-1-19 21:06:11] [FHEM] alexa device is alexa
[2019-1-19 21:06:11] [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.12%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-19 21:06:11] [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-1-19 21:06:11] [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-1-19 21:06:11] Server listening on: http://127.0.0.1:40875 for proxy connections
[2019-1-19 21:06:11] *** SSH: checking proxy configuration
[2019-1-19 21:06:11] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-1-19 21:06:11] Passed config: {"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":40875},"connections":[{"filter":"alexaName=..*","uid":999,"server":"127.0.0.1","webname":"fhem","name":"FHEM","port":"8083"}]}
[2019-1-19 21:06:11] sshautoconf: SSH key seems to exist
[2019-1-19 21:06:12] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-1-19 21:06:12] [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-1-19 21:06:12] [FHEM] got: 0 results
[2019-1-19 21:06:12] BearerToken '...E5367' read from alexa
[2019-1-19 21:06:12] 39_alexa.pm is new version: true
[2019-1-19 21:06:12] sshautoconf: completed successfully
[2019-1-19 21:06:12] *** SSH: proxy configuration set up done
[2019-1-19 21:06:12] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-1-19 21:06:12] [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-1-19 21:06:12] Starting SSH with -R 1234:127.0.0.1:40875 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-1-19 21:06:13] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-1-19 21:06:13] [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-1-19 21:06:13] *** SSH: proxy connection established
[2019-1-19 21:06:13] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 

jump to the top
aktuelles FHEM auf Raspberry B+, FHEM von fhem.de V.5.7, CUL868 V1.57, (6x FHT80B+ FHTTK, div. IT,div. FS20,Harmony Hub)

gvzdus

Ich würde sagen: Du bist ein glücklicher Mensch :-)

Dann mach mal weiter nach Wiki mit dem Skill-Verknüpfen...