[alexa-fhem | Generell] Alles zu Installation und damit verbundenen Problemen

Begonnen von prodigy7, 09 November 2016, 19:42:01

Vorheriges Thema - Nächstes Thema

TomLee


87insane

Hey und guten Morgen zusammen.....

aufgrund der MQTT2 Template Entwicklung bin ich auf ein kleines Problem gestoßen. Alexa-Fhem benötigt in setList ein on/off um auch schalten zu können (ohne dummy).
Nun ist es aber so, das mit Veränderung von stateFormat auch FHEM den on/off Befehl für irgendwas nutzt und dies zu Fehlfunktionen im erweitertem stateFormat führt.

Ich mache es mal kurz... Gibt es einen Weg, das Alexa-Fhem auch auf weitere Dinge triggern kann und das Gerät dann als Schalter erkennt? Es würde schon reichen anstelle von
on/off in setList ein on1/off1 zu schreiben. So wären meine Probleme weg....

PS: Wenn mehr Infos benötigt werden, gebe ich diese gerne....

Danke und einen schönen Freitag :)

justme1968

ZitatAlexa-Fhem benötigt in setList ein on/off um auch schalten zu können (ohne dummy).
nein. alexa-fhem benötigt on und off um einen schalter als solchen automatisch zu erkennen. unabhängig von dummy oder nicht.

ZitatNun ist es aber so, das mit Veränderung von stateFormat auch FHEM den on/off Befehl für irgendwas nutzt und dies zu Fehlfunktionen im erweitertem stateFormat führt.
nein. stateFormat hat mit der liste der möglichen set kommandos die ein device versteht nichts zu tun.

ZitatGibt es einen Weg, das Alexa-Fhem auch auf weitere Dinge triggern kann und das Gerät dann als Schalter erkennt?
genericDeviceType switch setzen und ein passendes homebridgeMapping anlegen.

ansonsten: bitte nicht das kommando zum schalten und das reading in dem der aktuelle zustand steht durcheinander schmeissen. schau dir an wie homebridgeMapping funktioniert. damit kannst du alles konfigurieren.
hue, tradfri, alexa-fhem, homebridge-fhem, LightScene, readingsGroup, ...

https://github.com/sponsors/justme-1968

87insane

Zitat von: justme1968 am 03 Mai 2019, 09:18:41
nein. alexa-fhem benötigt on und off um einen schalter als solchen automatisch zu erkennen. unabhängig von dummy oder nicht.
nein. stateFormat hat mit der liste der möglichen set kommandos die ein device versteht nichts zu tun.
genericDeviceType switch setzen und ein passendes homebridgeMapping anlegen.

ansonsten: bitte nicht das kommando zum schalten und das reading in dem der aktuelle zustand steht durcheinander schmeissen. schau dir an wie homebridgeMapping funktioniert. damit kannst du alles konfigurieren.

1. War auch so gemeint

2. Da gibt es einen komischen Nebeneffekt mit der aufgebohrten stateFormat Version. (https://forum.fhem.de/index.php/topic,94060.msg936023.html#msg936023) Da warte ich quasi schon seit zwei Tagen auf dich ;) Beta-User und Rudi sind auch bereits mit Vorschlägen dabei. Ich liebe die erweiterte Version von stateFormat. Einfach und schick. Mehrere Symbole Schaltbar usw. Erst mal ein riesen Dank!

3. Das würde ich machen wenn es nicht anders geht. Hatte beim googlen auch homebridgemapping gefunden. Da ich mir aber nicht sicher bin ob es ggf. Sinn macht, hier ggf. nochmal Hand an zu legen: https://forum.fhem.de/index.php/topic,97586.msg908277.html#msg908277
An sich stirbt keiner von der Kleinigkeit aber wäre schon sehr nice :)

Es mag durchaus sein, dass ich etwas falsch gemacht habe. Da aber sehr gute User bereits versucht haben zu helfen und es nachweislich ein "Nebeneffekt" ist, würde ich natürlich gern helfen. Ich selber bin aber kein Programmiere :( Lerne hier Tag für Tag immer ein wenig mehr. Hoffe du verstehst wie ich das meine und kannst ggf. was dazu sagen.

Danke!

fumpeltröte

Hallo zusammen,

ich habe heute auch versucht vom "alten" alexa-fhem auf den neuen connector zu migrieren. Leider mit ein paar Hürden... nachdem node erst nicht gefunden wurde (fehlender sym-link auf \usr\bin\node) kam dann beim Startversuch in der alexa log:


SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/bin/alexa:17:1)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)


