Autor Thema: Einladung zum Beta-Test: "FHEMlazy" zur einfacheren Alexa-Integration  (Gelesen 20606 mal)

Offline Byllyy

  • Jr. Member
  • **
  • Beiträge: 82
Ich habe auf einen neu aufgesetzten PI den Alexa Connector mit zugehöriger App aufgespielt. Die Installation lief gut und auch in der App
wurde alles Grün. Leider schaffe ich es nicht ein Gerät zu verknüpfen, dieses wird nie gefunden( Ist ein Dummy mit dem Attribut "alexaName").

Gibt es evtl ein Problem wenn man auch die alte Installation (Alexa-Fhem über Port 3000) noch aktiv auf einem anderen Pi hat.

Danke für eure Hilfe,
Byllyy


Hier noch der AlexaLog:
[2019-3-17 18:40:29] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-3-17 18:40:29] os.homedir()=/opt/fhem
[2019-3-17 18:40:29] this is alexa-fhem 0.5.26
[2019-3-17 18:40:29] connecting to FHEM ...
[2019-3-17 18:40:29] [FHEM] trying longpoll to listen for fhem events
[2019-3-17 18:40:29] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1552844429962
[2019-3-17 18:40:30] [FHEM] got csrfToken: csrf_142637027820726
[2019-3-17 18:40:30] [FHEM] Checking devices and attributes...
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] [FHEM] waiting for events ...
[2019-3-17 18:40:30] [FHEM] Fetching FHEM devices...
[2019-3-17 18:40:30] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] [FHEM] alexa device is alexa
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_142637027820726&XHR=1
[2019-3-17 18:40:30] Server listening on: http://127.0.0.1:46579 for proxy connections
[2019-3-17 18:40:30] *** SSH: checking proxy configuration
[2019-3-17 18:40:30] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-3-17 18:40:30] Passed config: {"connections":[{"name":"FHEM","filter":"alexaName=..*","uid":999,"webname":"fhem","port":"8083","server":"127.0.0.1"}],"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":46579}}
[2019-3-17 18:40:30] sshautoconf: SSH key seems to exist
[2019-3-17 18:40:30] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_142637027820726&XHR=1
*** FHEM: connected
[2019-3-17 18:40:30] [FHEM] got: 1 results
[2019-3-17 18:40:30] [FHEM] mySwitch1 is switch
[2019-3-17 18:40:30] [FHEM] mySwitch1 has
[2019-3-17 18:40:30] BearerToken '...CF97F' read from alexa
[2019-3-17 18:40:30] [FHEM] got .eventToken
[2019-3-17 18:40:30] refreshing token
[2019-3-17 18:40:30] 39_alexa.pm is new version: true
[2019-3-17 18:40:30] sshautoconf: completed successfully
[2019-3-17 18:40:30] *** SSH: proxy configuration set up done
[2019-3-17 18:40:30] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-3-17 18:40:30] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%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_142637027820726&XHR=1
[2019-3-17 18:40:30] Starting SSH with -R 1234:127.0.0.1:46579 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-3-17 18:40:31] failed to refresh token: invalid_grant: 'The request has an invalid grant parameter : refresh_token'
[2019-3-17 18:40:31] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-3-17 18:40:31] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%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_142637027820726&XHR=1
[2019-3-17 18:40:31] *** SSH: proxy connection established
[2019-3-17 18:40:31] SSH: Welcome at the reverse proxy!  This pseudoshell does not react to any input - do not get irritated.

Offline MadMax-FHEM

  • Hero Member
  • *****
  • Beiträge: 5031
  • NIVEAu ist keine Creme...
Poste doch ein list von deinem Dummy.

Hast du genericDeviceType switch (oder was anderes) und setList on off gesetzt!?

Nein eine alte Installation auf einem anderen PI ist egal.
Habe ich auch (noch) parallel auf 2 PIs laufen...

Gruß, Joachim
FHEM 5.9 PI3: HM-CFG-USB, 40x HM, ZWave-USB, 6x ZWave, EnOcean-PI, 3x EnOcean, HUE, CO2, ESP-Multisensor, FireTV, KODI, alexa-fhem, ...
FHEM 5.9 PI2: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, KODI, ha-bridge, ...
FHEM 5.9 PI3 (Test): HM-MOD-PCB, Snips, Google Home, ...

Offline Byllyy

  • Jr. Member
  • **
  • Beiträge: 82
Hier ein List vom Gerät:
Internals:
   FUUID      5c8d1b2b-f33f-ad1e-2a2e-f087fbb25c3508ce
   NAME       mySwitch1
   NR         16
   STATE      off
   TYPE       dummy
   READINGS:
     2019-03-16 17:04:02   state           off
Attributes:
   alexaName  Test
   alexaRoom  1
   genericDeviceType switch
   webCmd     on:off

Danke

Offline MadMax-FHEM

  • Hero Member
  • *****
  • Beiträge: 5031
  • NIVEAu ist keine Creme...
Das Attribut setList on off fehlt:

attr mySwitch1 setList on off
Dann sollte es eigentlich gehen.

Alexa reload nicht vergessen...

Gruß, Joachim
FHEM 5.9 PI3: HM-CFG-USB, 40x HM, ZWave-USB, 6x ZWave, EnOcean-PI, 3x EnOcean, HUE, CO2, ESP-Multisensor, FireTV, KODI, alexa-fhem, ...
FHEM 5.9 PI2: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, KODI, ha-bridge, ...
FHEM 5.9 PI3 (Test): HM-MOD-PCB, Snips, Google Home, ...

Offline Byllyy

  • Jr. Member
  • **
  • Beiträge: 82
Hallo Joachim,

vielen Dank für deine schnelle Hilfe, jetzt läuft es perfekt.

Danke noch mal und einen schönen Abend,
Byllyy

 

decade-submarginal