[Gelöst] alexa-fhem / FHEM Connector: Problem mit "get alexa proxyKey"

DaRealDan · 25 Januar 2021, 00:07:10

alexa-fhem als FHEM Connector hat über ein Jahr lang prima funktioniert. Seit rund einer Woche nun tuts nicht mehr. Heute habe ich mir das Problem in der FHEM Installation mal angeschaut.

Konnte keinen offensichtlichen Fehler finden, also einmal FHEM Connector Skill deaktiviert, aktiviert und bei einem Blick in FHEM dann "get alexa proxyKey" gedrückt.

Dabei bekomme ich aber nun einen extrem komischesn proxyKey, der vom FHEM Connector Account-Linking Login auch nicht akzeptiert wird...

Das soll angeblich der proxyKey sein: "05Fhd0@~;BG00f?Dc3@:=27+D=eF?3@;a58G"

Was ist falsch?
habe schon das alexa-fhem Modul aktualisiert sowie alexa-fhem. Erst "set alexa stop" dann "npm install -g alexa-fhem" und wieder "set alexa start" und es geht weiterhin nicht.

Hat jemand eine Idee?

gvzdus · 25 Januar 2021, 06:27:55

Nein, das ist kein schöner Proxy-Key. Wie auch immer die interne Speicherung des Keys in FHEM "zermarmelt" wurde: Am einfachsten einmal den Abschnitt mit "unregister" im Wiki durchspielen, danach kommt hoffentlich ein sauberer Proxy-Key, mit dem Du dann den Skill neu verknüpfen kannst.

DaRealDan · 25 Januar 2021, 08:20:52

Erledigt.

Danach kommt in FHEM folgende Meldung

alexaFHEM.ProxyConnection: stopped; Terminated with 255, ssh will restart at 09:18:47

Aus dem alexa-fhem.log

Code Auswählen


[2021-1-25 08:18:46] BearerToken '...1>CK' read from alexa
[2021-1-25 08:18:46] *** SSH: stdout message: Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 08:18:46] Reading alexaFHEM.ProxyConnection set to running;; Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 08:18:46] [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%20Your%20public%20key%20is%20not%20known%2C%20please%20register%20first.%20(retry%3A%203600%20seconds)%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 08:18:46] SSH: Your public key is not known, please register first. (retry: 3600 seconds)  
[2021-1-25 08:18:47] SSH: exited with 255 - will restart in 3600 seconds
[2021-1-25 08:18:47] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with 255, ssh will restart at 09:18:47
[2021-1-25 08:18: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%20stopped%3B%3B%20Terminated%20with%20255%2C%20ssh%20will%20restart%20at%2009%3A18%3A47%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

gvzdus · 25 Januar 2021, 10:59:04

Eigentlich wäre es jetzt so weit, dass Du den Skill neu verknüpfen könntest. Aber der Fetzen von dem Bearer-Token, der oben im Logfile zu erkennen ist, sieht genauso mistig aus.

Ich denke mal, mit einem

Code Auswählen

deletereading alexa alexaFhem.*
kannst Du tabula rasa machen (und danach das Alexa-Device stoppen und neu starten).

Sorry, ungetestet.

DaRealDan · 25 Januar 2021, 11:10:35

Danke! Habs probiert.

Erst alexa-fhem gestopped

Danach die Readings gelöscht und alexa-fhem neu gestartet

Fehlermeldung: stopped; Terminated with Connection to fhem-va.fhem.de closed by remote host. , ssh will restart at 12:08:45

Code Auswählen

[2021-1-25 11:08:42] BearerToken '...1>CK' read from alexa
[2021-1-25 11:08:43] *** SSH: stdout message: Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 11:08:43] Reading alexaFHEM.ProxyConnection set to running;; Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 11:08: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20Your%20public%20key%20is%20not%20known%2C%20please%20register%20first.%20(retry%3A%203600%20seconds)%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 11:08:43] SSH: Your public key is not known, please register first. (retry: 3600 seconds)  
[2021-1-25 11:08:45] Reading alexaFHEM.ProxyConnection set to running;; stderr=Connection to fhem-va.fhem.de closed by remote host.  
[2021-1-25 11:08:45] [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%3DConnection%20to%20fhem-va.fhem.de%20closed%20by%20remote%20host.%20%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 11:08:45] *** SSH: stderr: Connection to fhem-va.fhem.de closed by remote host.  
[2021-1-25 11:08:45] SSH: exited with 255 - will restart in 3600 seconds
[2021-1-25 11:08:45] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with Connection to fhem-va.fhem.de closed by remote host.  , ssh will restart at 12:08:45
[2021-1-25 11:08:45] [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%20Terminated%20with%20Connection%20to%20fhem-va.fhem.de%20closed%20by%20remote%20host.%20%20%2C%20ssh%20will%20restart%20at%2012%3A08%3A45%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

Außerdem sind die alten Readings wieder zurück (hatte sie vorher in eine Textdatei kopiert). Wird es irgendwo gecached?

gvzdus · 25 Januar 2021, 11:30:00

O je, ich hatte in Erinnerung, dass das Alexa-Modul penetrant im Merken ist.
Ja, das war ekelig hartnäckig.

Also Vorschlag:
Alexa-Device ganz löschen

Code Auswählen

{ setKeyValue ("alexaFHEM.bearerToken", undef) }
als FHEM-Befehl

Code Auswählen

{ setKeyValue ("alexaFHEM.skillRegKey", undef) }
als FHEM-Befehl

Alexa-Device neu anlegen.

DaRealDan · 25 Januar 2021, 11:33:26

Okay, sieht etwas besser aus, das Reading bleibt weg.

Nun aber:

Code Auswählen

[2021-1-25 11:31:40] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2021-1-25 11:31:40] *** SSH: stdout message: Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 11:31:40] Reading alexaFHEM.ProxyConnection set to running;; Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 11:31:40] [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%20Your%20public%20key%20is%20not%20known%2C%20please%20register%20first.%20(retry%3A%203600%20seconds)%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 11:31:40] SSH: Your public key is not known, please register first. (retry: 3600 seconds)  
[2021-1-25 11:31:43] SSH: exited with 255 - will restart in 3600 seconds
[2021-1-25 11:31:43] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with 255, ssh will restart at 12:31:43

