Changelog

Follow new updates and improvements to NervesCloud.

May 18th, 2026

Improved

UI

We have added the ability to select all devices in a filtered device list, allowing you to run bulk actions across all devices without having to select every single device on every page.

After selecting a device, a button will appear at the top of the bulk actions sidebar asking if you want to select all devices found in the filter.

These actions are performed in the background, so it doesn’t matter whether you select 20 devices, 200, 2,000, or 20,000; the action will be run on all of them.

May 15th, 2026

New

UI

You can now view a device’s firmware history, including whether it reverted to a previous firmware version or if the firmware is unknown to NervesCloud.

Over the coming weeks, we will be adding more information, including the source of the firmware update, eg, was it a manually requested update by a team member, or was the update part of a deployment release.

May 14th, 2026

New

UI

We have added support for product-level notifications to alert your team to potential issues.

Support for two notifications have been added:

  1. Device auth failing due to duplicate identifiers. This is specific to Shared Secrets auth, and the likely cause is related to devices being deleted but not destroyed (we soft delete devices by default).

  2. A soft deleted device has been cleaned up after two weeks. This hasn’t been enabled yet, but will be in the coming months. This will be documented in the changelog two weeks before its enabled.

More notifications will be added over time. If you have a suggestion or idea, please let us know.

March 11th, 2026

Early last week, while working to improve our UI, we discovered a security vulnerability in the open-source NervesHub platform.

Upon investigation, this security issue had been present for over three years. And after further investigation, we found a different security issue which had appeared 11 months ago.

We promptly fixed both issues and updated NervesCloud so that all our users and their devices were protected. And then, together with the Erlang Ecosystem Foundation, we put together a comprehensive security advisory, so it is transparently documented.

We have taken further steps to improve our test suite and are working on additional changes to help ensure these issues don’t recur.

Please read the Security Advisory on GitHub for more information.

And if you have any questions, comments, or feedback, please contact us at hello@nervescloud.com

March 1st, 2026

When a new Deployment Release is created, delta firmware is generated using the source firmware of devices currently in the Deployment Group and the new target firmware.

Deployments are paused while the deltas are generated, allowing you to deliver the smallest firmwares to your connected devices.

The deployment is resumed once all deltas have generated successfully.

If one or more deltas fail to generate or time out during generation, the deployment will stay paused until user intervention, either by deleting the failed firmware deltas or retrying the delta generation.