FHEM Forum

Hallo,

ich habe erfolgreich das Alexa-Fhem Connector Modul am laufen. Es funktioniert auch alles.

Allerdings erhalte ich ständig Meldungen im Logfile von einem Neustart von alexa-fhem

2019.01.27 09:40:59 3: alexa: read: end of file reached while sysread
2019.01.27 09:40:59 3: alexa: alexaFHEM stopped
2019.01.27 09:40:59 3: alexa: alexaFHEM starting
2019.01.27 09:40:59 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
2019.01.27 09:40:59 3: alexa: using logfile: ./log/alexa-2019-01-27.log
2019.01.27 09:41:20 3: alexa: read: end of file reached while sysread
2019.01.27 09:41:20 3: alexa: alexaFHEM stopped
2019.01.27 09:41:40 3: alexa: alexaFHEM starting
2019.01.27 09:41:40 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
2019.01.27 09:41:40 3: alexa: using logfile: ./log/alexa-2019-01-27.log



Das ist der Auszug aus dem Logfile

[2019-1-27 09:41:04] BearerToken '...609FA' read from alexa
[2019-1-27 09:41:04] 39_alexa.pm is new version: true
[2019-1-27 09:41:04] sshautoconf: completed successfully
[2019-1-27 09:41:04] *** SSH: proxy configuration set up done
[2019-1-27 09:41:04] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-1-27 09:41: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%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:04] Starting SSH with -R 1234:127.0.0.1:40705 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-1-27 09:41:04] [FHEM] got .eventToken
[2019-1-27 09:41:04] refreshing token
[2019-1-27 09:41:04] got fresh token
[2019-1-27 09:41:04] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-1-27 09:41: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%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:04] *** SSH: proxy connection established
[2019-1-27 09:41:04] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-1-27 09:41:19] [FHEM] longpoll ended, reconnect in: 200msec
[2019-1-27 09:41:20] [FHEM] trying longpoll to listen for fhem events
[2019-1-27 09:41:20] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1548578480027
[2019-1-27 09:41:20] [FHEM] got csrfToken: lassmichrein
[2019-1-27 09:41:20] [FHEM] Checking devices and attributes...
[2019-1-27 09:41:20] [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%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:20] [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%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:20] [FHEM] waiting for events ...
[2019-1-27 09:41:20] [FHEM] Fetching FHEM devices...
[2019-1-27 09:41:20] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:20] [FHEM] alexa device is alexa
[2019-1-27 09:41:20] [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.13%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:20] [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=lassmichrein&XHR=1
[2019-1-27 09:41:20] [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=lassmichrein&XHR=1
[2019-1-27 09:41:20] Server emitted error: {"errno":"EADDRINUSE","code":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":40705}
[2019-1-27 09:41:20] Terminating - starting the listener not possible (another instance running?)
[2019-1-27 09:41:41] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-1-27 09:41:41] os.homedir()=/opt/fhem
[2019-1-27 09:41:41] this is alexa-fhem 0.5.13
[2019-1-27 09:41:41] connecting to FHEM ...
[2019-1-27 09:41:42] [FHEM] trying longpoll to listen for fhem events
[2019-1-27 09:41:42] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1548578502762
[2019-1-27 09:41:42] [FHEM] got csrfToken: lassmichrein
[2019-1-27 09:41:42] [FHEM] Checking devices and attributes...
[2019-1-27 09:41:42] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:42] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:43] [FHEM] waiting for events ...
[2019-1-27 09:41:43] [FHEM] Fetching FHEM devices...
[2019-1-27 09:41:43] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:43] [FHEM] alexa device is alexa
[2019-1-27 09:41: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%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.13%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 09:41:43] Server listening on: http://127.0.0.1:44604 for proxy connections
[2019-1-27 09:41:43] *** SSH: checking proxy configuration
[2019-1-27 09:41:43] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-1-27 09:41:43] 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":44604},"connections":[{"uid":999,"server":"127.0.0.1","filter":"alexaName=..*","port":"8083","name":"FHEM","webname":"fhem"}]}
[2019-1-27 09:41:43] sshautoconf: SSH key seems to exist
[2019-1-27 09:41:44] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-1-27 09:41: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%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
*** FHEM: connected


Woran könnte das liegen?

Gruß Albi

Unglücklich ist alexa-fhem auf jeden Fall hier:

