FHEM Forum

FHEM - Hausautomations-Systeme => MQTT => Thema gestartet von: Tommi ratlos am 05 November 2025, 13:30:36

Titel: MQTT Home Assistant
Beitrag von: Tommi ratlos am 05 November 2025, 13:30:36
Hallo zusammen,

ich bastele jetzt schon ein paar Tage rum ohne das ich es hin bekomme.

Ich versuche ein Verbindung über MQTT zu Home Assistant herzustellen, um meine über Matter angebundenen Geräte (IKEA DIRIGERA) anzusprechen.


Mein Test Device sieht so aus
define xbaum MQTT2_DEVICE xbaum
attr xbaum userattr mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long
attr xbaum mqttSubscribe *:stopic={"$device/state"}
attr xbaum readingList xbaum:xbaum/state:.* state
attr xbaum room MQTT2_DEVICE
attr xbaum setList on:noArg xbaum/set on\
off:noArg xbaum/set off
attr xbaum webCmd on:off
#   CID        xbaum
#   DEF        xbaum
#   FUUID      6908a94e-f33f-c08c-b64b-f75b783d2a690f6b
#   IODev      MQTT2_FHEM_Server
#   LASTInputDev MQTT2_FHEM_Server
#   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_127.0.0.1_51506
#   MQTT2_FHEM_Server_MSGCNT 1
#   MQTT2_FHEM_Server_TIME 2025-11-05 12:56:49
#   MSGCNT     1
#   NAME       xbaum
#   NR         820
#   STATE      on
#   TYPE       MQTT2_DEVICE
#   eventCount 10
#   Helper:
#     DBLOG:
#       state:
#         logdb:
#           TIME       1762343809.23317
#           VALUE      on
#   OLDREADINGS:
#   READINGS:
#     2025-11-05 07:18:02   IODev           MQTT2_FHEM_Server
#     2025-11-05 12:56:49   state           on
#
setstate xbaum on
setstate xbaum 2025-11-05 07:18:02 IODev MQTT2_FHEM_Server
setstate xbaum 2025-11-05 12:56:49 state on

Wenn ich auf der console in FHEM mosquitto_pub -h localhost -i xbaum -t xbaum/state -m "on" -d eingebe schaltet das Device auf on.


Auf Home Assistant läuft kein Broker, ist mit dem FHEM MQTT2 Server verbunden.
Über die Funktion "Ein Paket veröffentlichen" in Hass kann ich den Broker in FHEM auch ansprechen.

Auf meinem Fhem sehe ich dann mosquitto_sub -h localhost -t '/#' -vxbaum/state offoder wenn ich es mit set versuche
xbaum/set on
Aber es passiert in beiden fällen nix.

Wo liegt mein Denkfehler. Eine Bridge brauch ich doch nur wenn auf Hass ein eigener Broker läuft?

Gruß
Thomas
Titel: Aw: MQTT Home Assistant
Beitrag von: Tommi ratlos am 05 November 2025, 13:56:00
Jetzt Antworte ich mir schon selbst. :-*

Habe gerade gesehen das in dem über Autocreate hinzugefügte Device "Hass" (Ist der Clientname in Home Assistant) die Readings aktualisiert werden.

define hass MQTT2_DEVICE hass
attr hass readingList hass:homeassistant/status:.* status\
hass:xbaum/set:.* set\
hass:hass/xbaum/set:.* set\
hass:xbaum/state:.* state\
hass:xbaum/set/state:.* state
attr hass room MQTT2_DEVICE
#   CFGFN     
#   CID        hass
#   DEF        hass
#   FUUID      690b2910-f33f-c08c-0bc1-a8116195dc916028
#   IODev      MQTT2_FHEM_Server
#   LASTInputDev MQTT2_FHEM_Server
#   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_10.65.69.91_49203
#   MQTT2_FHEM_Server_MSGCNT 10
#   MQTT2_FHEM_Server_TIME 2025-11-05 13:50:30
#   MSGCNT     10
#   NAME       hass
#   NR         831
#   STATE      on
#   TYPE       MQTT2_DEVICE
#   eventCount 15
#   Helper:
#     DBLOG:
#       set:
#         logdb:
#           TIME       1762343424.78328
#           VALUE      on
#       state:
#         logdb:
#           TIME       1762347013.53912
#           VALUE      off
#       status:
#         logdb:
#           TIME       1762339088.95994
#           VALUE      online
#   READINGS:
#     2025-11-05 11:38:08   IODev           MQTT2_FHEM_Server
#     2025-11-05 12:50:35   set             on
#     2025-11-05 13:50:30   state           on
#     2025-11-05 11:38:08   status          online
#     2025-11-05 12:36:35   subscriptions   cloudapp/QBUSMQTTGW/+/state cloudapp/QBUSMQTTGW/config cloudapp/QBUSMQTTGW/state connection/status drop_connect/discovery/# dsmr/# esphome/discover/# fully/deviceInfo/+ hass/xbaum/state homeassistant/alarm_control_panel/+/+/config homeassistant/alarm_control_panel/+/config homeassistant/binary_sensor/+/+/config homeassistant/binary_sensor/+/config homeassistant/button/+/+/config homeassistant/button/+/config homeassistant/camera/+/+/config homeassistant/camera/+/config homeassistant/climate/+/+/config homeassistant/climate/+/config homeassistant/cover/+/+/config homeassistant/cover/+/config homeassistant/device/+/+/config homeassistant/device/+/config homeassistant/device_automation/+/+/config homeassistant/device_automation/+/config homeassistant/device_tracker/+/+/config homeassistant/device_tracker/+/config homeassistant/event/+/+/config homeassistant/event/+/config homeassistant/fan/+/+/config homeassistant/fan/+/config homeassistant/humidifier/+/+/config homeassistant/humidifier/+/config homeassistant/image/+/+/config homeassistant/image/+/config homeassistant/lawn_mower/+/+/config homeassistant/lawn_mower/+/config homeassistant/light/+/+/config homeassistant/light/+/config homeassistant/lock/+/+/config homeassistant/lock/+/config homeassistant/notify/+/+/config homeassistant/notify/+/config homeassistant/number/+/+/config homeassistant/number/+/config homeassistant/scene/+/+/config homeassistant/scene/+/config homeassistant/select/+/+/config homeassistant/select/+/config homeassistant/sensor/+/+/config homeassistant/sensor/+/config homeassistant/siren/+/+/config homeassistant/siren/+/config homeassistant/switch/+/+/config homeassistant/switch/+/config homeassistant/tag/+/+/config homeassistant/tag/+/config homeassistant/text/+/+/config homeassistant/text/+/config homeassistant/update/+/+/config homeassistant/update/+/config homeassistant/vacuum/+/+/config homeassistant/vacuum/+/config homeassistant/valve/+/+/config homeassistant/valve/+/config homeassistant/water_heater/+/+/config homeassistant/water_heater/+/config pglab/discovery/# tasmota/discovery/#
#
setstate hass on
setstate hass 2025-11-05 11:38:08 IODev MQTT2_FHEM_Server
setstate hass 2025-11-05 12:50:35 set on
setstate hass 2025-11-05 13:50:30 state on
setstate hass 2025-11-05 11:38:08 status online
setstate hass 2025-11-05 12:36:35 subscriptions cloudapp/QBUSMQTTGW/+/state cloudapp/QBUSMQTTGW/config cloudapp/QBUSMQTTGW/state connection/status drop_connect/discovery/# dsmr/# esphome/discover/# fully/deviceInfo/+ hass/xbaum/state homeassistant/alarm_control_panel/+/+/config homeassistant/alarm_control_panel/+/config homeassistant/binary_sensor/+/+/config homeassistant/binary_sensor/+/config homeassistant/button/+/+/config homeassistant/button/+/config homeassistant/camera/+/+/config homeassistant/camera/+/config homeassistant/climate/+/+/config homeassistant/climate/+/config homeassistant/cover/+/+/config homeassistant/cover/+/config homeassistant/device/+/+/config homeassistant/device/+/config homeassistant/device_automation/+/+/config homeassistant/device_automation/+/config homeassistant/device_tracker/+/+/config homeassistant/device_tracker/+/config homeassistant/event/+/+/config homeassistant/event/+/config homeassistant/fan/+/+/config homeassistant/fan/+/config homeassistant/humidifier/+/+/config homeassistant/humidifier/+/config homeassistant/image/+/+/config homeassistant/image/+/config homeassistant/lawn_mower/+/+/config homeassistant/lawn_mower/+/config homeassistant/light/+/+/config homeassistant/light/+/config homeassistant/lock/+/+/config homeassistant/lock/+/config homeassistant/notify/+/+/config homeassistant/notify/+/config homeassistant/number/+/+/config homeassistant/number/+/config homeassistant/scene/+/+/config homeassistant/scene/+/config homeassistant/select/+/+/config homeassistant/select/+/config homeassistant/sensor/+/+/config homeassistant/sensor/+/config homeassistant/siren/+/+/config homeassistant/siren/+/config homeassistant/switch/+/+/config homeassistant/switch/+/config homeassistant/tag/+/+/config homeassistant/tag/+/config homeassistant/text/+/+/config homeassistant/text/+/config homeassistant/update/+/+/config homeassistant/update/+/config homeassistant/vacuum/+/+/config homeassistant/vacuum/+/config homeassistant/valve/+/+/config homeassistant/valve/+/config homeassistant/water_heater/+/+/config homeassistant/water_heater/+/config pglab/discovery/# tasmota/discovery/#


Da wollte ich das aber nicht haben.
Titel: Aw: MQTT Home Assistant
Beitrag von: Tommi ratlos am 05 November 2025, 14:17:15
Ich glaub es nicht, da versuche ich es jetzt schon seit Tagen und jetzt scheine ich es, Zumidest in eine Richtung hinzubekommen.

define xbaum MQTT2_DEVICE xbaum
attr xbaum userattr mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long
attr xbaum readingList hass:xbaum/state:.* state
attr xbaum room MQTT2_DEVICE
attr xbaum setList on:noArg xbaum/set on\
off:noArg xbaum/set off
attr xbaum webCmd on:off
#   CID        xbaum
#   DEF        xbaum
#   FUUID      6908a94e-f33f-c08c-b64b-f75b783d2a690f6b
#   IODev      MQTT2_FHEM_Server
#   LASTInputDev MQTT2_FHEM_Server
#   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_10.65.69.91_49203
#   MQTT2_FHEM_Server_MSGCNT 10
#   MQTT2_FHEM_Server_TIME 2025-11-05 14:12:29
#   MSGCNT     10
#   NAME       xbaum
#   NR         820
#   STATE      off
#   TYPE       MQTT2_DEVICE
#   eventCount 25
#   Helper:
#     DBLOG:
#       state:
#         logdb:
#           TIME       1762348349.09306
#           VALUE      off
#   OLDREADINGS:
#   READINGS:
#     2025-11-05 07:18:02   IODev           MQTT2_FHEM_Server
#     2025-11-05 14:12:29   state           off
#
setstate xbaum off
setstate xbaum 2025-11-05 07:18:02 IODev MQTT2_FHEM_Server
setstate xbaum 2025-11-05 14:12:29 state off

Jetzt reagiert das Device auf die Befehle aus Hass. Jetzt muss ich nur noch in die "Gegenrichtung" funktionieren.