FFT65B, FFTF65B, FFT55B, FFT55EB, FTFB, FTFSB, FFT60SB
(EEP A5-04-02 ODER A5-04-03)
EEP A5-04-02
Data_byte2 = rel. Luftfeuchtigkeit 0..100% (0..250)
Data_byte1 = Temperatur -20..+60°C (0..250)
Lerntelegramm: 0x10100D87
EEP A5-04-03
Data_byte3 = rel. Luftfeuchtigkeit 0..100% (0..255)
Data_byte2 und 1 = Temperatur -20..+60°C (0..1023)
Lerntelegramm: 0x10180D80
Das wundert mich etwas, da die Spannungdaten bei den Vorgängermodellen übertragen wurden:Internals:
NAME Klima_Aussen
STATE T: 10.7 H: 90 B: ok
TYPE EnOcean
READINGS:
2026-02-11 10:25:44 IODev TCM_ESP3_0
2026-02-11 10:26:37 battery ok
2026-02-11 16:20:49 dewpoint 9.1
2026-02-11 16:20:49 energyStorage charged
2026-02-11 16:20:49 humidity 90
2026-02-11 16:20:49 humidity_avg_day 89.4
2026-02-11 16:20:49 humidity_avg_month 85.2
2026-02-11 16:20:49 humidity_cum_day 5258506
2026-02-11 16:20:49 humidity_cum_month 85969470
2026-02-11 07:11:07 humidity_max_day 90.0
2026-02-07 05:23:24 humidity_max_month 90.0
2026-02-11 00:04:59 humidity_min_day 88.0
2026-02-07 09:54:36 humidity_min_month 13.0
2026-02-11 16:20:49 state T: 10.7 H: 90 B: ok
2026-02-11 16:20:49 temperature 10.7
2026-02-11 16:20:49 temperature_avg_day 9.0
2026-02-11 16:20:49 temperature_avg_month 5.1
2026-02-11 16:20:49 temperature_cum_day 532062.5
2026-02-11 16:20:49 temperature_cum_month 5111404.19999999
2026-02-11 14:34:00 temperature_max_day 11.7
2026-02-07 14:53:41 temperature_max_month 13.0
2026-02-11 00:04:59 temperature_min_day 7.5
2026-02-07 09:54:36 temperature_min_month -13.3
2026-02-11 16:20:49 voltage 4.4
Attributes:
IODev TCM_ESP3_0
eep A5-04-02
manufID 00D
subType tempHumiSensor.02
teachMethod 4BS
readingsBulkUpdate einfach verwenden.readingsBeginUpdate();
readingsBulkUpdate();
...
readingsBulkUpdate();
Dispatch();
readingsBulkUpdate();
...Das letzte readingsBulkUpdate liefert die Fehlermeldung2026.02.11 15:00:52 1: readingsUpdate(Denon,zone2,on) missed to call readingsBeginUpdate first.
2026.02.11 15:00:52 1: stacktrace:
2026.02.11 15:00:52 1: main::readingsBulkUpdate called by ./FHEM/70_DENON_AVR.pm (2234)
2026.02.11 15:00:52 1: main::DENON_AVR_Parse called by ./FHEM/70_DENON_AVR.pm (1671)
2026.02.11 15:00:52 1: main::DENON_AVR_Read called by fhem.pl (4007)
2026.02.11 15:00:52 1: main::CallFn called by fhem.pl (789)
Aus meiner Sicht habe ich readingsBeginUpdate "brav" aufgerufen.Zitat von: mrprohl2 am 27 Oktober 2025, 17:50:54Folgende Zeilen habe ich in der "30_HUEBridge.pm" manuell angepasst:Vielen Dank dafür.
Zeile 3006 in: my ($protocol,$host,$port,$path)= ("https",$2,443,$4);
Zeile 3022 in: $conn = IO::Socket::SSL->new(PeerAddr=>"$host:$port", Timeout=>$timeout, SSL_verify_mode=>0);
ZitatHast du für den Pi im Pi selbst eine statische IP konfiguriert?
Oder bekommt er eine statische IP vom DHCP-Server?
ZitatLäuft auf dem Pi der DHCP-Client? (Unter Raspbian dhclient, glaube ich, aber nicht sicher.)
ZitatSteht irgendwas DHCP-bezogenes im Syslog vom Pi unmittelbar nach dem Booten?
Steht irgendwas DHCP-bezogenes im Syslog vom Pi nach 24 Stunden uptime?
journalctl -b | grep -i dhcp
Feb 09 19:34:16 fhempi NetworkManager[682]: <info> [1770662056.1562] dhcp: init: Using DHCP client 'internal'
Feb 09 19:34:18 fhempi NetworkManager[682]: <info> [1770662058.2479] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 19:34:18 fhempi NetworkManager[682]: <info> [1770662058.2620] dhcp4 (eth0): state changed new lease, address=192.168.188.26
Feb 09 19:34:19 fhempi NetworkManager[682]: <info> [1770662059.7651] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 19:34:19 fhempi NetworkManager[682]: <info> [1770662059.8142] dhcp6 (eth0): state changed new lease
Feb 10 07:34:38 fhempi NetworkManager[682]: <info> [1770705278.9315] dhcp4 (eth0): state changed new lease, address=192.168.188.26
Feb 10 19:34:38 fhempi NetworkManager[682]: <info> [1770748478.9269] dhcp4 (eth0): state changed new lease, address=192.168.188.26
Feb 11 07:34:38 fhempi NetworkManager[682]: <info> [1770791678.9122] dhcp4 (eth0): state changed new lease, address=192.168.188.26ZitatWas gibt sudo ss -tulpn zurück?
sudo ss -tulpn
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 0.0.0.0:48386 0.0.0.0:* users:(("perl",pid=177849,fd=16),("perl",pid=2556,fd=16),("perl",pid=962,fd=16))
udp UNCONN 0 0 0.0.0.0:3478 0.0.0.0:* users:(("docker-proxy",pid=1766,fd=7))
udp UNCONN 0 0 192.168.188.26:5060 0.0.0.0:* users:(("perl",pid=2556,fd=4))
udp UNCONN 0 0 0.0.0.0:46046 0.0.0.0:* users:(("avahi-daemon",pid=596,fd=14))
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=596,fd=12))
udp UNCONN 0 0 0.0.0.0:10001 0.0.0.0:* users:(("docker-proxy",pid=1907,fd=7))
udp UNCONN 0 0 *:3478 *:* users:(("docker-proxy",pid=1796,fd=7))
udp UNCONN 0 0 [fe80::5246:ac5b:2ce4:8f98]:546 *:* users:(("NetworkManager",pid=682,fd=28))
udp UNCONN 0 0 *:5353 *:* users:(("avahi-daemon",pid=596,fd=13))
udp UNCONN 0 0 *:10001 *:* users:(("docker-proxy",pid=1914,fd=7))
udp UNCONN 0 0 *:59188 *:* users:(("avahi-daemon",pid=596,fd=15))
tcp LISTEN 0 32 0.0.0.0:1883 0.0.0.0:* users:(("perl",pid=962,fd=45))
tcp LISTEN 0 32 127.0.0.1:7072 0.0.0.0:* users:(("perl",pid=962,fd=17))
tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=812,fd=21))
tcp LISTEN 0 4096 0.0.0.0:8880 0.0.0.0:* users:(("docker-proxy",pid=1884,fd=7))
tcp LISTEN 0 4096 0.0.0.0:8843 0.0.0.0:* users:(("docker-proxy",pid=1859,fd=7))
tcp LISTEN 0 4096 0.0.0.0:443 0.0.0.0:* users:(("docker-proxy",pid=1985,fd=7))
tcp LISTEN 0 4096 0.0.0.0:99 0.0.0.0:* users:(("docker-proxy",pid=1954,fd=7))
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=813,fd=3))
tcp LISTEN 0 4096 0.0.0.0:8443 0.0.0.0:* users:(("docker-proxy",pid=1836,fd=7))
tcp LISTEN 0 32 0.0.0.0:8090 0.0.0.0:* users:(("perl",pid=962,fd=9))
tcp LISTEN 0 32 0.0.0.0:8084 0.0.0.0:* users:(("perl",pid=962,fd=19))
tcp LISTEN 0 4096 0.0.0.0:8080 0.0.0.0:* users:(("docker-proxy",pid=1813,fd=7))
tcp LISTEN 0 32 0.0.0.0:8083 0.0.0.0:* users:(("perl",pid=962,fd=5))
tcp LISTEN 0 511 0.0.0.0:8082 0.0.0.0:* users:(("node /opt/zigbe",pid=2524,fd=22))
tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=123528,fd=7))
tcp LISTEN 0 4096 [::]:8880 [::]:* users:(("docker-proxy",pid=1890,fd=7))
tcp LISTEN 0 4096 [::]:8843 [::]:* users:(("docker-proxy",pid=1867,fd=7))
tcp LISTEN 0 4096 [::]:443 [::]:* users:(("docker-proxy",pid=1991,fd=7))
tcp LISTEN 0 4096 [::]:99 [::]:* users:(("docker-proxy",pid=1960,fd=7))
tcp LISTEN 0 511 *:80 *:* users:(("apache2",pid=123466,fd=4),("apache2",pid=123465,fd=4),("apache2",pid=834,fd=4))
tcp LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=813,fd=4))
tcp LISTEN 0 4096 [::]:8443 [::]:* users:(("docker-proxy",pid=1841,fd=7))
tcp LISTEN 0 4096 [::]:8080 [::]:* users:(("docker-proxy",pid=1820,fd=7))
tcp LISTEN 0 128 [::1]:631 [::]:* users:(("cupsd",pid=123528,fd=6))
tcp LISTEN 0 511 *:3000 *:* users:(("node /usr/bin/a",pid=2240,fd=18))
tcp LISTEN 0 511 *:6329 *:* users:(("node /usr/bin/s",pid=1077,fd=19))
Erstmalig mit der FRITZ!Box verbunden als fhempi-3define TF_KG_Entf_Au EnOcean 05A83D32
attr TF_KG_Entf_Au userattr mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long
attr TF_KG_Entf_Au IODev TCM_ESP3_0
attr TF_KG_Entf_Au comment Eltako FFT60B
attr TF_KG_Entf_Au creator autocreate
attr TF_KG_Entf_Au eep A5-04-02
attr TF_KG_Entf_Au manufID 00D
attr TF_KG_Entf_Au mqttPublish temperature|humidity|dewpoint|absoluteHumidity:topic={"$base/$device/$name"} *:retain=1
attr TF_KG_Entf_Au mqttSubscribe state:stopic={"$base/$device"}
attr TF_KG_Entf_Au room Entfeuchtung,EnOcean,HASS,MQTT
attr TF_KG_Entf_Au stateFormat T: temperature°C RH: humidity% AH: absoluteHumidity g/m3 TP: dewpoint°C
attr TF_KG_Entf_Au subType tempHumiSensor.02
attr TF_KG_Entf_Au teachMethod 4BS
# DEF 05A83D32
# FUUID 6978afcf-f33f-c6d8-18a7-e55669fb014621ad
# IODev TCM_ESP3_0
# LASTInputDev TCM_ESP3_0
# MSGCNT 1399
# NAME TF_KG_Entf_Au
# NR 252
# NTFY_ORDER 50-TF_KG_Entf_Au
# STATE T: 7.5°C RH: 76% AH: 6.1 g/m3 TP: 3.5°C
# TCM_ESP3_0_DestinationID FFFFFFFF
# TCM_ESP3_0_MSGCNT 1399
# TCM_ESP3_0_PacketType 1
# TCM_ESP3_0_RSSI -45
# TCM_ESP3_0_ReceivingQuality excellent
# TCM_ESP3_0_RepeatingCounter 1
# TCM_ESP3_0_SubTelNum 12
# TCM_ESP3_0_TIME 2026-02-11 14:42:10
# TYPE EnOcean
# eventCount 1399
# READINGS:
# 2026-02-03 13:03:16 IODev TCM_ESP3_0
# 2026-02-11 14:42:10 absoluteHumidity 6.1
# 2026-02-04 11:41:15 battery low
# 2026-02-11 14:42:10 dewpoint 3.5
# 2026-02-04 11:41:15 energyStorage empty
# 2026-02-11 14:42:10 humidity 76
# 2026-02-11 14:42:10 state T: 7.5 H: 76 B: unknown
# 2026-01-27 13:32:19 teach 4BS teach-in accepted EEP A5-04-02 Manufacturer: Eltako
# 2026-02-11 14:42:10 temperature 7.5
# 2026-02-04 11:41:15 voltage 0.1
# helper:
# battery low
#
setstate TF_KG_Entf_Au T: 7.5°C RH: 76% AH: 6.1 g/m3 TP: 3.5°C
setstate TF_KG_Entf_Au 2026-02-03 13:03:16 IODev TCM_ESP3_0
setstate TF_KG_Entf_Au 2026-02-11 14:42:10 absoluteHumidity 6.1
setstate TF_KG_Entf_Au 2026-02-04 11:41:15 battery low
setstate TF_KG_Entf_Au 2026-02-11 14:42:10 dewpoint 3.5
setstate TF_KG_Entf_Au 2026-02-04 11:41:15 energyStorage empty
setstate TF_KG_Entf_Au 2026-02-11 14:42:10 humidity 76
setstate TF_KG_Entf_Au 2026-02-11 14:42:10 state T: 7.5 H: 76 B: unknown
setstate TF_KG_Entf_Au 2026-01-27 13:32:19 teach 4BS teach-in accepted EEP A5-04-02 Manufacturer: Eltako
setstate TF_KG_Entf_Au 2026-02-11 14:42:10 temperature 7.5
setstate TF_KG_Entf_Au 2026-02-04 11:41:15 voltage 0.1
set <name> pct 72 0
set <name> open 15 1
set <name> stop 1set <name> pct 50set <name> pct 50 1 nicht. Es kommt die Fehlermeldung "not enough parameter".off:noArg shellypstripg4-206ef10295f4/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":false}}\
on:noArg shellypstripg4-206ef10295f4/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":true}}kann ich nun steckdose 0 schalten.off:noArg shellypstripg4-206ef10295f4/rpc {"id":1,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":false}}\
on:noArg shellypstripg4-206ef10295f4/rpc {"id":1,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":true}}Zitat von: olwaldi am 11 Februar 2026, 10:23:11Beim Debuggen sieht man sofort, daß viele Geräte dem Denon-Receiver notifys zuschicken, z.B. meine Lampen oder Heizung. Was wäre hier eine sinnvolle Einschränkung? Aktuell nutze ich "unreflektiert"$hash->{NOTIFYDEV} = "global";Oder ist das schon "zu wenig"?
Grüßle, Michael