[2019-1-27 09:41:20] Server emitted error: {"errno":"EADDRINUSE","code":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":40705}
[2019-1-27 09:41:20] Terminating - starting the listener not possible (another instance running?)


Das ist aber schon sonderbar, denn selbst, wenn mehrere Prozesse laufen sollten, dürfte es eigentlich kein derartiges Problem verursachen, da der Listener-Port bei jedem Start neu "ausgewürfelt" wird. Prüfungsbitte 1 trotzdem: Wenn Du mit "ps -ef | grep alexa" guckst: Läuft da auch definitiv stets maximal 1 Prozess?

hast du jedes mal die EADDRINUSE meldung?

Hallo,

ja die Meldung wiederholt sich

[2019-1-27 17:40:30] [FHEM] longpoll ended, reconnect in: 200msec
[2019-1-27 17:40:30] [FHEM] trying longpoll to listen for fhem events
[2019-1-27 17:40:30] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=1548607215.028;fmt=JSON&timestamp=1548607230644
[2019-1-27 17:40:57] [FHEM] got csrfToken: lassmichrein
[2019-1-27 17:40:57] [FHEM] Checking devices and attributes...
[2019-1-27 17:40:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] [FHEM] waiting for events ...
[2019-1-27 17:40:57] [FHEM] Fetching FHEM devices...
[2019-1-27 17:40:57] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] [FHEM] alexa device is alexa
[2019-1-27 17:40:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.13%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=lassmichrein&XHR=1
[2019-1-27 17:40:57] Server emitted error: {"errno":"EADDRINUSE","code":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":41070}
[2019-1-27 17:40:57] Terminating - starting the listener not possible (another instance running?)
[2019-1-27 17:40:59] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely


Dieser "Neustart" Wiederholt sich immer genau stündlich...

Also momentan 16:40 - 17:40 - 18:40 usw usw

ich habe gerade keine idee...

eigentlich kann das nicht passieren das der proxy listener den port selber bestimmt und hier den nächsten freien nimmt. das der dann belegt ist sollte nicht passieren.

du hast nicht zufällig noch einen alten autostart laufen?

Hmm,

Konnte es sein, dass ich alexa fhem mit der "alten" Methode noch irgendwo mit drinnen habe.

Wie kann ich schauen ob Alexa-Fhem mehrmals gestartet wurde/wird

Da war doch irgenwas mit rc-update?


Vielleicht startet der raspberry tatsächlich Alexa-Fhem mehrmals


Ich mache mich mal auf die Suche....

Gruß Albi

Hi,
Gibt es hierzu schon neue Erkenntnisse?
Auch bei mir gibt es stündlich Neustarts bzw Reconnects.
Ich hatte bisher keinen Alexa Fhem Skill in Benutzung, eine Überschneidung bzw Reste einer alten Installation kann ich daher ausschließen.

Grüße
Michael

und du hast die gleichen log meldungen?

Hier mal ein Auszug aus dem Log
2.2019, 04:02:56] [FHEM] longpoll ended, reconnect in: 200msec
[5.2.2019, 04:02:57] [FHEM] trying longpoll to listen for fhem events
[5.2.2019, 04:02:57] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=1549335647.644;fmt=JSON&timestamp=1549335777004
[5.2.2019, 04:03:05] [FHEM] got csrfToken: aRg7Bx39fF
[5.2.2019, 04:03:05] [FHEM] Checking devices and attributes...
[5.2.2019, 04:03: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%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=aRg7Bx39fF&XHR=1
[5.2.2019, 04:03: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%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=aRg7Bx39fF&XHR=1
[5.2.2019, 04:03:05] [FHEM] waiting for events ...
[5.2.2019, 04:03:05] [FHEM] Fetching FHEM devices...
[5.2.2019, 04:03:05] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=aRg7Bx39fF&XHR=1
[5.2.2019, 04:03:05] [FHEM] alexa device is alexa


Passiert stündlich fast auf Sekunde genau.

/Michael

das ist kein neustart sondern nur ein reconnect für longpoll.

das ist normal und kein problem.

OK, Danke für die Info.
Hatte mich nur verwundert das ich diese stündlichen Meldungen auf meinem Testsystem nicht habe.

Wie kann man denn das Logging reduzieren oder ausschalten? Attr verbose 0 scheint jedenfalls keinen Einfluss zu haben.

/Michael

Da es auf meinem Testsystem keine longpoll reconnects gab und ich auf dem Produktionssystem in letzter Zeit auch vermehrt Reconnects des HMLan hatte, habe ich das ganze mal näher analysiert.
Die longpoll reconnects gingen immer einher mit einem Neustart von alexa-fhem und auch die EADDRINUSE Meldungen fanden sich regelmäßig in den Logs. Auffällig war, das diese Reconnects stündlich fast auf die Minute genau erfolgten und auch die Reconnects des HMLan zeitnah erfolgten. Ich könnte schließlich das Weather Modul in Verbindung mit der OpenWeatherMapAPI als Übeltäter identifizieren. Bei deaktiviertem Weather Modul gibt es weder longpoll reconnects noch Neustarts von Alexa-fhem und auch die Reconnects des HMLan sind verschwunden.

/Michael

die reinen longpoll reconnects sind in so weit normal weil die http connection nach einer weile zu gemacht werden muss da alle aufgelaufenen daten zwischengespeichert werden. der unterschied von test und produktivsystem ist vermutlich die menge an events. bei websocket ist das nicht nötig. das wäre eine option.

das EADDRINUSE ist aber ein problem. der hinweis auf WEATHER ist aber gut. mir ist vor einiger zeit ein problem mit fork im weather modul bemerkt und das hier könnte damit zusammen hängen.

Zitat von: justme1968 am 08 Februar 2019, 16:20:36
der hinweis auf WEATHER ist aber gut. mir ist vor einiger zeit ein problem mit fork im weather modul bemerkt und das hier könnte damit zusammen hängen.

Habe das Thema auf dem Schirm. Bin derzeit nur sehr eingeschränkt in der Lage, mich mit FHEM zu befassen. Ich sehe mir zu gegebener Zeit an, wie ich die fork-Sache überarbeite.

Grüße
Boris

Hallo zusammen,

ich habe ebenfalls das Problem mit den EADDRINUSE Meldungen.
Diese treten bei mir allerdings minütlich auf.

Das Weather Modul habe ich bereits auf disabled gesetzt - das Problem besteht aber weiterhin.
Gibt es hier noch weitere Erkenntnisse/Ideen?

[2019-4-15 14:39:40] [FHEM] got: 0 results
[2019-4-15 14:39:40] [FHEM] got .eventToken
[2019-4-15 14:39:40] refreshing token
[2019-4-15 14:39:40] 39_alexa.pm is new version: true
[2019-4-15 14:39:40] sshautoconf: completed successfully
[2019-4-15 14:39:40] *** SSH: proxy configuration set up done
[2019-4-15 14:39:40] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:39: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%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:39:40] Starting SSH with -R 1234:127.0.0.1:38929 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:39:40] BearerToken '...7072A' read from alexa
[2019-4-15 14:39:40] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:39: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%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:39:40] *** SSH: proxy connection established
[2019-4-15 14:39:40] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:39:40] got fresh token
[2019-4-15 14:40:36] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:40:36] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:40:36] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332036785
[2019-4-15 14:40:38] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:40:38] [FHEM] Checking devices and attributes...
[2019-4-15 14:40: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%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40: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%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:38] [FHEM] waiting for events ...
[2019-4-15 14:40:38] [FHEM] Fetching FHEM devices...
[2019-4-15 14:40:38] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:42] [FHEM] alexa device is alexa
[2019-4-15 14:40: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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40: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=myhcconnToken&XHR=1
[2019-4-15 14:40: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=myhcconnToken&XHR=1
[2019-4-15 14:40:42] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":38929}
[2019-4-15 14:40:42] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:40:43] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:40:43] os.homedir()=/opt/fhem
[2019-4-15 14:40:43] this is alexa-fhem 0.5.26
[2019-4-15 14:40:43] connecting to FHEM ...
[2019-4-15 14:40:43] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:40:43] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332043651
[2019-4-15 14:40:43] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:40:43] [FHEM] Checking devices and attributes...
[2019-4-15 14:40:43] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:43] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:43] [FHEM] waiting for events ...
[2019-4-15 14:40:43] [FHEM] Fetching FHEM devices...
[2019-4-15 14:40:43] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:40:43] [FHEM] got: 0 results
[2019-4-15 14:40:43] [FHEM] alexa device is alexa
[2019-4-15 14:40: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%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:44] Server listening on: http://127.0.0.1:33209 for proxy connections
[2019-4-15 14:40:44] *** SSH: checking proxy configuration
[2019-4-15 14:40:44] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:40:44] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":33209}}
[2019-4-15 14:40:44] sshautoconf: SSH key seems to exist
[2019-4-15 14:40:44] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:40: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%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:44] 39_alexa.pm is new version: true
[2019-4-15 14:40:44] sshautoconf: completed successfully
[2019-4-15 14:40:44] *** SSH: proxy configuration set up done
[2019-4-15 14:40:44] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:40: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=myhcconnToken&XHR=1
[2019-4-15 14:40:44] Starting SSH with -R 1234:127.0.0.1:33209 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:40:44] [FHEM] got .eventToken
[2019-4-15 14:40:44] refreshing token
[2019-4-15 14:40:44] BearerToken '...7072A' read from alexa
[2019-4-15 14:40:44] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:40: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%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:40:44] *** SSH: proxy connection established
[2019-4-15 14:40:44] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:40:44] got fresh token
[2019-4-15 14:41:39] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:41:39] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:41:39] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332099777
[2019-4-15 14:41:41] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:41:41] [FHEM] Checking devices and attributes...
[2019-4-15 14:41:41] [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%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:41] [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%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:41] [FHEM] waiting for events ...
[2019-4-15 14:41:41] [FHEM] Fetching FHEM devices...
[2019-4-15 14:41:41] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:44] [FHEM] alexa device is alexa
[2019-4-15 14:41: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%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:44] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":33209}
[2019-4-15 14:41:44] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:41:45] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:41:45] os.homedir()=/opt/fhem
[2019-4-15 14:41:45] this is alexa-fhem 0.5.26
[2019-4-15 14:41:45] connecting to FHEM ...
[2019-4-15 14:41:45] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:41:45] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332105695
[2019-4-15 14:41:45] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:41:45] [FHEM] Checking devices and attributes...
[2019-4-15 14:41:45] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:45] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:45] [FHEM] waiting for events ...
[2019-4-15 14:41:45] [FHEM] Fetching FHEM devices...
[2019-4-15 14:41:45] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:45] [FHEM] alexa device is alexa
[2019-4-15 14:41: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%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:46] Server listening on: http://127.0.0.1:43565 for proxy connections
[2019-4-15 14:41:46] *** SSH: checking proxy configuration
[2019-4-15 14:41:46] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:41:46] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":43565}}
[2019-4-15 14:41:46] sshautoconf: SSH key seems to exist
[2019-4-15 14:41:46] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:41: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%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:41:46] [FHEM] got: 0 results
[2019-4-15 14:41:46] [FHEM] got .eventToken
[2019-4-15 14:41:46] refreshing token
[2019-4-15 14:41:46] BearerToken '...7072A' read from alexa
[2019-4-15 14:41:46] 39_alexa.pm is new version: true
[2019-4-15 14:41:46] sshautoconf: completed successfully
[2019-4-15 14:41:46] *** SSH: proxy configuration set up done
[2019-4-15 14:41:46] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:41: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%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:46] Starting SSH with -R 1234:127.0.0.1:43565 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:41:46] got fresh token
[2019-4-15 14:41:46] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:41: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%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:41:46] *** SSH: proxy connection established
[2019-4-15 14:41:46] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:42:42] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:42:42] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:42:42] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332162786
[2019-4-15 14:42:44] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:42:44] [FHEM] Checking devices and attributes...
[2019-4-15 14:42: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%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42: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%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:44] [FHEM] waiting for events ...
[2019-4-15 14:42:44] [FHEM] Fetching FHEM devices...
[2019-4-15 14:42:44] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:46] [FHEM] alexa device is alexa
[2019-4-15 14:42: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%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:46] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":43565}
[2019-4-15 14:42:46] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:42:47] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:42:47] os.homedir()=/opt/fhem
[2019-4-15 14:42:47] this is alexa-fhem 0.5.26
[2019-4-15 14:42:47] connecting to FHEM ...
[2019-4-15 14:42:48] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:42:48] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332168254
[2019-4-15 14:42:48] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:42:48] [FHEM] Checking devices and attributes...
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] [FHEM] waiting for events ...
[2019-4-15 14:42:48] [FHEM] Fetching FHEM devices...
[2019-4-15 14:42:48] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] [FHEM] alexa device is alexa
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] Server listening on: http://127.0.0.1:40553 for proxy connections
[2019-4-15 14:42:48] *** SSH: checking proxy configuration
[2019-4-15 14:42:48] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:42:48] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":40553}}
[2019-4-15 14:42:48] sshautoconf: SSH key seems to exist
[2019-4-15 14:42:48] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:42:48] [FHEM] got: 0 results
[2019-4-15 14:42:48] [FHEM] got .eventToken
[2019-4-15 14:42:48] refreshing token
[2019-4-15 14:42:48] BearerToken '...7072A' read from alexa
[2019-4-15 14:42:48] 39_alexa.pm is new version: true
[2019-4-15 14:42:48] sshautoconf: completed successfully
[2019-4-15 14:42:48] *** SSH: proxy configuration set up done
[2019-4-15 14:42:48] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:42:48] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:48] Starting SSH with -R 1234:127.0.0.1:40553 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:42:49] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:42:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:42:49] *** SSH: proxy connection established
[2019-4-15 14:42:49] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:42:49] got fresh token
[2019-4-15 14:43:45] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:43:45] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:43:45] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332225738
[2019-4-15 14:43:47] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:43:47] [FHEM] Checking devices and attributes...
[2019-4-15 14:43:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:47] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:47] [FHEM] waiting for events ...
[2019-4-15 14:43:47] [FHEM] Fetching FHEM devices...
[2019-4-15 14:43:47] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:49] [FHEM] alexa device is alexa
[2019-4-15 14:43:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:49] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":40553}
[2019-4-15 14:43:49] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:43:50] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:43:50] os.homedir()=/opt/fhem
[2019-4-15 14:43:50] this is alexa-fhem 0.5.26
[2019-4-15 14:43:50] connecting to FHEM ...
[2019-4-15 14:43:51] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:43:51] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332231097
[2019-4-15 14:43:51] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:43:51] [FHEM] Checking devices and attributes...
[2019-4-15 14:43:51] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:51] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:51] [FHEM] waiting for events ...
[2019-4-15 14:43:51] [FHEM] Fetching FHEM devices...
[2019-4-15 14:43:51] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:43:51] [FHEM] got: 0 results
[2019-4-15 14:43:51] [FHEM] alexa device is alexa
[2019-4-15 14:43:51] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:43:51] [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=myhcconnToken&XHR=1
[2019-4-15 14:43:51] [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=myhcconnToken&XHR=1
[2019-4-15 14:43:51] Server listening on: http://127.0.0.1:36177 for proxy connections
[2019-4-15 14:43:51] *** SSH: checking proxy configuration
[2019-4-15 14:43:51] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:43:51] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":36177}}
[2019-4-15 14:43:51] sshautoconf: SSH key seems to exist
[2019-4-15 14:43:51] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:43:51] [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=myhcconnToken&XHR=1
[2019-4-15 14:43:51] 39_alexa.pm is new version: true
[2019-4-15 14:43:51] sshautoconf: completed successfully
[2019-4-15 14:43:51] *** SSH: proxy configuration set up done
[2019-4-15 14:43:51] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:43:51] [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=myhcconnToken&XHR=1
[2019-4-15 14:43:51] Starting SSH with -R 1234:127.0.0.1:36177 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:43:51] BearerToken '...7072A' read from alexa
[2019-4-15 14:43:51] [FHEM] got .eventToken
[2019-4-15 14:43:51] refreshing token
[2019-4-15 14:43:52] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:43:52] [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=myhcconnToken&XHR=1
[2019-4-15 14:43:52] *** SSH: proxy connection established
[2019-4-15 14:43:52] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:43:52] got fresh token
[2019-4-15 14:44:48] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:44:48] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:44:48] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332288787
[2019-4-15 14:44:50] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:44:50] [FHEM] Checking devices and attributes...
[2019-4-15 14:44:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:50] [FHEM] waiting for events ...
[2019-4-15 14:44:50] [FHEM] Fetching FHEM devices...
[2019-4-15 14:44:50] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:52] [FHEM] alexa device is alexa
[2019-4-15 14:44:52] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:52] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:52] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:52] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":36177}
[2019-4-15 14:44:52] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:44:53] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:44:53] os.homedir()=/opt/fhem
[2019-4-15 14:44:53] this is alexa-fhem 0.5.26
[2019-4-15 14:44:53] connecting to FHEM ...
[2019-4-15 14:44:54] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:44:54] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332294249
[2019-4-15 14:44:54] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:44:54] [FHEM] Checking devices and attributes...
[2019-4-15 14:44:54] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:54] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:54] [FHEM] waiting for events ...
[2019-4-15 14:44:54] [FHEM] Fetching FHEM devices...
[2019-4-15 14:44:54] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:44:54] [FHEM] got: 0 results
[2019-4-15 14:44:54] [FHEM] alexa device is alexa
[2019-4-15 14:44:54] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:44:54] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:54] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:54] Server listening on: http://127.0.0.1:35401 for proxy connections
[2019-4-15 14:44:54] *** SSH: checking proxy configuration
[2019-4-15 14:44:54] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:44:54] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":35401}}
[2019-4-15 14:44:54] sshautoconf: SSH key seems to exist
[2019-4-15 14:44:54] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:44:54] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:54] [FHEM] got .eventToken
[2019-4-15 14:44:54] refreshing token
[2019-4-15 14:44:54] BearerToken '...7072A' read from alexa
[2019-4-15 14:44:54] 39_alexa.pm is new version: true
[2019-4-15 14:44:54] sshautoconf: completed successfully
[2019-4-15 14:44:54] *** SSH: proxy configuration set up done
[2019-4-15 14:44:54] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:44:54] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:54] Starting SSH with -R 1234:127.0.0.1:35401 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:44:55] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:44:55] [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=myhcconnToken&XHR=1
[2019-4-15 14:44:55] *** SSH: proxy connection established
[2019-4-15 14:44:55] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:44:55] got fresh token
[2019-4-15 14:45:52] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:45:52] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:45:52] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332352256
[2019-4-15 14:45:54] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:45:54] [FHEM] Checking devices and attributes...
[2019-4-15 14:45:54] [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%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:54] [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%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:54] [FHEM] waiting for events ...
[2019-4-15 14:45:54] [FHEM] Fetching FHEM devices...
[2019-4-15 14:45:54] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:56] [FHEM] alexa device is alexa
[2019-4-15 14:45:56] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:56] [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=myhcconnToken&XHR=1
[2019-4-15 14:45:56] [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=myhcconnToken&XHR=1
[2019-4-15 14:45:56] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":35401}
[2019-4-15 14:45:56] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:45:57] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:45:57] os.homedir()=/opt/fhem
[2019-4-15 14:45:57] this is alexa-fhem 0.5.26
[2019-4-15 14:45:57] connecting to FHEM ...
[2019-4-15 14:45:57] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:45:57] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332357813
[2019-4-15 14:45:57] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:45:57] [FHEM] Checking devices and attributes...
[2019-4-15 14:45:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:57] [FHEM] waiting for events ...
[2019-4-15 14:45:57] [FHEM] Fetching FHEM devices...
[2019-4-15 14:45:57] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:45:58] [FHEM] got: 0 results
[2019-4-15 14:45:58] [FHEM] alexa device is alexa
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] Server listening on: http://127.0.0.1:44689 for proxy connections
[2019-4-15 14:45:58] *** SSH: checking proxy configuration
[2019-4-15 14:45:58] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:45:58] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":44689}}
[2019-4-15 14:45:58] sshautoconf: SSH key seems to exist
[2019-4-15 14:45:58] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] [FHEM] got .eventToken
[2019-4-15 14:45:58] refreshing token
[2019-4-15 14:45:58] 39_alexa.pm is new version: true
[2019-4-15 14:45:58] sshautoconf: completed successfully
[2019-4-15 14:45:58] *** SSH: proxy configuration set up done
[2019-4-15 14:45:58] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] Starting SSH with -R 1234:127.0.0.1:44689 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:45:58] BearerToken '...7072A' read from alexa
[2019-4-15 14:45:58] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:45:58] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:45:58] *** SSH: proxy connection established
[2019-4-15 14:45:58] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:45:58] got fresh token
[2019-4-15 14:46:55] [FHEM] longpoll ended, reconnect in: 200msec
[2019-4-15 14:46:55] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:46:55] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332415746
[2019-4-15 14:46:57] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:46:57] [FHEM] Checking devices and attributes...
[2019-4-15 14:46:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:46:57] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:46:57] [FHEM] waiting for events ...
[2019-4-15 14:46:57] [FHEM] Fetching FHEM devices...
[2019-4-15 14:46:57] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:00] [FHEM] alexa device is alexa
[2019-4-15 14:47:00] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:00] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:00] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:00] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":44689}
[2019-4-15 14:47:00] Terminating - starting the listener not possible (another instance running?)
[2019-4-15 14:47:01] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-4-15 14:47:01] os.homedir()=/opt/fhem
[2019-4-15 14:47:01] this is alexa-fhem 0.5.26
[2019-4-15 14:47:01] connecting to FHEM ...
[2019-4-15 14:47:01] [FHEM] trying longpoll to listen for fhem events
[2019-4-15 14:47:01] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1555332421917
[2019-4-15 14:47:02] [FHEM] got csrfToken: myhcconnToken
[2019-4-15 14:47:02] [FHEM] Checking devices and attributes...
[2019-4-15 14:47:02] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:02] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:02] [FHEM] waiting for events ...
[2019-4-15 14:47:02] [FHEM] Fetching FHEM devices...
[2019-4-15 14:47:02] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:02] [FHEM] alexa device is alexa
[2019-4-15 14:47:02] [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.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=myhcconnToken&XHR=1
[2019-4-15 14:47:02] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:02] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:02] Server listening on: http://127.0.0.1:36847 for proxy connections
[2019-4-15 14:47:02] *** SSH: checking proxy configuration
[2019-4-15 14:47:02] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-4-15 14:47:02] Passed config: {"connections":[{"filter":"alexaName=..*","name":"FHEM","webname":"fhem","uid":999,"port":"8083","server":"127.0.0.1"}],"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":36847}}
[2019-4-15 14:47:02] sshautoconf: SSH key seems to exist
[2019-4-15 14:47:03] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-4-15 14:47:03] [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=myhcconnToken&XHR=1
*** FHEM: connected
[2019-4-15 14:47:03] [FHEM] got: 0 results
[2019-4-15 14:47:03] BearerToken '...7072A' read from alexa
[2019-4-15 14:47:03] 39_alexa.pm is new version: true
[2019-4-15 14:47:03] sshautoconf: completed successfully
[2019-4-15 14:47:03] *** SSH: proxy configuration set up done
[2019-4-15 14:47:03] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-4-15 14:47:03] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:03] Starting SSH with -R 1234:127.0.0.1:36847 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-4-15 14:47:03] [FHEM] got .eventToken
[2019-4-15 14:47:03] refreshing token
[2019-4-15 14:47:03] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-4-15 14:47:03] [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=myhcconnToken&XHR=1
[2019-4-15 14:47:03] *** SSH: proxy connection established
[2019-4-15 14:47:03] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 
[2019-4-15 14:47:03] got fresh token

Hallo zusammen,

FHEM läuft bei mir in einer Docker Umgebung.
Leider bekomme ich alle 5 Minuten folgenden Fehler.

3/28/2020, 1:10:18 PM] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":39901}
[3/28/2020, 1:10:18 PM] Terminating - starting the listener not possible (another instance running?)

Ich kann jedoch bisher nicht erkennen, dass dieser Port schon verwendet wird.
netstat zeigt nur eine Port an und der wird von localhost genutzt. Sieht für micht erstmal richtig aus.

Hi, hab eben mal ins Log geschaut...habe auch stündlich die alexa start/stop meldungen..

Hier das alexa log
2020-07-22 20:00:06 caching: dmy_Alexa_Familie_Woche-state: off
[2020-7-22 8:00:06 PM] [FHEM] dmy_Alexa_Geburtstag is switch
[2020-7-22 8:00:06 PM] [FHEM] dmy_Alexa_Geburtstag has
[2020-7-22 8:00:06 PM] [FHEM]   On [state;on,off]
[2020-7-22 8:00:06 PM] [FHEM] dmy_Alexa_Geburtstag will not send proactive events
[2020-7-22 8:00:06 PM] [FHEM] dmy_Alexa_Geburtstag uses ID: 5f077377-f33f-7d29-a515-70a5141994a750d0
  2020-07-22 20:00:06 caching: dmy_Alexa_Geburtstag-state: off
[2020-7-22 8:00:06 PM] BearerToken '...4E28A' read from alexa
[2020-7-22 8:00:06 PM] 39_alexa.pm is new version: true
[2020-7-22 8:00:06 PM] sshautoconf: completed successfully
[2020-7-22 8:00:06 PM] *** SSH: proxy configuration set up done
[2020-7-22 8:00:06 PM] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2020-7-22 8:00:06 PM] [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_351728676652254&XHR=1
[2020-7-22 8:00:06 PM] Starting SSH with -R 1234:127.0.0.1:35091 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2020-7-22 8:00:07 PM] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2020-7-22 8:00:07 PM] [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_351728676652254&XHR=1
[2020-7-22 8:00:07 PM] *** SSH: proxy connection established
[2020-7-22 8:00:07 PM] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated. 


Hallo zusammen,

gibt es zu dem Problem schon was neues? Ich bin schon am verzweifeln. Ich habe die gleiche Fehlermeldung minütlich und es wird immer der Tunnel als auch alexa-Fhem beendet. Ich finde die Ursache einfach nicht und auch keine funktionierende Lösung online.

Hier noch mal die Meldung :
[20.1.2021, 23:58:54] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":40439}
[20.1.2021, 23:58:54] Terminating - starting the listener not possible (another instance running?)

2 Annahmen:

• 40439 ist ein zufällig gewürfelter Port - da gibt es jedes Mal eine andere Nummer, richtig?
  
• Alexa startet durchaus, und dann gibt es plötzlich Ärger?

Ich habe bei mir in der Historie am 5. Januar so einen Fall gefunden. Natürlich lief alexa-fhem schon lange auf diesem Port, weswegen die eigentlich Meldung sinnlos ist: Wenn alexa-fhem den Port sich initial reservieren konnte, kann ihm den nicht plötzlich jemand wegnehmen. Ich habe mal nach Bugs in NodeJS gesucht, aber ich komme nur auf Hits von Verzweifelten, die nicht wissen, dass ein Port nur von einem Prozess belegt werden kann :-). Bei mir passierte der Fehler in dem Kontext, dass ich gerade ein Gerät in FHEM gelöscht hatte, und alexa-fhem kurz Kommunikation mit dem FHEM-Server darüber führte. Selbst, wenn diese fehlgeschlagen wäre, hätte sich das nicht auf den Listener-Port auswirken dürfen. Seht Ihr einen Kontext? Mein Node ist 10.21.0 unter Buster / RPi 3B+

