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

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

Vorheriges Thema - Nächstes Thema

Mumpitz

hallo zusammen

Ich wollte mir heute abend alexaFHEM installiere. Dazu bin ich nach der Anleitung im Wiki vorgegangen. Leider habe ich bereits ein Problem, sobald ich das device definiere:
Es erscheint ein Reading alexFHEM.ProxyConnection error...

hier ein list des Device:

Internals:
   CFGFN     
   FD         63
   FUUID      5ccb32f9-f33f-915e-301b-f75dc1e5b70801fa
   FVERSION   39_alexa.pm:0.190980/2019-04-02
   LAST_START 2019-05-02 20:23:47
   LAST_STOP  2019-05-02 20:23:47
   NAME       alexa
   NOTIFYDEV  global,global:npmjs.*alexa-fhem.*
   NR         1937
   NTFY_ORDER 50-alexa
   PARTIAL   
   PID        8658
   STARTS     2
   STATE      running /usr/bin/alexa-fhem
   TYPE       alexa
   active     0
   alexa-fhem version 0.5.27
   currentlogfile ./log/alexa-2019-05-02.log
   logfile    ./log/alexa-%Y-%m-%d.log
   CoProcess:
     cmdFn      alexa_getCMD
     name       alexaFHEM
     state      running /usr/bin/alexa-fhem
   READINGS:
     2019-05-02 20:23:47   alexaFHEM       running /usr/bin/alexa-fhem
     2019-05-02 20:23:56   alexaFHEM.ProxyConnection error; ssh-keygen returned error - key_save_private: No such file or directory

   helper:
Attributes:
   alexaFHEM-config ./alexa-fhem.cfg
   alexaFHEM-log ./log/alexa-%Y-%m-%d.log
   alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um

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

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

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

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

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

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

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

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


Hat jemand eine Idee wo ich ansetzen kann?

gvzdus

Beim Lesen oder Posten von dem, was im "alexa...log" steht. Beginnend am besten bei
*** SSH: checking proxy configuration
bis dahin, wo der Fehler kommt.
Falls Du es hier postest, bitte ein eventuell enthaltenes BearerToken (Lange Hex-Sequenzen) ausXen!

Mumpitz

Zitat von: gvzdus am 02 Mai 2019, 20:35:16
Beim Lesen oder Posten von dem, was im "alexa...log" steht. Beginnend am besten bei
*** SSH: checking proxy configuration
bis dahin, wo der Fehler kommt.
Falls Du es hier postest, bitte ein eventuell enthaltenes BearerToken (Lange Hex-Sequenzen) ausXen!

hier das log:
[2019-5-2 20:28:36] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:28:36] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:28:35] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:28:35] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 20:28:35] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:28:35] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:28:28] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:28:28] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":53834},"connections":[{"name":"FHEM","uid":0,"webname":"fhem","port":"8083","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 20:28:28] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:28:28] *** SSH: checking proxy configuration

gvzdus

Oje, das alte Homedir-Problem:
sshautoconf: home=/
bedeutet, dass er ins Hauptverzeichnis schreiben will.
Genaugenommen probiere "ich" 5 verschiedene Variablen durch, um das elende Homedir zu finden:
const srcNames = [ "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE", "process.env.PWD" ];

Er loggt eigentlich auch das Ergebnis dieser Suche, beginnend mit "os.homedir() = ..." - die Stelle findest Du nicht?

Mumpitz

Zitat von: gvzdus am 02 Mai 2019, 21:14:47
Oje, das alte Homedir-Problem:
sshautoconf: home=/
bedeutet, dass er ins Hauptverzeichnis schreiben will.
Genaugenommen probiere "ich" 5 verschiedene Variablen durch, um das elende Homedir zu finden:
const srcNames = [ "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE", "process.env.PWD" ];

Er loggt eigentlich auch das Ergebnis dieser Suche, beginnend mit "os.homedir() = ..." - die Stelle findest Du nicht?

