Skip to content

Changelog

This page collects recent changes to the nRF Cloud APIs, portal, and documentation.

If a category is not included in a given changelog, there are no changes within that category since the previous deployment date.

Archived changelogs by year

February 14, 2024

This section lists changes deployed on February 14, 2024.

New features

In the nRF Cloud portal:

  • Added interface to auto-onboard a device during the claiming process.

In the nRF Cloud APIs:

  • Added QZSS support over CoAP.
  • Added new REST API endpoints for adding devices to your team for further flexibility and automation in the onboarding of devices to nRF Cloud:

  • Added ListTags REST API endpoint to list all device groups to which you are assigned, if your role is an Editor or Viewer.

Enhancements

In the nRF Cloud portal:

  • Creating a FOTA job now shows all of the devices in the job, not just those that have executions.
  • FOTA update Overall Progress card in the portal now includes the number of devices that have timed out.

In the nRF Cloud APIs:

  • ListFOTAJobs and FetchFOTAJob endpoints now include a devices field in the executionStats of the job or jobs in the response stating the number of eligible devices for the job. The executions field has changed to show 0 before the job is deployed, and the number of eligible devices for the job after it has been deployed. Previously, it always showed the number of eligible devices.

Bug fixes

In the nRF Cloud portal:

  • Editors and Viewers can now see groups.
  • Fixed issue with undefined number of devices on old FOTA jobs.
  • Fixed issue where sending A-GNSS data to the device would show two Location Services cards in the device view.
  • Updated permissions for C2C messaging to match the APIs.
  • Fixed multiple issues with provisioning groups with rules.
  • Fixed issue with error message when upgrading to Pro plan.
  • Fixed issue with terminal scrolling.
  • Fixed issue with pop-up saying device not found after deletion.

In the nRF Cloud APIs:

  • Better error message when updating an existing anchor.
  • FOTA retry jobs do not include devices that rejected the update. If the only failures for a FOTA job are devices that rejected the update, no retry job will be created.
  • Old product name “nRF Connect for Cloud” changed to “nRF Cloud” in emailed team invitations.
  • Fixed validation logic for GetLocationFromCellsOrWifiNetworks and GetLocationFromWifiNetworks.

Documentation

January 4, 2024

This section lists changes deployed on January 4, 2024.

New features

In the nRF Cloud portal:

  • Fatal app errors should no longer fully crash the site, but tell the user to reach out to support if the problem persists.

In the nRF Cloud APIs:

  • For nRF Cloud Location Services:
    • Added anchors feature.
  • If any devices in a FOTA job fail to update their firmware, a new job is created automatically with the same firmware bundle, for only the devices that failed. The new job can be applied at any time to retry the update for the failed devices.

Enhancements

In the nRF Cloud portal:

  • Redesigned the device view, mainly for LTE devices.
  • Updated the getting started section on the dashboard to correctly tell users how to add a device.
  • Active and Archived buttons on the Alerts page are now tabs.

In the nRF Cloud APIs:

  • For nRF Cloud Location Services:

    • Added ability to specify request cells as NB-IoT or LTE CAT-M for enhanced positioning.

Bug fixes

In the nRF Cloud portal:

  • Stay on current page when refreshing for rules and FOTA.
  • Fixed issue where selected alerts did not clear when switching tables.
  • Fixed styles for Provisioning Groups card.
  • Cleared error when registering a credit card.
  • Fixed issue where group selectors did not properly set values on tag manager.
  • Smooth scrolling behavior for larger data sets across app tables.
  • Fixed issue where new user address displayed a comma, even when there was no address data.
  • Fixed vertical spacing issue on pricing pop-up.
  • Viewers are no longer able to edit groups.
  • Fixed issue where Location card did not allow a custom date range.
  • Fixed distance miscalculation in group maps.
  • Updated text alignment for FOTA job execution statuses.
  • Fixed issue where user profile was blank after registering a new user.

In the nRF Cloud APIs:

  • In a ListApiUsage request, the start and end date format must match, either YYYY-MM or YYYY-MM-DD.
  • When a FOTA job is deployed, in some cases, the job is immediately canceled and a 422 status code (Unprocessable Content) is returned along with the message Empty job target. Previously, a 500 status code with message Internal Server Error was returned.

    This applies to the following cases:

    • if all devices in a FOTA job are ineligible to be updated with the given firmware bundle.
    • if there are no devices in the FOTA job’s group.
    • if none of the devices in the FOTA job’s list of devices exist.

Documentation