[TOC]
- Developer Portal
- Youtube videos
- Q&A Platform
- Github code samples
- Network coverage : 32 countries and counting ;)
- BCX17 Intro slides
You need the unique ID of the device (printed on the back), and its PAC(provided 1 to 1)
Head out to the Sigfox backend and fill in the form.
(If you already have a Sigfox account, log in first)
You will receive an automated email asking you to setup your password and confirm your account
You're good to go!
⚠ It may take up to one hour to attach the device to your account, in case it was previously attached to a demo account.
Good things come to those who wait 😉
Double-press the Sensit button.
The LED should blink for ~6 seconds, while its sending a first message
Log-in to your Sigfox account, and then access the DEVICE TYPE menu, then click on the name of the newly created device type. It should be called Sensit EVK
Enter the Associated Devices menu, and click on the ID of the only one listed.
Your incoming messages will appear here, listing the time of reception, raw data payload & reception quality indicators.
To push incoming data to your server, you need to use the callbacks mechanism.
Callbacks are configured at the device type level. Which means that the day you'll have 3 millions units of your device, you'll need to set the configuration once for all of them
In your device type entry, click on the callbacks menu in the left panel.
The callbacks screen list the configured callbacks, and allow you to activate/deactivate any of them on the fly.
On the callbacks page click on the New button in the top right corner.
Select AWS IoT or Azure IoTHub if you want to use these services, through the easy Sigfox bridge built with them.
Select custom callback if you just want to set up a callback to any URL.
Then select DATA > UPLINK to make sure it will be called upon any incoming transmission.
Then set up URI, HTTP method, content type, HTTP headers & request body
Checkout the documentation about the Sensit frames. The data is sent packed in a few bytes, containing active mode, sensor values, battery status, ...
- Uplink messages : Messages from the device to the network
- Downlink messages : Messages from the network to the device
⚠ To enforce the ETSI regulation on the 868MHz, the Sensit won't send more than 6 messages per hour (duty cycle).
If you need to send more than that for testing purposed during the week end, contact Nicolas
The complete documentation of the OL2385 development kit is available on NXP website
Please get in touch with Vivek Tyagi if you need more information about this kit.
⚠ API should be used as a sync/backup mechanism.
We recommend using the callbacks (push) as primary data access channel. No need to poll the API every second ;)
Extensive documentation of the Sigfox API available here
You'll also find the API documentation in the Group > Api Access menu.
Once you set up a pair of API credentials (look for the new button on the top right), you'll have a link to the documentation matching the access rights you chose.
Mohammad Zubair (@Bosch SI) wrote a Sigfox adapter for the Eclipse Hono platform.
Read the documentation & step-by-step guide here