mqtt with fhem

Begonnen von bend94, 19 Juni 2019, 14:43:54

Vorheriges Thema - Nächstes Thema

Beta-User

(sorry, don't want to get involved in MQTT_GENERIC_BRIDGE discussion, as I'm also not familiar with that; just some remarks on topics prior to the use of it):

- Imo, you'd better use just one MQTT server deamon in your setup, not both MQTT2_SERVER _and_ mosquitto. So use MQTT2_CLIENT listening to port 1883 as IO for the communication between FHEM and mosquitto (as all other clients like nodered, domoticz-mqtt and whatever other devices (like ESP8266 with tasmota) you use)
But leave autocreate turned off, if you are just planing to "mqtt-ize" FHEM-devices!

- When using MQTT_GENERIC_BRIDGE, in general this MQTT_GENERIC_BRIDGE device just enables all other type of devices to "talk in mqtt", so better avoid additionally using other type of event handlers like notify to do the same (this ist possible and no general issue, but imo sticking with MQTT_GENERIC_BRIDGE will help you to understand how the MQTT_GENERIC_BRIDGE mechanism works).
Besinde the above, MQTT_GENERIC_BRIDGE just keeps some central settings like topic structures and so on.
All other configuration work regarding other FHEM devices is done in the new attributes at each of the FHEM devices you already defined prior to the MQTT_GENERIC_BRIDGE (or will define in the future).

(Please: in case of questions wrt. that, ask in the other thread you already opened)

Additionally: Please use code tagging for the future (the "#"-button above the smileys)
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: ZigBee2mqtt, MiLight@ESP-GW, BT@OpenMQTTGw | ZWave | SIGNALduino | MapleCUN | RHASSPY
svn: u.a Weekday-&RandomTimer, Twilight,  div. attrTemplate-files, MySensors