Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Drag & Drop Files, Choose Files to Upload You can upload up to 2 files.

How to group devices and software builds inside my project

Once data is flowing into your project, you’ll want to look at slices of your fleet: one board revision, one build, or the devices affected by a particular crash. This topic starts with the identifiers every device reports about its hardware and software, then shows where in nRF Cloud you can use them to select a group of devices: device search, dashboards, and issues.

Build identifiers

Every piece of data a device sends to nRF Cloud, and every OTA update request it makes, carries three values that describe what the device is and what it is running: a hardware version, a software type, and a software version. Together with the device ID from the first topic in this lesson, these are the labels nRF Cloud uses to group your fleet and decide which updates a device should get.

Hardware version

The hardware version identifies the physical hardware the software runs on. A device always has exactly one hardware version. It separates board revisions of the same product, such as evt and pvt.

When working with a Nordic development kit, the hardware version is by default CONFIG_BOARD, the board name your firmware is built for (for example, nrf54l15dk). When you create an OTA release, it has to match exactly, or devices won’t be offered the update.

The first hardware version a device reports stays its hardware version, even if the device later reports a different one. You can edit it from the device page if needed.

Software type

Some devices run more than one firmware image. For example, a multi-core SoC such as the nRF53 runs one image on the application core and another on the network core. If each image reported to nRF Cloud on its own, each would have its own software type, such as app and net. You can think of the software type as a namespace that software versions live inside.

Each hardware version has one primary software type. This is the main firmware that nRF Cloud shows as the device’s software version on the device page and uses in fleet charts. For application firmware on nRF Cloud, the primary software type is app.

Software version

A software version is a single release of one software type, such as 1.2.0. nRF Cloud matches each build to its symbol file by Build ID (see Build identification and symbol files), so upload the symbol file for every build you ship, even if several builds share one version string. nRF Cloud uses software versions to:

  • Show how issues and metrics are distributed across releases
  • Reopen a resolved issue if it reappears in a newer version
  • Decide whether a device needs an OTA update

Because OTA compares versions to decide what is newer, use a scheme that sorts predictably. nRF Cloud recommends semantic versioning (SemVer): 1.0.0 for releases, 1.0.0-rc.1 for pre-releases, and 1.0.0-nightly.20261007 for automated builds.

IdentifierAnswersExamplePer device
Hardware versionWhat board is this?shapemate-pvtExactly one
Software typeWhich image on that board?appOne or more
Software versionWhich build of that image?1.2.0One per software type

More on this

Some products may have several firmware build variants depending on the offered feature set or region it is deployed in. To identify a different firmware build, the software version can be tagged, for example, 1.2.0-variant-a.

Device search

Every device has a unique device ID (see Device identification), so the Fleet → Devices tab is the quickest way to find one specific device. The same page lets you filter the fleet by cohort, hardware version, current software version, and many other properties. You can combine filters to narrow down a group. The software version filter matches the version of each device’s primary software type.

Once you have a group, you can save the search to come back to it later. This gives you a device set (see Device Sets and Saved Device Searches). You can also use Bulk Action → Change Cohort to move the matching devices into another cohort.

Dashboards

Dashboard filters narrow every chart on the page to a group of devices. For example, filter to one software version to see how stable that release is. Charts with a Drilldown badge go one step further: clicking a segment opens the Devices tab filtered to the devices behind that data point. Lesson 4 covers dashboard filters and drilldown in more detail.

Issues

You can also start from a problem and work back to the devices it affects. In the Devices tab, the Impacted Issues filter selects every device affected by one or more issues. Check what those devices have in common, such as a hardware version or software version. If a fix needs to reach only those devices, move them into their own cohort for a targeted OTA rollout.

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.