Kann man die "Registrierung" mit dem Server manuell starten?

gvzdus · 25 Januar 2021, 13:08:58

Dein Fall ist übrigens der 2. mir bekannte. Kannst Du eingrenzen, was mutmaßlich den kaputten Proxy-Key ausgelöst hat? Die Readings werden bei jedem Alexa-Start gelesen (also z.B. beim FHEM-Neustart), mit "kaputt" kann es nicht funktionieren.

DaRealDan · 25 Januar 2021, 13:13:13

Es ging nicht mehr nachdem ich über die Shell

Code Auswählen

killall -9 perl
/etc/init.d/fhem start

gemacht hatte. FHEM war gecrashed und musste daher Perl abschießen.

Danach war der proxyKey hinüber.

Nur: Ich bekomme es jetzt aktuell auch nicht mehr ans Laufen

Ideen?

gvzdus · 25 Januar 2021, 13:50:11

Eigentlich läuft alles automatisch in diesem Zustand ab. Beim Start wird geprüft, ob Du schon registriert bist, ggf. neu registriert, ein neues Token generiert u.s.w.

Scheint aber nicht zu funktionieren - aber Dein Logfile-Auszug ist zu kurz.
Besondern relevant sind alle Zeilen, die irgendwie SSH erwähnen, vor allem "sshautoconf".
Irrelevant sind Geräte, die gelesen werden, oder auch wie irgendwelche Keys lauten (solange sie schönes Hex sind).

DaRealDan · 25 Januar 2021, 14:06:36

Hier dann nochmal ein "Neustart" von alexa-fhem und alle Logs passend dazu (mit Parameter -D)

Interessanter Teil?

Code Auswählen

[2021-1-25 14:00:24] Server listening on: http://127.0.0.1:56473 for proxy connections
[2021-1-25 14:00:24] *** SSH: checking proxy configuration
[2021-1-25 14:00:24] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2021-1-25 14:00:24] sshautoconf: TypeError: Converting circular structure to JSON
[2021-1-25 14:00:24] sshautoconf: completed successfully
[2021-1-25 14:00:24] *** SSH: proxy configuration set up done
[2021-1-25 14:00:24] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH

Full Log

Code Auswählen

[2021-1-25 14:00:23] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2021-1-25 14:00:23] os.homedir()=/root
[2021-1-25 14:00:23] os.homedir() set to /root, but this is not writable
[2021-1-25 14:00:23] process.env.HOME=/root
[2021-1-25 14:00:23] process.env.HOME set to /root, but this is not writable
[2021-1-25 14:00:23] process.env.HOMEPATH=undefined
[2021-1-25 14:00:23] process.env.USERPROFILE=undefined
[2021-1-25 14:00:23] process.env.PWD=/opt/fhem
[2021-1-25 14:00:23] this is alexa-fhem 0.5.58
[2021-1-25 14:00:23] connecting to FHEM ...
[2021-1-25 14:00:23] [FHEM] defaults to: will not send proactive events
[2021-1-25 14:00:24] [FHEM] trying longpoll to listen for fhem events
[2021-1-25 14:00:24] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1611579624217
[2021-1-25 14:00:24] [FHEM] got csrfToken: 
[2021-1-25 14:00:24] [FHEM] Checking devices and attributes...
[2021-1-25 14:00:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2021-1-25 14:00:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2021-1-25 14:00:24] [FHEM] waiting for events ...
[2021-1-25 14:00:24] [FHEM] Fetching FHEM devices...
[2021-1-25 14:00:24] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2021-1-25 14:00:24] [FHEM] alexa device is alexa
[2021-1-25 14:00:24] [FHEM] mappings for alexa: {}
[2021-1-25 14:00:24] [FHEM] alexa will not send proactive events
[2021-1-25 14:00:24] [FHEM] alexa uses ID: 600e9df1-f33f-542b-4f0d-e55eaa7f4523158b

[2021-1-25 14:00:24] [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
[2021-1-25 14:00:24] Server listening on: http://127.0.0.1:56473 for proxy connections
[2021-1-25 14:00:24] *** SSH: checking proxy configuration
[2021-1-25 14:00:24] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2021-1-25 14:00:24] sshautoconf: TypeError: Converting circular structure to JSON
[2021-1-25 14:00:24] sshautoconf: completed successfully
[2021-1-25 14:00:24] *** SSH: proxy configuration set up done
[2021-1-25 14:00:24] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2021-1-25 14:00:24] [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
[2021-1-25 14:00:24] Starting SSH with -R 1234:127.0.0.1:56473 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
*** FHEM: connected


[2021-1-25 14:00:24] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2021-1-25 14:00:24] *** SSH: stdout message: Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 14:00:24] Reading alexaFHEM.ProxyConnection set to running;; Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 14:00:24] [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%20Your%20public%20key%20is%20not%20known%2C%20please%20register%20first.%20(retry%3A%203600%20seconds)%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 14:00:24] SSH: Your public key is not known, please register first. (retry: 3600 seconds)  
[2021-1-25 14:00:25] SSH: exited with 255 - will restart in 3600 seconds
[2021-1-25 14:00:25] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with 255, ssh will restart at 15:00:25
[2021-1-25 14:00: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%3B%20Terminated%20with%20255%2C%20ssh%20will%20restart%20at%2015%3A00%3A25%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

gvzdus · 25 Januar 2021, 15:58:32

Oha, jetzt heisst es Rätseln, wo die "Circular JSON"-Exception fliegt.

Erste These: Beim Versuch, das Environment auszugeben. Dann müsste Folgendes helfen, weil er die Stelle dann überspringt:

Code Auswählen

sudo -u fhem mkdir /opt/fhem/.alexa

Vielleicht ist aber auch die /opt/fhem/alexa-fhem.cfg kaputt? Die wird ggf. automatisch neu erzeugt, Du kannst sie löschen.

DaRealDan · 25 Januar 2021, 18:21:19

So langsam dreh ich hier durch

Danke für Deine Mühe und die Lösungswege, aber im Moment führt jeder Schritt anscheinend zu neuen Problemen.

1. alexa-fhem stopped
2. Device Deleted
3. .alexa-fhem.cfg deleted
4. Neues define alexa alexa
5. Dann start alexa-fhem

Daraus folgt:

Siehe:

Code Auswählen

[2021-1-25 18:12:33] Got SIGTERM, shutting down alexa-fhem...
[2021-1-25 18:12:33] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2021-1-25 18:12: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%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:12:40] using config from ./alexa-fhem.cfg
[2021-1-25 18:12:40] Couldn't find a config file at './alexa-fhem.cfg'. Look at config-sample.json for an example.
[2021-1-25 18:13:00] using config from ./alexa-fhem.cfg
[2021-1-25 18:13:00] Couldn't find a config file at './alexa-fhem.cfg'. Look at config-sample.json for an example.
[2021-1-25 18:13:20] using config from ./alexa-fhem.cfg
[2021-1-25 18:13:20] Couldn't find a config file at './alexa-fhem.cfg'. Look at config-sample.json for an example.
[2021-1-25 18:13:40] using config from ./alexa-fhem.cfg
[2021-1-25 18:13:40] Couldn't find a config file at './alexa-fhem.cfg'. Look at config-sample.json for an example.

DaRealDan · 25 Januar 2021, 18:29:14

Hab nochmal ein npm install -i alexa-fhem gemacht
Vorher shutdown der FHEM Instanz und delete fhem

Nun ist alexa-fhem 0.5.59 installiert.

Dann noch /opt/fhem/.alexa gelöscht und alexa-fhem.cfg

Dann FHEM gestartet, neues define alexa alexa

Nun wurde eine neue alexa-fhem.cfg angelegt mit folgendem Inhalt

Code Auswählen


   "sshproxy" : {
      "description" : "FHEM Connector",
      "ssh" : "/usr/bin/ssh"
   },
   "connections" : [
      {
         "uid" : 999,
         "filter" : "alexaName=..*",
         "port" : "8083",
         "server" : "127.0.0.1",
         "webname" : "fhem",
         "name" : "FHEM"
      }
   ]
}

Auch wurde der .alexa Ordner angelegt (der ist leer)

Und das Log sagt folgendes:

Code Auswählen

[2021-1-25 18:25:34] [FHEM] alexa device is alexa
[2021-1-25 18:25:34] [FHEM] alexa will not send proactive events
[2021-1-25 18:25:34] [FHEM] alexa uses ID: 600efeec-f33f-542b-956c-1bbf16e189504301
[2021-1-25 18:25: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%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.59%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:25: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:25: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:25:34] Server listening on: http://127.0.0.1:56385 for proxy connections
[2021-1-25 18:25:34] *** SSH: checking proxy configuration
[2021-1-25 18:25:34] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2021-1-25 18:25:34] sshautoconf: env={"MAIL":"/var/mail/root","SSH_CLIENT":"172.17.0.1 49110 2222","USER":"root","SHLVL":"1","HOME":"/root","OLDPWD":"/opt/fhem","SSH_TTY":"/dev/pts/0","LOGNAME":"root","_":"/etc/init.d/fhem","TERM":"xterm","PERL_LWP_SSL_VERIFY_HOSTNAME":"0","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","SHELL":"/bin/bash","NODE_PATH":"/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript","PWD":"/opt/fhem","SSH_CONNECTION":"172.17.0.1 49110 172.17.0.2 2222"}
[2021-1-25 18:25:34] sshautoconf: Creating directory /opt/fhem/.alexa
[2021-1-25 18:25:34] sshautoconf: TypeError: Converting circular structure to JSON
[2021-1-25 18:25:34] sshautoconf: completed successfully
[2021-1-25 18:25:34] *** SSH: proxy configuration set up done
[2021-1-25 18:25:34] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2021-1-25 18:25: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%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:25:34] Starting SSH with -R 1234:127.0.0.1:56385 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2021-1-25 18:25:35] *** SSH: stdout message: Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 18:25:35] Reading alexaFHEM.ProxyConnection set to running;; Your public key is not known, please register first. (retry: 3600 seconds)

[2021-1-25 18:25:35] [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%20Your%20public%20key%20is%20not%20known%2C%20please%20register%20first.%20(retry%3A%203600%20seconds)%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2021-1-25 18:25:35] SSH: Your public key is not known, please register first. (retry: 3600 seconds)  
*** FHEM: connected

gvzdus · 25 Januar 2021, 18:51:11

Ich spiele das nachher nach. Worst Case ist bei der 0.58 für Neunutzer was schief gelaufen.