You can use the Lemonbeat Connector to retrieve data from devices connected through the Lemonbeat IoT Platform.
The Lemonbeat Connector is based on a specific micro-service letting Servitly to communicate with the AMQP server, the endpoint where IoT data are initially collected.
Periodically (every 5 minutes) through the API, the connector retrieves from each customer the AMQP connection information.
In this way, the connector verifies the presence of new connections to be established with an AMQP server or invalid ones to be evicted.
This means that when a new customer is created within Servitly or a Lemonbeat Connector configuration is updated (e.g. expired certificate), IoT data may take at most 5 minutes to be read and displayed within the dashboards.
Here is described the data flow from the remote device to Servitly.
A device data is published to the AMQP server.
An LsDl message is notified to the Lemonbeat Connector.
The LsDl message is parsed and converted to the Servitly standard JSON format, using the field names as metric names.
The transformed message is forwarded to Servitly by using the standard MQTT channel and the device UUID and topic part.
Here is described the data flow from Servitly to the remote device.
A user changes a configuration parameter or executes a command from the dashboard.
A message is published on the MQTT channel and made available to the Lemonbeat Connector.
An LsBl message is created encapsulating the data.
The LsBl message is sent to the Lemonbeat backend through the REST API and finally dispatched to the remote device.
First of all, the Lemonbeat plugin must be enabled by entering the Administration / Plugins page.
- Location information pushing from Servitly to the Lemonbeat platform. This allows technicians to have an updated list of locations when configuring a new building.
Once enabled, on the tenant level or for each customer, it is possible to configure the Lemonbeat Connector.
The connector configuration requires to provide:
broker endpoints and credentials for listening to device IoT data.
backend credentials for performing REST API requests.
certificates for client authentication and secure channel establishment.