User Tools

Site Tools


mqtt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
mqtt [2020/04/09 08:21] emozolyakmqtt [2022/01/15 03:18] – ↷ Links adapted because of a move operation 127.0.0.1
Line 1: Line 1:
 ====== MQTT protocol ====== ====== MQTT protocol ======
  
-MQTT or Message Queue Telemetry Transport is a protocol focused on applications in M2M (Machine-to-Machine Interaction) and IIoT (Industrial Internet of Things) systems. Information transfer to MQTT is implemented according to the Publisher/Subscriber scheme and occurs through an intermediate server (Broker). The data source (Publisher) sends data to the server (Broker), other systems and devices, being Subscribers, read them from there.+MQTT or Message Queue Telemetry Transport is a protocol focused on applications in M2M (Machine-to-Machine Interaction) and IIoT (Industrial [[:iot|Internet of Things]]) systems. Information transfer to MQTT is implemented according to the Publisher/Subscriber scheme and occurs through an intermediate server (Broker). The data source (Publisher) sends data to the server (Broker), other systems and devices, being Subscribers, read them from there.
  
 This method of interaction is well suited for event-based messaging, when the devices themselves periodically communicate. This method of interaction is well suited for event-based messaging, when the devices themselves periodically communicate.
 In version 4.0 WebHMI has the ability to work in both Broker and Publisher/Subscriber mode, so it can be used as an IoT Edge gateway to integrate the monitoring object into large IoT solutions such as “smart city”, etc., or on the contrary, to receive data from remote devices (sensors) via the Internet, without the need to integrate IP networks. In version 4.0 WebHMI has the ability to work in both Broker and Publisher/Subscriber mode, so it can be used as an IoT Edge gateway to integrate the monitoring object into large IoT solutions such as “smart city”, etc., or on the contrary, to receive data from remote devices (sensors) via the Internet, without the need to integrate IP networks.
  
-{{ ::mqtt.png?direct&400 |}}+{{ network:mqtt.png?direct&400 |}}
  
 The setup pages is similar to other connections setup and there is a MQTT tab for specific settings: The setup pages is similar to other connections setup and there is a MQTT tab for specific settings:
  
-{{ ::mqtt_basic_tab.png?direct&400 |}}+{{ network:mqtt_basic_tab.png?direct&400 |}}
  
-{{ ::mqtt_comm_tab.png?direct&400 |}}+{{ network:mqtt_comm_tab.png?direct&400 |}}
 In the MQTT tab you set credentials neccessary to connect to the client. If you leave them emty, the client will connect to internal broker.  In the MQTT tab you set credentials neccessary to connect to the client. If you leave them emty, the client will connect to internal broker. 
-{{ ::mqtt_credentials.png?direct&400 |}}+{{ network:mqtt_credentials.png?direct&400 |}}
  
 The internal brokder have to be switch on in the settings menu: The internal brokder have to be switch on in the settings menu:
  
-{{ ::mqtt_server_checkbox.png?direct&400 |}}+{{ network:mqtt_server_checkbox.png?direct&400 |}}
  
mqtt.txt · Last modified: 2023/02/13 15:39 by emozolyak

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki