39_alexa.pm und alexa-fhem test version

Begonnen von justme1968, 03 Januar 2019, 22:43:10

Vorheriges Thema - Nächstes Thema

matthias soll

Danke für deine Hilfe!!!
Mein Log sieht soweit ich das sehen kann auch gut aus...
[2020-5-16 3:23:30 AM] Reading alexaFHEM.ProxyConnection set to running;; stderr=packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe 
[2020-5-16 3:23:30 AM] [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%3Dpacket_write_wait%3A%20Connection%20to%2088.99.31.202%20port%2058824%3A%20Broken%20pipe%20%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:23:30 AM] *** SSH: stderr: packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe 
[2020-5-16 3:23:30 AM] SSH: exited with 255 - will restart in 107.54226315823752 seconds
[2020-5-16 3:23:30 AM] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe  , ssh will restart at 03:25:18
[2020-5-16 3:23:30 AM] [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%20packet_write_wait%3A%20Connection%20to%2088.99.31.202%20port%2058824%3A%20Broken%20pipe%20%20%2C%20ssh%20will%20restart%20at%2003%3A25%3A18%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:25:18 AM] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2020-5-16 3:25:18 AM] [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
[2020-5-16 3:25:18 AM] Starting SSH with -R 1234:127.0.0.1:40199 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2020-5-16 3:25:19 AM] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2020-5-16 3:25:19 AM] [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
[2020-5-16 3:25:19 AM] *** SSH: proxy connection established
[2020-5-16 3:25:19 AM] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2020-5-16 8:43:04 AM] reloading http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing CharlotteLicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing Heizung from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing JetteLicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing MQTT2_LRlamp_CH1 from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing MQTT2_LRlamp_CH2 from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing TV_on from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing Terrasse from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing WG_Belechtung from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing backlight from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing lamp1_wohnzimmer from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing tree from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing wintergartenlicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] [FHEM] Fetching FHEM devices...
[2020-5-16 8:43:04 AM] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2020-5-16 8:43:05 AM] [FHEM] got: 12 results
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht is switch
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht uses ID: 5e34774f-f33f-bbdb-81bd-f6816bee42c712d6
[2020-5-16 8:43:05 AM] [FHEM] Heizung is switch
[2020-5-16 8:43:05 AM] [FHEM] Heizung has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] Heizung will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] Heizung uses ID: 5e24a4cb-f33f-bbdb-e2df-7bc984434c4adad4
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht is switch
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht uses ID: 5e34774f-f33f-bbdb-952c-8c201d6ff94f8227
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 is switch
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 uses ID: 5dc825f1-f33f-bbdb-e48e-1c7661d7d7a3aeae
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 is switch
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 uses ID: 5e53f705-f33f-bbdb-c888-edfd86130b13af52
[2020-5-16 8:43:05 AM] [FHEM] TV_on is switch
[2020-5-16 8:43:05 AM] [FHEM] TV_on has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] TV_on will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] TV_on uses ID: 5c49d87b-f33f-59e6-5d6c-771a26e7ca102d7f
[2020-5-16 8:43:05 AM] [FHEM] Terrasse is switch
[2020-5-16 8:43:05 AM] [FHEM] Terrasse has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] Terrasse will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] Terrasse uses ID: 5e34774f-f33f-bbdb-8f43-2329215b39e4367f
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung is switch
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung uses ID: 5e273d31-f33f-bbdb-ca7e-d02b95165a26728b
[2020-5-16 8:43:05 AM] [FHEM] backlight is switch
[2020-5-16 8:43:05 AM] [FHEM] backlight has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] backlight will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] backlight uses ID: 5e34774f-f33f-bbdb-5784-4e5cba808fcf49a5
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer is switch
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer uses ID: 5dd6b162-f33f-bbdb-62ab-fc1f2b4bfb5fcbf8
[2020-5-16 8:43:05 AM] [FHEM] tree is switch
[2020-5-16 8:43:05 AM] [FHEM] tree has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] tree will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] tree uses ID: 5c49d87b-f33f-59e6-b662-090fbcdbd4a820f2
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht is switch
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht has
[2020-5-16 8:43:05 AM] [FHEM]   On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht uses ID: 5e347750-f33f-bbdb-200d-0124688d53628afc
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available


Also zumindes sind da 12 geräte gefunden worden......

gvzdus

Auch das sieht gut aus. Und Du hast Alexa nach der Einrichtung suchen lassen? "Alexa, suche neue Geräte!" Was wird Dir auf der Seite bei der Skillverknüpfung, also nach der Eingabe des Proxykeys angezeigt? (Du kann den Skill jederzeit wieder entfernen und neu verknüpfen, vor allem, wenn Du noch gar keine Geräte siehst.

matthias soll

Danke für die Info. Skill neu verknüpfen...
Das muss ich noch probieren....
Alexa findet bisher keine neuen Geräte

gvzdus

Also konkret: Auf der Seite nach dem Absenden des Reg-Keys: Da werden eine Reihe von "grünen Okays" angezeigt. Aus dem Kopf: Proxy-Verbindung, u.s.w. Und m.W. auch die Anzahl der gefundenen Devices.

matthias soll

Shit ich glaube jetzt funktioniert es.
Ich wusste nicht, das ich das Skill komplett löschen und neu installieren muss wenn ich das schonmal gemacht hatte.
Danke für deine Hilfe!!!!!


gvzdus

Es gibt eigentlich nur folgende Szenarien, wo das nötig sein kann:

  • Wenn irgendwie der bekannte SSH-Key verloren ging, z.B., weil man "mal richtig aufgeräumt hat" oder auf eine neue Instanz (Hardware, SD-Karte) umgezogen ist
  • Wenn zwar die Geräte in Alexa da sind, aber aktives Reporting (Alexa fängt von alleine an zu sprechen) nicht mehr funktioniert

matthias soll

Richtig ich habe schwer aufgeräumt und bin auf eine neue sd Karte umgezogen.
Nachdem ich das Skill neu installiert habe läuft alles wieder wie gewohnt. Danke für die Hilfe!!!

MadMax-FHEM

Zitat von: matthias soll am 17 Mai 2020, 12:10:47
Richtig ich habe schwer aufgeräumt und bin auf eine neue sd Karte umgezogen.
Nachdem ich das Skill neu installiert habe läuft alles wieder wie gewohnt. Danke für die Hilfe!!!

Drum hab ich bei mir im fhem-Backup auch eine Kopie der ssh-Schlüssel drin...

Nicht nur wegen alexa-fhem, sondern auch wegen ssh zu anderen Servern meiner "Landschaft"...

Gruß, Joachim
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)

Mickie

#953
Hallo zusammen..

Bei mir erscheint bei "get proxyKey" kein Popup mit dem Key. hat jemand eine Idee?
Hatte auf einer alten Instanz Alexa am laufen und habe jetzt die Hardware (RPI 3 + Speicherkarte) getauscht.
Der Skill ist deinstalliert und alles neu installiert ohne alte Backups.

Danke vorab.

Hat sich erledigt.

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

dann Alexa neustarten und schon war der Key da.
Danke für die Unterstützung

MadMax-FHEM

Hab nicht (wirklich) verstanden was du nun genau gemacht hast bzw. nicht gemacht hast!?

Alte SD in neuen PI!?

Warum dann Skill deinstalliert etc.!?

Oder:

neuen PI UND neue SD und alles NEU OHNE irgendwelche Backups (sei es fhem oder sonst was)!?

Also bitte mal genau schildern wie du vorgegangen bist und was du (mit dem "alten" PI und was mit dem "neuen" PI) gemacht hast, also genaue Schritte die du durchgeführt hast.

Welches System ist dann das neue!?

Raspbian Buster LITE!!!!? Oder was anderes!?

Läuft alexa-fhem!?
Welche Version...

Gruß, Joachim
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)

Mickie

Habe den Raspi mit Buster neu installiert. Dann Fhem und natürlich auch alexa-fhem.
Problem war, dass der Key nicht abgefragt werden konnte.

Mit sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister und dem Neustart von Alexa hat es dann geklappt.
Danke für die Unterstützung

coolheizer

Leider komme ich nicht weiter, oftmals kommt ein "xxx reagiert leider nicht".

Dann funktonieren die Geräte wieder.

Anfangs (vor ~1 Jahr) hatte noch alles einwandfrei funktionier, irgendwann kamen fehler, hatte es aber auf unsere schlechte Internet Verbindung geschoben, jetzt haben wir LTE und Inet rennt.
Allerdings kommt immerwieder "Gerät reagiert leider nicht)

