MQTT usefulness explained

Random
1

Hello

I would like to propose a UX improvement, but before proposing it and saying anything stupid

could someone explain the purpose of MQTT beyond fake devices

thanks

2

Hello @Prof_Techno
Node-RED is used to fill gaps for applications that are not integrated into Gladys and so MQTT serves as the bridge between my devices and Gladys, for example: my 433 MHz sensors, my Harmony remote, my temperature sensors read via a BLE gateway? and also all the tinkering based on ESP32, ESP8266, D1 mini, which use MQTT to transmit their info to Gladys. It’s much more than virtual sensors :wink:

1 Like
3

@Prof_Techno thinks that MQTT is a (central) place where devices make information available for other devices, everyone puts what they want (or almost) and everyone takes what they want (or, again, almost).

On my setup, I have an external MQTT broker, on which I’ve connected:

  • zigbee2mqqt (externe) which sends/receives data to/from this MQTT broker
  • Jeedom which sends information to MQTT (via the MQTT Manager plugin)
  • node-red which sends information (Tempo tariff)
  • zwaveJS (installed locally on my Jeedom) which sends/receives information to/from MQTT
  • Gladys which sends/receives information.

Basically I can have lots of different systems talk to each other and share the same information.

I’m not a specialist so my terms and examples may be limited and not technical at all :sweat_smile: