Device Inventory

The Device Inventory provides access to all devices in your project. It can be found via Fleet → Devices. You can use it to perform the following tasks:

• Finding devices matching certain criteria
• Saving a search for later use
• Creating a Device Set chart to visualize the size of a population of devices over time
• Importing devices from a .csv file
• Exporting devices to a .csv file
• Bulk-changing properties of devices
• ... and more!

Device Inventory

Device Search

The Device Inventory has powerful filters that you can leverage to quickly find the devices you are looking for.

Each type of filter is explained below in more detail.

Wildcards

Some filters support using a * (wildcard) character at the beginning and/or end of the search term:

• *example: matches any term ending with example
• example*: matches any term starting with example
• *example*: matches any term containing example

Note: the * character is not supported in the middle of the search term.

Combining Multiple Filters

When multiple filters are applied at the same time, they are combined with an AND operator. Some filters support entering multiple values, for example the Device Serial filter. In this case, an OR operator is used "within" that filter. In the example below, the search will return devices that have:

• Device Serial starting with MFLT OR starting with ACME
• AND
• Device Serial ending with 88 OR ending with 55

Example of combining multiple filters

Negating a Filter

Several filters — Device Serial, Current Cohort, Nickname, Hardware Version, Visibility Level, and Visibility Assignment Mode — have an operator dropdown next to the filter name. Switch it from any of to not to exclude the values you enter instead of matching them.

Searching Devices by Device Serial

One or more Device Serials or wildcard patterns can be used in this field.

The example below finds Devices with a Device Serial, matching MFLT0000013, or starting with MFLT, or containing 15 or ending with 9:

Searching Devices by Current Cohort

One or more Cohorts can be used in this field.

The example below finds Devices that are currently in the Cohort Production or Test:

Searching Devices by Nickname

An exact match or a wildcards pattern can be used in this field.

The example below finds Devices that have a Nickname starting with Buggy:

Searching Devices by Current Software Version

The Software Version filter supports several ways to match or exclude versions. Multiple expressions or values within a single filter row are logically OR'd together. You can also add further rows with + and condition; separate rows within the Current Software Version block are combined with an AND operator.

The example below finds Devices that are currently running Software Version 1.1.1 or 1.1.0:

The example below finds Devices that are NOT (∉) running Software Version 1.0.0:

Comparison operators: Type a comparison operator followed by a version string to match versions using natsort ordering. The example below finds Devices that are running Software Versions greater than 1.0 (e.g. 1.0.1, 2.0).

Semver-aware comparison is also available when entering a comparison operator followed by a valid semver version (e.g. >1.0.1 but not >1.0). This will only match on valid semver versions. For example, >1.0.1 will not match 2.0 with semver comparison, but it will match with natsort comparison.

Regex: Type a regular expression pattern to match versions using regex (e.g. ^1\.1\.[0-9]* to match all 1.1.x semver versions).

Searching Devices by Hardware Version

One or more Hardware Versions can be used in this field.

The example below finds Devices that have the Hardware Version pvt:

Searching Devices by First/Last Seen

This filter can be used to find devices that have first or last been seen within a certain time frame, or have never been seen at all. The latter is possible in case devices have been imported via .csv but have not yet uploaded any data to Memfault.

Each row has a time range dropdown offering:

• Last 24 hours, Last 7 days, Last 30 days, Last 60 days: relative presets that always follow the current time.
• Anytime: seen at some point, at any time.
• Never: never seen at all.
• Custom range: pick your own time range.

In the example below, the search is narrowed to Devices last seen in the last 24 hours, and the dropdown is open on the First Seen row:

Searching Devices by Staged-rollout Release

Select devices that are staged to receive a staged-rollout Release. See documentation on Over-the-Air Updates for more information.

Searching Devices by Developer Mode

Select devices that are in Server-Side Developer Mode. See documentation on Developer Mode for more information.

Searching Devices by Visibility Level

Select devices by their effective Visibility Level — the level in force on the device, whether it was assigned manually or automatically.

The dropdown lists the Visibility Levels configured for your project, plus Unassigned for devices that do not currently hold a level. Which levels a project has differs from project to project, so your list may not match the example below.

Searching Devices by Visibility Assignment Mode

Select devices by how their Visibility Level was assigned:

• Automatic: Memfault manages the device's Visibility Level, optimizing for the best use of your available quota. The level may change over time.
• Manual: the Visibility Level was set explicitly, and Memfault will not change it.
• Off: the device receives only the bare-minimum entitlements needed to check in.

The example below finds Devices that are currently at the High Visibility Level AND had that level assigned manually:

Searching Devices by Config State

This filter can be used to find devices based on the sync state of Device configuration (only applicable to Linux and Android SDKs). The Device configuration contains the settings that are applied to the device, such as Fleet Sampling Resolutions, dynamic SDK Settings, and more.

Searching Devices by Device Attributes

This filter finds devices by Device Attribute. Different operators can be used to filter by attributes. Only a single, literal value can be provided.

The example below finds Devices that have a Device Attribute region with the value EU:

Searching Devices by Aggregated Metric

To filter or sort Devices based on a metric's aggregate value, add a Historical Data filter and select Aggregated Metric.

This filter allows you to specify the type of report, an aggregation function (min, mean, or max), and a threshold value for each timeseries metric. You can add multiple combinations of metrics, aggregation functions, or report types in the same search; each combination will have its own column in the results.

As with the Report Count filter, you can also add conditions on timeseries metrics to filter which reports are aggregated, and use Collected on Software Version… to restrict the aggregation to reports captured on specific Software Versions.

The example below finds Devices that have a mean value of less than 50 for the battery_soc_pct metric over the last 7 days.

Searching Devices by Report Count

To find devices based on the number of matching reports they have uploaded, add a Historical Data filter and select Report count.

This filter allows you to specify the type of report and the count of reports to filter by. In addition, you can add conditions on timeseries metrics to filter the reports by, before counting them. It's possible to use the same metric multiple times.

All conditions are combined with an AND operator and operate together on each report.

Optionally, use Collected on Software Version… to only count reports that were captured on specific Software Versions.

The example below finds Devices that have uploaded more than 3 Heartbeat reports with timeseries metric battery_soc_pct greater than 50 AND voice_command_count greater than 5, between 2026-08-27 and 2026-09-03, on Software Version 1.1.0:

Searching Devices by Device Vital

To find devices based on a Device Vital, add a Device Vitals filter.

This filter also allows you to add conditions to filter the reports by, just like the Report Count filter.

Optionally, filtering can be done on the Software Version that the reports were captured on.

The example below finds Devices that have an expected battery life of 10 hours or less, based on Heartbeat reports that have more than 1000 steps, were captured between 2024-06-21 and 2024-06-27, on Software Version 1.0.0 or 1.1.0:

Searching Devices by Reboot Reason

To find devices by why they rebooted, add a Historical Data filter and select Rebooted due to....

Pick one or more reboot reasons, then set a comparison operator and a count to match how many such reboots occurred in the selected time range (for example, > 0 times). Only reboot reasons actually seen in the selected range are offered, so pick the date range first.

Optionally, use Collected on Software Version… to only count reboots that were reported on specific Software Versions.

The example below finds Devices that rebooted at least once between 2026-08-27 and 2026-09-03 due to a "User Shutdown" or "Assert" reboot, on any Software Version:

Searching Devices Impacted by Issues

This filter allows you to find devices that have been impacted by specific Issues or Issues matching certain filter criteria. Click the pencil icon to edit the filters or select specific Issues:

The filter modal allows you to set detailed criteria for the Issues, including filtering by Reason, Trace count, and other Issue attributes. You can also optionally select specific issues by using the checkboxes:

Searching Devices with a Custom Filter

Memfault can set up project-specific Custom Filters for advanced queries that the standard filters don't cover. Each Custom Filter has its own name and its own set of parameters, and some also support filtering by Software Version.

The Custom Filter button only appears if one or more Custom Filters have been configured for your project. contact us if you'd like one set up.

Saved Device Searches

After building a search, you can save it for reuse via the save button next to the filter panel:

• Save as new: creates a new Saved Device Search
• Save changes: updates an existing Saved Device Search, if applicable

The Reset filters button discards all filters and reverts to the default, unfiltered Devices page. To clear any unsaved edits made to a saved search, you can re-select it in the dropdown.

Managing Saved Device Searches

Saved searches can be renamed, deleted, or favorited from either the dropdown on the Devices page or the All Saved Searches page.

Your favorited searches and the All Saved Searches page are available as links in the expandable Devices section of the sidebar.

note

A Saved Device Search cannot be deleted while linked to a Device Set chart.

Saved Device Searches can also be used to filter Dashboards.

Creating Device Set Charts

See Device Set charts for more information.

Importing Devices from .csv

Click the "Create Devices using CSV" button to open the modal that allows you to upload a CSV file to create devices in bulk. Use the following format:

• Required columns: device_serial and hardware_version.
• Optional: cohort.

The Cohort column

• Newly created devices without a value in the Cohort column will be added to the default Cohort.
• It must contain Cohort slugs (not Cohort display names). All Cohort slugs can be found Fleet → Cohorts

Bulk Actions

Bulk Action: Change Cohort

Using the "Bulk Action" -> "Change Cohort" menu, you can bulk-update the Cohort of all matching Devices at once. Use search filters to define the desired list of Devices first.

Bulk Action: Export

Using the "Export" menu, you can bulk export lists of Devices and associated information as a CSV file. Use search filters to define the desired list of Devices and then export that list as a CSV. Once the CSV is generated, it will be emailed to you. This makes it easy to share information on specific groups of Devices to teams in the organization outside Memfault for further processing in external tools or scripts for logistics, reporting, etc.

By default, on export the CSV will include basic information about the Device such as serial number, Cohort, software and Hardware Version etc. and a user can also choose to include Device Attributes and Vitals in the export if required.

Vitals can be exported for predefined lookback periods, or within custom timeframes.

Bulk Action: Update Staged

Using the "Bulk Action" -> "Change Staged" you can change the staged flag of multiple Devices. The staged flag controls whether a Device can see the staged Releases that are activated its Cohort.

Normally, this flag is set automatically when you change the rollout percentage slider. However, that mechanism randomly picks devices while the bulk action allows for more control like deciding the order in which to mark Devices as staged.

Bulk Action: Update Fleet Sampling Resolution

This action allows you to set the aspect resolution of multiple devices at once and is explained in more detail here.

Deleting Devices

Devices can be deleted individually from the Device Details page, via the three-dots menu in the top-right corner:

Deleting a device is a permanent action and cannot be undone. All data associated with the device will be permanently removed from Memfault.

Performing this action requires admin level permissions.

Deleting devices in bulk is not supported at this time. If you need to delete many devices, please contact Memfault support for assistance.