[alexa-fhem | Generell] Alles zu Installation und damit verbundenen Problemen

[rallye]

Zu meinem o.a. Problem:
Ich habe FHEM nochmals auf ein nagelneu installiertes Raspberian (Bookworm) installiert und mit einer "leeren" Minimalkonfiguration begonnen wie sie von FHEM, wenn keine Konfigurationsdaten vorhanden sind erzeugt werden.
Ich habe die im WIKI beschriebenen Installationsschritte wie folgt durchgeführt:

Code Auswählen Erweitern

sudo apt-get install nodejs npm
node --version
sudo npm install -g alexa-fhem
und nach Neustart von FHEM ein

Code Auswählen Erweitern

update
shutdown restart
durchgeführt. Im Anschluss habe ich wie beschrieben das

Code Auswählen Erweitern

define alexa alexa
eingegeben und nach einiger Zeit die Fehlermeldung in der Reading-Section

Code Auswählen Erweitern

alexaFHEM.ProxyConnection
error; Reverse Proxy replied with neither registered nor unregistered status: out:  err:fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey).Selbstverständlich habe ich alle im WIKI beschriebenen Überprüfungen durchgeführt, aber alles (bis auf die Funktionalität von Alexa, und natürlich die Fehlermeldung) scheint normal.
Anbei noch mein Alexa-Log:

Code Auswählen Erweitern

[13.2.2025, 11:25:12] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[13.2.2025, 11:25:12] os.homedir()=/opt/fhem
[13.2.2025, 11:25:12] this is alexa-fhem 0.5.65
[13.2.2025, 11:25:12] connecting to FHEM ...
[13.2.2025, 11:25:12] [FHEM] defaults to: will not send proactive events
[13.2.2025, 11:25:12] [FHEM] trying longpoll to listen for fhem events
[13.2.2025, 11:25:12] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=>
[13.2.2025, 11:25:12] [FHEM] got csrfToken: csrf_208085174102096
[13.2.2025, 11:25:12] [FHEM] Checking devices and attributes...
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22>
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_208085174>
[13.2.2025, 11:25:12] [FHEM] waiting for events ...
[13.2.2025, 11:25:12] [FHEM] Fetching FHEM devices...
[13.2.2025, 11:25:12] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&fwcsrf=csrf_208085174>
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%20addToAttrList(%20%22homebridgeMapping%3A>
[13.2.2025, 11:25:12] [FHEM] homebridgeMapping attribute created.
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BaddToAttrList(%20%22genericDeviceType%3Asec>
[13.2.2025, 11:25:12] [FHEM] alexa device is alexa
[13.2.2025, 11:25:12] [FHEM] alexa will not send proactive events
[13.2.2025, 11:25:12] [FHEM] alexa uses ID: 67adc888-f33f-e168-a5c4-552c18118af8c040
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:12] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:12] Server listening on: http://127.0.0.1:35161 for proxy connections
[13.2.2025, 11:25:12] *** SSH: checking proxy configuration
[13.2.2025, 11:25:12] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.s>
[13.2.2025, 11:25:12] sshautoconf: env={"LANG":"de_AT.UTF-8","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:>
[13.2.2025, 11:25:12] sshautoconf: Creating directory /opt/fhem/.alexa
[13.2.2025, 11:25:12] Passed config: {
  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',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      requestTimeout: 300000,
      headersTimeout: 60000,
      keepAliveTimeout: 5000,
      connectionsCheckingInterval: 30000,
      joinDuplicateHeaders: undefined,
      rejectNonStandardBodyWrites: false,
      _events: [Object: null prototype],
      _eventsCount: 4,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: true,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      highWaterMark: 16384,
      httpAllowHalfOpen: false,
      timeout: 0,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 135,
      [Symbol(kUniqueHeaders)]: null,
      [Symbol(http.server.connections)]: ConnectionsList {},
      [Symbol(http.server.connectionsCheckingInterval)]: Timeout {
        _idleTimeout: 30000,
        _idlePrev: [TimersList],
        _idleNext: [TimersList],
        _idleStart: 670,
        _onTimeout: [Function: bound checkConnections],
        _timerArgs: undefined,
        _repeat: 30000,
        _destroyed: false,
        [Symbol(refed)]: false,
        [Symbol(kHasPrimitive)]: false,
        [Symbol(asyncId)]: 137,
        [Symbol(triggerId)]: 136
      }
    }
  },
  connections: [
    {
      port: '8083',
      filter: 'alexaName=..*',
      server: '127.0.0.1',
      uid: 999,
      webname: 'fhem',
      name: 'FHEM'
    }
  ]
}
[13.2.2025, 11:25:12] sshautoconf: No SSH public key found, we have to generate one.
[13.2.2025, 11:25:15] sshautoconf: Generating public/private rsa key pair.
Your identification has been saved in /opt/fhem/.ssh/id_rsa
Your public key has been saved in /opt/fhem/.ssh/id_rsa.pub
The key fingerprint is:
SHA256:2heqfplvImF5XYhCLcCz4upWfxqK6C+nJLPalH9rvis fhem@RasPi5-Server
The key's randomart image is:
+---[RSA 4096]----+
|   ... .         |
|    o o .        |
|     + . . .     |
|  . . . . . .    |
| . .   oS...     |
|  .o  +o....     |
|oo+ .o.ooo.      |
|=B.oE.=o=..      |
|O=*o.BX* +.      |
+----[SHA256]-----+
[13.2.2025, 11:25:15] sshautoconf: aborted with Reverse Proxy replied with neither registered nor unregistered status: >
fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey).

[13.2.2025, 11:25:15] *** SSH: proxy configuration failed: Reverse Proxy replied with neither registered nor unregister>
fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey).

*** FHEM: connected
[13.2.2025, 11:25:15] [FHEM] got: 0 results
[13.2.2025, 11:25:15] [FHEM] genericDeviceType attribute was not known. please restart.
[13.2.2025, 11:25:35] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[13.2.2025, 11:25:35] os.homedir()=/opt/fhem
[13.2.2025, 11:25:35] this is alexa-fhem 0.5.65
[13.2.2025, 11:25:35] connecting to FHEM ...
[13.2.2025, 11:25:35] [FHEM] defaults to: will not send proactive events
[13.2.2025, 11:25:35] [FHEM] trying longpoll to listen for fhem events
[13.2.2025, 11:25:35] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=>
[13.2.2025, 11:25:35] [FHEM] got csrfToken: csrf_208085174102096
[13.2.2025, 11:25:35] [FHEM] Checking devices and attributes...
[13.2.2025, 11:25:35] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22>
[13.2.2025, 11:25:35] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_208085174>
[13.2.2025, 11:25:35] [FHEM] waiting for events ...
[13.2.2025, 11:25:35] [FHEM] Fetching FHEM devices...
[13.2.2025, 11:25:35] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&fwcsrf=csrf_208085174>
[13.2.2025, 11:25:35] [FHEM] alexa device is alexa
[13.2.2025, 11:25:35] [FHEM] alexa will not send proactive events
[13.2.2025, 11:25:35] [FHEM] alexa uses ID: 67adc888-f33f-e168-a5c4-552c18118af8c040
[13.2.2025, 11:25:35] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:35] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:35] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>
[13.2.2025, 11:25:35] Server listening on: http://127.0.0.1:35259 for proxy connections
[13.2.2025, 11:25:35] *** SSH: checking proxy configuration
[13.2.2025, 11:25:35] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.s>
[13.2.2025, 11:25:35] Passed config: {
  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',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      requestTimeout: 300000,
      headersTimeout: 60000,
      keepAliveTimeout: 5000,
      connectionsCheckingInterval: 30000,
      joinDuplicateHeaders: undefined,
      rejectNonStandardBodyWrites: false,
      _events: [Object: null prototype],
      _eventsCount: 4,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: true,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      highWaterMark: 16384,
      httpAllowHalfOpen: false,
      timeout: 0,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 120,
      [Symbol(kUniqueHeaders)]: null,
      [Symbol(http.server.connections)]: ConnectionsList {},
      [Symbol(http.server.connectionsCheckingInterval)]: Timeout {
        _idleTimeout: 30000,
        _idlePrev: [TimersList],
        _idleNext: [TimersList],
        _idleStart: 511,
        _onTimeout: [Function: bound checkConnections],
        _timerArgs: undefined,
        _repeat: 30000,
        _destroyed: false,
        [Symbol(refed)]: false,
        [Symbol(kHasPrimitive)]: false,
        [Symbol(asyncId)]: 122,
        [Symbol(triggerId)]: 121
      }
    }
  },
  connections: [
    {
      port: '8083',
      filter: 'alexaName=..*',
      server: '127.0.0.1',
      uid: 999,
      webname: 'fhem',
      name: 'FHEM'
    }
  ]
}
[13.2.2025, 11:25:35] sshautoconf: SSH key seems to exist
[13.2.2025, 11:25:35] sshautoconf: aborted with Reverse Proxy replied with neither registered nor unregistered status: >

[13.2.2025, 11:25:35] *** SSH: proxy configuration failed: Reverse Proxy replied with neither registered nor unregister>

*** FHEM: connected
[13.2.2025, 11:25:35] [FHEM] got: 0 results
[13.2.2025, 11:25:35] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[13.2.2025, 11:25:36] Reading alexaFHEM.ProxyConnection set to error;; Reverse Proxy replied with neither registered no>

[13.2.2025, 11:25:36] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22>


Was genau bedeutet dieMeldung

Code Auswählen Erweitern

[13.2.2025, 11:25:35] sshautoconf: SSH key seems to exist
? Hat das damit zu tun, dass Alexa bereits in einer anderen Installation von mir gelaufen/registriert ist bzw war? Und wie bekomme ich das wieder weg?

Danke Rallye


Nachtrag: Das Problem hat sich erledigt. Bookworm benötigt eine "Sonderbehandlung". Siehe ==> https://forum.fhem.de/index.php?topic=126292.msg1283802#msg1283802

[rallye]

Nachdem ich mich nun weitergehandelt habe und Alexa in meiner Bare-Metal Installation unter Bookworm doch am Laufen habe wollte ich den Skill neu registrieren. Leider Fehlanzeige. Ich habe den "alten" Skill, den ich in der Dockerumgebung verwendet habe gelöscht und den neuen Key eingegeben, doch leider mag Amazon nicht.
Mein Alexa-Device meint es besteht eine ssh-Verbindung, der Skillconnector meint die ssh-Verbindung besteht nicht.

Code Auswählen Erweitern

defmod alexa alexa
attr alexa alexaFHEM-config ./alexa-fhem.cfg
attr alexa alexaFHEM-log ./log/alexa-%Y-%m-%d.log
attr alexa 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
attr alexa alexaTypes #Type=<alias>[,<alias2>[,...]]\
light=licht,lampen\
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
attr alexa devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
attr alexa echoRooms #<deviceId>=<room>\

attr alexa fhemIntents #IntentName=<sample utterance>\
gutenMorgen=guten morgen\
guteNacht=gute nacht
attr alexa persons #<personId>=<name>\

attr alexa stateFormat alexaFHEM

setstate alexa running /usr/local/bin/alexa-fhem
setstate alexa 2025-02-14 10:38:06 alexaFHEM running /usr/local/bin/alexa-fhem
setstate alexa 2025-02-14 10:38:07 alexaFHEM.ProxyConnection running;; SSH connected
setstate alexa 2025-02-14 10:38:05 alexaFHEM.bearerToken crypt:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
setstate alexa 2025-02-14 10:38:05 alexaFHEM.skillRegKey crypt:yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy


Auch die nachfolgenden Zeilen schauen für mich gut aus...

Code Auswählen Erweitern

sepp@RasPi5-Server:/opt/fhem $ sudo -u fhem ssh -i .ssh/id_rsa -p 58824 fhem-va.fhem.de status
Registered.
Registered on 2025-02-13T11:24:20Z as 59CF1F12.
Habt ihr einen Tip für mich, bitte?

Gruß RallyeDu darfst diesen Dateianhang nicht ansehen.

[juergen012]

Moin,
aus dem Wiki:

Registrierungskey vergessen, Registrierung zurücksetzen
Auf der Kommandoshell:

pi@raspberrypi:~# sudo -u fhem ssh -p 58824 fhem-va.fhem.de status
Registered.
Registered on 2019-01-13T15:38:13Z.
heisst, das der Vereinsserver eigentlich alles hat, was er will. Es wird kein neuer Schlüssel generiert. Wenn Du die Situation zurücksetzen möchtest, wäre die hässliche Methode, Deinen SSH-Key zu löschen. Eleganter ist, die Registrierung auf Vereinsseite zu löschen:

pi@raspberrypi:~# sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister
Your registration has been removed
löscht Deinen Schlüssel mitsamt allen dort gespeicherten Daten auf Vereinsseite. Bei Restart von alexa-fhem in FHEM-WEB wird jetzt ein neuer Registrierungskey angefordert.

[rallye]

aus dem Wiki

Wieder mal Tomaten auf den Augen gehabt! Danke!!

Gruß Rallye

[Mundus]

Hi!

Nach (sehr) langer Zeit, kümmere ich mich auch mal wieder um mein FHEM-System. Ich wollte gerne Alexa-FHEM installieren und glaube mich zu erinnern, dass es problematisch sein sollte, FHEM und FHEM ALexa auf einem RasPi laufen zu lassen.

Bei meiner jetzigen Recherche habe ich dazu nichts (mehr) gefunden. Könnt ihr mir sagen, ob es problematisch ist, die Hauptinstanz FHEM und FHEM-ALexa auf einem Gerät zu installieren und zu nutzen?

Code Auswählen Erweitern

Mein Gerät:
Raspberry Pi 3 Model B Rev 1.2p

Installation:
Version: PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


[MadMax-FHEM]

Jessie?!

Wirklich!!!?

Das wird nicht gehen...

Ansonsten ist es überhaupt kein Problem beides auf einem PI zu haben...

Läuft bei mir schon Jahre zusammen.
Wichtig (für Neuanfänger): alexa-fhem Connector Anleitung/Wiki nehmen...

Aber wie geschrieben dürfte Jessie nicht mehr gehen und sollte mMn auch sonst nicht mehr genutzt werden...

Auch wenn jetzt kommt: läuft nur im Heimnetz ohne Zugang von außen, never touch und so etc.

Aber verm. Zugang nach außen und halt (verm.) im Netz mit Kommunikation zu anderen Geräten usw.

Gruß, Joachim

[fz55]

Hallo,

ich bin gerade beim Umziehen meiner FHEM-Installation von einem Raspberry Pi Model 3 auf Model 5. Soweit hat auch alles funktioniert (FHEM-Backup vom Altsystem eingespielt). Nur mit alexa-fhem habe ich ein Problem. Ich bin nach dem FHEMWiki "FHEM Connector für Amazon Alexa" vorgegangen und habe /opt/fhem/.ssh vom Altsystem (mit dieser Ergänzung) kopiert.

Leider lässt sich alexa-fhem nicht starten:

Code Auswählen Erweitern

[22.2.2025, 12:19:50] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[22.2.2025, 12:19:50] os.homedir()=/opt/fhem
[22.2.2025, 12:19:50] this is alexa-fhem 0.5.65
[22.2.2025, 12:19:50] connecting to FHEM ...
[22.2.2025, 12:19:50] [FHEM] defaults to: will not send proactive events
[22.2.2025, 12:19:50] [FHEM] trying longpoll to listen for fhem events
[22.2.2025, 12:19:50] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1740223190520
[22.2.2025, 12:19:50] [FHEM] got csrfToken: csrf_286322422639795
[22.2.2025, 12:19:50] [FHEM] Checking devices and attributes...
[22.2.2025, 12:19:50] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:50] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:50] [FHEM] waiting for events ...
[22.2.2025, 12:19:50] [FHEM] Fetching FHEM devices...
[22.2.2025, 12:19:50] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:51] [FHEM] alexa device is alexa
[22.2.2025, 12:19:51] [FHEM] alexa will not send proactive events
[22.2.2025, 12:19:51] [FHEM] alexa uses ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx
[22.2.2025, 12:19:51] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.65%22%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:51] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:51] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_286322422639795&XHR=1
[22.2.2025, 12:19:51] Server listening on: http://127.0.0.1:42979 for proxy connections
[22.2.2025, 12:19:51] *** SSH: checking proxy configuration
[22.2.2025, 12:19:51] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[22.2.2025, 12:19:51] Passed config: {
  connections: [
    {
      uid: 999,
      port: '8083',
      filter: 'alexaName=..*',
      webname: 'fhem',
      server: '127.0.0.1',
      name: 'FHEM'
    }
  ],
  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',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      requestTimeout: 300000,
      headersTimeout: 60000,
      keepAliveTimeout: 5000,
      connectionsCheckingInterval: 30000,
      joinDuplicateHeaders: undefined,
      rejectNonStandardBodyWrites: false,
      _events: [Object: null prototype],
      _eventsCount: 4,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: true,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      highWaterMark: 16384,
      httpAllowHalfOpen: false,
      timeout: 0,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 204,
      [Symbol(kUniqueHeaders)]: null,
      [Symbol(http.server.connections)]: ConnectionsList {},
      [Symbol(http.server.connectionsCheckingInterval)]: Timeout {
        _idleTimeout: 30000,
        _idlePrev: [TimersList],
        _idleNext: [TimersList],
        _idleStart: 1086,
        _onTimeout: [Function: bound checkConnections],
        _timerArgs: undefined,
        _repeat: 30000,
        _destroyed: false,
        [Symbol(refed)]: false,
        [Symbol(kHasPrimitive)]: false,
        [Symbol(asyncId)]: 206,
        [Symbol(triggerId)]: 205
      }
    }
  }
}
[22.2.2025, 12:19:51] sshautoconf: SSH key seems to exist
[22.2.2025, 12:19:51] sshautoconf: Our SSH key is known at the reverse proxy, good!
[22.2.2025, 12:19:51] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_286322422639795&XHR=1
*** FHEM: connected
[22.2.2025, 12:19:51] [FHEM] got: 39 results
[22.2.2025, 12:19:51] [FHEM] Airgradient is AirQualitySensor
[22.2.2025, 12:19:51] [FHEM] Airgradient has
[22.2.2025, 12:19:51] [FHEM]   Custom Power [power]
[22.2.2025, 12:19:51] [FHEM]   On [state;on,off]
[22.2.2025, 12:19:51] [FHEM]   CurrentTemperature [temperature]
[22.2.2025, 12:19:51] [FHEM]   CurrentRelativeHumidity [humidity]
[22.2.2025, 12:19:51] [FHEM]   CarbonDioxideLevel [CO2]
[22.2.2025, 12:19:51] [FHEM] Airgradient will not send proactive events
[22.2.2025, 12:19:51] [FHEM] Airgradient uses ID: 61d314f3-f33f-eac9-200c-c10ad96f2b05257d
  2025-02-22 12:19:51 caching: Airgradient-power: ON
[22.2.2025, 12:19:51] [FHEM] Airgradient-power not a number: ON
  2025-02-22 12:19:51 caching: Airgradient-state: on
  2025-02-22 12:19:51 caching: Airgradient-temperature: 21.8
  2025-02-22 12:19:51 caching: Airgradient-humidity: 31.6
  2025-02-22 12:19:51 caching: Airgradient-CO2: 1272
.
.
.
[22.2.2025, 12:19:51] [FHEM] Drucker is switch
[22.2.2025, 12:19:51] [FHEM] Drucker has
[22.2.2025, 12:19:51] [FHEM]   Custom Power [power]
[22.2.2025, 12:19:51] [FHEM]   On [state;on,off]
[22.2.2025, 12:19:51] [FHEM] Drucker will not send proactive events
[22.2.2025, 12:19:51] [FHEM] Drucker uses ID: 63b58716-f33f-eac9-417e-a03c499abb156428
  2025-02-22 12:19:51 caching: Drucker-power: OFF
[22.2.2025, 12:19:51] [FHEM] Drucker-power not a number: OFF
  2025-02-22 12:19:51 caching: Drucker-state: off
[22.2.2025, 12:19:51] [FHEM] GW_innen is thermometer
[22.2.2025, 12:19:51] [FHEM] GW_innen has
[22.2.2025, 12:19:51] [FHEM] GW_innen will not send proactive events
[22.2.2025, 12:19:51] [FHEM] GW_innen uses ID: 64b31aa1-f33f-eac9-4dac-e79b848bc2ab72d7
/usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:1218
        var name = ModeController.asset.split(":")[0];
                                        ^