Ein alexa-fhem -D -c /opt/fhem/alexa-fhem.cfg > debug.log über die kommandozeile funktioniert leider nicht:
[11/07/2020, 11:35:56] [FHEM] There was a problem connecting to FHEM (null)
[11/07/2020, 11:35:56] [FHEM]   401: Authorization Required


-D zum alexaFHEM-params attribut hinzufügen:

[11/07/2020, 11:46: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=c&XHR=1
[11/07/2020, 11:46:38] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":43107}
[11/07/2020, 11:46:38] Terminating - starting the listener not possible (another instance running?)
[11/07/2020, 11:46:39] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[11/07/2020, 11:46:40] os.homedir()=/opt/fhem
[11/07/2020, 11:46:40] this is alexa-fhem 0.5.55
[11/07/2020, 11:46:40] connecting to FHEM ...
[11/07/2020, 11:46:40] [FHEM] defaults to: will not send proactive events
[11/07/2020, 11:46:41] [FHEM] trying longpoll to listen for fhem events
[11/07/2020, 11:46:41] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594460801536
[11/07/2020, 11:46:41] [FHEM] got csrfToken: x
[11/07/2020, 11:46:41] [FHEM] Checking devices and attributes...
[11/07/2020, 11:46:41] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%xxy(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=o&XHR=1
[11/07/2020, 11:46:41] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=xr&XHR=1
[11/07/2020, 11:46:41] [FHEM] waiting for events ...
[11/07/2020, 11:46:41] [FHEM] Fetching FHEM devices...
[11/07/2020, 11:46:41] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=xr&XHR=1
[11/07/2020, 11:46:42] [FHEM] alexa device is alexa
[11/07/2020, 11:46:42] [FHEM] alexa will not send proactive events
[11/07/2020, 11:46:42] [FHEM] alexa uses ID: 5f0xxxx
[11/07/2020, 11:46: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.55%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=xr&XHR=1
[11/07/2020, 11:46: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=x&XHR=1
[11/07/2020, 11:46: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=x&XHR=1
[11/07/2020, 11:46:42] Server listening on: http://127.0.0.1:39079 for proxy connections
[11/07/2020, 11:46:42] *** SSH: checking proxy configuration
[11/07/2020, 11:46:42] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[11/07/2020, 11:46:42] 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":39079},"connections":[{"name":"FHEM","webname":"fhem","filter":"alexaName=..*","server":"127.0.0.1","port":"8083","uid":999}]}
[11/07/2020, 11:46:42] sshautoconf: SSH key seems to exist
[11/07/2020, 11:46:43] sshautoconf: Our SSH key is known at the reverse proxy, good!
[11/07/2020, 11:46: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=x&XHR=1
*** FHEM: connected
[11/07/2020, 11:46:43] [FHEM] got: 14 results
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung is switch
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung has
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung uses ID: 5db85d09-f33f-de02-f113-7cbd651a895ba0e6
  2020-07-11 11:46:43 caching: Aussenbeleuchtung-state: off
[11/07/2020, 11:46:43] [FHEM] Denon is switch
[11/07/2020, 11:46:43] [FHEM] Denon has
[11/07/2020, 11:46:43] [FHEM]   Custom Volume [volume;cached]
[11/07/2020, 11:46:43] [FHEM]   Mute [mute]
[11/07/2020, 11:46:43] [FHEM]   Custom Power [power]
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Denon will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Denon uses ID: 5c8a745b-f33f-de02-5af9-43776d8ef42c297c
  2020-07-11 11:46:43 caching: Denon-volume: 17.5
[11/07/2020, 11:46:43] [FHEM]     caching: Custom Volume: 18 (as number; from '17.5')
  2020-07-11 11:46:43 caching: Denon-mute: off
  2020-07-11 11:46:43 caching: Denon-power: on
[11/07/2020, 11:46:43] [FHEM] Denon-power not a number: on
  2020-07-11 11:46:43 caching: Denon-state: on
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l is light
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l has
[11/07/2020, 11:46:43] [FHEM]   PositionState [motor]
[11/07/2020, 11:46:43] [FHEM]   FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM]   CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM]   TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l will not send proactive events
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l uses ID: OEQ1312732
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-motor: stop:93.5
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-D-firmware: 2.11
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-pct: 93.5
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r is light
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r has
[11/07/2020, 11:46:43] [FHEM]   PositionState [motor]
[11/07/2020, 11:46:43] [FHEM]   FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM]   CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM]   TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r will not send proactive events
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r uses ID: OEQ1310914
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-motor: stop:on
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-D-firmware: 2.11
  2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-pct: 100
[11/07/2020, 11:46:43] [FHEM] FireTV is switch
[11/07/2020, 11:46:43] [FHEM] FireTV has
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] FireTV will not send proactive events
[11/07/2020, 11:46:43] [FHEM] FireTV uses ID: 5c8a745e-f33f-de02-1d89-4d08327f4b5d5b8a
  2020-07-11 11:46:43 caching: FireTV-state: on
[11/07/2020, 11:46:43] [FHEM] Garage_1 is switch
[11/07/2020, 11:46:43] [FHEM] Garage_1 has
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM]   valueOn [auf]
[11/07/2020, 11:46:43] [FHEM] Garage_1 will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Garage_1 uses ID: 5db3fe97-f33f-de02-9a3c-5b05b09ada6880e6
  2020-07-11 11:46:43 caching: Garage_1-state: on
[11/07/2020, 11:46:43] [FHEM] Garage_2 is switch
[11/07/2020, 11:46:43] [FHEM] Garage_2 has
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Garage_2 will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Garage_2 uses ID: 5db40275-f33f-de02-e1bd-d3649e5460ab6b30
  2020-07-11 11:46:43 caching: Garage_2-state: on
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima is thermostat
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima has
[11/07/2020, 11:46:43] [FHEM]   TargetTemperature [desired-temp]
[11/07/2020, 11:46:43] [FHEM]   Custom Actuation [ValvePosition]
[11/07/2020, 11:46:43] [FHEM]   CurrentTemperature [measured-temp]
[11/07/2020, 11:46:43] [FHEM]   CurrentHeatingCoolingState [undefined]
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima will not send proactive events
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima uses ID: CUL_HM.5FA47004
  2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-desired-temp: 5.0
  2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-ValvePosition: 0
[11/07/2020, 11:46:43] [FHEM]     caching: Custom Actuation: 0 (as number; from '0')
  2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-measured-temp: 17.3
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima is thermostat
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima has
[11/07/2020, 11:46:43] [FHEM]   TargetTemperature [desired-temp]
[11/07/2020, 11:46:43] [FHEM]   Custom Actuation [ValvePosition]
[11/07/2020, 11:46:43] [FHEM]   CurrentTemperature [measured-temp]
[11/07/2020, 11:46:43] [FHEM]   CurrentHeatingCoolingState [undefined]
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima will not send proactive events
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima uses ID: CUL_HM.5FA99D04
  2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-desired-temp: 24.0
  2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-ValvePosition: 100
[11/07/2020, 11:46:43] [FHEM]     caching: Custom Actuation: 100 (as number; from '100')
  2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-measured-temp: 21.7
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur is thermometer
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur has
[11/07/2020, 11:46:43] [FHEM]   StatusLowBattery [battery]
[11/07/2020, 11:46:43] [FHEM]   CurrentTemperature [temperature]
[11/07/2020, 11:46:43] [FHEM]   CurrentRelativeHumidity [humidity]
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur uses ID: 5c8e84b4-f33f-de02-9d27-615f1a8f73328845
  2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-battery: ok
  2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-temperature: 19.1
  2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-humidity: 46
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l is blind
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l has
[11/07/2020, 11:46:43] [FHEM]   PositionState [motor]
[11/07/2020, 11:46:43] [FHEM]   FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM]   CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM]   TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l will not send proactive events
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l uses ID: OEQ1312811
  2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-motor: stop:on
  2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-D-firmware: 2.11
  2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-pct: 100
[11/07/2020, 11:46:43] [FHEM] Poolheizung is thermometer
[11/07/2020, 11:46:43] [FHEM] Poolheizung has
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM]   CurrentTemperature [DS18B20-2_Temperature]
[11/07/2020, 11:46:43] [FHEM] Poolheizung will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Poolheizung uses ID: 5f052f05-f33f-de02-13af-b53ede879c3a52ef
  2020-07-11 11:46:43 caching: Poolheizung-state: on
  2020-07-11 11:46:43 caching: Poolheizung-DS18B20-2_Temperature: 21.25