[2019-5-2 21:05: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 21:05:20] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 21:05:19] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 21:05:19] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 21:05:19] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 21:05:19] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 21:05:12] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 21:05:12] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":40836},"connections":[{"name":"FHEM","uid":0,"port":"8083","webname":"fhem","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 21:05:12] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 21:05:12] *** SSH: checking proxy configuration
[2019-5-2 21:05:12] Server listening on: http://127.0.0.1:40836 for proxy connections
[2019-5-2 21:05:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 21:05:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 21:05:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 21:05:12] [FHEM] alexa device is alexa
[2019-5-2 21:05:12] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 21:05:12] [FHEM] Fetching FHEM devices...
[2019-5-2 21:05:12] [FHEM] waiting for events ...
[2019-5-2 21:05:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 21:05:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 21:05:12] [FHEM] Checking devices and attributes...
[2019-5-2 21:05:12] [FHEM] got csrfToken:
[2019-5-2 21:05:11] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556823911950
[2019-5-2 21:05:11] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 21:05:10] connecting to FHEM ...
[2019-5-2 21:05:10] this is alexa-fhem 0.5.27
[2019-5-2 21:05:10] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 21:05:10] using config from ./alexa-fhem.cfg
[2019-5-2 21:03:53] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 21:03:53] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-2 21:03:53] Got SIGTERM, shutting down alexa-fhem...
[2019-5-2 20:28:36] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:28:36] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:28:35] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:28:35] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 20:28:35] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:28:35] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:28:28] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:28:28] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":53834},"connections":[{"name":"FHEM","uid":0,"webname":"fhem","port":"8083","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 20:28:28] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:28:28] *** SSH: checking proxy configuration
[2019-5-2 20:28:28] Server listening on: http://127.0.0.1:53834 for proxy connections
[2019-5-2 20:28:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:28:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:28:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:28:28] [FHEM] alexa device is alexa
[2019-5-2 20:28:28] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 20:28:28] [FHEM] Fetching FHEM devices...
[2019-5-2 20:28:28] [FHEM] waiting for events ...
[2019-5-2 20:28:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 20:28:28] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 20:28:28] [FHEM] Checking devices and attributes...
[2019-5-2 20:28:28] [FHEM] got csrfToken:
[2019-5-2 20:28:28] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556821708058
[2019-5-2 20:28:28] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 20:28:26] connecting to FHEM ...
[2019-5-2 20:28:26] this is alexa-fhem 0.5.27
[2019-5-2 20:28:26] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 20:28:26] using config from ./alexa-fhem.cfg
[2019-5-2 20:28:25] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:28:25] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-2 20:28:25] Got SIGTERM, shutting down alexa-fhem...
[2019-5-2 20:23: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%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:23:56] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:23:55] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:23:55] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 20:23:55] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:23:55] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:23:50] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:23:50] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":34990},"connections":[{"name":"FHEM","uid":0,"webname":"fhem","port":"8083","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 20:23:50] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:23:50] *** SSH: checking proxy configuration
[2019-5-2 20:23:50] Server listening on: http://127.0.0.1:34990 for proxy connections
[2019-5-2 20:23: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%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:23: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%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:23: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%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:23:50] [FHEM] alexa device is alexa
[2019-5-2 20:23:49] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 20:23:49] [FHEM] Fetching FHEM devices...
[2019-5-2 20:23:49] [FHEM] waiting for events ...
[2019-5-2 20:23:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 20:23:49] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 20:23:49] [FHEM] Checking devices and attributes...
[2019-5-2 20:23:49] [FHEM] got csrfToken:
[2019-5-2 20:23:49] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556821429670
[2019-5-2 20:23:49] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 20:23:48] connecting to FHEM ...
[2019-5-2 20:23:48] this is alexa-fhem 0.5.27
[2019-5-2 20:23:48] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 20:23:48] using config from ./alexa-fhem.cfg
[2019-5-2 20:23: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%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:23:46] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-2 20:23:46] Got SIGTERM, shutting down alexa-fhem...
[2019-5-2 20:12:19] [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%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:12:19] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:12:18] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:12:18] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 20:12:18] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:12:18] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:12:12] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:12:12] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":44510},"connections":[{"name":"FHEM","uid":0,"webname":"fhem","port":"8083","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 20:12:12] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:12:12] *** SSH: checking proxy configuration
[2019-5-2 20:12:12] Server listening on: http://127.0.0.1:44510 for proxy connections
[2019-5-2 20:12:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:12:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:12:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:12:12] [FHEM] alexa device is alexa
[2019-5-2 20:12:12] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 20:12:12] [FHEM] Fetching FHEM devices...
[2019-5-2 20:12:12] [FHEM] waiting for events ...
[2019-5-2 20:12:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 20:12:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 20:12:12] [FHEM] Checking devices and attributes...
[2019-5-2 20:12:12] [FHEM] got csrfToken:
[2019-5-2 20:12:12] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556820732374
[2019-5-2 20:12:12] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 20:12:11] connecting to FHEM ...
[2019-5-2 20:12:11] this is alexa-fhem 0.5.27
[2019-5-2 20:12:11] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 20:12:11] using config from ./alexa-fhem.cfg
[2019-5-2 20:11: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%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:11:52] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-5-2 20:11:52] Got SIGTERM, shutting down alexa-fhem...
[2019-5-2 20:03: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%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:03:51] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:03:50] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:03:50] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 20:03:50] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:03:50] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:03:47] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:03:47] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":41069},"connections":[{"filter":"alexaName=..*","name":"FHEM","uid":0,"port":"8083","webname":"fhem","server":"127.0.0.1"}]}
[2019-5-2 20:03:47] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:03:46] *** SSH: checking proxy configuration
[2019-5-2 20:03:46] Server listening on: http://127.0.0.1:41069 for proxy connections
[2019-5-2 20:03: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&XHR=1
[2019-5-2 20:03: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&XHR=1
[2019-5-2 20:03: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.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:03:46] [FHEM] alexa device is alexa
[2019-5-2 20:03:46] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 20:03:46] [FHEM] Fetching FHEM devices...
[2019-5-2 20:03:46] [FHEM] waiting for events ...
[2019-5-2 20:03:46] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 20:03:46] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 20:03:46] [FHEM] Checking devices and attributes...
[2019-5-2 20:03:46] [FHEM] got csrfToken:
[2019-5-2 20:03:46] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556820226532
[2019-5-2 20:03:46] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 20:03:45] connecting to FHEM ...
[2019-5-2 20:03:45] this is alexa-fhem 0.5.27
[2019-5-2 20:03:45] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 20:03:45] using config from ./alexa-fhem.cfg
[2019-5-2 20:03:24] [FHEM] genericDeviceType attribute was not known. please restart.
[2019-5-2 20:03:24] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 20:03:24] [FHEM] got: 0 results
*** FHEM: connected
[2019-5-2 20:03:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BaddToAttrList(%20%22genericDeviceType%3Asecurity%2Cignore%2Cswitch%2Coutlet%2Clight%2Cblind%2Cthermometer%2Cthermostat%2Ccontact%2Cgarage%2Cwindow%2Clock%2Cscene%22%20)%20%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:03:24] [FHEM] homebridgeMapping attribute created.
[2019-5-2 20:03:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%20addToAttrList(%20%22homebridgeMapping%3AtextField-long%22%20)%20%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 20:03:24] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 20:03:24] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 20:03:21] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 20:03:21] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":43593},"connections":[{"filter":"alexaName=..*","name":"FHEM","uid":0,"port":"8083","webname":"fhem","server":"127.0.0.1"}]}
[2019-5-2 20:03:21] sshautoconf: Creating directory /.alexa
[2019-5-2 20:03:21] sshautoconf: env={"CONSOLE":"/dev/console","HOME":"/","OLDPWD":"/","runlevel":"2","INIT_VERSION":"sysvinit-2.88","TERM":"linux","COLUMNS":"82","PATH":"/sbin:/usr/sbin:/bin:/usr/bin","RUNLEVEL":"2","PREVLEVEL":"N","SHELL":"/bin/sh","PWD":"/opt/fhem","previous":"N","LINES":"26","PERL_JSON_BACKEND":"Cpanel::JSON::XS,JSON::XS,JSON::PP,JSON::backportPP"}
[2019-5-2 20:03:21] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 20:03:21] *** SSH: checking proxy configuration
[2019-5-2 20:03:21] Server listening on: http://127.0.0.1:43593 for proxy connections
[2019-5-2 20:03:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:03:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:03:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 20:03:21] [FHEM] alexa device is alexa
[2019-5-2 20:03:21] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 20:03:21] [FHEM] Fetching FHEM devices...
[2019-5-2 20:03:21] [FHEM] waiting for events ...
[2019-5-2 20:03:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 20:03:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 20:03:21] [FHEM] Checking devices and attributes...
[2019-5-2 20:03:21] [FHEM] got csrfToken:
[2019-5-2 20:03:20] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556820200952
[2019-5-2 20:03:20] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 20:03:19] connecting to FHEM ...
[2019-5-2 20:03:19] this is alexa-fhem 0.5.27
[2019-5-2 20:03:19] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 20:03:18] using config from ./alexa-fhem.cfg


Dies ist mein ganzes Log!

gvzdus

Hmmh. Fragen:
1) FHEM wird automatisch gestartet und läuft als User fhem?
2) Eigentlich sollte er "/" als Verzeichnis nicht akzeptieren, denn da darf er kein Unterverzeichnis .ssh anlegen. Mich irritiert, dass die Prüfung fehlschlägt. Könntest Du daher bitte ein "ls -ld /" auf der Kommandozeile absetzen? Bei mir sieht das so aus:
root@raspberrypi:/opt/fhem/FHEM# ls -ld /
drwxr-xr-x 23 root root 4096 Dez 19  2017 /


Datum ist natürlich Schall und Rauch, aber wenn da am Anfang "drwxrwxrwx" steht, dann bitte einmal
sudo chmod 755 /
absetzen.

Mumpitz

Zitat von: gvzdus am 02 Mai 2019, 21:36:28
Hmmh. Fragen:
1) FHEM wird automatisch gestartet und läuft als User fhem?
2) Eigentlich sollte er "/" als Verzeichnis nicht akzeptieren, denn da darf er kein Unterverzeichnis .ssh anlegen. Mich irritiert, dass die Prüfung fehlschlägt. Könntest Du daher bitte ein "ls -ld /" auf der Kommandozeile absetzen? Bei mir sieht das so aus:
root@raspberrypi:/opt/fhem/FHEM# ls -ld /
drwxr-xr-x 23 root root 4096 Dez 19  2017 /


