Developer
Ask a QuestionBlecon WebsiteBlecon Console
  • Learn Blecon
    • Introduction
    • Blecon Modems
      • Device Identity and Network Security
      • Modem Firmware vs Modem Library
      • Using the Modem
      • Communicating with the cloud
      • Sending data from the cloud to a device
    • Blecon Hotspots
    • Blecon Networks
      • Blecon Accounts
      • Registering devices
        • The Blecon Scanner
        • Blecon Scanner Developer Guide
      • Blecon Events
      • Cloud Integrations
  • Cloud Integrations
    • Webhook
    • AWS S3
    • AWS SQS
    • AWS EventBridge
    • Memfault
  • Getting Started Guides
    • Getting started index
    • Install the Blecon Modem Firmware
    • Set up a Blecon Hotspot
    • Use Blecon from your computer with the Blecon CLI
    • Create a Network and register a device
    • Send device requests and events to your web service
    • Use Blecon from a Development Board
    • Use the Blecon Modem from an MCU
  • Device Guides
    • KKM S5-BCN
  • Development Board Guides
    • Supported Development Boards
    • Ezurio DVK-BL54L15
    • Fanstel EV-BM15C
    • InsightSiP ISP2454-LX-EB
    • Nordic nRF52840DK
    • Nordic nRF54L15DK
    • Minew ME54BE01
    • Panasonic PAN-B511 EVB
    • Raytac AN54L15Q-DB
    • u-Blox EVK-NORA-B20
  • Modem Reference
    • Modem Firmware Releases
      • nRF54L15 DK
      • nRF52840 Dongle
      • nRF52840 DK
    • CLI Releases
    • SDK Releases
    • Modem API Reference
    • Modem Protocol Reference
      • Request Frames
      • Command Protocol
      • UART Transport
    • Guides and best practices
      • Retrieve a device's identity
  • Cloud Reference
    • Configuration API
    • Advanced event routing
  • Hotspot Reference
    • Blecon Hub
Powered by GitBook

Get Support

  • Ask a question
On this page
  • Polling
  • Push Notifications
  1. Learn Blecon
  2. Blecon Modems

Sending data from the cloud to a device

How to send data to a device based on an external event

PreviousCommunicating with the cloudNextBlecon Hotspots

Last updated 1 month ago

With Blecon, devices are always clients. Like other network clients such as web browsers, they are not directly reachable from the service.

This model suits low-power, occasionally connected devices very well. Most of the time, Blecon devices will be asleep and disconnected from the network.

Polling

The primary mechanism for getting data from the cloud to the device is for the device to request that data using a regular Blecon request. This works well for things such as configuration updates and firmware updates. For example, you might want the device to request this information once a day.

Polling rates have natural limitations, specifically in how much battery power you want to consume.

Push Notifications

Where you need more low-latency communication, we offer a Push Notification function. When set, the Blecon Network will connect to the device as soon as the device is in range.

The device must then react to the connection event and immediately issue a standard Blecon Request to retrieve the required information.

Your cloud service sets push notifications using the . See request_connection in the API documentation below:

Blecon API
https://apidocs.blecon.net/docs/api/legpqj1h1drul-update-a-device