Versionen sollten doch eigentlich passen, oder?

root@cubietruck:~# node --version
v10.15.3
root@cubietruck:~# alexa-fhem --version
0.5.27


Hat da jemand evtl einen Rat?

VG
fumpel



justme1968

ist das der gleiche user unter dem auch fhem läuft? ich tippe auf mehrer installierte node versionen.

was liefert "node -v" aus fhem bzw "which node" ?
hue, tradfri, alexa-fhem, homebridge-fhem, LightScene, readingsGroup, ...

https://github.com/sponsors/justme-1968

fumpeltröte

...und das wars auch schon! Jetzt klappts... Ganz lieben Dank für die Hilfe! :)

War blöd... hätte ich auch drauf kommen müssen.

VG
fumpel

wthiess

Hallo!
Möchte auf die neue Alexa "FHEM Connector für Amazon Alexa" umsteigen.
Muss ich alle Lamda aws Sachen löschen?
Gibt es eine Umstiegsanleitung?
Bzw. Was muss ich im Fhem ändern?
Oder muss ich alles neu machen?
lg
Wolfgang
Raspberry Pi 3; 8xRelais; Aptodec Nano V3.0 Pro; FS1000a; RF-5V; Hama TS33C; 3x Brennerstuhl FunkSteckdosen; 9x Dooya funk Rollo; KWL Systemair VR400; Thermokon Modbusthermostat; diverse China Modbus Thermostate; 1-wire Bus; Telegram; QuickFhem; FhemNative; Firmata; Alexa ......

binford6000

Zitat von: wthiess am 11 Mai 2019, 21:48:23
Hallo!
Möchte auf die neue Alexa "FHEM Connector für Amazon Alexa" umsteigen.
Muss ich alle Lamda aws Sachen löschen?
Gibt es eine Umstiegsanleitung?
Bzw. Was muss ich im Fhem ändern?
Oder muss ich alles neu machen?
lg
Wolfgang

Hallo,
ich hab damals ganz einfach folgendes gemacht:

  • altes alexa gestoppt
  • alte Startautomatismen deaktiviert
  • Falls keine Custom Skills am Start sind Ports schließen
  • Und dann einfach bei https://wiki.fhem.de/wiki/FHEM_Connector_f%C3%BCr_Amazon_Alexa weitergelesen
  • Custom Skills können ebenfalls üder den FHEM-Connector weiter genutzt werden (Ports dann weiter offen lassen)

VG Sebastian

MadMax-FHEM

FHEM PI3B+ Bullseye: HM-CFG-USB, 40x HM, ZWave-USB, 13x ZWave, EnOcean-PI, 15x EnOcean, HUE/deCONZ, CO2, ESP-Multisensor, Shelly, alexa-fhem, ...
FHEM PI2 Buster: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, Shelly, ha-bridge, ...
FHEM PI3 Buster (Test)

wthiess

Raspberry Pi 3; 8xRelais; Aptodec Nano V3.0 Pro; FS1000a; RF-5V; Hama TS33C; 3x Brennerstuhl FunkSteckdosen; 9x Dooya funk Rollo; KWL Systemair VR400; Thermokon Modbusthermostat; diverse China Modbus Thermostate; 1-wire Bus; Telegram; QuickFhem; FhemNative; Firmata; Alexa ......

Gasmast3r

Hallo leute habe die Tage mein FHEM Rechner neu aufgesetzt mit Hürden,naja.

so nun bekomme ich Alexa in der neuen version nicht mehr zum laufen.

Bekomme kein Reading und den key um den skill zu Aktivieren.

Habe SSH Verbindung für meine EQ3BT Thermostate die über 3 andere PI's gesteuert werden.
list Alexa