[11/07/2020, 11:46:43] [FHEM] SATReceiver is light
[11/07/2020, 11:46:43] [FHEM] SATReceiver has
[11/07/2020, 11:46:43] [FHEM]   Custom Volume [volume;cached]
[11/07/2020, 11:46:43] [FHEM]   Mute [mute]
[11/07/2020, 11:46:43] [FHEM]   Custom Power [power]
[11/07/2020, 11:46:43] [FHEM]   On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] SATReceiver will not send proactive events
[11/07/2020, 11:46:43] [FHEM] SATReceiver uses ID: 5c8a745c-f33f-de02-2e1a-a7c3160eec5522aa
  2020-07-11 11:46:43 caching: SATReceiver-volume: 100
[11/07/2020, 11:46:43] [FHEM]     caching: Custom Volume: 100 (as number; from '100')
  2020-07-11 11:46:43 caching: SATReceiver-mute: -
  2020-07-11 11:46:43 caching: SATReceiver-power: off
[11/07/2020, 11:46:43] [FHEM] SATReceiver-power not a number: off
  2020-07-11 11:46:43 caching: SATReceiver-state: off
[11/07/2020, 11:46:44] [FHEM] Strassenbewaesserung: no service type detected
[11/07/2020, 11:46:44] [FHEM] no device created for Strassenbewaesserung (MQTT_DEVICE)
[11/07/2020, 11:46:44] BearerToken '...B181F' read from alexa
[11/07/2020, 11:46:44] [FHEM] got .eventToken
[11/07/2020, 11:46:44] refreshing token
[11/07/2020, 11:46:44] 39_alexa.pm is new version: true
[11/07/2020, 11:46:44] sshautoconf: completed successfully
[11/07/2020, 11:46:44] *** SSH: proxy configuration set up done
[11/07/2020, 11:46:44] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[11/07/2020, 11:46: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%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:44] Starting SSH with -R 1234:127.0.0.1:39079 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[11/07/2020, 11:46:44] got fresh token
[11/07/2020, 11:46:45] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[11/07/2020, 11:46: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%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:45] *** SSH: proxy connection established
[11/07/2020, 11:46:45] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
  2020-07-11 11:46:50 caching: Mebus_Aussentemperatur-temperature: 19.0
[11/07/2020, 11:46:50] [FHEM]     caching: CurrentTemperature: 19 (as number; from '19.0')


Hoffe ich habe hier keine sicherheitsrelevanten Sachen im Log den csrf Token habe ich geändert.

Was habe ich schon alles gemacht:
Node Js komplett deinstalliert:

sudo rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* /usr/local/lib/dtrace/node.d ~/.npm ~/.node-gyp /opt/local/bin/node /opt/local/include/node /opt/local/lib/node_modules

sudo rm -rf /usr/local/lib/node*

sudo rm -rf /usr/local/include/node*

sudo rm -rf /usr/local/bin/node*


Node Node.js v14 installiert:
curl -sL https://deb.nodesource.com/setup_14.x | bash -
apt-get install -y nodejs


Danach musste alexa-fhem neu installiert werden:
sudo npm install -g alexa-fhem

nach einem Neustart vom pi war dann auch wieder alexa aktiviert.

Device in FHEM gelöscht und am Server unregister
sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister

Den Skill in der App deaktiviert und neu registriert.

Ein List alexa:

Save config ?
1_Wohnzimmer
2_ROLLLADEN
3_Handy
4_Beregnung
5_SYSTEM
6_Heizung
7_Alexa
8_Amazon
CUL_HM
CUL_TCM97001
CUL_WS
ESPEasy
FLAMINGO
IT
MQTT2_DEVICE
OREGON
Plots
SD_BELL
SD_UT
SD_WS
SD_WS07
SIGNALduino_un
Unsorted
Wetter-vorhersage
icoEverything Everything
Logfile
Commandref
Remote doc
Edit files
Select style
Event monitor
Update
UpdateCheck
Restart

Internals:
   FD         13
   FUUID      5f094ae8-f33f-de02-b693-32cc3527f13fa79f
   FVERSION   39_alexa.pm:0.216510/2020-04-12
   LAST_START 2020-07-11 11:46:38
   LAST_STOP  2020-07-11 11:46:38
   NAME       alexa
   NOTIFYDEV  global,global:npmjs.*alexa-fhem.*
   NR         658
   NTFY_ORDER 50-alexa
   PARTIAL   
   PID        2008
   STARTS     9
   STATE      running /usr/bin/alexa-fhem
   TYPE       alexa
   active     0
   alexa-fhem version 0.5.55
   currentlogfile ./log/alexa-2020-07-11.log
   logfile    ./log/alexa-%Y-%m-%d.log
   CoProcess:
     cmdFn      alexa_getCMD
     name       alexaFHEM
     state      running /usr/bin/alexa-fhem
   READINGS:
     2020-07-11 11:46:38   alexaFHEM       running /usr/bin/alexa-fhem
     2020-07-11 11:46:45   alexaFHEM.ProxyConnection running; SSH connected
     2020-07-11 07:15:59   alexaFHEM.bearerToken crypt:xxxxxxx
     2020-07-11 07:15:59   alexaFHEM.skillRegKey crypt:xxxxxxx
   helper:
Attributes:
   alexaFHEM-auth crypt:xxxx
   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
   persons    #<personId>=<name>

   room       7_Alexa
   stateFormat alexaFHEM
   verbose    5



Token und key habe ich hier mit x versehen.


Was kann ich noch testen?

Habe allowed_WEB in verdacht mir dazwischen zu funken, komisch nur das es mal funktioniert und dann mal wieder nicht.

Im Log Das
[11/07/2020, 11:46:38] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":43107}
[11/07/2020, 11:46:38] Terminating - starting the listener not possible (another instance running?)


Ist das ein Hinweis das irgendwie eine 2 Instanz von alexa Läuft? wenn ja wie bekomme ich raus wie ich diese beende?

ein
ps -ef | grep alexa
liefert:
fhem      2008   500  0 11:46 ?        00:00:10 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
root      2870  1088  0 12:16 pts/0    00:00:00 grep alexa

zurück.

Gruß Karsten
FHEM 5.8 auf Raspberry Pi 3, HM-MOD-UART und  MapleCUN.
HM-MOD-Re-8 für Velux Rolladensteuerung.
HM-CC-RT-DN.
HM-SEC-SCo.
HM-LC-Bl1PBU-FM.

gvzdus

Vorab: Ich hoffe, Du hast nicht zu viel "gebastelt". Meist hakt es nämlich deswegen.

Zur Fehlermeldung: "Address in use": Der nodejs-Prozess macht einen Port auf, über den er vom SSH-Prozess Requests entgegennimmt. Die Kette auf dem Raspi etc. ist also:
fhem <-> alexa-fhem <-> SSH.
Dafür, dass die Kommunikation fhem <-> alexa-fhem nicht klappt, gibt es in Deinem Logfile keine Anzeichen. Die Geräte werden ja von alexa-fhem sauber gelesen. Die Fehlermeldung wird beim Start der "alexa-fhem <-> SSH"-Strecke erzeugt, führt aber dazu, dass sich alexa-fhem beendet und einen neuen Versuch macht. Eigentlich wird der Port "ausgewürfelt" und sollte daher frei sein. Wenn Du allerdings in Deiner alexa-fhem.cfg irgendeinen Port fest konfiguriert hast ("port" unter "sshproxy"), dann ist natürlich nicht gesagt, dass dieser Port auch frei ist. Dann würde ich das Setting löschen.

Ob nun 2 Prozesse laufen oder nicht, solltest Du mit "ps" ja feststellen können.

coolheizer

#958
Hallo gvzdus,

ja sitze schon Tagelang an dem Problem, keine Ahnung was ich schon alles erfolglos versucht habe.

Hatte gerade die Sicherung vom letzten Jahr aufgespielt, damit klappt es leider auch nicht.

Wenn ich Geräte schalten möchte kommt " Gerät reagiert leider nicht" teilweise wird dann minuten später dann doch geschaltet.


ein ps -ef | egrep '(alexa|ssh)'

