Deployment Group Tag Behavior -- Empty Group on No Tag Selected
When creating a new deployment group without assigning a tag, devices without tags are automatically added to the group. The expected behavior is that if no tag is specified, the deployment group should remain empty and require devices to be added manually. Having untagged devices auto-assigned to a new group creates a risk of unintended firmware deployments going out to the wrong devices. Requesting that the default behavior be updated so that a new deployment group starts empty unless a tag is explicitly assigned.
Eduardo Castro 2 months ago
Feature Request
Deployment Group Tag Behavior -- Empty Group on No Tag Selected
When creating a new deployment group without assigning a tag, devices without tags are automatically added to the group. The expected behavior is that if no tag is specified, the deployment group should remain empty and require devices to be added manually. Having untagged devices auto-assigned to a new group creates a risk of unintended firmware deployments going out to the wrong devices. Requesting that the default behavior be updated so that a new deployment group starts empty unless a tag is explicitly assigned.
Eduardo Castro 2 months ago
Feature Request
Planned
Sort device list by firmware version and OTA update status
User Story As a firmware release manager, I want to sort the device list by firmware version and update status, so that I can quickly identify which devices have not updated during a rollout without having to manually scan the entire list. Description The release page provides a useful overview of a firmware rollout and links directly to the list of devices in that release. However, once inside the device list, there is no way to sort by firmware version. When a release is mostly complete and only a handful of devices remain, identifying those stragglers requires scanning row by row. The requested sort behavior is: Primary sort: firmware version Secondary sort within each firmware version group: OTA update status, ordered as Active > Quarantine/Timeout > Update Off This combination allows teams to immediately see what firmware version each device is running, and within that group, which devices are healthy versus which failed or timed out during the update.
Eduardo Castro 3 months ago
Planning
Planned
Sort device list by firmware version and OTA update status
User Story As a firmware release manager, I want to sort the device list by firmware version and update status, so that I can quickly identify which devices have not updated during a rollout without having to manually scan the entire list. Description The release page provides a useful overview of a firmware rollout and links directly to the list of devices in that release. However, once inside the device list, there is no way to sort by firmware version. When a release is mostly complete and only a handful of devices remain, identifying those stragglers requires scanning row by row. The requested sort behavior is: Primary sort: firmware version Secondary sort within each firmware version group: OTA update status, ordered as Active > Quarantine/Timeout > Update Off This combination allows teams to immediately see what firmware version each device is running, and within that group, which devices are healthy versus which failed or timed out during the update.
Eduardo Castro 3 months ago
Planning
Completed
Tag autocomplete -- show existing tags as you type
When adding a tag to a post or item, there is currently no autocomplete or suggestion list. If I want to reuse a tag I have used before, I have to remember the exact wording or copy and paste it from another unit This leads to inconsistent tagging and makes it harder to filter or find content by tag. The request is to show a dropdown of already-used tags as the user types. This is standard behavior in most tagging systems and would significantly improve tag consistency across the board.
Eduardo Castro 3 months ago
Planning
Completed
Tag autocomplete -- show existing tags as you type
When adding a tag to a post or item, there is currently no autocomplete or suggestion list. If I want to reuse a tag I have used before, I have to remember the exact wording or copy and paste it from another unit This leads to inconsistent tagging and makes it harder to filter or find content by tag. The request is to show a dropdown of already-used tags as the user types. This is standard behavior in most tagging systems and would significantly improve tag consistency across the board.
Eduardo Castro 3 months ago
Planning
Completed
Update the CLI install script to work on Linux
https://raw.githubusercontent.com/nerves-hub/nerves_hub_cli/master/install.sh Following installation instructions: ```sh $ curl --proto '=https' --tlsv1.2 -fsSL https://raw.githubusercontent.com/nerves-hub/nerves_hub_cli/master/install.sh | sh sh: 31: [[: not found sh: 37: [[: not found sh: 7: [[: not found sh: 16: [[: not found gzip: stdin: not in gzip format tar: Child died with signal 13 tar: Error is not recoverable: exiting now ```
Ben Rogmans 5 months ago
Planning
Completed
Update the CLI install script to work on Linux
https://raw.githubusercontent.com/nerves-hub/nerves_hub_cli/master/install.sh Following installation instructions: ```sh $ curl --proto '=https' --tlsv1.2 -fsSL https://raw.githubusercontent.com/nerves-hub/nerves_hub_cli/master/install.sh | sh sh: 31: [[: not found sh: 37: [[: not found sh: 7: [[: not found sh: 16: [[: not found gzip: stdin: not in gzip format tar: Child died with signal 13 tar: Error is not recoverable: exiting now ```
Ben Rogmans 5 months ago
Planning
Feature request: cancelling outstanding user invites
When sent to the wrong address, they remain open forever - confronting you with your mistakes forever 😅
Ben Rogmans 5 months ago
Feature Request
Feature request: cancelling outstanding user invites
When sent to the wrong address, they remain open forever - confronting you with your mistakes forever 😅
Ben Rogmans 5 months ago
Feature Request
Support scripts: run on deployment group
As a user, I would like to run support scripts in bulk so that I can retrieve certain information for an entire deployment group (or set a certain setting, if support scripts take parameters).
Ben Rogmans 5 months ago
Feature Request
Support scripts: run on deployment group
As a user, I would like to run support scripts in bulk so that I can retrieve certain information for an entire deployment group (or set a certain setting, if support scripts take parameters).
Ben Rogmans 5 months ago
Feature Request
Support scripts: taking parameters
As an engineer I want to be able to use variable input data for support scripts, that are passed as function arguments, so that I can prepare easy to use support scripts for operational staff.
Ben Rogmans 5 months ago
Feature Request
Support scripts: taking parameters
As an engineer I want to be able to use variable input data for support scripts, that are passed as function arguments, so that I can prepare easy to use support scripts for operational staff.
Ben Rogmans 5 months ago
Feature Request
Completed
Release description and notes
Allow for releases to be given a description and notes when they are created. This is useful for tracking the reasons for the change, and what’s included in the firmware update.
Josh Kalderimis 6 months ago
Planning
Completed
Release description and notes
Allow for releases to be given a description and notes when they are created. This is useful for tracking the reasons for the change, and what’s included in the firmware update.
Josh Kalderimis 6 months ago
Planning
Planned
Required Releases
Allow releases to be marked as ‘required’ so that devices in a deployment are forced to update to specific versions before receiving the latest. eg. A deployment has 3 releases in its history, v1, v2, and v3. If no releases are marked as ‘required’, v3 will be sent to devices, but if v2 is a ‘required’ release and there are devices still on v1 firmware, they will be requested to update to v2 first before then being asked to update to v3.
Josh Kalderimis 6 months ago
Planning
Planned
Required Releases
Allow releases to be marked as ‘required’ so that devices in a deployment are forced to update to specific versions before receiving the latest. eg. A deployment has 3 releases in its history, v1, v2, and v3. If no releases are marked as ‘required’, v3 will be sent to devices, but if v2 is a ‘required’ release and there are devices still on v1 firmware, they will be requested to update to v2 first before then being asked to update to v3.
Josh Kalderimis 6 months ago
Planning
Planned
CircleCI Orb
Similar to the recently shipped GitHub Action, this would allow users to more easily ship new firmware to NervesCloud and their devices. https://circleci.com/docs/orbs/author/manual-orb-authoring-process/#create-a-namespace https://circleci.com/developer/orbs/orb/dwave/orb-examples#orb-source https://oneuptime.com/blog/post/2026-01-27-circleci-orbs/view https://github.com/cypress-io/circleci-orb https://medium.com/@speeddragon/building-an-orb-in-circleci-elixir-example-4960d4be02f3
Josh Kalderimis 6 months ago
Planning
Planned
CircleCI Orb
Similar to the recently shipped GitHub Action, this would allow users to more easily ship new firmware to NervesCloud and their devices. https://circleci.com/docs/orbs/author/manual-orb-authoring-process/#create-a-namespace https://circleci.com/developer/orbs/orb/dwave/orb-examples#orb-source https://oneuptime.com/blog/post/2026-01-27-circleci-orbs/view https://github.com/cypress-io/circleci-orb https://medium.com/@speeddragon/building-an-orb-in-circleci-elixir-example-4960d4be02f3
Josh Kalderimis 6 months ago
Planning
Planned
Allow the CLI to return JSON
This would allow the firmware uploading GitHub Action to parse the output and display it nicely in the GitHub UI
Josh Kalderimis 6 months ago
Planning
Planned
Allow the CLI to return JSON
This would allow the firmware uploading GitHub Action to parse the output and display it nicely in the GitHub UI
Josh Kalderimis 6 months ago
Planning
Completed
GitHub Action
Add a GitHub Action to simplify to uploading of Nerves firmware, including updating a deployment with the newly uploaded firmware. https://github.com/nervescloud/upload-nerves-firmware
Josh Kalderimis 6 months ago
Planning
Completed
GitHub Action
Add a GitHub Action to simplify to uploading of Nerves firmware, including updating a deployment with the newly uploaded firmware. https://github.com/nervescloud/upload-nerves-firmware
Josh Kalderimis 6 months ago
Planning
In Progress
Deployment workflows
Allow deployments to define workflows which contain one or more connected stages with their own conditions and concurrency settings.
Josh Kalderimis 6 months ago
Planning
In Progress
Deployment workflows
Allow deployments to define workflows which contain one or more connected stages with their own conditions and concurrency settings.
Josh Kalderimis 6 months ago
Planning
Planned
Slack notifications
Allow Slack workspaces to connect to NervesHub for event notifications, similar to Webhook notifications
Josh Kalderimis 6 months ago
Planning
Planned
Slack notifications
Allow Slack workspaces to connect to NervesHub for event notifications, similar to Webhook notifications
Josh Kalderimis 6 months ago
Planning