TypeError: Cannot read properties of undefined (reading 'split')
    at /usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:1218:41
    at Array.forEach (<anonymous>)
    at FHEMDevice.fromHomebridgeMapping (/usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:1217:36)
    at new FHEMDevice (/usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:2653:8)
    at FHEM.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:987:39)
    at Array.map (<anonymous>)
    at FHEM.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/fhem.js:984:31)
    at self.callback (/usr/local/lib/node_modules/alexa-fhem/node_modules/postman-request/request.js:313:12)
    at Request.emit (node:events:517:28)
    at Request.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/node_modules/postman-request/request.js:1638:10)
    at Request.emit (node:events:517:28)
    at Gunzip.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/node_modules/postman-request/request.js:1509:12)
    at Object.onceWrapper (node:events:631:28)
    at Gunzip.emit (node:events:517:28)
    at endReadableNT (node:internal/streams/readable:1400:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Node.js v18.19.0
Weiß jemand, was hier schief läuft?

Grüße
Reiner

[passibe]

Zeig mal ein list vom GW_innen device. Da ist irgendwas im HomebridgeMapping falsch, glaube ich.

[fz55]

Es war auch meine Vermutung, dass GW_innen das Problem auslöst und hatte es in FHEM alt+neu und in der Alexa-App gelöscht - leider ohne Erfolg. Unter FHEM alt ist es ja auch jahrelang gelaufen. Inzwischen habe ich GW_innen wieder definiert:

Code Auswählen Erweitern

define GW_innen MQTT2_DEVICE
attr GW_innen IODev mqtt2_mosquitto
attr GW_innen alexaName gewächshaus innen
attr GW_innen alias Gewächshaus(innen)
attr GW_innen devicetopic gewaechshaus
attr GW_innen event-min-interval (temp|hum).*:900,battery_ok:3600
attr GW_innen event-on-change-reading .*
attr GW_innen fp_myHome 60,309,3,temperature,GW_innen
attr GW_innen genericDeviceType thermometer
attr GW_innen group Sensoren
attr GW_innen icon gewachshaus
attr GW_innen readingList tele/rtl_433/inFactory-TH/118:.* {  json2nameValue($EVENT)  }
attr GW_innen room Garten
attr GW_innen sortby 10
attr GW_innen stateFormat Time: [$name:time:t] / T: [$name:temperature] °C / H: [$name:humidity] %
attr GW_innen timestamp-on-change-reading battery_ok
attr GW_innen userReadings temperature:temperature_F:.* { f2c(ReadingsNum($NAME,"temperature_F",212));; }
#   CFGFN     
#   DEF       
#   FUUID      67ba1da3-f33f-eac9-bb74-e6eece643de043d4
#   IODev      mqtt2_mosquitto
#   NAME       GW_innen
#   NR         671
#   STATE      Time: [GW_innen:time:t] / T: [GW_innen:temperature] °C / H: [GW_innen:humidity] %
#   TYPE       MQTT2_DEVICE
#   READINGS:
#     2025-02-22 19:57:27   IODev           mqtt2_mosquitto
#
setstate GW_innen Time: [GW_innen:time:t] / T: [GW_innen:temperature] °C / H: [GW_innen:humidity] %
setstate GW_innen 2025-02-22 19:57:27 IODev mqtt2_mosquitto



[Mundus]

Jessie?!

Wirklich!!!?

Das wird nicht gehen...

Ansonsten ist es überhaupt kein Problem beides auf einem PI zu haben...

Läuft bei mir schon Jahre zusammen.
Wichtig (für Neuanfänger): alexa-fhem Connector Anleitung/Wiki nehmen...

Danke @Joachim!

Setze gerade ein neues System auf und "Update" alles. Danach wage ich mich mal an FHEM-Alexa (Wiki habe ich schon parallel offen ).

[passibe]

Inzwischen habe ich GW_innen wieder definiert

Hat GW_innen (inzwischen) denn auch irgendwelche (Temperatur-)Readings außer IODev?
Könnte sein, dass da das Problem liegt, dass alexa-fhem eben versucht das temperature- oder humidity-Reading zu lesen aber halt nix kriegt und daran kaputtgeht.
Gib uns gerne nochmal ein aktuelles List, idealerweise dann auch mit Sensorwerten, falls das Problem noch besteht.

[fz55]

Ich glaube ja nicht, dass es am GW_Innen-Device liegt. Bei der Neuanlage von GW_innen habe ich jetzt den Mosquitto-Server des Altsystems definiert, da z. Zt. am Neusystem kein Mosquitto läuft.

Code Auswählen Erweitern

Internals:
   FUUID      64b31aa1-f33f-eac9-4dac-e79b848bc2ab72d7
   IODev      mqtt2_RPI3
   NAME       GW_innen
   NR         494
   STATE      Time: 2025-02-24 15:15:52 / T: 16.3 °C / H: 65 %
   TYPE       MQTT2_DEVICE
   READINGS:
     2025-02-24 15:28:46   IODev           mqtt2_RPI3
     2025-02-24 15:09:28   battery_ok      0
     2025-02-24 15:15:52   channel         3
     2025-02-24 15:15:52   humidity        65
     2025-02-24 15:15:52   id              118
     2025-02-24 15:15:52   mic             CRC
     2025-02-24 15:15:52   model           inFactory-TH
     2025-02-24 15:14:34   temperature     16.3
     2025-02-24 15:15:52   temperature_F   61.4
     2025-02-24 15:15:52   time            2025-02-24 15:15:51
Attributes:
   IODev      mqtt2_RPI3
   alexaName  gewächshaus innen
   alias      Gewächshaus(innen)
   devicetopic gewaechshaus
   event-min-interval (temp|hum).*:900,battery_ok:3600
   event-on-change-reading .*
   fp_myHome  60,309,3,temperature,GW_innen
   genericDeviceType thermometer
   group      Sensoren
   icon       gewachshaus
   readingList tele/rtl_433/inFactory-TH/118:.* {  json2nameValue($EVENT)  }
   room       Garten
   sortby     10
   stateFormat Time: [$name:time:t] / T: [$name:temperature] °C / H: [$name:humidity] %
   timestamp-on-change-reading battery_ok
   userReadings temperature:temperature_F:.* { f2c(ReadingsNum($NAME,"temperature_F",212)); }
Ich frage mich, warum am Altsystem die Eintäge in /opt/fhem/.ssh angenommen werden, am Neusystem aber zusätzlich eine config-file benötigt wird, obwohl auf beiden Systemen BOOKWORM läuft.

ssh config:

Code Auswählen Erweitern

Host fhem-va.fhem.de
  HostkeyAlgorithms +ssh-rsa
  PubkeyAcceptedAlgorithms +ssh-rsa
Warum läuft der SSH-Proxy nicht, obwohl "sudo -u fhem ssh -p 58824 fhem-va.fhem.de status" mit

Code Auswählen Erweitern

Registered.
Registered on 2021-01-16T14:17:12Z as xxxxxxx. antwortet?

[fz55]

Ich bin einen Schritt weiter.

Am Altsystem habe ich die ssh-Änderungen in /etc/ssh/ssh_config vorgenommen, deshalb ist dort keine config in /opt/fhem/.ssh notwendig. Aber das war ja nicht mein Hauptproblem.

Dass alexa-fhem nicht startet bzw. gleich wieder abbricht, liegt an Devices die mit dem Attribut genericDeviceType mode definiert sind, z.B.:

Code Auswählen Erweitern

defmod dym_jl_Esszimmerrollo dummy
attr dym_jl_Esszimmerrollo alexaName Esszimmerrollo
attr dym_jl_Esszimmerrollo genericDeviceType mode
attr dym_jl_Esszimmerrollo homebridgeMapping ModeController:mode,cmd=mode,mode=state,values=auf;;zu;;schatten;;stop;;schliessen
attr dym_jl_Esszimmerrollo room Jarolift
attr dym_jl_Esszimmerrollo setList mode:auf,zu,schatten,stop,schliessen
attr dym_jl_Esszimmerrollo webCmd mode
Nach dem ich alle diese Devices am Neusystem gelöscht habe, läuft Alexa dort stabil. Kann mir jemand sagen, warum diese Devices am Neusystem Probleme verursachen?

Grüße
Reiner

[passibe]

Was sagt denn das Log von alexa-fhem beim Start zu diesen devices?
Bzw. mit welcher Fehlermeldung startet alexa-fhem nicht/bricht ab?

[fz55]

Am Neusystem habe ich ein Update von node auf V23.7.0 gemacht - hat aber nichts gebracht.

Sobald alexa-fhem das Device mit ModeController-Definition anfasst, wird alexa-fhem neu gestartet. Hier das Log:

Code Auswählen Erweitern

[27.2.2025, 11:10:48] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[27.2.2025, 11:10:48] os.homedir()=/opt/fhem
[27.2.2025, 11:10:48] this is alexa-fhem 0.5.65
[27.2.2025, 11:10:48] connecting to FHEM ...
[27.2.2025, 11:10:48] [FHEM] defaults to: will not send proactive events
[27.2.2025, 11:10:49] [FHEM] trying longpoll to listen for fhem events
[27.2.2025, 11:10:49] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1740651049115
[27.2.2025, 11:10:53] [FHEM] got csrfToken: csrf_475605073134707
[27.2.2025, 11:10:53] [FHEM] Checking devices and attributes...
[27.2.2025, 11:10:53] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:53] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:53] [FHEM] waiting for events ...
[27.2.2025, 11:10:53] [FHEM] Fetching FHEM devices...
[27.2.2025, 11:10:53] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:54] [FHEM] alexa device is alexa
[27.2.2025, 11:10:54] [FHEM] mappings for alexa: {}
[27.2.2025, 11:10:54] [FHEM] alexa will not send proactive events
[27.2.2025, 11:10:54] [FHEM] alexa uses ID: 5e5ba3e3-f33f-eac9-73c0-4734a5aed3a744a5
[27.2.2025, 11:10:54] [FHEM] homebridgeMapping: #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
Brightness=verb=setze,valuePrefix=auf,values=100:dim100;50:dim50;25:dim25,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
TargetPosition=verb=schliesse,values=down

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
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { '25': 'dim25', '50': 'dim50', '100': 'dim100' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { rot: '0', 'grün': '128', blau: '200' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { rot: '0', 'grün': '120', blau: '220' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { auf: '100', zu: '0' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { down: 'down' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM] value2homekit: { 'AMAZON.NUMBER': 'AMAZON.NUMBER' }
[27.2.2025, 11:10:54] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.65%22%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:54] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:54] perfectOfVerb:
[27.2.2025, 11:10:54] {
  stelle: 'gestellt',
  schalte: 'geschaltet',
  'färbe': 'gefärbt',
  mach: 'gemacht'
}
[27.2.2025, 11:10:54] verbsOfIntent:
[27.2.2025, 11:10:54] [
  OnIntent: [ 'schalte' ],
  prozentIntent: [ 'stelle', 'setze' ],
  HueIntent: [ 'stelle' ],
  HueIntentB: [ 'färbe' ],
  SaturationIntent: [ 'stelle' ],
  SaturationIntentB: [ 'sättige' ],
  TargetPositionIntent: [ 'mach' ],
  TargetPositionIntentC: [ 'schliesse' ],
  gradIntent: [ 'stelle' ]
]
[27.2.2025, 11:10:54] characteristicsOfIntent:
[27.2.2025, 11:10:54] {
  OnIntent: [ 'On' ],
  prozentIntent: [ 'Brightness', 'TargetPosition', 'Volume' ],
  HueIntent: [ 'Hue' ],
  HueIntentB: [ 'Hue' ],
  SaturationIntent: [ 'Saturation' ],
  SaturationIntentB: [ 'Saturation' ],
  TargetPositionIntent: [ 'TargetPosition' ],
  TargetPositionIntentC: [ 'TargetPosition' ],
  gradIntent: [ 'TargetTemperature' ]
}
[27.2.2025, 11:10:54] prefixOfIntent:
[27.2.2025, 11:10:54] {
  OnIntent: undefined,
  prozentIntent: 'auf',
  HueIntent: 'auf',
  HueIntentB: undefined,
  SaturationIntent: 'auf',
  SaturationIntentB: undefined,
  TargetPositionIntent: undefined,
  TargetPositionIntentC: undefined,
  gradIntent: 'auf'
}
[27.2.2025, 11:10:54] suffixOfIntent:
[27.2.2025, 11:10:54] {
  OnIntent: undefined,
  prozentIntent: 'prozent',
  HueIntent: undefined,
  HueIntentB: undefined,
  SaturationIntent: undefined,
  SaturationIntentB: undefined,
  TargetPositionIntent: undefined,
  TargetPositionIntentC: undefined,
  gradIntent: 'grad'
}
[27.2.2025, 11:10:54] alexaTypes:
[27.2.2025, 11:10:54] {
  light: [ 'licht', 'lampen' ],
  blind: [
    'rolladen',
    'rolläden',
    'jalousie',
    'jalousien',
    'rollo',
    'rollos'
  ]
}
[27.2.2025, 11:10:54] roomOfEcho:
[27.2.2025, 11:10:54] {}
[27.2.2025, 11:10:54] personOfId:
[27.2.2025, 11:10:54] {}
[27.2.2025, 11:10:54] fhemIntents:
[27.2.2025, 11:10:54] {
  FHEMgutenMorgenIntent: 'gutenMorgen',
  FHEMguteNachtIntent: 'guteNacht'
}
[27.2.2025, 11:10:54] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_475605073134707&XHR=1
[27.2.2025, 11:10:54] Server listening on: http://127.0.0.1:33687 for proxy connections
[27.2.2025, 11:10:54] *** SSH: checking proxy configuration
[27.2.2025, 11:10:54] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[27.2.2025, 11:10:54] 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',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      requestTimeout: 300000,
      headersTimeout: 60000,
      keepAliveTimeout: 5000,
      connectionsCheckingInterval: 30000,
      requireHostHeader: true,
      joinDuplicateHeaders: undefined,
      rejectNonStandardBodyWrites: false,
      _events: [Object: null prototype],
      _eventsCount: 4,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      _listeningId: 2,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: true,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      highWaterMark: 65536,
      httpAllowHalfOpen: false,
      timeout: 0,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(shapeMode)]: false,
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 234,
      [Symbol(kUniqueHeaders)]: null,
      [Symbol(http.server.connections)]: ConnectionsList {},
      [Symbol(http.server.connectionsCheckingInterval)]: Timeout {
        _idleTimeout: 30000,
        _idlePrev: [TimersList],
        _idleNext: [TimersList],
        _idleStart: 5780,
        _onTimeout: [Function: bound checkConnections],
        _timerArgs: undefined,
        _repeat: 30000,
        _destroyed: false,
        [Symbol(refed)]: false,
        [Symbol(kHasPrimitive)]: false,
        [Symbol(asyncId)]: 236,
        [Symbol(triggerId)]: 235,
        [Symbol(kAsyncContextFrame)]: undefined
      }
    }
  },
  connections: [
    {
      port: '8083',
      server: '127.0.0.1',
      webname: 'fhem',
      uid: 999,
      filter: 'alexaName=..*',
      name: 'FHEM'
    }
  ]
}
[27.2.2025, 11:10:54] sshautoconf: SSH key seems to exist
[27.2.2025, 11:10:54] sshautoconf: Our SSH key is known at the reverse proxy, good!
[27.2.2025, 11:10:54] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_475605073134707&XHR=1
*** FHEM: connected
[27.2.2025, 11:10:55] [FHEM] got: 28 results
[27.2.2025, 11:10:55] [FHEM] homebridgeMapping: CarbonDioxideLevel=CO2,AirQuality=1
[27.2.2025, 11:10:55] [FHEM] mappings for Airgradient: {
  'E863F10D-079E-48FF-8F27-9C2605A29F52': { name: 'Power', reading: 'power', format: 'FLOAT', factor: 1 },
  On: {
    reading: 'state',
    valueOff: '/off|Off|OFF|A0|000000/',
    cmdOn: 'on',
    cmdOff: 'off'
  },
  CurrentTemperature: { reading: 'temperature', minValue: -30 },
  CurrentRelativeHumidity: { reading: 'humidity' },
  CarbonDioxideLevel: { reading: 'CO2', AirQuality: '1' }
}
[27.2.2025, 11:10:55] [FHEM] Airgradient is AirQualitySensor
[27.2.2025, 11:10:55] [FHEM] Airgradient has
[27.2.2025, 11:10:55] [FHEM]   Custom Power [power]
[27.2.2025, 11:10:55] [FHEM]   On [state;on,off]
[27.2.2025, 11:10:55] [FHEM]   CurrentTemperature [temperature]
[27.2.2025, 11:10:55] [FHEM]   CurrentRelativeHumidity [humidity]
[27.2.2025, 11:10:55] [FHEM]   CarbonDioxideLevel [CO2]
[27.2.2025, 11:10:55] [FHEM] Airgradient will not send proactive events
[27.2.2025, 11:10:55] [FHEM] Airgradient uses ID: 61d314f3-f33f-eac9-200c-c10ad96f2b05257d
  2025-02-27 11:10:55 caching: Airgradient-power: ON
[27.2.2025, 11:10:55] [FHEM] Airgradient-power factor: value NaN mapped to NaN
[27.2.2025, 11:10:55] [FHEM] Airgradient-power not a number: ON
  2025-02-27 11:10:55 caching: Airgradient-state: on
  2025-02-27 11:10:55 caching: Airgradient-temperature: 21.0
  2025-02-27 11:10:55 caching: Airgradient-humidity: 36.7
  2025-02-27 11:10:55 caching: Airgradient-CO2: 1219
[27.2.2025, 11:10:55] [FHEM] Drucker is switch
[27.2.2025, 11:10:55] [FHEM] Drucker has
[27.2.2025, 11:10:55] [FHEM]   Custom Power [power]
[27.2.2025, 11:10:55] [FHEM]   On [state;on,off]
[27.2.2025, 11:10:55] [FHEM] Drucker will not send proactive events
[27.2.2025, 11:10:55] [FHEM] Drucker uses ID: 63b58716-f33f-eac9-417e-a03c499abb156428
  2025-02-27 11:10:55 caching: Drucker-power: OFF
[27.2.2025, 11:10:55] [FHEM] Drucker-power factor: value NaN mapped to NaN
[27.2.2025, 11:10:55] [FHEM] Drucker-power not a number: OFF
  2025-02-27 11:10:55 caching: Drucker-state: off
[27.2.2025, 11:10:55] [FHEM] mappings for Fensterbank: {
  On: {
    reading: 'state',
    valueOff: '/off|Off|OFF|A0|000000/',
    cmdOn: 'on',
    cmdOff: 'off'
  }
}
[27.2.2025, 11:10:55] [FHEM] Fensterbank is light
[27.2.2025, 11:10:55] [FHEM] Fensterbank has
[27.2.2025, 11:10:55] [FHEM]   On [state;on,off]
[27.2.2025, 11:10:55] [FHEM] Fensterbank will not send proactive events
[27.2.2025, 11:10:55] [FHEM] Fensterbank uses ID: IT.0FFF00FFFF 0F F0
  2025-02-27 11:10:55 caching: Fensterbank-state: off
[27.2.2025, 11:10:55] [FHEM] mappings for GW_innen: {
  CurrentTemperature: { reading: 'temperature', minValue: -30 },
  CurrentRelativeHumidity: { reading: 'humidity' }
}
[27.2.2025, 11:10:55] [FHEM] GW_innen is thermometer
[27.2.2025, 11:10:55] [FHEM] GW_innen has
[27.2.2025, 11:10:55] [FHEM]   CurrentTemperature [temperature]
[27.2.2025, 11:10:55] [FHEM]   CurrentRelativeHumidity [humidity]
[27.2.2025, 11:10:55] [FHEM] GW_innen will not send proactive events
[27.2.2025, 11:10:55] [FHEM] GW_innen uses ID: 64b31aa1-f33f-eac9-4dac-e79b848bc2ab72d7
  2025-02-27 11:10:55 caching: GW_innen-temperature: 6.2
  2025-02-27 11:10:55 caching: GW_innen-humidity: 93