Liefert pi@raspberrypi:~ $ ps -ef | egrep '(alexa|ssh)'
root       475     1  0 09:20 ?        00:00:00 /usr/sbin/sshd -D
root       664   475  0 09:21 ?        00:00:00 sshd: root@notty
root       689   664  0 09:21 ?        00:00:00 /usr/lib/openssh/sftp-server
root       873   475  0 09:25 ?        00:00:03 sshd: root@pts/0
fhem      5399  5180  0 10:49 ?        00:00:07 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
fhem      5411  5399  0 10:49 ?        00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:44003 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root      6013   475  0 11:03 ?        00:00:00 sshd: pi [priv]
pi        6042  6013  0 11:03 ?        00:00:00 sshd: pi@pts/1
pi        6655  6045  0 11:14 pts/1    00:00:00 grep -E --color=auto (alexa|ssh)
pi@raspberrypi:~ $


und ein ps -e
pi@raspberrypi:~ $ ps -e
  PID TTY          TIME CMD
    1 ?        00:00:04 systemd
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 rcu_gp
    4 ?        00:00:00 rcu_par_gp
    8 ?        00:00:00 mm_percpu_wq
    9 ?        00:00:01 ksoftirqd/0
   10 ?        00:00:05 rcu_sched
   11 ?        00:00:00 rcu_bh
   12 ?        00:00:00 migration/0
   13 ?        00:00:00 cpuhp/0
   14 ?        00:00:00 cpuhp/1
   15 ?        00:00:00 migration/1
   16 ?        00:00:00 ksoftirqd/1
   18 ?        00:00:01 kworker/1:0H-kblockd
   19 ?        00:00:00 cpuhp/2
   20 ?        00:00:00 migration/2
   21 ?        00:00:00 ksoftirqd/2
   23 ?        00:00:01 kworker/2:0H-kblockd
   24 ?        00:00:00 cpuhp/3
   25 ?        00:00:00 migration/3
   26 ?        00:00:00 ksoftirqd/3
   29 ?        00:00:00 kdevtmpfs
   30 ?        00:00:00 netns
   34 ?        00:00:00 khungtaskd
   35 ?        00:00:00 oom_reaper
   36 ?        00:00:00 writeback
   37 ?        00:00:00 kcompactd0
   38 ?        00:00:00 crypto
   39 ?        00:00:00 kblockd
   40 ?        00:00:00 watchdogd
   42 ?        00:00:00 rpciod
   43 ?        00:00:00 kworker/u9:0-hci0
   44 ?        00:00:00 xprtiod
   47 ?        00:00:06 kswapd0
   48 ?        00:00:00 nfsiod
   59 ?        00:00:00 kthrotld
   60 ?        00:00:00 iscsi_eh
   61 ?        00:00:00 dwc_otg
   62 ?        00:00:00 DWC Notificatio
   63 ?        00:00:00 vchiq-slot/0
   64 ?        00:00:00 vchiq-recy/0
   65 ?        00:00:00 vchiq-sync/0
   66 ?        00:00:00 vchiq-keep/0
   67 ?        00:00:00 SMIO
   69 ?        00:00:00 irq/86-mmc1
   71 ?        00:00:00 mmc_complete
   75 ?        00:00:01 kworker/3:1H-kblockd
   76 ?        00:00:00 jbd2/mmcblk0p2-
   77 ?        00:00:00 ext4-rsv-conver
   81 ?        00:00:00 ipv6_addrconf
  122 ?        00:00:04 systemd-journal
  128 ?        00:00:00 irq/166-usb-001
  142 ?        00:00:00 systemd-udevd
  177 ?        00:00:00 SMIO
  187 ?        00:00:00 mmal-vchiq
  188 ?        00:00:00 mmal-vchiq
  189 ?        00:00:00 mmal-vchiq
  220 ?        00:00:00 cfg80211
  225 ?        00:00:00 brcmf_wq/mmc1:0
  226 ?        00:00:00 brcmf_wdog/mmc1
  260 ?        00:00:00 systemd-timesyn
  297 ?        00:00:00 alsactl
  299 ?        00:00:00 systemd-logind
  301 ?        00:00:00 cron
  302 ?        00:00:00 thd
  305 ?        00:00:09 avahi-daemon
  306 ?        00:00:01 rsyslogd
  307 ?        00:00:10 rngd
  315 ?        00:00:00 dbus-daemon
  316 ?        00:00:00 wpa_supplicant
  356 ?        00:00:00 avahi-daemon
  393 ?        00:00:00 wpa_supplicant
  457 ?        00:00:00 dhcpcd
  459 ?        00:01:14 java
  462 ?        00:00:03 mosquitto
  465 tty1     00:00:00 agetty
  471 ?        00:00:00 hciattach
  473 ?        00:00:00 kworker/u9:2-hci0
  475 ?        00:00:00 sshd
  476 ?        00:00:00 bluetoothd
  664 ?        00:00:00 sshd
  670 ?        00:00:00 systemd
  673 ?        00:00:00 (sd-pam)
  689 ?        00:00:00 sftp-server
  873 ?        00:00:03 sshd
  884 pts/0    00:00:00 bash