Internals:
   FD         39
   FUUID      5cd9b105-f33f-ae7c-f487-2b583200a6718c8c
   FVERSION   39_alexa.pm:0.190980/2019-04-02
   LAST_START 2019-05-13 20:18:10
   LAST_STOP  2019-05-13 20:18:06
   NAME       alexa
   NOTIFYDEV  global,global:npmjs.*alexa-fhem.*
   NR         195
   NTFY_ORDER 50-alexa
   PARTIAL   
   PID        3775
   STARTS     2
   STATE      running /usr/bin/alexa-fhem
   TYPE       alexa
   active     0
   alexa-fhem version 0.5.27
   currentlogfile ./log/alexa-2019-05-13.log
   logfile    ./log/alexa-%Y-%m-%d.log
   CoProcess:
     cmdFn      alexa_getCMD
     name       alexaFHEM
     state      running /usr/bin/alexa-fhem
   READINGS:o80
     2019-05-13 20:18:10   alexaFHEM       running /usr/bin/alexa-fhem
     2019-05-13 20:18:13   alexaFHEM.ProxyConnection running; SSH connected
     2019-05-13 20:01:44   alexaFHEM.bearerToken crypt:540f24570603077c77542070770a0050
   helper:
Attributes:
   alexaFHEM-config ./alexa-fhem.cfg
   alexaFHEM-log ./log/alexa-%Y-%m-%d.log
   alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um

Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent

Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220

Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER

TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent

TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad

Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent

#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
   alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
   devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
   echoRooms  #<deviceId>=<room>

   fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nacht
   room       Alexa
   stateFormat alexaFHEM


Terminal

fhem@Server:~$ ps -ef | egrep '(alexa|ssh)'
root       402     1  0 20:10 ?        00:00:00 /usr/sbin/sshd -D
root       500   402  0 20:10 ?        00:00:00 sshd: fhem [priv]
fhem       509   500  0 20:10 ?        00:00:00 sshd: fhem@pts/0
fhem      3775   404  1 20:18 ?        00:00:02 node /usr/bin/alex
fhem      3815  3775  0 20:18 ?        00:00:00 /usr/bin/ssh -R 12
terval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
fhem      4233  4217  0 20:20 pts/0    00:00:00 grep -E (alexa|ssh
fhem@Server:~$ node -v
v8.16.0
fhem@Server:~$ which node
/usr/bin/node
fhem@Server:~$


Logfile Alexa

[2019-5-13 20:01:42] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:01:42] os.homedir()=/opt/fhem
[2019-5-13 20:01:42] this is alexa-fhem 0.5.27
[2019-5-13 20:01:42] connecting to FHEM ...
[2019-5-13 20:01:42] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:01:42] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557770502717
[2019-5-13 20:01:42] [FHEM] got csrfToken: csrf_169431990535164
[2019-5-13 20:01:42] [FHEM] Checking devices and attributes...
[2019-5-13 20:01:42] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] [FHEM] waiting for events ...
[2019-5-13 20:01:42] [FHEM] Fetching FHEM devices...
[2019-5-13 20:01:42] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] [FHEM] alexa device is alexa
[2019-5-13 20:01:42] [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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:42] Server listening on: http://127.0.0.1:33443 for proxy connections
[2019-5-13 20:01:42] *** SSH: checking proxy configuration
[2019-5-13 20:01:43] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:01:43] sshautoconf: env={"LANG":"de_DE.UTF-8","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","HOME":"/opt/fhem","LOGNAME":"fhem","USER":"fhem","SHELL":"/bin/bash","INVOCATION_ID":"f0d13b7c223b453b9fa34a8ddd4719be","JOURNAL_STREAM":"8:179843","MOJO_REACTOR":"Mojo::Reactor::Poll","PERL_LWP_SSL_VERIFY_HOSTNAME":"0"}
[2019-5-13 20:01:43] sshautoconf: Creating directory /opt/fhem/.alexa
[2019-5-13 20:01:43] 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":33443},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:01:43] sshautoconf: SSH key seems to exist
[2019-5-13 20:01:43] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:43] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:43] [FHEM] homebridgeMapping attribute created.
[2019-5-13 20:01:43] [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&fwcsrf=csrf_169431990535164&XHR=1
*** FHEM: connected
[2019-5-13 20:01:43] [FHEM] got: 0 results
[2019-5-13 20:01:43] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-13 20:01:43] 39_alexa.pm is new version: true
[2019-5-13 20:01: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%3Bset%20alexa%20proxyToken%2078A6744EF5EDC244%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:01:44] [FHEM] genericDeviceType attribute was not known. please restart.
[2019-5-13 20:02:04] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:02:04] os.homedir()=/opt/fhem
[2019-5-13 20:02:04] this is alexa-fhem 0.5.27
[2019-5-13 20:02:04] connecting to FHEM ...
[2019-5-13 20:02:05] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:02:05] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557770525433
[2019-5-13 20:02:05] [FHEM] got csrfToken: csrf_169431990535164
[2019-5-13 20:02:05] [FHEM] Checking devices and attributes...
[2019-5-13 20:02:05] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] [FHEM] waiting for events ...
[2019-5-13 20:02:05] [FHEM] Fetching FHEM devices...
[2019-5-13 20:02:05] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] [FHEM] alexa device is alexa
[2019-5-13 20:02:05] [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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:05] Server listening on: http://127.0.0.1:44437 for proxy connections
[2019-5-13 20:02:05] *** SSH: checking proxy configuration
[2019-5-13 20:02:05] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:02:05] 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":44437},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:02:05] sshautoconf: SSH key seems to exist
[2019-5-13 20:02:06] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-5-13 20:02:06] [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&fwcsrf=csrf_169431990535164&XHR=1
*** FHEM: connected
[2019-5-13 20:02:06] [FHEM] got: 0 results
[2019-5-13 20:02:06] BearerToken '...DC244' read from alexa
[2019-5-13 20:02:06] 39_alexa.pm is new version: true
[2019-5-13 20:02:06] sshautoconf: completed successfully
[2019-5-13 20:02:06] *** SSH: proxy configuration set up done
[2019-5-13 20:02:06] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-5-13 20:02:06] [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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:06] Starting SSH with -R 1234:127.0.0.1:44437 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-5-13 20:02:07] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-5-13 20:02: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%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&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:07] *** SSH: proxy connection established
[2019-5-13 20:02:07] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-5-13 20:02:49] Got SIGTERM, shutting down alexa-fhem...
[2019-5-13 20:02:49] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-13 20:02: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%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:49] Stopping SSH ...
[2019-5-13 20:02:49] Reading alexaFHEM.ProxyConnection set to stopped
[2019-5-13 20:02: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%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_169431990535164&XHR=1
[2019-5-13 20:02:49] *** SSH: exited with 143
[2019-5-13 20:03:13] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:03:13] os.homedir()=/opt/fhem
[2019-5-13 20:03:13] this is alexa-fhem 0.5.27
[2019-5-13 20:03:13] connecting to FHEM ...
[2019-5-13 20:03:14] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:03:14] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557770594083
[2019-5-13 20:03:15] [FHEM] got csrfToken: csrf_619635355097563
[2019-5-13 20:03:15] [FHEM] Checking devices and attributes...
[2019-5-13 20:03:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:15] [FHEM] waiting for events ...
[2019-5-13 20:03:15] [FHEM] Fetching FHEM devices...
[2019-5-13 20:03:15] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:16] [FHEM] alexa device is alexa
[2019-5-13 20:03:16] [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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:16] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:16] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:16] Server listening on: http://127.0.0.1:42277 for proxy connections
[2019-5-13 20:03:16] *** SSH: checking proxy configuration
[2019-5-13 20:03:16] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:03:16] 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":42277},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:03:16] sshautoconf: SSH key seems to exist
[2019-5-13 20:03:17] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-5-13 20:03:17] [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&fwcsrf=csrf_619635355097563&XHR=1
*** FHEM: connected
[2019-5-13 20:03:17] [FHEM] got: 0 results
[2019-5-13 20:03:17] BearerToken '...DC244' read from alexa
[2019-5-13 20:03:17] 39_alexa.pm is new version: true
[2019-5-13 20:03:17] sshautoconf: completed successfully
[2019-5-13 20:03:17] *** SSH: proxy configuration set up done
[2019-5-13 20:03:17] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-5-13 20:03:17] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:17] Starting SSH with -R 1234:127.0.0.1:42277 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-5-13 20:03:18] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-5-13 20:03:18] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:03:18] *** SSH: proxy connection established
[2019-5-13 20:03:18] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-5-13 20:04:27] Got SIGTERM, shutting down alexa-fhem...
[2019-5-13 20:04:27] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-13 20:04: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%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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:27] Stopping SSH ...
[2019-5-13 20:04:27] Reading alexaFHEM.ProxyConnection set to stopped
[2019-5-13 20:04: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:27] *** SSH: exited with 143
[2019-5-13 20:04:30] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:04:30] os.homedir()=/opt/fhem
[2019-5-13 20:04:30] this is alexa-fhem 0.5.27
[2019-5-13 20:04:30] connecting to FHEM ...
[2019-5-13 20:04:31] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:04:31] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557770671324
[2019-5-13 20:04:31] [FHEM] got csrfToken: csrf_619635355097563
[2019-5-13 20:04:31] [FHEM] Checking devices and attributes...
[2019-5-13 20:04:31] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] [FHEM] waiting for events ...
[2019-5-13 20:04:31] [FHEM] Fetching FHEM devices...
[2019-5-13 20:04:31] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] [FHEM] alexa device is alexa
[2019-5-13 20:04:31] [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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:31] Server listening on: http://127.0.0.1:36651 for proxy connections
[2019-5-13 20:04:31] *** SSH: checking proxy configuration
[2019-5-13 20:04:31] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:04:31] 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":36651},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:04:31] sshautoconf: SSH key seems to exist
[2019-5-13 20:04:32] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-5-13 20:04:32] [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&fwcsrf=csrf_619635355097563&XHR=1
*** FHEM: connected
[2019-5-13 20:04:32] [FHEM] got: 0 results
[2019-5-13 20:04:32] BearerToken '...DC244' read from alexa
[2019-5-13 20:04:32] 39_alexa.pm is new version: true
[2019-5-13 20:04:32] sshautoconf: completed successfully
[2019-5-13 20:04:32] *** SSH: proxy configuration set up done
[2019-5-13 20:04:32] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-5-13 20:04:32] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:32] Starting SSH with -R 1234:127.0.0.1:36651 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-5-13 20:04:33] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-5-13 20:04:33] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:04:33] *** SSH: proxy connection established
[2019-5-13 20:04:33] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-5-13 20:09:36] Got SIGTERM, shutting down alexa-fhem...
[2019-5-13 20:09:36] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-13 20:09:36] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:09:36] Stopping SSH ...
[2019-5-13 20:09:36] Got SIGTERM, shutting down alexa-fhem...
[2019-5-13 20:09:36] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-13 20:09:36] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:09:36] Stopping SSH ...
[2019-5-13 20:09:36] Reading alexaFHEM.ProxyConnection set to stopped
[2019-5-13 20:09:36] [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&fwcsrf=csrf_619635355097563&XHR=1
[2019-5-13 20:09:36] *** SSH: exited with 143
[2019-5-13 20:10:27] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:10:27] os.homedir()=/opt/fhem
[2019-5-13 20:10:27] this is alexa-fhem 0.5.27
[2019-5-13 20:10:27] connecting to FHEM ...
[2019-5-13 20:10:28] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:10:28] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557771028978
[2019-5-13 20:10:30] [FHEM] got csrfToken: csrf_98635813853856
[2019-5-13 20:10:30] [FHEM] Checking devices and attributes...
[2019-5-13 20:10:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] [FHEM] waiting for events ...
[2019-5-13 20:10:30] [FHEM] Fetching FHEM devices...
[2019-5-13 20:10:30] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] [FHEM] alexa device is alexa
[2019-5-13 20:10:30] [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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:30] Server listening on: http://127.0.0.1:45175 for proxy connections
[2019-5-13 20:10:30] *** SSH: checking proxy configuration
[2019-5-13 20:10:30] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:10:30] 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":45175},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:10:30] sshautoconf: SSH key seems to exist
[2019-5-13 20:10:31] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-5-13 20:10:31] [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&fwcsrf=csrf_98635813853856&XHR=1
*** FHEM: connected
[2019-5-13 20:10:31] [FHEM] got: 0 results
[2019-5-13 20:10:33] BearerToken '...DC244' read from alexa
[2019-5-13 20:10:33] 39_alexa.pm is new version: true
[2019-5-13 20:10:33] sshautoconf: completed successfully
[2019-5-13 20:10:33] *** SSH: proxy configuration set up done
[2019-5-13 20:10:33] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-5-13 20:10:33] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:33] Starting SSH with -R 1234:127.0.0.1:45175 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-5-13 20:10:34] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-5-13 20:10:34] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:10:34] *** SSH: proxy connection established
[2019-5-13 20:10:34] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-5-13 20:18:04] Got SIGTERM, shutting down alexa-fhem...
[2019-5-13 20:18:04] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-13 20:18:04] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:04] Stopping SSH ...
[2019-5-13 20:18:04] Reading alexaFHEM.ProxyConnection set to stopped
[2019-5-13 20:18:04] [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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:04] *** SSH: exited with 143
[2019-5-13 20:18:10] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-5-13 20:18:10] os.homedir()=/opt/fhem
[2019-5-13 20:18:10] this is alexa-fhem 0.5.27
[2019-5-13 20:18:10] connecting to FHEM ...
[2019-5-13 20:18:11] [FHEM] trying longpoll to listen for fhem events
[2019-5-13 20:18:11] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1557771491483
[2019-5-13 20:18:11] [FHEM] got csrfToken: csrf_98635813853856
[2019-5-13 20:18:11] [FHEM] Checking devices and attributes...
[2019-5-13 20:18:11] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:11] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:11] [FHEM] waiting for events ...
[2019-5-13 20:18:11] [FHEM] Fetching FHEM devices...
[2019-5-13 20:18:11] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:11] [FHEM] alexa device is alexa
[2019-5-13 20:18: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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18: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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18: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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:11] Server listening on: http://127.0.0.1:37679 for proxy connections
[2019-5-13 20:18:11] *** SSH: checking proxy configuration
[2019-5-13 20:18:11] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-5-13 20:18:11] 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":37679},"connections":[{"webname":"fhem","port":"8083","server":"127.0.0.1","uid":999,"filter":"alexaName=..*","name":"FHEM"}]}
[2019-5-13 20:18:11] sshautoconf: SSH key seems to exist
[2019-5-13 20:18:12] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-5-13 20:18: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&fwcsrf=csrf_98635813853856&XHR=1
*** FHEM: connected
[2019-5-13 20:18:12] [FHEM] got: 0 results
[2019-5-13 20:18:12] BearerToken '...DC244' read from alexa
[2019-5-13 20:18:12] 39_alexa.pm is new version: true
[2019-5-13 20:18:12] sshautoconf: completed successfully
[2019-5-13 20:18:12] *** SSH: proxy configuration set up done
[2019-5-13 20:18:12] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-5-13 20:18: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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:12] Starting SSH with -R 1234:127.0.0.1:37679 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-5-13 20:18:13] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-5-13 20:18: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&fwcsrf=csrf_98635813853856&XHR=1
[2019-5-13 20:18:13] *** SSH: proxy connection established
[2019-5-13 20:18:13] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-5-13 20:18:39] reloading http://127.0.0.1:8083/fhem
[2019-5-13 20:18:39] [FHEM] Fetching FHEM devices...
[2019-5-13 20:18:39] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_98635813853856&XHR=1
*** FHEM: connected
[2019-5-13 20:18:39] [FHEM] got: 0 results


ich selber kann keinen fehler erkennen, mag an meiner fähigkeiten liegen.

Achso System ist ein Acer Veriton g260 mit Debian 9

hoffe ihr könnt mir da helfen

Gasmast3r

Hallo konte mein Problem lösen, habe folgendes im Forum gefunden.


sudo -u fhem bash
ssh -p 58824 fhem-va.fhem.de status
ssh -p 58824 fhem-va.fhem.de unregister

Invers

Ich wüsste gerne, ob ich den Connector gleichzeitig auf 2 Rechnern laufen lassen kann.
Das Wiki gibt da leider nichts her.
Falls das geht - wie mache ich das?
Falls das nicht geht, was muss ich tun, um den vorhandenen Zugang im neuen Pi zu nutzen? Und was muss ich tun, um dann den alten Pi, der ja noch die Zugangsdaten enthält, dazu zu bringen, den neuen nicht zu "stören"?
Am neuen Pi habe ich schon
sudo apt-get install nodejs npm
sudo npm install -g alexa-fhem

gemacht. Hoffentlich war das nicht zu voreilig.

Bevor ich was falsch mache, frage ich lieber mal hier nach.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

gvzdus

Es scheitert daran, dass Du nicht bei Amazon mehrere Instanzen des gleichen Skills eröffnen kannst. Wenn Andre oder ich einen zweiten, 100% identischen Skill einreichen würden, wäre es möglich (wenn wir den bei Amazon durchbekämen). Dann könntest Du Skill 2 mit der zweiten Instanz verknüpfen.
Natürlich könntest Du auch selber einen Entwicklerskill mit dem Code installieren - aber auch mit "Bittebitte" würde ich Dir nicht das Secret für den Aufruf beim Vereinsserver geben, das unsere Lambda-Funktion dahin schickt :-)

Wenn Dein zweiter Raspberry "Blank" ist (kein SSH-Key für user "fhem" generiert), kein SkillRegKey im Alexa-Modul registriert, löscht Du einmal den FHEM Connector-Skill und gehst einfach ganz normal der Anleitung entlang nach vor, dann fragt er Dich ja wieder nach dem (dann neuen) Registrierungsschlüssel.