By [ad_1]
Prepare your own IoT Hub with this MQTT Broker. Set with users, TLS, WebSocket and/or TCP/IP.
The parameters can be configured like this:
We can define the LAN we want to provide MQTT service in this setting. If Bind IP is defined with 0.0.0.0, it enables all the interfaces… set the IP to select only one interface. This is very useful when you need to separate LANs and disable MQTT access from outside.
The WebSocket protocol is an independent TCP-based protocol. Its only relationship to HTTP is that its handshake is interpreted by HTTP servers as an Upgrade request. By default the WebSocket protocol uses port 80 for regular WebSocket connections and port 443 for WebSocket connections tunnelled over TLS.
This timeout closes the socket if no activity is found within the socket connection.
This setting enables Persistent Connections.
If the client enables this, the broker stores the following information (even if the client is offline).
- Existence of a session (even if there are no subscriptions).
- All the subscriptions of the client.
- All messages in a Quality of Service (QoS) 1 or 2 flow that the client has not yet confirmed.
- All new QoS 1 or 2 messages that the client missed while offline.
- All QoS 2 messages received from the client that is not yet completely acknowledged.
When the client reconnects, the information is available immediately.
This setting is used when multiple clients connect at the same time, and it defines the maximum queue of clients at peak. This setting should not be changed for a small to medium-sized IoT project. For a global concept connection, it might be required to increase the queue, which will increase the memory consumption.
This setting defines the maximum pending messages that missed the delivery confirmation when using QoS 1 or 2. If the maximum number of pending messages is reached the buffer will discard the oldest in line.
This setting is used to define the URL where the broker is serving. http://*:5000;http://localhost:5001
For MQTT installations this resource allows retrieving the needed information to connect and authorize with an MQTT broker.
In this field, you can define a name for the broker. Coreflux will provide a random one if it is left empty.
Fill in all the described fields, for instance, your local machine IP Address, or leave them as default and start the asset installation. When ready start the new asset.
The broker should be installed and up and running. Please ensure that you add the Port configured (by default 1883) to your firewall settings.
For C# users please check :
[ad_2]
Source link