Hallo,

also der lokale Port ist zufällig und es wird jede Minute ein neuer Port geöffnet. Ich hab das ganze mal analysiert und musste feststellen, dass Alexa-Fhem auf dem Port bereits lauscht und dann versucht ihn ein zweites mal zu öffnen. Dann kommt es natürlich zu der gezeigten Fehlermeldung und dam Abbruch von Alexa-Fhem als auch zu dem SSH-Tunnel.

Ich nutze NodeJS 10.19.0 auf einem leistungsstarken Proxmox-Server

Wie kommst Du zu der Überzeugung, dass alexa-fhem versucht, den Serverport ein zweites Mal zu öffnen? Welche Version von alexa-fhem setzt Du ein?

ich benutze folgende Version :  alexa-fhem@0.5.57

Ich hab dem Prozess Alexa-Fhem mit strace mal auf die Finger geschaut und gesehen, dass er den Port öffnen will, obwohl er schon von dem gleichen Prozess geöffnet wurde. War garnicht so einfach bzw. musste schnell tippen....

wenn das hilft, kann ich mal den kompletten trace posten, ist aber größer ...

Ahja, noch zu der Frage welches Problem ich damit habe: Das Thema ist dass der SSH-Tunnel und Alexa-Fhem minütlich durchstartet werden und nur ca. 30 Sekunden von der Minute wirklich aktiv ist. Sprich die anderenen 30 Sekunden von der Minute sind die Devices von Alexa nicht erreichbar und es nervt, wenn man in der Hälfte aller Fälle erst 30 Sekunden warten muss, bis man den Befehl noch mal an die Alexa absetzen kann.

