Skip to main content

Lemonbeat

Support
  • Updated

Create services for smart buildings using the Lemonbeat smart meters and sensors.

Lemonbeat

The Lemonbeat Connector can be used to exchange data from devices connected through the Lemonbeat IoT Platform.

System Architecture

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.

Lemonbeat Architecture

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.

 

Data Listening

The flow of data from the remote device to Servitly follows the following steps:

  1. A device data is published to the AMQP server.

  2. An LsDl message is notified to the Lemonbeat Connector.

  3. The LsDl message is parsed and converted to the Servitly standard JSON format, using the field names as metric names.

  4. The transformed message is forwarded to Servitly by using the standard MQTT channel and the device UUID and topic part.

 

Data Publishing

The flow of data from Servitly to the remote device follows the following steps:

  1. A user changes a configuration parameter or executes a command from the dashboard.

  2. A message is published on the MQTT channel and made available to the Lemonbeat Connector.

  3. An LsBl message is created encapsulating the data.

  4. The LsBl message is sent to the Lemonbeat backend through the REST API and finally dispatched to the remote device.

 

Plugin Configuration

To enable this plugin, you need to:
  1. Go to the Integrations / Plugins page.
  2. Select the IoT Connectors category.
  3. Locate the Lemonbeat card.
  4. Click on the card switch to activate the plugin.
  5. Configure the plugin properties and save.

 

Here is the list of all the properties that can be used in the plugin configuration.

PROPERTIES
Base API URL The Lemonbeat backend URL used for managing automations.
Type: STRING | Optional
Username The username used for Lemonbeat backend authentication.
Type: STRING | Optional
Password The password used for Lemonbeat backend authentication.
Type: PASSWORD | Optional

 

Connector Configuration

Once enabled, on the tenant level or for each customer, it is possible to configure the Lemonbeat Connector.

Lemonbeat Configuration

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.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.