Libelium Waspmote

Libelium Waspmote - Plug & Sense! loggers can be configured to send data to in a few easy steps. Waspmotes can communicate directly or use a Meshlium to connect large sensor networks.


Source configuration

  1. Create a Data Source and select Data logger as the Source Type. Choose Libelium from the list and click Next.

  1. Select Waspmote / Plug & Sense! as the Model. Click Next.

  1. Select TCP Server as the transport type if the Waspmote will connect directly to (alternatively jump to Step 4 for Meshlium connection). A Waspmote Id will be automatically generated. Select the timezone of the logger’s clock and click Next.

  1. Select Meshlium if the Waspmote will send data via a Meshlium (alternatively jump to Step 6). Enter the Meshlium Id and optional Auth key if configured in the application on the device. Click Verify.


The application in the Meshlium device needs to be started and initial connection established with before it can be used as a transport.

  1. Select the Waspmote you would like to acquire data from and click Next.

  1. Parameters will be automatically created on initial data acquisition. Click Finish to complete the setup.


You can disable/enable parameters from the Data Source properties dialog after initial creation.

Device settings

Use the settings below for Direct Connection or Meshlium Connection with your Waspmote.

Direct Connection

Refer to our example Waspmote operating programs for use with 3G (download) and 4G modems (download) to establish a direct connection to

Apply the following settings to the variables at the top of the operating program:

Use the unique Waspmote Id generated during Data Source creation. eg. “8494091048”

Meshlium Connection

Connect to the web interface on the Meshlium device, open the Cloud Connector configuration and Save the following settings prior to clicking Start to run the application:

Meshlium Name
Enter a name to help identify this device
Auth Key
Optional secret key required to create a Data Source that uses this device in (or leave blank for none).


Use the Events view with the detail level set to Debug for reviewing communication history and diagnosing configuration issues.

PDF HTML Epub Powered by Read The Docs