The ProvisioningService allows for out-of-the-box device provisioning. This feature may be used for easy and fast deployment of a large number of devices that have similar configurations, applications, or areas of application. The entire process is described in the Remote Access section
The main goal of device provisioning is to allow a user to automatically configure a new device without the need to directly interact with the device. The Everyware Cloud platform takes care of the configuration of the device with the parameters given by the user.
The ProvisioningService configuration can be accessed by navigating to the Cloud Connections section and selecting the ProvisioningService configuration entry for the specific cloud connection:
This service provides the following configuration parameters needed for this connection to be established:
Broker URL - supplies the broker URL as one of the following, depending on where your account is:
- Sandbox: mqtts://broker-sandbox.everyware-cloud.com:8883
- Production: mqtts://broker-eurotech-provision.everyware-cloud.com:8883
Client ID - supplies the unique client identifier within the whole account. Our platform uses MAC addresses of the main network card of the device (columns removed) to obtain a unique client identifier. This identifier must follow the naming convention defined by the v.3.1.1 MQTT specification.
Username - identifies the username that matches the one that was provided when the provision request was created on the platform. If it does not match, the device will not be able to connect to the Provision Broker. If left empty, this is automatically determined by the client software, e.g. as the MAC address of the main network interface (generally uppercase and without ':') followed by '-' and the device serial number. The serial number is obtained from the kura.serialNumber property of the kura.properties file.
Password - identifies the password that matches the one that was provided when the provision request was created on the platform. If it does not match, the device will not be able to connect to the Provision Broker.
Once provisioned with Everyware Cloud (EC), the gateway is expecting to receive signed control messages.
If a provisioned gateway needs to be moved from one EC account to the other, the device provisioning needs to be performed again, setting the enabled option to true and the provisioned option to false
Starting from ESF 7, provisioning is no longer limited to the default cloud connection, but can be performed on any cloud connection.
It is not possible perform provisioning of multiple cloud connections on the same Everyware Cloud (EC) instance.
Updated about 1 year ago