Ich habe jetzt auch mal aktualisiert auf 0.5.57.

Lass' uns doch erst mal eingrenzen, ob alexa-fhem zum zweiten Mal "listenen" will, oder NodeJS schräg ist. Dafür wäre eine Logzeile vor dem Listener sinnvoll.

Verzeichnis ist bei mir: /usr/local/lib/node_modules/alexa-fhem/lib

Hier in der Datei "server.js":

Zeile 179 ändern:
log.error ("Server (proxy) emitted error: " + JSON.stringify(res));

Zeile 189 einfügen (direkt vor "server.listen(..."):
log.info("Start listening for proxy server on ", this._config.sshproxy.port);

Und vielleicht auch noch:
Zeile 362 ändern:
log.error ("Server (normal) emitted error: " + JSON.stringify(res));

Zeile 369 einfügen (direkt vor "server.listen(..."):
log.info ("Start listening for normal server on ", this._config.alexa.port);

Dann in FHEM "set alexa restart"

Ergebnis - viele Zeilen mal weglassend - sollte dann ein:

[21.1.2021, 20:32:59] Start listening for proxy server on  undefined
[21.1.2021, 20:32:59] Server listening on: http://127.0.0.1:46275 for proxy connections

sein. Und spannend wird es, ob noch einmal "Start listening" auftaucht.

Also, ich hab die Änderungen übernommen, Alexa-Fhem gestoppt und folgenden Befehl abgesetzt :


sudo -u fhem strace -o strace.log alexa-fhem -D -c /opt/fhem/alexa-fhem.cfg >debug.log 2>&1


Die beiden Logfiles sind angehangen. Hier das wichtigste: ja es kommen zwei "Start listening" innerhalb von knapp einer Minute. Hier die entsprechenden Zeilen:


[21.1.2021, 23:17:15] Start listening for proxy server on  undefined
[21.1.2021, 23:17:15] Server listening on: http://127.0.0.1:42323 for proxy connections
[21.1.2021, 23:18:02] Start listening for proxy server on  42323
[21.1.2021, 23:18:02] Server  (proxy) emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":42323}


Was mach ich falsch?

Du machst mutmaßlich nichts falsch. Gibt es bei Dir irgendwas, was periodisch neue Geräte anlegt oder löscht oder am Alexa-Device minütlich etwas macht?

Ich habe einen Verdacht und versuche, ihn mit Andre / justme1968 zu klären.

Hallo,

also in FHEM ist schon ordentlich was los und ja, es werden auch Geräte bzw. at-Devices angelegt, aber es werden keine Devices mit einem Attribute alexaName angelegt. Ich habe aber in letzter Zeit viele Geräte angefasst und verändert.