3101 ?        00:00:03 kworker/u8:1+events_unbound
4834 ?        00:00:01 kworker/0:2H-mmc_complete
4891 ?        00:00:00 kworker/u8:2-events_unbound
5180 ?        00:04:10 perl
5289 ?        00:00:00 kworker/1:0-mm_percpu_wq
5399 ?        00:00:07 node
5411 ?        00:00:00 ssh
5608 ?        00:00:00 kworker/3:0-mm_percpu_wq
5910 ?        00:00:00 kworker/0:1-mm_percpu_wq
5935 ?        00:00:00 kworker/0:1H
5962 ?        00:00:00 kworker/3:1-mm_percpu_wq
6013 ?        00:00:00 sshd
6021 ?        00:00:00 kworker/3:0H
6022 ?        00:00:00 kworker/1:2H
6023 ?        00:00:00 systemd
6026 ?        00:00:00 (sd-pam)
6042 ?        00:00:00 sshd
6045 pts/1    00:00:00 bash
6098 ?        00:00:00 kworker/2:0-events
6197 ?        00:00:00 kworker/1:1-mm_percpu_wq
6248 ?        00:00:00 kworker/0:2-events
6399 ?        00:00:00 kworker/2:2H
6424 ?        00:00:00 kworker/2:1-events_freezable
6475 ?        00:00:00 kworker/3:2H
6476 ?        00:00:00 kworker/1:1H
6503 ?        00:00:00 kworker/3:2
6504 ?        00:00:00 kworker/0:0H
6529 ?        00:00:00 kworker/1:2
6556 ?        00:00:00 kworker/0:0-events
6680 pts/1    00:00:00 ps
pi@raspberrypi:~ $


War das mit "ps" jetzt richtig?

Kann mit der Auflistung leider nix so richtig anfangen, hoffe dir sagt das etwas.

Noch Ideen was ich noch versuchen kann?


Edit sagt:

An der alexa-fhem.cfg hatt ich nicht rum gespielt, hatte sie aber trotzdem auch schon auf Standart zurück gesetzt.

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


pps.
Könnte es sein das am Vereinsserver irgendetwas mit meiner Verbindung nicht hinhaut, die Daten zu langsam zurück gesendet werden?
FHEM 5.8 auf Raspberry Pi 3, HM-MOD-UART und  MapleCUN.
HM-MOD-Re-8 für Velux Rolladensteuerung.
HM-CC-RT-DN.
HM-SEC-SCo.
HM-LC-Bl1PBU-FM.

gvzdus

Das sieht alles gut und richtig aus. An dem "-L"-Parameter von ssh sehe ich auch, dass der lokale Port dynamisch ausgewürfelt wird.
Du schreibst "Über LTE". Die Mobilfunkanbieter haben oft NAT-Devices / Firewalls, die nach sehr kurzer Zeit eine "stehende" TCP-Verbindung (wie zum Vereinsserver aufgebaut) vergessen. Dann kann der Vereinsserver Dich nicht kontaktieren. Die mit "-oServerAliveInterval=90" angegebenen 90 Sekunden für das "Ping" zum Vereinsserver *sollten* eigentlich reichen. Du kannst sie aber mal versuchsweise z.B. auf 30 Sekunden anpassen:

/usr/lib/node_modules/alexa-fhem/lib/server.js

Alternative: Du nennst mir (ggf. per Pmail - ist aber nicht so kritisch) die erste HEX-Gruppe (8 Zeichen bis zum 1. Bindestrich) von Deinem Proxy-Key - quasi Deine "User-ID"  *und* einen Zeitpunkt des "Reagiert nicht". Dann gucke ich mal auf dem Server nach. Kommando: "get alexa proxyKey"