Datum ist natürlich Schall und Rauch, aber wenn da am Anfang "drwxrwxrwx" steht, dann bitte einmal
sudo chmod 755 /
absetzen.

hallo
danke für deine Hilfe:

Frage 1: fhem wird automatisch gestartet
Frage 2: Die Ausgabe bringt folgendes:
root@raspberrypi:/opt/fhem# ls -ld /
drwxr-xr-x 23 root root 4096 May  2 20:03 /
root@raspberrypi:/opt/fhem#


was ich noch erwähnen muss ist, dass ich gestern von wheezy auf jessie geupdatet habe. Tut das was zur Sache?

hier die Rechte:


root@raspberrypi:/opt/fhem# ls -lha /opt/fhem
total 1.5M
drwxr-xr-x 16 fhem dialout 4.0K May  2 21:04 .
drwxr-xr-x  6 root root    4.0K May  1 21:06 ..
-rw-r--r--  1 fhem dialout  309 May  2 21:04 alexa-fhem.cfg
-rw-r--r--  1 fhem dialout  309 May  2 20:12 alexa-fhem.cfg.previous
drwxr-xr-x  2 fhem dialout 4.0K May 20  2015 backup
drwxr-xr-x  2 fhem dialout 268K May  2 20:16 backup_cfg-state
-rwxr-xr-x  1 fhem dialout  537 Jun 19  2016 battcheck
-rwxr-xr-x  1 fhem dialout 1.4K Nov 22  2016 batterie_gtag_neu.sh
-rwxr-xr-x  1 fhem dialout  260 Nov 22  2016 batterie_gtag_reto.sh
-rwxr-xr-x  1 fhem dialout  537 Jun 19  2016 batterie_gtag.sh
-rwxr-xr-x  1 fhem dialout  694 Dec 17  2017 cam_copyandnumber.sh
drwxr-xr-x  2 fhem dialout 4.0K Aug 26  2015 certs
-rwxr-xr-x  1 fhem dialout 282K Apr 21 15:42 CHANGED
-rwxr-xr-x  1 fhem dialout 9.8K Jun 12  2016 --char-read
-rwxr-xr-x  1 fhem dialout  39K Apr  7 16:34 configDB.pm
drwxr-xr-x 32 fhem dialout 4.0K Aug 22  2016 contrib
drwxr-xr-x  2 fhem dialout 4.0K Mar 15  2015 demolog
drwxr-xr-x  4 fhem dialout 4.0K Jul  2  2017 docs
drwxr-xr-x  2 fhem dialout 4.0K Feb 27  2017 ESPEasy
drwxr-xr-x  7 fhem dialout  20K May  2 21:04 FHEM
-rwxr-xr-x  1 fhem dialout 211K May  2 20:16 fhem.cfg
-rwxr-xr-x  1 fhem dialout  22K Mar 18 19:18 fhem.cfg.demo
-rwxr-xr-x  1 fhem dialout    0 May  2 22:15 fhem.heartbeat
-rwxr-xr-x  1 fhem dialout 150K Oct 13  2017 fhem_okt.cfg
-rwxr-xr-x  1 fhem dialout  76K Oct  9  2015 fhem_old.cfg
-rwxr-xr-x  1 fhem dialout  89K Dec  1  2015 fhem_older.cfg
-rwxr--r--  1 fhem dialout 154K Apr  7 16:34 fhem.pl
-rwxr-xr-x  1 fhem dialout  24K Jan  7  2016 homestatus.log
-rwxr-xr-x  1 fhem dialout  11K Jun 12  2016 lepresenced
lrwxrwxrwx  1 fhem dialout   29 Aug 26  2015 log -> /media/usbstick_neu/fhem/log/
drwxr-xr-x  2 fhem dialout 4.0K Oct  2  2015 logs
-rwxr-xr-x  1 fhem dialout  40K Apr 21 15:42 MAINTAINER.txt
drwxr-xr-x  2 fhem dialout 4.0K Aug 26  2015 old_log
-rwxr-xr-x  1 fhem dialout    0 Aug 11  2017 plot0.png
-rwxr-xr-x  1 fhem dialout    0 Aug 11  2017 plot1.png
-rwxr-xr-x  1 fhem dialout    0 Aug 11  2017 plot2.png
-rwxr-xr-x  1 fhem dialout    0 Aug 11  2017 plot3.png
-rwxr-xr-x  1 fhem dialout   89 Aug 12  2017 plot.svg
-rwxr-xr-x  1 fhem dialout  761 Nov  9  2014 README_DEMO.txt
drwxr-xr-x 24 fhem dialout 4.0K May 12  2018 restoreDir
-rwxr-xr-x  1 fhem dialout  20K Apr 16  2015 RINCON_B8E9378CF62001400_MR_Speak.mp3
drwxr-xr-x  2 fhem dialout 4.0K Jan 29  2017 script
drwxr-xr-x  2 fhem dialout 4.0K Feb 10  2016 unused
drwxr-xr-x 11 fhem dialout 4.0K Oct 13  2017 www
root@raspberrypi:/opt/fhem#


und hier der letzte Stand des Log:
[2019-5-2 22:27:22] [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%20error%3B%3B%20ssh-keygen%20returned%20error%20-%20key_save_private%3A%20No%20such%20file%20or%20directory%0D%0A%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1

[2019-5-2 22:27:22] Reading alexaFHEM.ProxyConnection set to error;; ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 22:27:21] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-5-2 22:27:21] [FHEM] got: 0 results
*** FHEM: connected

[2019-5-2 22:27:21] *** SSH: proxy configuration failed: ssh-keygen returned error - key_save_private: No such file or directory

[2019-5-2 22:27:21] sshautoconf: aborted with ssh-keygen returned error - key_save_private: No such file or directory
[2019-5-2 22:27:16] sshautoconf: No SSH public key found, we have to generate one.
[2019-5-2 22:27:16] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":35106},"connections":[{"name":"FHEM","uid":0,"port":"8083","webname":"fhem","filter":"alexaName=..*","server":"127.0.0.1"}]}
[2019-5-2 22:27:16] sshautoconf: home=/, spath=/.alexa, cpath=./alexa-fhem.cfg, sshpath=/.ssh
[2019-5-2 22:27:16] *** SSH: checking proxy configuration
[2019-5-2 22:27:16] Server listening on: http://127.0.0.1:35106 for proxy connections
[2019-5-2 22:27:16] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 22:27:16] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 22:27:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.27%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 22:27:15] [FHEM] alexa device is alexa
[2019-5-2 22:27:15] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-5-2 22:27:15] [FHEM] Fetching FHEM devices...
[2019-5-2 22:27:15] [FHEM] waiting for events ...
[2019-5-2 22:27:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-5-2 22:27:15] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-5-2 22:27:15] [FHEM] Checking devices and attributes...
[2019-5-2 22:27:15] [FHEM] got csrfToken:
[2019-5-2 22:27:15] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1556828835573
[2019-5-2 22:27:15] [FHEM] trying longpoll to listen for fhem events
[2019-5-2 22:27:14] connecting to FHEM ...
[2019-5-2 22:27:14] this is alexa-fhem 0.5.27
[2019-5-2 22:27:14] os.homedir()=/
*** CONFIG: parsed completely
[2019-5-2 22:27:14] using config from ./alexa-fhem.cfg
[2019-5-2 22:27:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-5-2 22:27:12] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating

gvzdus

Mich irritiert, dass der Check "Kann ich hier schreiben?" offenbar falsch ausfällt. Ab Zeile 35 findest Du in

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

die Routine:

  const srcNames = [ "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE", "process.env.PWD" ];
  for (let src of srcNames) {
    const val = eval(src);
    log.info(src + "=" + val);
    if (val) {
      try {
        fs.accessSync(val, fs.constants.W_OK);
        homedir = val;
        return homedir;
      } catch (e) {
        log.warn(src + " set to " + val + ", but this is not writable");
      }
    }
  }
  log.error("No suitable, writable users home directory found")


Wenn Du heute noch ein Erfolgserlebnis brauchst, kannst Du ja im Array so

const srcNames = [ "process.env.PWD", "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE" ];

die Reihenfolge verändern, denn "process.env.PWD" ist bei Dir richtig gesetzt. Aber das ist nur ein Workaround...

Mumpitz

Zitat von: gvzdus am 02 Mai 2019, 23:02:50
Mich irritiert, dass der Check "Kann ich hier schreiben?" offenbar falsch ausfällt. Ab Zeile 35 findest Du in

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

die Routine:

  const srcNames = [ "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE", "process.env.PWD" ];
  for (let src of srcNames) {
    const val = eval(src);
    log.info(src + "=" + val);
    if (val) {
      try {
        fs.accessSync(val, fs.constants.W_OK);
        homedir = val;
        return homedir;
      } catch (e) {
        log.warn(src + " set to " + val + ", but this is not writable");
      }
    }
  }
  log.error("No suitable, writable users home directory found")


Wenn Du heute noch ein Erfolgserlebnis brauchst, kannst Du ja im Array so

const srcNames = [ "process.env.PWD", "os.homedir()", "process.env.HOME", "process.env.HOMEPATH", "process.env.USERPROFILE" ];

die Reihenfolge verändern, denn "process.env.PWD" ist bei Dir richtig gesetzt. Aber das ist nur ein Workaround...

Guten Morgen!
Das hat geholfen. Nun startet alexa ohne Fehlermeldung und die benötigten Readings sind vorhanden.

Besten Dank!

gvzdus

Zur Dokumentation: Ich habe mich mit Mumpitz noch per Pmail ausgetauscht - es war ein ganz allgemeines Rechteproblem vom Upgrade.

juemuc

Zitat von: juemuc am 01 Mai 2019, 20:18:47
Hallo zusammen,

wie habt Ihr Euren Fensterkntakt definiert, sodass er  von Alexa erkannt wird? Ich wollte das Feature testen, dass Alexa die Info liefert, ob das Fenster offen oder geschlossen ist. Die neueste ALEXA-Version 0.5.27 habe ich installiert. Hier meine Definition des Fensterkontaktes:
Im Alexa-Log ist dieser Eintrag vorhanden:In der Alexa-App wird der Kontakt nicht gefunden.

Was mache ich falsch?
Viele Grüße
Jürgen

Hat hier keiner einen Tipp für mich?

Viele Grüße
Jürgen
3x Sonos Play 1, 1x Sonos Arc + Sub, 1 Sonos-One, 1x Sonos Playbar
FB6690 + FB7490 mit 4x Dect 200 und 3 Dect-ULE-Thermostate,  raspberry3B+, HM Funkmodul HM-MOD-RPI-PCB, HM Klingelsensor HM-Sen-DB-PCB, HM (IP) Fensterkontakte und  Amazon Echo Dot,  piVCCU, pi OS (bookworm).

