Nach dem Aktualisieren des ssh clients (https://packages.debian.org/de/testing/openssh-client) auf meinem Debian testing erhalte ich folgenden Fehler:
alexaFHEM.ProxyConnection error; Reverse Proxy replied with neither registered nor unregistered status: out: err:Unable to negotiate with 88.99.31.202 port 58824: no matching host key type found. Their offer: ssh-rsa
Ich nehme an, es hängt hiermit zusammen:
Zitat
openssh (1:8.8p1-1) unstable; urgency=medium
OpenSSH 8.8 includes a number of changes that may affect existing
configurations:
* This release disables RSA signatures using the SHA-1 hash algorithm by
default. This change has been made as the SHA-1 hash algorithm is
cryptographically broken, and it is possible to create chosen-prefix
hash collisions for <USD$50K.
For most users, this change should be invisible and there is no need to
replace ssh-rsa keys. OpenSSH has supported RFC8332 RSA/SHA-256/512
signatures since release 7.2 and existing ssh-rsa keys will
automatically use the stronger algorithm where possible.
Incompatibility is more likely when connecting to older SSH
implementations that have not been upgraded or have not closely tracked
improvements in the SSH protocol. For these cases, it may be necessary
to selectively re-enable RSA/SHA1 to allow connection and/or user
authentication via the HostkeyAlgorithms and PubkeyAcceptedAlgorithms
options. For example, the following stanza in ~/.ssh/config will enable
RSA/SHA1 for host and user authentication for a single destination
host:
Host old-host
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
We recommend enabling RSA/SHA1 only as a stopgap measure until legacy
implementations can be upgraded or reconfigured with another key type
(such as ECDSA or Ed25519).
-- Colin Watson <cjwatson@debian.org> Tue, 15 Feb 2022 19:20:21 +0000
Ich verwende:
- alexa-fhem version 0.5.62
- fhem.pl:25684/2022-02-15 perl:5.034000 os:linux user:fhem
Ebenfalls probiert:
sudo -u fhem ssh -p 58824 fhem-va.fhem.de status
Unable to negotiate with 88.99.31.202 port 58824: no matching host key type found. Their offer: ssh-rsa
Mir ist nicht klar, was nun zu tun ist.
Wenn ich es richtig verstehe, wurden meine ssh-keys mit RSA/SHA1 generiert, was man aus security-Sicht nicht mehr haben will. RSA/SHA-256/512 wäre ok und der Server unterstützt ja anscheinend ssh-rsa. Also brauche ich neue keys? Wenn ja, wie sollte ich vorgehen, um sie zu generieren?
Danke und Grüsse
Moin zusammen,
ich habe genau das selbe Problem
[22.2.2022, 06:54:08] Server listening on: http://127.0.0.1:40697 for proxy connections
[22.2.2022, 06:54:08] *** SSH: checking proxy configuration
[22.2.2022, 06:54:08] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[22.2.2022, 06:54:08] 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 {
insecureHTTPParser: undefined,
_events: [Object: null prototype],
_eventsCount: 3,
_maxListeners: undefined,
_connections: 0,
_handle: [TCP],
_usingWorkers: false,
_workers: [],
_unref: false,
allowHalfOpen: true,
pauseOnConnect: false,
httpAllowHalfOpen: false,
timeout: 0,
keepAliveTimeout: 5000,
maxHeadersCount: null,
headersTimeout: 60000,
_connectionKey: '4:127.0.0.1:0',
[Symbol(IncomingMessage)]: [Function: IncomingMessage],
[Symbol(ServerResponse)]: [Function: ServerResponse],
[Symbol(kCapture)]: false,
[Symbol(asyncId)]: 143
}
},
connections: [
{
filter: 'alexaName=..*',
uid: 999,
server: '192.168.188.21',
webname: 'fhem',
port: '8083',
name: 'FHEM'
}
]
}
[22.2.2022, 06:54:08] sshautoconf: SSH key seems to exist
[22.2.2022, 06:54:08] sshautoconf: aborted with Reverse Proxy replied with neither registered nor unregistered status: out: err:Unable to negotiate with 88.99.31.202 port 58824: no matching host key type found. Their offer: ssh-rsa
[22.2.2022, 06:54:08] *** SSH: proxy configuration failed: Reverse Proxy replied with neither registered nor unregistered status: out: err:Unable to negotiate with 88.99.31.202 port 58824: no matching host key type found. Their offer: ssh-rsa
was ich nicht verstehe
der aufruf erfolgt über
ssh -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
aber die Keys die mit der Createkey.sh erstellt werden sind ja
cert.pem
key.pem
die werden ja garnicht benutzt er scheint sich irgendwie eine falsche config zu ziehen aufjedenfall nicht die aus /opt/fhem/.alexa/config.json
{
"alexa": {
"port": 3000,
"name": "Alexa TEST",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"applicationId": "amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"oauthClientID": "amzn1.application-oa2-client.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"permissions": {"<skill-id>": { "client_id": "xyz", "client_secret": "123"}}
},
"sshproxy" : {
"description" : "FHEM Connector",
"ssh" : "/usr/bin/ssh"
},
"connections": [
{
"name": "FHEM",
"server": "192.168.188.21",
"port": "8083",
"webname": "fhem",
"filter": "room=alexa"
}
]
}
ich hab die lösung selber gefunden
evtl. hilft es dir
pico pico /etc/ssh/ssh_config
darein bitte folgendes
HostKeyAlgorithms ssh-rsa,ssh-dss
PubkeyAcceptedKeyTypes ssh-rsa,ssh-dss
Danke dir! Ich dachte auch, dass /opt/fhem/.ssh/ relevant ist. Aber das config-file dort hat sich nicht ausgewirkt.
So klappt's jetzt auch bei mir:
# cat /etc/ssh/ssh_config
[...]
Host fhem-va.fhem.de
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
Zitat von: smmmo am 22 Februar 2022, 22:28:49Danke dir! Ich dachte auch, dass /opt/fhem/.ssh/ relevant ist. Aber das config-file dort hat sich nicht ausgewirkt.
So klappt's jetzt auch bei mir:
# cat /etc/ssh/ssh_config
[...]
Host fhem-va.fhem.de
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
Das gleiche hat bei mir jetzt auch geklappt.
Danke und Gruß,
Thorsten
Zitat von: smmmo am 22 Februar 2022, 22:28:49Danke dir! Ich dachte auch, dass /opt/fhem/.ssh/ relevant ist. Aber das config-file dort hat sich nicht ausgewirkt.
So klappt's jetzt auch bei mir:
# cat /etc/ssh/ssh_config
[...]
Host fhem-va.fhem.de
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
Herzlichen Dank,
ich ärgere mich damit schon seit Wochen rum...
Jetzt klappt es auch wieder bei mir.
Zitat von: smmmo am 22 Februar 2022, 22:28:49Danke dir! Ich dachte auch, dass /opt/fhem/.ssh/ relevant ist. Aber das config-file dort hat sich nicht ausgewirkt.
So klappt's jetzt auch bei mir:
# cat /etc/ssh/ssh_config
[...]
Host fhem-va.fhem.de
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
Vielen Dank :)
Ich hatte das gleiche Problem nach einer (ziemlich heftigen) Upgrade-Orgie meines ubuntu-Servers von Linux 18.04 -> 20.04 -> 22.04.
Mit den beiden Einträgen in der ssh_config läuft auch der FHEM-Alexa-Connector wieder :)
Vielen Dank für diesen Thread.
Nach einem Update meines Raspi von Bullseye nach Bookworm hatte ich das gleiche Problem.
Die beiden Zeilen in der ssh_config haben geholfen :)
Habe auch auf Bookworm umgestellt bzw. neues System eingerichtet und bin auch über das Thema ssh gestolpert.
Eintrag in die ssh_config hat geholfen.
Vielleicht bitte noch im Wiki vermerken.
Dabei auch mal erwähnen das jetzt Skill Installieren nur noch mit der APP geht. Alexa konfigurieren über PC mit https://alexa.amazon.de/ geht nicht mehr... man wird gezwungen die App zu nutzen... wie ich das hasse.... wenn man am PC sitzt und fehler sucht und neuen Proxykey eingeben muss.
Zitat von: laserrichi am 12 Februar 2024, 16:17:11Vielleicht bitte noch im Wiki vermerken.
Kannst du auch tun 8) :) ;)
https://wiki.fhem.de/wiki/FHEMWiki:Administratoren
Zitat von: laserrichi am 12 Februar 2024, 16:17:11Alexa konfigurieren über PC mit https://alexa.amazon.de/ (https://alexa.amazon.de/) geht nicht mehr... man wird gezwungen die App zu nutzen... wie ich das hasse....
Ja, bin auch kein Freund von "das geht nur noch per App"... :-\
Gruß, Joachim
Zitat von: laserrichi am 12 Februar 2024, 16:17:11... wenn man am PC sitzt und fehler sucht und neuen Proxykey eingeben muss.
Den skill konnte ich gestern noch am Rechner auf irgend einer Amazon Seite deaktivieren und neu aktivieren, und den key per c&p einfügen.
Aber generell mag ich es auch nicht am Rechner zu sitzen und ständig das Smartphone zu nehmen um die App zu nutzen. Die alte alexa Seite vermisse ich sehr.
du meinst hier ?
https://va.fhem.de/register/index.html (https://va.fhem.de/register/index.html)
huhu, bin noch ein bisschen unbeholfen in Linux und so...
wo genau und wie muss ich das den nun eintragen?
Zitat von: smmmo am 22 Februar 2022, 22:28:49Danke dir! Ich dachte auch, dass /opt/fhem/.ssh/ relevant ist. Aber das config-file dort hat sich nicht ausgewirkt.
So klappt's jetzt auch bei mir:
# cat /etc/ssh/ssh_config
[...]
Host fhem-va.fhem.de
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
wenn ich den Beitrag von brain666 richtig interprtiere muss ich mit pico ( ich nehm an das ist ein editor) das file
etc/ssh/ssh_configöffnen und den code
HostKeyAlgorithms ssh-rsa,ssh-dss
PubkeyAcceptedKeyTypes ssh-rsa,ssh-dss
einfügen, das öffnet bei mir allerdings 2 files nacheinander... ein leeres namens pico
und eins wo ganz viel text drin steht... wo da muss ich den nun was eintragen? in die erste datei nur den code
# cat /etc/ssh/ssh_config und in die zweite dann
hinter
Host *?? ich bin etwas Verwirrd... sorry für meine vieleicht dumme fragen aber bin hald ein altes windows kind das füher mal mit dos rumgespielt hat aber Linux kenn ich erst seit FHEM bzw seit dem Raspberry Pi für FHEM :)
Zitat von: brain666 am 22 Februar 2022, 08:24:36ich hab die lösung selber gefunden
evtl. hilft es dir
pico pico /etc/ssh/ssh_config
darein bitte folgendes
HostKeyAlgorithms ssh-rsa,ssh-dss
PubkeyAcceptedKeyTypes ssh-rsa,ssh-dss
Gruß Tobias
Zitat von: WarBird am 25 Februar 2024, 01:03:44huhu, bin noch ein bisschen unbeholfen in Linux und so...
Dann wäre ich vorsichtig hier an Systemdateien "rumzuschrauben"...
Bzw. vorher sichern...
Wie editierst du Dateien auf dem Raspi?
Hoffentlich nicht: kopieren (per Filezilla o.ä.) auf einen Windows-Rechner, dann dort editieren und wieder zurück...
Zitat von: WarBird am 25 Februar 2024, 01:03:44wo genau und wie muss ich das den nun eintragen?
Naja, das steht doch mehrfach im Thread:
/etc/ssh/ssh_config
Du wirst allerdings root Rechte brauchen, also sudo...
D.h. mit deinem bevorzugten Linux-Editor (commandline) z.B. pico oder nano oder was halt immer...
Damit oben genannte Datei öffnen (verm. mit sudo / oder als root) und dann am Ende die Einträge vornehmen.
Allerdings habe ich eben mal "man ssh_config" gelesen und es gäbe auch die Möglichkeit die Einträge nur für den User fhem vorzunehmen:
/opt/fhem/.ssh/config
Weil bei der hier genannten Variante wird es systemweit umgestellt, also werden ab nun systemweit "schlechtere" Schlüssel akzeptiert...
https://askubuntu.com/questions/836048/ssh-returns-no-matching-host-key-type-found-their-offer-ssh-dss
http://www.openssh.com/legacy.html
EDIT: die Variante mit pico pico /opt/fhem/.ssh/config erschließt sich mir nicht. Eigentlich müsste pico /opt/fhem/.ssh/config reichen aber halt (verm.) sudo oder als root...
Gruß, Joachim
ohman bei mir klappt es irgendwie nicht :(
root@debian:~# sudo -u fhem ssh -p 58824 fhem-va.fhem.de status
Unregistered.
Your SSH key ist not registered.
alexaFHEM.ProxyConnection
error; Reverse Proxy replied with neither registered nor unregistered status: out: err:fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey)
root@debian:/opt/fhem/.ssh# sudo -u fhem ssh -i id_rsa -p 58824 fhem@fhem-va.fhem.de status
fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey).
root@debian:/opt/fhem/.ssh# sudo -u fhem ssh -i /opt/fhem/.ssh/id_rsa -p 58824 fhem@fhem-va.fhem.de register
fhem@fhem-va.fhem.de: Permission denied (keyboard-interactive,publickey).
Jetzt ist es verbunden laut fhem alexa
Auch laut console
Aber hier sagt er nein :(
Checking your key:
Status ActivationKey: Good Key
Checking connection status:
Status SSH: NOT online - no SSH session established
Status Reverse-Portmapping: -
Status nodejs-Connectivity: -
Status nodejs-Interaction: -
5016 1066 0 16:31 ? 00:00:02 node /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
fhem 5039 5016 0 16:31 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:36561 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root 5955 939 0 16:36 ? 00:00:00 sshd-session: root [priv]
root 5964 5955 0 16:36 ? 00:00:00 sshd-session: root@pts/0
root 6292 5965 0 16:38 pts/0 00:00:00 grep -E (alexa|ssh)
root@debian:/opt/fhem/.ssh# ps -ef | egrep '(alexa|ssh)'
root 939 1 0 16:16 ? 00:00:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root 5955 939 0 16:36 ? 00:00:00 sshd-session: root [priv]
Ich habe alexa in fhem auch mal gelöscht und neu gemacht
Und mit den key neugeholt
Aber nichts :(
Da stimmt doch was mit dem key nicht den ich in fhem alexa bekomme ?
(assuming that alexa-fhem is running on localhost:3000)
root@debian:/opt/fhem/.ssh# sudo -u fhem ssh -i ./id_rsa -p 58824 fhem@fhem-va.fhem.de status
Registered.
Registered on 2025-05-09T14:52:09Z as 155714CE.
root@debian:/opt/fhem/.ssh# ping fhem-va.fhem.de
PING fhem-va.fhem.de (188.40.131.57) 56(84) bytes of data.
64 bytes from vmhost.fhem.de (188.40.131.57): icmp_seq=1 ttl=52 time=42.4 ms
64 bytes from vmhost.fhem.de (188.40.131.57): icmp_seq=2 ttl=52 time=40.6 ms
64 bytes from vmhost.fhem.de (188.40.131.57): icmp_seq=3 ttl=52 time=42.7 ms
^C
--- fhem-va.fhem.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 20
9.5.2025, 16:53:57] Starting SSH with -R 1234:127.0.0.1:35089 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[9.5.2025, 16:53:57] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[9.5.2025, 16:53:57] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[9.5.2025, 16:53:57] *** SSH: proxy connection established
[9.5.2025, 16:53:57] SSH: Welcome at the reverse proxy
Ohman ich habe keine Idee mehr :(
Der haussegen hängt schief meine Frau kann nix einschalten
Ich hoffe auf Hilfe von den Profis
define alexa alexa
attr alexa alexaFHEM-auth crypt:025c5a5956590f570f040f5554075351
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
# .FhemMetaInternals 1
# FD 23
# FUUID 681e0b23-f33f-078c-5aad-362ae1a2497104ca
# FVERSION 39_alexa.pm:0.238200/2021-02-24
# LAST_START 2025-05-09 17:11:01
# LAST_STOP 2025-05-09 17:11:00
# NAME alexa
# NOTIFYDEV global,global:npmjs.*alexa-fhem.*
# NR 645
# NTFY_ORDER 50-alexa
# PARTIAL
# PID 12734
# STARTS 2
# STATE running /usr/local/bin/alexa-fhem
# TYPE alexa
# active 0
# alexa-fhem version 0.5.65
# currentlogfile ./log/alexa-2025-05-09.log
# eventCount 10
# logfile ./log/alexa-%Y-%m-%d.log
# .attraggr:
# .attrminint:
# CoProcess:
# cmdFn alexa_getCMD
# name alexaFHEM
# state running /usr/local/bin/alexa-fhem
# READINGS:
# 2025-05-09 17:11:01 alexaFHEM running /usr/local/bin/alexa-fhem
# 2025-05-09 17:11:05 alexaFHEM.ProxyConnection running; SSH connected
# 2025-05-09 16:53:40 alexaFHEM.bearerToken crypt:217a06000a500b207b767c5054010404
# 2025-05-09 16:53:40 alexaFHEM.skillRegKey crypt:2508747508270a2514767d56247406010171752703750d76204c757b08070500507b75747c520e530f05
# helper:
#
setstate alexa running /usr/local/bin/alexa-fhem
setstate alexa 2025-05-09 17:11:01 alexaFHEM running /usr/local/bin/alexa-fhem
setstate alexa 2025-05-09 17:11:05 alexaFHEM.ProxyConnection running;; SSH connected
setstate alexa 2025-05-09 16:53:40 alexaFHEM.bearerToken crypt:217a06000a500b207b767c5054010404
setstate alexa 2025-05-09 16:53:40 alexaFHEM.skillRegKey crypt:2508747508270a2514767d56247406010171752703750d76204c757b08070500507b75747c520e530f05
Es sieht doch erst mal so aus, als würde es laufen (beim schnell vom Handy kucken).
Was steht denn im alexa-fhem Log, wenn du alexa-fhem startest?
Hast du fhem Devices an alexa-fhem "bekannt gegeben"?
Poste doch mal ein list eines Devices, dass du per Sprache schalten willst.
Gruß, Joachim
Ich habs rausgefunden
/opt/fhem/.ssh gelöscht
Das ist jetzt leer scheinbar zieht er das ssh file woanders her.
Aber ich kann 1 device nicht schalten in alexa
Dieses
define DVESBAD_547472 MQTT2_DEVICE DVESBAD_547472
attr DVESBAD_547472 alexaName Led-BAd
attr DVESBAD_547472 autocreate 1
attr DVESBAD_547472 comment NOTE: For on-for-timer SetExtensions are used. You may add on-for-timer option running on the device. The following is limited to 1h max duration, but will not affect future simple "on" commands:<br>on-for-timer {my $duration = $EVTPART1*10;; 'cmnd/cmnd/BADtasmota_547472/Backlog POWER1 1;; delay '.$duration.';; POWER1 0'}<br>See the "Praxisbeispiele" in the wiki for "pulseTime1" alternative option and it's restrictions.
attr DVESBAD_547472 devStateIcon {my $text = ' uptime: '.ReadingsVal($name,"Uptime","unknown").sprintf(" aktuell: %.1f W Tag: %.2f kWh Gestern: %.3f kWh Gesamt: %.4f kWh", ReadingsVal($name,"ENERGY_Power","-1"), ReadingsVal($name,"ENERGY_Today","-1"), ReadingsVal($name,"ENERGY_Yesterday","-1"), ReadingsVal($name,"ENERGY_Total","-1"));;;; my $onl = ReadingsVal($name,"LWT","false") eq "Online"?"10px-kreis-gruen":"10px-kreis-rot";;;; my $light = ReadingsVal($name,"state","off");;;;"<div><a href=\"http://".ReadingsVal($name,"IPAddress",ReadingsVal($name,"Info2_IPAddress","none"))." \"target=\"_blank\">".FW_makeImage($onl).'</a> <a href="/fhem?cmd.dummy=set '.$name.' toggle&XHR=1">'.FW_makeImage($light)."</a>$text<b></b>"}
attr DVESBAD_547472 genericDeviceType switch
attr DVESBAD_547472 icon hue_filled_outlet
attr DVESBAD_547472 jsonMap POWER1:0 POWER2:0 POWER3:0 POWER4:0 Dimmer:0 Channel_0:0 Channel_1:0 Channel_2:0 Channel_3:0 Channel_4:0 Channel_5:0 HSBColor:0 Color:0
attr DVESBAD_547472 model tasmota_basic_state_power1
attr DVESBAD_547472 readingList tele/BADtasmota_547472/LWT:.* LWT\
tele/BADtasmota_547472/STATE:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/BADtasmota_547472/SENSOR:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/BADtasmota_547472/INFO.:.* { $EVENT =~ m,^..Info[1-3]..(.+).$, ? json2nameValue($1,'',$JSONMAP) : json2nameValue($EVENT,'',$JSONMAP) }\
tele/BADtasmota_547472/UPTIME:.* { json2nameValue($EVENT,'',$JSONMAP) }\
stat/BADtasmota_547472/POWER1:.* state\
stat/BADtasmota_547472/RESULT:.* { json2nameValue($EVENT,'',$JSONMAP) }
attr DVESBAD_547472 room MQTT2_DEVICE
attr DVESBAD_547472 setList off:noArg cmnd/BADtasmota_547472/POWER1 0\
on:noArg cmnd/BADtasmota_547472/POWER1 1\
toggle:noArg cmnd/BADtasmota_547472/POWER1 2\
setOtaUrl:textField cmnd/BADtasmota_547472/OtaUrl $EVTPART1\
upgrade:noArg cmnd/BADtasmota_547472/upgrade 1
attr DVESBAD_547472 setStateList on off toggle
attr DVESBAD_547472 stateFormat {sprintf("aktuell: %.1f W Tag: %.2f kWh Gestern: %.3f kWh Gesamt: %.4f kWh", ReadingsVal($name,"ENERGY_Power","-1"), ReadingsVal($name,"ENERGY_Today","-1"), ReadingsVal($name,"ENERGY_Yesterday","-1"), ReadingsVal($name,"ENERGY_Total","-1"))}
attr DVESBAD_547472 webCmd :
# .FhemMetaInternals 1
# CID DVESBAD_547472
# DEF DVESBAD_547472
# FUUID 681e2d52-f33f-078c-dee5-7131d9632fe59bb8
# FVERSION 10_MQTT2_DEVICE.pm:0.295280/2025-01-16
# IODev m2s
# LASTInputDev meinMQTT2Client
# MSGCNT 58
# NAME DVESBAD_547472
# NR 645
# STATE aktuell: 0.0 W Tag: 0.01 kWh Gestern: 0.000 kWh Gesamt: 0.0110 kWh
# TYPE MQTT2_DEVICE
# eventCount 55
# m2s_CONN m2s_192.168.188.166_51557
# m2s_MSGCNT 29
# m2s_TIME 2025-05-09 18:59:10
# meinMQTT2Client_MSGCNT 29
# meinMQTT2Client_TIME 2025-05-09 18:59:10
# .DT:
# DEVICETOPIC DVESBAD_547472
# .attraggr:
# .attrminint:
# JSONMAP:
# Channel_0 0
# Channel_1 0
# Channel_2 0
# Channel_3 0
# Channel_4 0
# Channel_5 0
# Color 0
# Dimmer 0
# HSBColor 0
# POWER1 0
# POWER2 0
# POWER3 0
# POWER4 0
# OLDREADINGS:
# READINGS:
# 2025-05-09 18:59:10 ANALOG_Temperature 13.7
# 2025-05-09 18:59:10 ENERGY_ApparentPower 0
# 2025-05-09 18:59:10 ENERGY_Current 0.000
# 2025-05-09 18:59:10 ENERGY_Factor 0.00
# 2025-05-09 18:59:10 ENERGY_Period 0
# 2025-05-09 18:59:10 ENERGY_Power 0
# 2025-05-09 18:59:10 ENERGY_ReactivePower 0
# 2025-05-09 18:59:10 ENERGY_Today 0.011
# 2025-05-09 18:59:10 ENERGY_Total 0.011
# 2025-05-09 18:59:10 ENERGY_TotalStartTime 2025-04-25T12:46:54
# 2025-05-09 18:59:10 ENERGY_Voltage 0
# 2025-05-09 18:59:10 ENERGY_Yesterday 0.000
# 2025-05-09 18:59:10 Heap 24
# 2025-05-09 18:34:31 IODev m2s
# 2025-05-09 18:59:10 LoadAvg 19
# 2025-05-09 18:59:10 MqttCount 2
# 2025-05-09 18:54:28 SaveData on
# 2025-05-09 18:54:27 SetOption26 on
# 2025-05-09 18:59:10 Sleep 50
# 2025-05-09 18:59:10 SleepMode Dynamic
# 2025-05-09 18:54:27 StateText1 off
# 2025-05-09 18:54:27 StateText2 on
# 2025-05-09 18:54:27 StateText3 toggle
# 2025-05-09 18:54:27 StateText4 hold
# 2025-05-09 18:59:10 TempUnit C
# 2025-05-09 18:59:10 Time 2025-05-09T17:59:10
# 2025-05-09 18:59:10 Uptime 0T00:30:09
# 2025-05-09 18:59:10 UptimeSec 1809
# 2025-05-09 18:59:10 Wifi_AP 1
# 2025-05-09 18:59:10 Wifi_BSSId E0:28:6D:95:7F:8C
# 2025-05-09 18:59:10 Wifi_Channel 6
# 2025-05-09 18:59:10 Wifi_Downtime 0T00:00:03
# 2025-05-09 18:59:10 Wifi_LinkCount 1
# 2025-05-09 18:59:10 Wifi_Mode 11n
# 2025-05-09 18:59:10 Wifi_RSSI 84
# 2025-05-09 18:59:10 Wifi_SSId EM WLAN
# 2025-05-09 18:59:10 Wifi_Signal -58
# 2025-05-09 18:54:26 attrTemplateVersion 20210523
# 2025-05-09 18:54:38 state off
#
setstate DVESBAD_547472 aktuell: 0.0 W Tag: 0.01 kWh Gestern: 0.000 kWh Gesamt: 0.0110 kWh
setstate DVESBAD_547472 2025-05-09 18:59:10 ANALOG_Temperature 13.7
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_ApparentPower 0
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Current 0.000
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Factor 0.00
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Period 0
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Power 0
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_ReactivePower 0
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Today 0.011
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Total 0.011
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_TotalStartTime 2025-04-25T12:46:54
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Voltage 0
setstate DVESBAD_547472 2025-05-09 18:59:10 ENERGY_Yesterday 0.000
setstate DVESBAD_547472 2025-05-09 18:59:10 Heap 24
setstate DVESBAD_547472 2025-05-09 18:34:31 IODev m2s
setstate DVESBAD_547472 2025-05-09 18:59:10 LoadAvg 19
setstate DVESBAD_547472 2025-05-09 18:59:10 MqttCount 2
setstate DVESBAD_547472 2025-05-09 18:54:28 SaveData on
setstate DVESBAD_547472 2025-05-09 18:54:27 SetOption26 on
setstate DVESBAD_547472 2025-05-09 18:59:10 Sleep 50
setstate DVESBAD_547472 2025-05-09 18:59:10 SleepMode Dynamic
setstate DVESBAD_547472 2025-05-09 18:54:27 StateText1 off
setstate DVESBAD_547472 2025-05-09 18:54:27 StateText2 on
setstate DVESBAD_547472 2025-05-09 18:54:27 StateText3 toggle
setstate DVESBAD_547472 2025-05-09 18:54:27 StateText4 hold
setstate DVESBAD_547472 2025-05-09 18:59:10 TempUnit C
setstate DVESBAD_547472 2025-05-09 18:59:10 Time 2025-05-09T17:59:10
setstate DVESBAD_547472 2025-05-09 18:59:10 Uptime 0T00:30:09
setstate DVESBAD_547472 2025-05-09 18:59:10 UptimeSec 1809
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_AP 1
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_BSSId E0:28:6D:95:7F:8C
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_Channel 6
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_Downtime 0T00:00:03
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_LinkCount 1
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_Mode 11n
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_RSSI 84
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_SSId EM WLAN
setstate DVESBAD_547472 2025-05-09 18:59:10 Wifi_Signal -58
setstate DVESBAD_547472 2025-05-09 18:54:26 attrTemplateVersion 20210523
setstate DVESBAD_547472 2025-05-09 18:54:38 state off
Hier mal eins welches funktioniert
define inthira_ir MQTT2_DEVICE DVES_8FFB3A
attr inthira_ir IODev m2s
attr inthira_ir alexaName fm.tasmota2
attr inthira_ir alias Kühltruhe
attr inthira_ir autocreate 0
attr inthira_ir devStateIcon off:taster_ch_aus_rot@red on:taster_ch_an_gruen@green offline:taster_ch_an_gruen@blue:off
attr inthira_ir event-on-change-reading .*
attr inthira_ir group ir2
attr inthira_ir icon message_socket
attr inthira_ir readingList tele/tasmota_8FFB3A/LWT:.* LWT\
tele/tasmota_8FFB3A/STATE:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_8FFB3A/SENSOR:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_8FFB3A/INFO.:.* { $EVENT =~ m,^..Info[1-3]..(.+).$, ? json2nameValue($1,'',$JSONMAP) : json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_8FFB3A/UPTIME:.* { json2nameValue($EVENT,'',$JSONMAP) }\
stat/tasmota_8FFB3A/POWER1:.* state\
stat/tasmota_8FFB3A/RESULT:.* { json2nameValue($EVENT,'',$JSONMAP) }\
DVES_8FFB3A:tasmota/discovery/A4E57C8FFB3A/config:.* { json2nameValue($EVENT, 'config_', $JSONMAP) }\
DVES_8FFB3A:tasmota/discovery/A4E57C8FFB3A/sensors:.* { json2nameValue($EVENT, 'sensors_', $JSONMAP) }
attr inthira_ir room MQTT2_DEVICE
attr inthira_ir setList off:noArg cmnd/tasmota_8FFB3A/POWER1 0\
on:noArg cmnd/tasmota_8FFB3A/POWER1 1
attr inthira_ir stateFormat [$name:state]\
|<span style='color:#008800'>[$name:ENERGY_Power:r1]</span> Watt\
| heute: [$name:ENERGY_Today:r1] kWh <span style='color:#FF0000'>[$name:kosten2:r2] €</span>\
| gesamt: [$name:ENERGY_Total:r1] kWh <span style='color:#FF0000'>[$name:kosten:r2] €</span>
attr inthira_ir userReadings state {ReadingsVal($name,"POWER1","")}, Verbrauch difference {1000*ReadingsVal($name,"ENERGY_Total",0);;;;},\
kosten {sprintf("%0.2f ", ReadingsNum("inthira_ir","ENERGY_Total",0)*ReadingsNum("einstellung_Strompreis_je_KWH","state",0)/100)},\
kosten2 {sprintf("%0.2f ", ReadingsNum("inthira_ir","ENERGY_Today",0)*ReadingsNum("einstellung_Strompreis_je_KWH","state",0)/100)},\
temperature {sprintf("%0.1f ", ReadingsNum("Inthira","temperature",0))}\
attr inthira_ir webCmd :
# .FhemMetaInternals 1
# CID DVES_8FFB3A
# DEF DVES_8FFB3A
# FUUID 623c2b09-f33f-078c-f91f-2af32c6cba45d08c
# FVERSION 10_MQTT2_DEVICE.pm:0.295280/2025-01-16
# IODev m2s
# LASTInputDev meinMQTT2Client
# MSGCNT 121
# NAME inthira_ir
# NR 437
# STATE on
#|<span style='color:#008800'>0.0</span> Watt
#| heute: 0.3 kWh <span style='color:#FF0000'>0.09 €</span>
#| gesamt: 100.7 kWh <span style='color:#FF0000'>33.22 €</span>
# TYPE MQTT2_DEVICE
# eventCount 69
# m2s_CONN m2s_192.168.188.70_53184
# m2s_MSGCNT 61
# m2s_TIME 2025-05-09 19:02:58
# meinMQTT2Client_MSGCNT 60
# meinMQTT2Client_TIME 2025-05-09 19:02:58
# .DT:
# DEVICETOPIC inthira_ir
# .attraggr:
# .attreocr:
# .*
# .attrminint:
# .userReadings:
# HASH(0x55c750e09bf8)
# HASH(0x55c750ecfb20)
# HASH(0x55c750ecfb08)
# HASH(0x55c750ecff28)
# HASH(0x55c750ed0018)
# READINGS:
# 2024-08-17 02:59:59 Command Unknown
# 2025-05-09 19:02:58 ENERGY_ApparentPower 0
# 2025-05-09 19:02:58 ENERGY_Current 0.000
# 2025-05-09 19:02:58 ENERGY_Factor 0.00
# 2025-05-09 19:02:58 ENERGY_Period 0
# 2025-05-09 19:02:58 ENERGY_Power 0
# 2025-05-09 19:02:58 ENERGY_ReactivePower 0
# 2025-05-09 19:02:58 ENERGY_Today 0.258
# 2025-05-09 19:02:58 ENERGY_Total 100.670
# 2025-05-09 19:02:58 ENERGY_TotalStartTime 2024-08-16T08:21:15
# 2025-05-09 19:02:58 ENERGY_Voltage 237
# 2025-05-09 19:02:58 ENERGY_Yesterday 0.372
# 2024-09-17 16:13:42 FallbackTopic cmnd/DVES_8FFB3A_fb/
# 2024-09-17 16:13:42 GroupTopic cmnd/tasmotas/
# 2025-05-09 19:02:58 Heap 26
# 2024-09-17 16:13:42 Hostname tasmota-8FFB3A-6970
# 2025-05-09 18:34:32 IODev m2s
# 2024-09-17 16:13:42 IPAddress 192.168.188.70
# 2025-05-09 18:34:38 LWT Online
# 2025-05-09 19:02:58 LoadAvg 19
# 2024-09-17 16:13:42 Module NOUS A1T
# 2025-05-09 19:02:58 MqttCount 379
# 2025-05-09 19:02:58 POWER1 on
# 2022-04-03 14:04:51 PowerSetCal 11026
# 2024-09-17 16:13:42 RestartReason Power On
# 2025-05-09 19:02:58 Sleep 50
# 2025-05-09 19:02:58 SleepMode Dynamic
# 2022-05-20 13:01:48 TelePeriod 60
# 2025-05-09 19:02:58 Time 2025-05-09T18:02:56
# 2025-05-09 19:02:58 Uptime 234T04:00:17
# 2025-05-09 19:02:58 UptimeSec 20232017
# 2025-05-09 19:02:58 Verbrauch 0
# 2024-09-17 16:13:42 Version 10.0.0(tasmota)
# 2022-04-03 13:59:15 VoltageSetCal 1635
# 2024-09-17 16:13:42 WebServerMode Admin
# 2025-05-09 19:02:58 Wifi_AP 1
# 2025-05-09 19:02:58 Wifi_BSSId B0:F2:08:64:A8:AD
# 2025-05-09 19:02:58 Wifi_Channel 11
# 2025-05-09 19:02:58 Wifi_Downtime 0T00:26:13
# 2025-05-09 19:02:58 Wifi_LinkCount 10
# 2025-05-09 19:02:58 Wifi_Mode 11n
# 2025-05-09 19:02:58 Wifi_RSSI 98
# 2025-05-09 19:02:58 Wifi_SSId EM WLAN
# 2025-05-09 19:02:58 Wifi_Signal -51
# 2025-05-09 18:34:38 config_btn_1 0
# 2025-05-09 18:34:38 config_btn_2 0
# 2025-05-09 18:34:38 config_btn_3 0
# 2025-05-09 18:34:38 config_btn_4 0
# 2025-05-09 18:34:38 config_btn_5 0
# 2025-05-09 18:34:38 config_btn_6 0
# 2025-05-09 18:34:38 config_btn_7 0
# 2025-05-09 18:34:38 config_btn_8 0
# 2025-05-09 18:34:38 config_dn Tasmota
# 2025-05-09 18:34:38 config_fn_1 Tasmota
# 2025-05-09 18:34:38 config_ft %prefix%/%topic%/
# 2025-05-09 18:34:38 config_hn tasmota-8FFB3A-6970
# 2025-05-09 18:34:38 config_if 0
# 2025-05-09 18:34:38 config_ip 192.168.188.70
# 2025-05-09 18:34:38 config_lk 0
# 2025-05-09 18:34:38 config_lt_st 0
# 2025-05-09 18:34:38 config_mac A4E57C8FFB3A
# 2025-05-09 18:34:38 config_md NOUS A1T
# 2025-05-09 18:34:38 config_ofln Offline
# 2025-05-09 18:34:38 config_onln Online
# 2025-05-09 18:34:38 config_rl_1 1
# 2025-05-09 18:34:38 config_rl_2 0
# 2025-05-09 18:34:38 config_rl_3 0
# 2025-05-09 18:34:38 config_rl_4 0
# 2025-05-09 18:34:38 config_rl_5 0
# 2025-05-09 18:34:38 config_rl_6 0
# 2025-05-09 18:34:38 config_rl_7 0
# 2025-05-09 18:34:38 config_rl_8 0
# 2025-05-09 18:34:38 config_sho_1 0
# 2025-05-09 18:34:38 config_sho_2 0
# 2025-05-09 18:34:38 config_sho_3 0
# 2025-05-09 18:34:38 config_sho_4 0
# 2025-05-09 18:34:38 config_so_11 0
# 2025-05-09 18:34:38 config_so_114 0
# 2025-05-09 18:34:38 config_so_117 0
# 2025-05-09 18:34:38 config_so_13 0
# 2025-05-09 18:34:38 config_so_17 0
# 2025-05-09 18:34:38 config_so_20 0
# 2025-05-09 18:34:38 config_so_30 0
# 2025-05-09 18:34:38 config_so_4 0
# 2025-05-09 18:34:38 config_so_68 0
# 2025-05-09 18:34:38 config_so_73 0
# 2025-05-09 18:34:38 config_so_82 0
# 2025-05-09 18:34:38 config_state_1 off
# 2025-05-09 18:34:38 config_state_2 on
# 2025-05-09 18:34:38 config_state_3 toggle
# 2025-05-09 18:34:38 config_state_4 hold
# 2025-05-09 18:34:38 config_sw 10.0.0
# 2025-05-09 18:34:38 config_swc_1 -1
# 2025-05-09 18:34:38 config_swc_2 -1
# 2025-05-09 18:34:38 config_swc_3 -1
# 2025-05-09 18:34:38 config_swc_4 -1
# 2025-05-09 18:34:38 config_swc_5 -1
# 2025-05-09 18:34:38 config_swc_6 -1
# 2025-05-09 18:34:38 config_swc_7 -1
# 2025-05-09 18:34:38 config_swc_8 -1
# 2025-05-09 18:34:38 config_t tasmota_8FFB3A
# 2025-05-09 18:34:38 config_tp_1 cmnd
# 2025-05-09 18:34:38 config_tp_2 stat
# 2025-05-09 18:34:38 config_tp_3 tele
# 2025-05-09 18:34:38 config_ty 0
# 2025-05-09 18:34:38 config_ver 1
# 2024-08-16 09:21:15 json2nameValueErrorText json2nameValue: no closing } found
# 2024-08-16 09:21:15 json2nameValueInput {"EnergyTotal":{"Total":0.191,"Yesterday":0.560,"Today":0.191}
# 2025-05-09 19:02:58 kosten 33.22
# 2025-05-09 19:02:58 kosten2 0.09
# 2025-05-09 18:34:38 sensors_sn_ENERGY_ApparentPower 49
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Current 0.206
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Factor 0.88
# 2025-03-14 03:01:47 sensors_sn_ENERGY_Period 0
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Power 43
# 2025-05-09 18:34:38 sensors_sn_ENERGY_ReactivePower 23
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Today 0.249
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Total 100.660
# 2025-05-09 18:34:38 sensors_sn_ENERGY_TotalStartTime 2024-08-16T08:21:15
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Voltage 237
# 2025-05-09 18:34:38 sensors_sn_ENERGY_Yesterday 0.372
# 2025-05-09 18:34:38 sensors_sn_Time 2025-05-09T17:34:37
# 2025-05-09 18:34:38 sensors_ver 1
# 2025-05-09 19:02:58 state on
# 2025-05-09 18:35:29 subscriptions cmnd/DVES_8FFB3A_fb/# cmnd/tasmota_8FFB3A/# cmnd/tasmotas/#
# 2022-06-15 07:30:43 sunpos_azimuth 75.9128133246138
# 2022-06-15 07:30:43 sunpos_elevation 18.9194974222393
# 2025-05-09 19:02:58 temperature 0.0
#
setstate inthira_ir on\
|<span style='color:#008800'>0.0</span> Watt\
| heute: 0.3 kWh <span style='color:#FF0000'>0.09 €</span>\
| gesamt: 100.7 kWh <span style='color:#FF0000'>33.22 €</span>
setstate inthira_ir 2024-08-17 02:59:59 Command Unknown
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_ApparentPower 0
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Current 0.000
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Factor 0.00
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Period 0
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Power 0
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_ReactivePower 0
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Today 0.258
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Total 100.670
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_TotalStartTime 2024-08-16T08:21:15
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Voltage 237
setstate inthira_ir 2025-05-09 19:02:58 ENERGY_Yesterday 0.372
setstate inthira_ir 2024-09-17 16:13:42 FallbackTopic cmnd/DVES_8FFB3A_fb/
setstate inthira_ir 2024-09-17 16:13:42 GroupTopic cmnd/tasmotas/
setstate inthira_ir 2025-05-09 19:02:58 Heap 26
setstate inthira_ir 2024-09-17 16:13:42 Hostname tasmota-8FFB3A-6970
setstate inthira_ir 2025-05-09 18:34:32 IODev m2s
setstate inthira_ir 2024-09-17 16:13:42 IPAddress 192.168.188.70
setstate inthira_ir 2025-05-09 18:34:38 LWT Online
setstate inthira_ir 2025-05-09 19:02:58 LoadAvg 19
setstate inthira_ir 2024-09-17 16:13:42 Module NOUS A1T
setstate inthira_ir 2025-05-09 19:02:58 MqttCount 379
setstate inthira_ir 2025-05-09 19:02:58 POWER1 on
setstate inthira_ir 2022-04-03 14:04:51 PowerSetCal 11026
setstate inthira_ir 2024-09-17 16:13:42 RestartReason Power On
setstate inthira_ir 2025-05-09 19:02:58 Sleep 50
setstate inthira_ir 2025-05-09 19:02:58 SleepMode Dynamic
setstate inthira_ir 2022-05-20 13:01:48 TelePeriod 60
setstate inthira_ir 2025-05-09 19:02:58 Time 2025-05-09T18:02:56
setstate inthira_ir 2025-05-09 19:02:58 Uptime 234T04:00:17
setstate inthira_ir 2025-05-09 19:02:58 UptimeSec 20232017
setstate inthira_ir 2025-05-09 19:02:58 Verbrauch 0
setstate inthira_ir 2024-09-17 16:13:42 Version 10.0.0(tasmota)
setstate inthira_ir 2022-04-03 13:59:15 VoltageSetCal 1635
setstate inthira_ir 2024-09-17 16:13:42 WebServerMode Admin
setstate inthira_ir 2025-05-09 19:02:58 Wifi_AP 1
setstate inthira_ir 2025-05-09 19:02:58 Wifi_BSSId B0:F2:08:64:A8:AD
setstate inthira_ir 2025-05-09 19:02:58 Wifi_Channel 11
setstate inthira_ir 2025-05-09 19:02:58 Wifi_Downtime 0T00:26:13
setstate inthira_ir 2025-05-09 19:02:58 Wifi_LinkCount 10
setstate inthira_ir 2025-05-09 19:02:58 Wifi_Mode 11n
setstate inthira_ir 2025-05-09 19:02:58 Wifi_RSSI 98
setstate inthira_ir 2025-05-09 19:02:58 Wifi_SSId EM WLAN
setstate inthira_ir 2025-05-09 19:02:58 Wifi_Signal -51
setstate inthira_ir 2025-05-09 18:34:38 config_btn_1 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_2 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_3 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_4 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_5 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_6 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_7 0
setstate inthira_ir 2025-05-09 18:34:38 config_btn_8 0
setstate inthira_ir 2025-05-09 18:34:38 config_dn Tasmota
setstate inthira_ir 2025-05-09 18:34:38 config_fn_1 Tasmota
setstate inthira_ir 2025-05-09 18:34:38 config_ft %prefix%/%topic%/
setstate inthira_ir 2025-05-09 18:34:38 config_hn tasmota-8FFB3A-6970
setstate inthira_ir 2025-05-09 18:34:38 config_if 0
setstate inthira_ir 2025-05-09 18:34:38 config_ip 192.168.188.70
setstate inthira_ir 2025-05-09 18:34:38 config_lk 0
setstate inthira_ir 2025-05-09 18:34:38 config_lt_st 0
setstate inthira_ir 2025-05-09 18:34:38 config_mac A4E57C8FFB3A
setstate inthira_ir 2025-05-09 18:34:38 config_md NOUS A1T
setstate inthira_ir 2025-05-09 18:34:38 config_ofln Offline
setstate inthira_ir 2025-05-09 18:34:38 config_onln Online
setstate inthira_ir 2025-05-09 18:34:38 config_rl_1 1
setstate inthira_ir 2025-05-09 18:34:38 config_rl_2 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_3 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_4 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_5 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_6 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_7 0
setstate inthira_ir 2025-05-09 18:34:38 config_rl_8 0
setstate inthira_ir 2025-05-09 18:34:38 config_sho_1 0
setstate inthira_ir 2025-05-09 18:34:38 config_sho_2 0
setstate inthira_ir 2025-05-09 18:34:38 config_sho_3 0
setstate inthira_ir 2025-05-09 18:34:38 config_sho_4 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_11 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_114 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_117 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_13 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_17 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_20 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_30 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_4 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_68 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_73 0
setstate inthira_ir 2025-05-09 18:34:38 config_so_82 0
setstate inthira_ir 2025-05-09 18:34:38 config_state_1 off
setstate inthira_ir 2025-05-09 18:34:38 config_state_2 on
setstate inthira_ir 2025-05-09 18:34:38 config_state_3 toggle
setstate inthira_ir 2025-05-09 18:34:38 config_state_4 hold
setstate inthira_ir 2025-05-09 18:34:38 config_sw 10.0.0
setstate inthira_ir 2025-05-09 18:34:38 config_swc_1 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_2 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_3 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_4 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_5 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_6 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_7 -1
setstate inthira_ir 2025-05-09 18:34:38 config_swc_8 -1
setstate inthira_ir 2025-05-09 18:34:38 config_t tasmota_8FFB3A
setstate inthira_ir 2025-05-09 18:34:38 config_tp_1 cmnd
setstate inthira_ir 2025-05-09 18:34:38 config_tp_2 stat
setstate inthira_ir 2025-05-09 18:34:38 config_tp_3 tele
setstate inthira_ir 2025-05-09 18:34:38 config_ty 0
setstate inthira_ir 2025-05-09 18:34:38 config_ver 1
setstate inthira_ir 2024-08-16 09:21:15 json2nameValueErrorText json2nameValue: no closing } found
setstate inthira_ir 2024-08-16 09:21:15 json2nameValueInput {"EnergyTotal":{"Total":0.191,"Yesterday":0.560,"Today":0.191}
setstate inthira_ir 2025-05-09 19:02:58 kosten 33.22
setstate inthira_ir 2025-05-09 19:02:58 kosten2 0.09
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_ApparentPower 49
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Current 0.206
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Factor 0.88
setstate inthira_ir 2025-03-14 03:01:47 sensors_sn_ENERGY_Period 0
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Power 43
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_ReactivePower 23
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Today 0.249
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Total 100.660
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_TotalStartTime 2024-08-16T08:21:15
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Voltage 237
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_ENERGY_Yesterday 0.372
setstate inthira_ir 2025-05-09 18:34:38 sensors_sn_Time 2025-05-09T17:34:37
setstate inthira_ir 2025-05-09 18:34:38 sensors_ver 1
setstate inthira_ir 2025-05-09 19:02:58 state on
setstate inthira_ir 2025-05-09 18:35:29 subscriptions cmnd/DVES_8FFB3A_fb/# cmnd/tasmota_8FFB3A/# cmnd/tasmotas/#
setstate inthira_ir 2022-06-15 07:30:43 sunpos_azimuth 75.9128133246138
setstate inthira_ir 2022-06-15 07:30:43 sunpos_elevation 18.9194974222393
setstate inthira_ir 2025-05-09 19:02:58 temperature 0.0
Eine Idee?
Zitat von: brain666 am 09 Mai 2025, 19:04:09/opt/fhem/.ssh gelöscht
Das ist jetzt leer scheinbar zieht er das ssh file woanders her.
Würde mich wundern...
Mich wundert, dass das 2te Device ohne genericDeviceType (zumindest konnte ich da jetzt nix finden) geht aber egal.
Deine alexa-name Attribute sind naja.
Willst du das Gerät per Sprache wirklich mit diesem Namen ansprechen/schalten?
Und das hier könnte fraglich sein:
Zitat von: brain666 am 09 Mai 2025, 19:04:09attr DVESBAD_547472 alexaName Led-BAd
Wo sind die Auszüge aus dem alexa-fhem Log beim Start von alexa-fhem?
Was sagt denn "Alexa/Amazon", wenn du das Gerät schalten willst?
Gruß, Joachim
define DVES_547472 MQTT2_DEVICE DVES_547472
attr DVES_547472 alexaName ledbad
attr DVES_547472 autocreate 0
attr DVES_547472 comment NOTE: For on-for-timer SetExtensions are used. You may add on-for-timer option running on the device. The following is limited to 1h max duration, but will not affect future simple "on" commands:<br>on-for-timer {my $duration = $EVTPART1*10;; 'cmnd/cmnd/tasmota_547472/Backlog POWER1 1;; delay '.$duration.';; POWER1 0'}<br>See the "Praxisbeispiele" in the wiki for "pulseTime1" alternative option and it's restrictions.
attr DVES_547472 devStateIcon {my $text = ' uptime: '.ReadingsVal($name,"Uptime","unknown").sprintf(" aktuell: %.1f W Tag: %.2f kWh Gestern: %.3f kWh Gesamt: %.4f kWh", ReadingsVal($name,"ENERGY_Power","-1"), ReadingsVal($name,"ENERGY_Today","-1"), ReadingsVal($name,"ENERGY_Yesterday","-1"), ReadingsVal($name,"ENERGY_Total","-1"));;;; my $onl = ReadingsVal($name,"LWT","false") eq "Online"?"10px-kreis-gruen":"10px-kreis-rot";;;; my $light = ReadingsVal($name,"state","off");;;;"<div><a href=\"http://".ReadingsVal($name,"IPAddress",ReadingsVal($name,"Info2_IPAddress","none"))." \"target=\"_blank\">".FW_makeImage($onl).'</a> <a href="/fhem?cmd.dummy=set '.$name.' toggle&XHR=1">'.FW_makeImage($light)."</a>$text<b></b>"}
attr DVES_547472 genericDeviceType switch
attr DVES_547472 icon hue_filled_outlet
attr DVES_547472 jsonMap POWER1:0 POWER2:0 POWER3:0 POWER4:0 Dimmer:0 Channel_0:0 Channel_1:0 Channel_2:0 Channel_3:0 Channel_4:0 Channel_5:0 HSBColor:0 Color:0
attr DVES_547472 model tasmota_POW
attr DVES_547472 readingList tele/tasmota_547472/LWT:.* LWT\
tele/tasmota_547472/STATE:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_547472/SENSOR:.* { json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_547472/INFO.:.* { $EVENT =~ m,^..Info[1-3]..(.+).$, ? json2nameValue($1,'',$JSONMAP) : json2nameValue($EVENT,'',$JSONMAP) }\
tele/tasmota_547472/UPTIME:.* { json2nameValue($EVENT,'',$JSONMAP) }\
stat/tasmota_547472/POWER1:.* state\
stat/tasmota_547472/RESULT:.* { json2nameValue($EVENT,'',$JSONMAP) }
attr DVES_547472 room MQTT2_DEVICE
attr DVES_547472 setList off:noArg cmnd/tasmota_547472/POWER1 0\
on:noArg cmnd/tasmota_547472/POWER1 1\
toggle:noArg cmnd/tasmota_547472/POWER1 2
attr DVES_547472 setStateList on off toggle
attr DVES_547472 stateFormat {sprintf("aktuell: %.1f W Tag: %.2f kWh Gestern: %.3f kWh Gesamt: %.4f kWh", ReadingsVal($name,"ENERGY_Power","-1"), ReadingsVal($name,"ENERGY_Today","-1"), ReadingsVal($name,"ENERGY_Yesterday","-1"), ReadingsVal($name,"ENERGY_Total","-1"))}
attr DVES_547472 webCmd :
# CFGFN
# CID DVES_547472
# DEF DVES_547472
# FUUID 681edb29-f33f-078c-bae8-8cd1377bf71434a0
# IODev m2s
# LASTInputDev meinMQTT2Client
# MSGCNT 12
# NAME DVES_547472
# NR 646
# STATE aktuell: -1.0 W Tag: -1.00 kWh Gestern: -1.000 kWh Gesamt: -1.0000 kWh
# TYPE MQTT2_DEVICE
# eventCount 27
# m2s_CONN m2s_192.168.188.166_60317
# m2s_MSGCNT 6
# m2s_TIME 2025-05-10 06:51:51
# meinMQTT2Client_MSGCNT 6
# meinMQTT2Client_TIME 2025-05-10 06:51:51
# .DT:
# DEVICETOPIC DVES_547472
# .attraggr:
# .attrminint:
# JSONMAP:
# Channel_0 0
# Channel_1 0
# Channel_2 0
# Channel_3 0
# Channel_4 0
# Channel_5 0
# Color 0
# Dimmer 0
# HSBColor 0
# POWER1 0
# POWER2 0
# POWER3 0
# POWER4 0
# OLDREADINGS:
# READINGS:
# 2025-05-10 06:50:49 IODev m2s
# 2025-05-10 06:51:51 SaveData on
# 2025-05-10 06:51:51 SetOption26 on
# 2025-05-10 06:51:50 StateText1 off
# 2025-05-10 06:51:51 StateText2 on
# 2025-05-10 06:51:51 StateText3 toggle
# 2025-05-10 06:51:51 StateText4 hold
# 2025-05-10 06:51:50 attrTemplateVersion 20210903
#
setstate DVES_547472 aktuell: -1.0 W Tag: -1.00 kWh Gestern: -1.000 kWh Gesamt: -1.0000 kWh
setstate DVES_547472 2025-05-10 06:50:49 IODev m2s
setstate DVES_547472 2025-05-10 06:51:51 SaveData on
setstate DVES_547472 2025-05-10 06:51:51 SetOption26 on
setstate DVES_547472 2025-05-10 06:51:50 StateText1 off
setstate DVES_547472 2025-05-10 06:51:51 StateText2 on
setstate DVES_547472 2025-05-10 06:51:51 StateText3 toggle
setstate DVES_547472 2025-05-10 06:51:51 StateText4 hold
setstate DVES_547472 2025-05-10 06:51:50 attrTemplateVersion 20210903
type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f","cookie":{"device":"DVES_547472","fuuid":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"}},"payload":{}}}
[10.5.2025, 06:47:10] <<<< [ssh] {"header":{"namespace":"Alexa","name":"ErrorResponse","payloadVersion":"3","messageId":"bf3ba8cb-1016-4338-80da-a92c0dc15e8d","correlationToken":"-"},"payload":{"type":"NO_SUCH_ENDPOINT","message":"unknown"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f","cookie":{"device":"DVES_547472","fuuid":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"}}}
[10.5.2025, 06:47:10] >>>> [ssh] {"directive":{"header":{"messageId":"233ebadc-9567-487d-a486-a05042d88b90","namespace":"Alexa","name":"ReportState","payloadVersion":"3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"623c2b09-f33f-078c-f91f-2af32c6cba45d08c","cookie":{"device":"inthira_ir","fuuid":"623c2b09-f33f-078c-f91f-
Ich habe den ledbad nochmal neu angelegt.
Es steht in der alexa app nur warte auf mqtt2-device
Dann kommt fehler in der app.
Löschen kann ich das ledbad auch nicht in der alex app.
4aa4c44b4f4f","namespace":"Alexa","name":"ReportState","payloadVersion":"3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f","cookie":{"device":"DVES_547472","fuuid":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"}},"payload":{}}}
[10.5.2025, 06:59:31] <<<< [ssh] {"context":{"properties":[]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"a4f52d79-2233-4836-bd3f-b0f9942f6781","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"},"payloa
4aa4c44b4f4f","namespace":"Alexa","name":"ReportState","payloadVersion":"3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f","cookie":{"device":"DVES_547472","fuuid":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"}},"payload":{}}}
[10.5.2025, 06:59:31] <<<< [ssh] {"context":{"properties":[]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"a4f52d79-2233-4836-bd3f-b0f9942f6781","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"680b76c0-f33f-078c-3951-585fd7bebc1b0c9f"},"payload":{}}}
[10.5.2025, 06:59:31] >>>> [ssh] {"directive":{"header":{"messageId":"326a70b0-68ea-400d-9594-98edce2f977a","namespace":"Alexa","name":"ReportState","payloadVersion":"3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"623c33f6-f33f-078c-f01e-6bb67b3195c0b609","cookie":{"device":"FM_Wama","fuuid":"623c33f6-f33f-078c-f01e-6bb67b3195c0b609"}},"payload":{}}}
[10.5.2025, 06:59:31] [FHEM] caching: On: 0 (as number; from 'off')
[10.5.2025, 06:59:31] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"OFF","timeOfSample":"2025-05-10T04:59:31.673Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"650ad5dc-991d-4377-8390-68e594308697","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"646B718-721F87C240D508E3"},"endpointId":"623c33f6-f33f-078c-f01e-6bb67b3195c0b609"},"payload":{}}}
jump to the top
Ffuid habe ich gerade mal in der fhem cfg angepasst klappt auch nicht.
Was meinst du mit ffuid angepasst?
Manuell in der fhem.cfg? <- lassen!
Warum postest du nicht, wie angefragt das alexa-fhem Log beim Start von alexa-fhem?
Bzgl. löschen gibt es wohl (aktuell) seitens Amazon Probleme...
alexaName ledbad <- naja...
EDIT: nach Änderungen alexa-fhem neu gestartet bzw. reload ausgeführt?
Was geht, bzw. was nicht?
Wird das Device in der App erkannt/angezeigt?
Lässt es sich da schalten?
Wenn mit Sprache: was ist die Antwort? Was wird erkannt? <- History in der App
Gruß, Joachim
://127.0.0.1:33889 for proxy connections
[10.5.2025, 09:06:48] *** SSH: checking proxy configuration
[10.5.2025, 09:06:48] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[10.5.2025, 09:06:48] 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,
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: 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(shapeMode)]: false,
[Symbol(kCapture)]: false,
[Symbol(async_id_symbol)]: 202,
[Symbol(kUniqueHeaders)]: null,
[Symbol(http.server.connections)]: ConnectionsList {},
[Symbol(http.server.connectionsCheckingInterval)]: Timeout {
_idleTimeout: 30000,
_idlePrev: [TimersList],
_idleNext: [TimersList],
_idleStart: 4457,
_onTimeout: [Function: bound checkConnections],
_timerArgs: undefined,
_repeat: 30000,
_destroyed: false,
[Symbol(refed)]: false,
[Symbol(kHasPrimitive)]: false,
[Symbol(asyncId)]: 204,
[Symbol(triggerId)]: 203
}
}
},
connections: [
{
filter: 'alexaName=..*',
uid: 999,
name: 'FHEM',
server: '192.168.188.21',
webname: 'fhem',
port: '8083'
}
]
}
[10.5.2025, 09:06:48] sshautoconf: SSH key seems to exist
[10.5.2025, 09:06:48] sshautoconf: Our SSH key is known at the reverse proxy, good!
[10.5.2025, 09:06:48] [FHEM] executing: http://192.168.188.21: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&XHR=1
*** FHEM: connected
[10.5.2025, 09:06:48] [FHEM] got: 6 results
[10.5.2025, 09:06:48] [FHEM] DVES_547472 is switch
[10.5.2025, 09:06:48] [FHEM] DVES_547472 has
[10.5.2025, 09:06:48] [FHEM] On [undefined;on,off]
[10.5.2025, 09:06:48] [FHEM] DVES_547472 will not send proactive events
[10.5.2025, 09:06:48] [FHEM]
Sorry am mobile ist schwere
Mache später mal am Laptop
[10.5.2025, 09:06:32] Got SIGTERM, shutting down alexa-fhem...
[10.5.2025, 09:06:32] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[10.5.2025, 09:06:32] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%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%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[10.5.2025, 09:06:32] Stopping SSH ...
[10.5.2025, 09:06:32] Reading alexaFHEM.ProxyConnection set to stopped
[10.5.2025, 09:06:32] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[10.5.2025, 09:06:32] *** SSH: exited with 255
[10.5.2025, 09:06:44] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[10.5.2025, 09:06:44] os.homedir()=/opt/fhem
[10.5.2025, 09:06:44] this is alexa-fhem 0.5.65
[10.5.2025, 09:06:44] connecting to FHEM ...
[10.5.2025, 09:06:44] [FHEM] defaults to: will not send proactive events
[10.5.2025, 09:06:44] [FHEM] trying longpoll to listen for fhem events
[10.5.2025, 09:06:44] [FHEM] starting longpoll: http://192.168.188.21:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1746860804843
[10.5.2025, 09:06:47] [FHEM] got csrfToken:
[10.5.2025, 09:06:47] [FHEM] Checking devices and attributes...
[10.5.2025, 09:06:47] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[10.5.2025, 09:06:47] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[10.5.2025, 09:06:47] [FHEM] waiting for events ...
[10.5.2025, 09:06:47] [FHEM] Fetching FHEM devices...
[10.5.2025, 09:06:47] [FHEM] fetching: http://192.168.188.21:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&XHR=1
[10.5.2025, 09:06:48] [FHEM] alexa device is alexa
[10.5.2025, 09:06:48] [FHEM] alexa will not send proactive events
[10.5.2025, 09:06:48] [FHEM] alexa uses ID: 681e23bc-f33f-078c-be49-a21dbbf28f87e6e3
[10.5.2025, 09:06:48] [FHEM] executing: http://192.168.188.21: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&XHR=1
[10.5.2025, 09:06:48] [FHEM] executing: http://192.168.188.21: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&XHR=1
[10.5.2025, 09:06:48] [FHEM] executing: http://192.168.188.21: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&XHR=1
[10.5.2025, 09:06:48] Server listening on: http://127.0.0.1:33889 for proxy connections
[10.5.2025, 09:06:48] *** SSH: checking proxy configuration
[10.5.2025, 09:06:48] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[10.5.2025, 09:06:48] 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,
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: 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(shapeMode)]: false,
[Symbol(kCapture)]: false,
[Symbol(async_id_symbol)]: 202,
[Symbol(kUniqueHeaders)]: null,
[Symbol(http.server.connections)]: ConnectionsList {},
[Symbol(http.server.connectionsCheckingInterval)]: Timeout {
_idleTimeout: 30000,
_idlePrev: [TimersList],
_idleNext: [TimersList],
_idleStart: 4457,
_onTimeout: [Function: bound checkConnections],
_timerArgs: undefined,
_repeat: 30000,
_destroyed: false,
[Symbol(refed)]: false,
[Symbol(kHasPrimitive)]: false,
[Symbol(asyncId)]: 204,
[Symbol(triggerId)]: 203
}
}
},
connections: [
{
filter: 'alexaName=..*',
uid: 999,
name: 'FHEM',
server: '192.168.188.21',
webname: 'fhem',
port: '8083'
}
]
}
[10.5.2025, 09:06:48] sshautoconf: SSH key seems to exist
[10.5.2025, 09:06:48] sshautoconf: Our SSH key is known at the reverse proxy, good!
[10.5.2025, 09:06:48] [FHEM] executing: http://192.168.188.21: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&XHR=1
*** FHEM: connected
[10.5.2025, 09:06:48] [FHEM] got: 6 results
[10.5.2025, 09:06:48] [FHEM] DVES_547472 is switch
[10.5.2025, 09:06:48] [FHEM] DVES_547472 has
[10.5.2025, 09:06:48] [FHEM] On [undefined;on,off]
[10.5.2025, 09:06:48] [FHEM] DVES_547472 will not send proactive events
[10.5.2025, 09:06:48] [FHEM] DVES_547472 uses ID: 680b76c0-f33f-078c-3951-585fd7bebc1b0c9f
[10.5.2025, 09:06:48] [FHEM] FM_Wama is switch
[10.5.2025, 09:06:48] [FHEM] FM_Wama has
[10.5.2025, 09:06:48] [FHEM] On [state;on,off]
[10.5.2025, 09:06:48] [FHEM] FM_Wama will not send proactive events
[10.5.2025, 09:06:48] [FHEM] FM_Wama uses ID: 623c33f6-f33f-078c-f01e-6bb67b3195c0b609
2025-05-10 09:06:48 caching: FM_Wama-state: off
[10.5.2025, 09:06:48] [FHEM] Heizluefter_FM is switch
[10.5.2025, 09:06:48] [FHEM] Heizluefter_FM has
[10.5.2025, 09:06:48] [FHEM] On [state;on,off]
[10.5.2025, 09:06:48] [FHEM] Heizluefter_FM will not send proactive events
[10.5.2025, 09:06:48] [FHEM] Heizluefter_FM uses ID: 623c3679-f33f-078c-e108-0329abc2cf40f145
2025-05-10 09:06:48 caching: Heizluefter_FM-state: off
[10.5.2025, 09:06:48] [FHEM] SE_bad is switch
[10.5.2025, 09:06:48] [FHEM] SE_bad has
[10.5.2025, 09:06:48] [FHEM] On [state;on,off]
[10.5.2025, 09:06:48] [FHEM] CurrentTemperature [temperature]
[10.5.2025, 09:06:48] [FHEM] SE_bad will not send proactive events
[10.5.2025, 09:06:48] [FHEM] SE_bad uses ID: 62384720-f33f-078c-6d94-cb7c0a0ca3f53169
2025-05-10 09:06:48 caching: SE_bad-state: on
2025-05-10 09:06:48 caching: SE_bad-temperature: 0.0
[10.5.2025, 09:06:48] [FHEM] ahri_ir is switch
[10.5.2025, 09:06:48] [FHEM] ahri_ir has
[10.5.2025, 09:06:48] [FHEM] On [state;on,off]
[10.5.2025, 09:06:48] [FHEM] CurrentTemperature [temperature]
[10.5.2025, 09:06:48] [FHEM] ahri_ir will not send proactive events
[10.5.2025, 09:06:48] [FHEM] ahri_ir uses ID: 623c2b09-f33f-078c-aef2-d4574ce4d73c2f4f
2025-05-10 09:06:48 caching: ahri_ir-state: on
2025-05-10 09:06:48 caching: ahri_ir-temperature: 0.0
[10.5.2025, 09:06:48] [FHEM] inthira_ir is switch
[10.5.2025, 09:06:48] [FHEM] inthira_ir has
[10.5.2025, 09:06:48] [FHEM] On [state;on,off]
[10.5.2025, 09:06:48] [FHEM] CurrentTemperature [temperature]
[10.5.2025, 09:06:48] [FHEM] inthira_ir will not send proactive events
[10.5.2025, 09:06:48] [FHEM] inthira_ir uses ID: 623c2b09-f33f-078c-f91f-2af32c6cba45d08c
2025-05-10 09:06:48 caching: inthira_ir-state: on
2025-05-10 09:06:48 caching: inthira_ir-temperature: 0.0
2025-05-10 09:06:49 caching: SE_bad-temperature: 0.0
[10.5.2025, 09:06:49] [FHEM] caching: CurrentTemperature: 0 (as number; from '0.0 ')
[10.5.2025, 09:06:49] BearerToken '...508E3' read from alexa
[10.5.2025, 09:06:50] [FHEM] got .eventToken
[10.5.2025, 09:06:50] refreshing token
[10.5.2025, 09:06:50] 39_alexa.pm is new version: true
[10.5.2025, 09:06:50] sshautoconf: completed successfully
[10.5.2025, 09:06:50] *** SSH: proxy configuration set up done
[10.5.2025, 09:06:50] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[10.5.2025, 09:06:50] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[10.5.2025, 09:06:50] Starting SSH with -R 1234:127.0.0.1:33889 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[10.5.2025, 09:06:50] failed to refresh token: invalid_grant: 'The request has an invalid grant parameter : refresh_token. User may have revoked or didn't grant the permission.'
[10.5.2025, 09:06:50] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[10.5.2025, 09:06:50] [FHEM] executing: http://192.168.188.21:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[10.5.2025, 09:06:50] *** SSH: proxy connection established
[10.5.2025, 09:06:50] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
Bitte in code-Tags, danke.
Außerdem wäre es besser (gewesen) einen neuen Thread aufzumachen.
Inzwischen hat das Problem mit dem "gekaperten" Ursprungs-Thread ja nix mehr zu tun...
Gruß, Joachim
Zitat von: brain666 am 10 Mai 2025, 09:21:16[10.5.2025, 09:06:48] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
Wie gedacht: /opt/fhem/.ssh ;)
Und wenn ich mir die ersten Posts von dir anschaue: hattest du mal eine alte alexa-fhem Installation? Wo man noch Port 3000 freigeben musste?
Umgestiegen?
Neu installiert und dann gemixte Installation?
Inzwischen, wenn man neu anfängt mit alexa-fhem Connector geht es doch ganz einfach.
Man muss keine ssh-Dinge tun, keine config anlegen (max. fhem-Server-Connection anpassen, falls alexa.-fhem und fhem nicht auf demselben Rechner laufen / oder man einen anderen Filter als "alexaName" will)
Gruß, Joachim
Zitat von: brain666 am 10 Mai 2025, 09:21:16[10.5.2025, 09:06:48] [FHEM] DVES_547472 is switch
[10.5.2025, 09:06:48] [FHEM] DVES_547472 has
[10.5.2025, 09:06:48] [FHEM] On [undefined;on,off]
Du hast offenbar (wild) rumgeändert (und nichts erwähnt was [genau]), weil:
zuerst:
Zitatdefine DVESBAD_547472 MQTT2_DEVICE DVESBAD_547472
dann/aktuell:
Zitatdefine DVES_547472 MQTT2_DEVICE DVES_547472
inklusive "Durcheinander" bei den Topics usw. (bin jetzt kein mqtt-Spezialist aber ob da [weiterhin] alles passt?)
Erkannt wird aktuell eben DVES_547472 aber mit nicht ganz klarem Zustand...
Ich denke, dass da das Problem liegt.
D.h. erst mal das Device "sauber" machen, dann sollte das auch mit alexa-fhem klappen.
Bzgl. alexaName: es sollte halt nicht zu "kryptisch" sein und sich auch sprechen lassen und v.a. von Alexa eindeutig und einfach zu verstehen sein.
ledbad z.B. musst du verm. wirklich genauso ausspechen.
Also nicht l e d Bad (kann funktionieren, muss aber nicht). Denn das wäre dann u,U, ein alexaName so: l.e.d. bad
Aber das ist ein anderes Problem und kannst du in der Alexa-App prüfen, also was erkannt wurde usw.
Räume gehen bei Amazon/Alexa über Gruppen...
Nur als Anmerkung...
Gruß, Joachim