Das Alexa-Device wird nicht periodisch verändert. Ich hatte es nur inzwischen schon etliche male neu angelegt und auf default zurückgesetzt, um den Fehler einzugrenzen.

weiter oben war schon ein oder zwei mal ein anderes fhem modul für die probleme verantwortlich.

kannst du bitte testhalber mal fhem auf ein absolutes minimum abspecken? am liebten nur alexa und test dummy zum schalten.

Das ist schon eine Herausforderung, aber ich setzt mich mal ran. Meine fhem.conf ist eine halbes MB groß.

vermutlich ist es das einfachste wenn du in einer zweiten installation bei 0 anfängst und dein haupt fhem in ruhe lässt.

Vielleicht einfacher: Hast Du massenhaft & minütlich Meldungen wie
DELETEATTR
im fhem-Logfile?

also in den Logs von heute habe ich noch nicht ein DELETEATTR, dennoch habe ich minütlich einen Neustart von Alexa-fhem.

Ich bau gerade eine neue Instanz auf. Wozu hat man denn Proxmox :-D
Da werde ich auch gleich mal probieren, ob die gleiche Config in einer neuen Installation läuft. Kann ja auch sein, dass ich am System irgend was krumm habe.

ich habe eben eine alexa-fhem version gepublished die in einem fall die symptome des problems (d.h. den neustart des reverse tunnels mit darauf folgendem EADDRINUSE fehler) verhindert.

das ganze sollte aber nur setzen und/oder löschen von attributen im alexa device hervorgerufen worden sein. und behebt das einmalig auftreten bei georg.

das minütliche auftreten kann damit eigentlich nichts zu tun haben. eventuell werden die symptome dadurch aber auch unterdrückt. nach der ursache sollte aber trotzdem noch gesucht werden.

eventuell das fork problem von oben. oder mehrere systeme mit gleichem key.

So, DEINEN Fall habe ich mit etwas sorgfältigerem Lesen des Debug-Log identifiziert:

Der Vereinsproxy wirft Deine SSH-Verbindung (sehr schnell) wieder raus. Das macht er eigentlich nur unter einem Umstand: Zwei SSH-Verbindungen, ein Key. Dann fliegt die ältere Verbindung raus, wenn die neuere kommt.

Beliebter Fehler, wenn man FHEM komplett für den Kumpel oder sich selbst cloned, und dabei keinen neuen SSH-Key für den fhem-User erstellt bzw. den alten löscht.

Reicht das an Hinweis? Sonst sagt mir per Pmail die erste Hex-Gruppe Deines Proxy-Keys, und ich gucke auf den Vereinsserver.

Die Vermutung, dass es aus irgend einem Grund eine zweite Verbindung gibt, hatte ich auch schon. Zumal ich die letzten Tage auch einen alten FHEM-Server starten musste.

Ich finde aber keine zweite SSH-Verbindung. Weder auf dem Server noch am InternetGW.

ich habe auch schon komplett die ssh-keys, die Alexa-Fhem-Installation inkl. aller Configs und die npm-installation gelöscht und neu angelegt.

Ebenso habe ich eine Möglichkeit gefunden, um den Key am "Vereinsserver"  zurückzusetzen, aber ich glaube das war noch von der letzten Version von Alexa-Fhem.

Ich schicke dir noch die Hex-Gruppe meines Proxy-Keys per PN

Ich hab gerade mal auf die Version 0.5.59 von Alexa-Fhem geupdatet.

Also jetzt läuft es durch und wird nicht jede Minute neu gestartet.

Ich weiß jetzt noch nicht, ob es das war bzw. ob das Update die Ursache behoben hat oder nur die Auswirkung des Neustarts unterdrückt.
In dem Log sehe ich, dass er jede Minute die Devices neu scannt, aber nix anlegt, weil sie ja schon existieren.

Braucht ihr noch mal ein log?

Jedenfalls bin ich euch jetzt schon sehr dankbar für die Hilfe!!! :-)

bei dir ist nur das symptom des neustarts behoben.

die eigentliche ursache ist immer noch unklar.

Wenn ich euch irgendwie helfen kann, dann sagt bescheid. Ich helfe jederzeit gerne!