Device Private Deployment Broker Configuration - Platform Registration

The platform registration method enables devices to automatically pull and save their private deployment Broker configurations after going online, making it suitable for batch automatic configuration of a large number of devices.
Please access the [IoT Console] on the platform, add a message server, and register the MQTT Broker you just set up.

During initial testing, limit the scope of use of the message server to avoid affecting other devices on the workbench (if any).
Please go to the "Message Servers" page in the left navigation bar of the console and add a message server.
1. During initial testing, limit the scope of use of the message server to avoid affecting other devices on the workbench (if any).
2. Multiple message servers can be added, and their usage priority can be adjusted by dragging.

Adding Method

The following is the corresponding filling method for each item

Item Description
Scope of Use Specify which devices can connect to this message server. It can be set to "All" (all devices under the workbench and devices to be online in the future), or devices with specified IDs, groups, or product types.
The priority order from high to low is: Device > Group > Product > Workbench.
For example: If the specified Product P1 uses Message Server A, all devices of Product Type P1 will connect to Message Server A; however, if a specific Device D1 is set to use Message Server B, Device D1 will connect to Message Server B.
Time Interface If the device has no requirement for standard time, this field can be left blank (not recommended for production environments)
When the device goes online, it will send an HTTP request to the specified URL to synchronize the time between the Broker and itself. This is very important.
The specific implementation method of the time service is described in detail in the "NTP Interface" section.
Note: The NTP service here is an HTTP request (a URL), not the system's NTP service. Do not fill in the domain name of the NTP server in the NTP address field.
Registration Interface The registration interface enables a flexible device access mechanism and is optional
When the device goes online, it will send an HTTP request to the specified URL to obtain the address (host / port), topic, and user information (client / username / password) required to connect to the Broker. If this interface is not specified (or the interface does not return such information), the device will use its pre-configured information.
The specific implementation method and return format are described in detail in the "Registration Interface" section.
If the registration interface is filled in and the following information is output in the interface, then the following information fields are all optional.
Address Fill in the IP address (usually the IP address or domain name of the server where the Broker service is located) and port exposed by the Broker service. Ensure it is interconnected with the wireless network that the device will connect to later; it can be a local area network (LAN) IP address.
(It is recommended to use an IP address instead of a domain name, as DNS resolution failures may occur on many public network lines)
If left blank: The address information needs to be output through the registration interface;
If filled in: If the registration interface outputs address information, the address information from the registration interface will be used first; if the registration interface does not output address information, the filled-in information will be used.
Device Topic Fill in the topic used by the device to subscribe to and publish messages. Leave it blank, or fill in "key", "client", or other values.
The complete topic subscribed to by the device is: {pre}/{type}/{side}, where
{pre} is the topic prefix:
When "key" is filled in (or left blank), the topic is: thing/Product Code/Device Code/{type}/{side};
When "client" is filled in, the topic is: thing/Product Code/Device Client/{type}/{side};
When other non-empty strings are filled in, the topic is: [Entered Value]/{type}/{side}
{type} is the message type
{side} indicates client or server: server / client
User Information Fill in the user information required for the device to log in to the Broker: ClientID, Username, Password.
The "Client" (client), "Device ID" (key), and "Device Password" (secret) correspond to the "Client ID", "Username", and "Password" required to log in to the Broker respectively.
If left blank: The user information needs to be output through the registration interface;
If filled in: If the registration interface outputs user information, the user information from the registration interface will be used first; if the registration interface does not output user information, the filled-in information will be used.
All three items above support variables: {device} will be replaced with the Device ID; {product} will be replaced with the Product Code.
For example, for a Smart Voice Speaker 3 with ID "12345": "device-{device}" will be replaced with "device-12345"; "pwd-{product}" will be replaced with "pwd-Ft3DpHSwDF".
Name Optional / For labeling purposes only; the device will not save this information
Start Immediately Check this box to make the settings take effect immediately after adding. (This effect only refers to whether the settings of this message server are valid, and does not control the message server or devices)