Mumpitz

Zitat von: gvzdus am 03 Mai 2019, 20:22:59
Zur Dokumentation: Ich habe mich mit Mumpitz noch per Pmail ausgetauscht - es war ein ganz allgemeines Rechteproblem vom Upgrade.

Hallo zusammen

Ja genau. Das Problem war damit gelöst. Besten Dank an Dich, gvzdus

justme1968

@juemuc: da du hmccu verwendest und nicht cul_hm brauchst du wie immer ein hombridgeMapping mit ContactSensorState:reading=<reading> oder CurrentDoorState:reading=<reading> und passenden values. siehe wiki.

bitte eine funktionierende version posten.
hue, tradfri, alexa-fhem, homebridge-fhem, LightScene, readingsGroup, ...

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

juemuc

Hallo justme1968,

danke für den Hinweis. Es funktioniert. Anbei meine Definition:
defmod HM_Sec_SCo_OEQ0424862 HMCCUDEV OEQ0424862
attr HM_Sec_SCo_OEQ0424862 IODev HMCCU3
attr HM_Sec_SCo_OEQ0424862 alexaName Küchenfenster
attr HM_Sec_SCo_OEQ0424862 alias HM Fensterkontakt Küche
attr HM_Sec_SCo_OEQ0424862 devStateStyle style="text-align:right"
attr HM_Sec_SCo_OEQ0424862 genericDeviceType contact
attr HM_Sec_SCo_OEQ0424862 group HM Fenster-/Türkontakte
attr HM_Sec_SCo_OEQ0424862 hmstatevals ERROR!7:sabotage;;SABOTAGE!1:sabotage
attr HM_Sec_SCo_OEQ0424862 homebridgeMapping ContactSensorState=state,values=closed:CONTACT_DETECTED;;open:CONTACT_NOT_DETECTED
attr HM_Sec_SCo_OEQ0424862 icon hm-sec-win@black
attr HM_Sec_SCo_OEQ0424862 stateFormat {"Status: ".ReadingsVal($name,"state" ,"")." / LastOpen: ".ReadingsVal($name,"LastOpen","")}
attr HM_Sec_SCo_OEQ0424862 statedatapoint 1.STATE
attr HM_Sec_SCo_OEQ0424862 substitute STATE!(0|false):closed,(1|true):open
attr HM_Sec_SCo_OEQ0424862 userReadings LastOpen:1.STATE.* {if (ReadingsVal($name,"state","") eq "open") {ReadingsTimestamp($name,"state","") =~ /^(\d+)-(\d+)-(\d+)\s(\d+:\d+:\d+)$/;; return "$3.$2.$1 - $4";;} else {ReadingsVal($name,"LastOpen","")}}


Viele Grüße
Jürgen
3x Sonos Play 1, 1x Sonos Arc + Sub, 1 Sonos-One, 1x Sonos Playbar
FB6690 + FB7490 mit 4x Dect 200 und 3 Dect-ULE-Thermostate,  raspberry3B+, HM Funkmodul HM-MOD-RPI-PCB, HM Klingelsensor HM-Sen-DB-PCB, HM (IP) Fensterkontakte und  Amazon Echo Dot,  piVCCU, pi OS (bookworm).

sTaN

Hallo Zusammen,

habe den Thread lange nicht mehr verfolgt und wollte mich gerade mal über die Entwicklung informieren. Gibt es irgendwo auf GitHub oder sonst wo eine Changelog von alexa-fhem? [emoji848]
Ich bin aktuell bei 0.5.15 und wollte mal schauen, was sich in den letzten Versionen verändert hat und bei Bedarf updaten. Sehe auf npmjs.com zwar die Versionen (aktuellste ist wohl 0.5.27) aber nicht die Änderungen

Gruß
sTaN
Raspberry Pi 3
2 x CUL CC1101-USB-Lite 868MHz
FS20 Komponenten, Philips HUE, Alexa-Fhem, MAX! Geräte, homebridge, harmony, Unifi, FirtzBox, MQTT, Aurora, Denon, Sonos, TabletUI, CALENDAR, EGPM2LAN, Pushover