Difference between revisions of "MQTTBROKER"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=== Communication === | === Communication === | ||
| − | |||
*'''IP Port''': TCP/IP port assigned to the broker | *'''IP Port''': TCP/IP port assigned to the broker | ||
Revision as of 11:37, 22 July 2019
This driver acts as an MQTT broker for Hsyco. It can connects with many clients but can only receive messages without forwarding them.
HSYCO Configuration
Add the MQTTBROKER I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- IP Port: TCP/IP port assigned to the broker
Authentication
- Username: optional default username for clients
- Password: optional default password for clients
Options
| ID | Default | Values | Description |
|---|---|---|---|
| startupevents | false | true | generate IO events also during the driver’s start-up phase |
| false | start generating events only after HSYCO is aligned with the current status of the system | ||
| acceptunknown | false | true | accept connection from clients whose id isn't specified in mqttbrokerauth.ini |
| false | doesn't accept connection from clients whose id isn't specified in mqttbrokerauth.ini |
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | initialization of the driver failed or loop cycle failed | |
| client.<clientId>.connected | 1 | R | clientId is connected to the broker |
| 0 | R | clientId isn't connected to the broker | |
| client.<clientId>.topic.<topicName> | <message> | R | clientId published a message on topicName |