.
.
.
[27.2.2025, 11:10:55] [FHEM] Kellertreppe is light
[27.2.2025, 11:10:55] [FHEM] Kellertreppe has
[27.2.2025, 11:10:55] [FHEM]   Custom Power [power]
[27.2.2025, 11:10:55] [FHEM]   On [state;on,off]
[27.2.2025, 11:10:55] [FHEM] Kellertreppe will not send proactive events
[27.2.2025, 11:10:55] [FHEM] Kellertreppe uses ID: 63b6b674-f33f-eac9-64cb-2c37afcdc7419304
  2025-02-27 11:10:55 caching: Kellertreppe-power: OFF
[27.2.2025, 11:10:55] [FHEM] Kellertreppe-power factor: value NaN mapped to NaN
[27.2.2025, 11:10:55] [FHEM] Kellertreppe-power not a number: OFF
  2025-02-27 11:10:55 caching: Kellertreppe-state: toggle
[27.2.2025, 11:10:55] [FHEM] homebridgeMapping: ModeController:mode,cmd=mode,mode=state,values=auf;zu;schatten;stop;oeffnen;schliessen;hoch;runter

Am Altsystem ist alexa-fhem wesentlich gesprächiger und bringt bei diesem Device folgende Meldungen:

Code Auswählen Erweitern

[27.2.2025, 11:27:12] [FHEM] dym_jl_Esszimmerrollo is mode
[27.2.2025, 11:27:12] [FHEM] dym_jl_Esszimmerrollo has
[27.2.2025, 11:27:12] [FHEM]   ModeController [mode]
[27.2.2025, 11:27:12] [FHEM] dym_jl_Esszimmerrollo will not send proactive events
[27.2.2025, 11:27:12] [FHEM] dym_jl_Esszimmerrollo uses ID: 62dbd2c3-f33f-eac9-db89-ee7846f840b0b93c
[27.2.2025, 11:27:12] [FHEM] value2homekit: { auf: 'auf', zu: 'zu', schatten: 'schatten', stop: 'stop' }
[27.2.2025, 11:27:12] [FHEM] homebridgeMapping: ModeController:mode,cmd=mode,mode=state,values=auf;zu;schatten;stop
[27.2.2025, 11:27:12] [FHEM] mappings for dym_jl_Fensterrollo: {
  ModeController: {
    reading: 'mode',
    cmd: 'mode',
    mode: 'state',
    values: [ 'auf', 'zu', 'schatten', 'stop' ]
  }
}
Hier die auf beiden Systemen identische Definition des Devices:

Code Auswählen Erweitern

defmod dym_jl_Esszimmerrollo dummy
attr dym_jl_Esszimmerrollo userattr relatedTo
attr dym_jl_Esszimmerrollo alexaName Esszimmerrollo
attr dym_jl_Esszimmerrollo genericDeviceType mode
attr dym_jl_Esszimmerrollo homebridgeMapping ModeController:mode,cmd=mode,mode=state,values=auf;;zu;;schatten;;stop
attr dym_jl_Esszimmerrollo relatedTo mq_jl_Esszimmerrollo
attr dym_jl_Esszimmerrollo room Jarolift
attr dym_jl_Esszimmerrollo setList mode:auf,zu,schatten,stop
attr dym_jl_Esszimmerrollo webCmd mode