LTE Beacon: Web IDE Micro-app deployment guide
In this article, you will learn about the deployment functionality of our IDE: what it is, how it works, and how to use it.
What’s ahead (aka Table of Contents)
In a nutshell
IoT App deployment allows you to streamline the release of production versions of your IoT apps to LTE Beacons. It allows version control, and makes working with data easier.
Drafts vs. releases
There are two stages in the lifelf a Micro-app: the draft and the release. A draft is the development version of
your Micro-app. A draft can be modified and uploaded to the Beacon that’s currently connected to your browser via
When working with a Micro-app draft, every time you want to upload a new version to the Beacon, you have to connect the device to your machine via Web Bluetooth.
When you deploy your IoT App to your Beacon(s) via the Deployment interface, a ‘snapshot’ of the Micro-app is created and turned into the release version. A release is the production version of your IoT app. You can edit the Cloud code of a release, but not its Micro-app code.
Once you deploy the Micro-app to production and assign it to your LTE Beacon(s), the devices will pull the latest version via LTE during the next sync. No need to for an active Web Bluetooth connection!
Deploying your Micro-app
You can turn your draft into a release version of your Micro-app using the Deployment Interface.
To access the Deployment Interface, click the ‘Deploy Remotely’ button in the upper-right corner of the IDE.
The interface lets you choose any number of your LTE Beacons to deploy the Micro-app to.
Once you’ve chosen the Beacons you want to deploy to, click the ‘Schedule Release’. Your Beacon will pull the Micro-app during the next sync.
Back in the Web IDE, you’ll notice that the Micro-app code is now greyed-out and you’re no longer able to modify it.
The ‘Deploy Remotely’ button has also been replaced by the ‘Manage Deployment’ button.
You can click it to go back to the Deployment Interface and assign or unassign devices.
An important feature of the Deployment Manager is version control. Each time you deploy a new ‘snapshot’ of your Micro-app, the new version will appear in the IoT App Settings Panel. This way, you can access all your previous releases and see which Beacons they are currently assigned to. The name of each Release gets generated automatically, according to the format: [App_Name] - 001, where the number corresponds to the IoT App’s iteration.
Any data (device_events) incoming from an LTE Beacon with an IoT App assigned to it will get associated with that IoT App’s current release version in the Estimote Cloud. Over at the Estimote Web IDE, the Cloud Event Log will display events incoming from all of the Beacons using that particular release version. Each event will contain the ID of the Beacon it came from. The events will trigger the Cloud Code of the assigned release.
The Cloud Settings Panel contains a link to the REST endpoint where you can access the data sent-in by the devices using the current Micro-app release.