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

April 17, 2024

This section lists changes deployed on April 17, 2024.

New features

In the nRF Cloud portal:

  • Refactored mobile navigation to function similarly to the full-screen sidebar.

Enhancements

In the nRF Cloud portal:

  • Improved device status to give more general device information: Added firmware versions to device list, as well as connection protocol and connectivity status (if MQTT) to the device view. Groups view shows the same values as the device view.

For nRF Cloud Location Services:

  • Sanitized anchor name on creation or update. Names must be maximum 32 characters, using only numbers, letters, underscores, dashes, and spaces. All other characters will be removed and no error will be returned.
  • Cache times for GNSS ephemerides from the QZSS constellation are more accurate.

Bug fixes

In the nRF Cloud portal:

  • Fixed issue where proxy field widths shrank too much on mobile screens.
  • Added overflow support to alerts card types.
  • Added check for group names that are too long.
  • Fixed issue where alert URLs had extraneous paramaters attached.

In the nRF Cloud APIs:

  • For nRF Cloud Location Services:

    • If multiple anchors are returned in a location request, they are now sorted in descending order of signal strength.

  • For the FOTA Service:

    • FOTA jobs with no user-defined job name now create retry jobs named after the job ID, rather than "undefined".
    • In the REST API, the ListFOTAJobs endpoint now returns the correct total when there are job deletions in progress. These jobs are not included in the list.
    • Fixed a case where requests to obtain device details returned a status code of 500. This affected the REST API endpoints FetchDevice and ListDevices. The same issue caused the portal to show no devices instead of the list of devices on the Devices page.
    • Fixed a bug that prevented devices with uppercase letters in their ID from using some nRF Cloud services when connecting over CoAP.

Documentation

  • Updated external links to docs.nordicsemi.com.
  • Removed finished command from provisioning configuration documentation, as the user no longer needs to manually add this command.

  • Improvements to Working with teams page:

    • How to switch between teams.
    • How to remove a user from a team.
    • Updated the steps to transfer and accept ownership of a team.

  • Added steps to remove devices from a team.

  • Added steps for viewing device locations and alerts from the Groups view in the nRF Cloud portal.
  • Updated steps for FOTA through the nRF Cloud portal.
  • Improvements to device identity documentation.

March 13, 2024

This section lists changes deployed on March 13, 2024.

New features

Added support to CoAP for updating the desired state.

Enhancements

In the nRF Cloud portal:

  • Added more metrics of Location service response data for better monitoring, analysis, and error reporting.
  • Updated buttons throughout the site to match Nordic branding more closely.
  • When downloading data from the terminal card, it now downloads the JSON file.

  • Refreshing the FOTA update view now updates every 10 seconds down from 25 seconds.

  • Viewers and editors can now see group permissions.

In the nRF Cloud APIs:

  • The statuses of in-progress FOTA executions are updated more frequently in FOTA REST API requests.
  • Improved messaging for errors returned by various Device management REST API endpoints.
  • Added a new REST API endpoint FetchOpenApiSpec for describing the existing URL https://api.nrfcloud.com/v1/openapi.json.
  • Added a new REST API endpoint GetSystemStatus for describing the existing URL https://api.nrfcloud.com/v1/status.

In the nRF Cloud APIs and portal:

  • FOTA job executions now show as Cancelled instead of Failed if the device is deleted before it begins the FOTA update.
  • Eliminated the delay between the user updating a device group and showing the change in subsequent REST API requests and in the portal.
  • The bulk ops feature has been deprecated for Identity and Provisioning Services.

Bug fixes

In the nRF Cloud portal:

  • Fixed handling of multiple retries of a FOTA job.
  • Added a loader to Location Services page map card.
  • Header texts are displayed properly.
  • Disabled the toggle button on the group view Alerts card.
  • Removed role check from group view Location card. All users can now see the Location card on the group page.
  • Updated the documentation link for Location Services.
  • Fixed text overflow for emails in the Invitations card.

In the nRF Cloud API:

  • Fixed permissions error with the GetLocationHistory endpoint.
  • When an invalid NMEA string is passed to the RecordGnssCoordinates endpoint, a status code 422 (Unprocessable Content) is returned instead of 500 (Internal Server Error).
  • The ListFOTAJobs endpoint now returns the correct total when the pageLimit is greater than the number of items returned in the list.
  • Corrected some information in the openapi.json file generated by the https://api.nrfcloud.com/v1/openapi.json URL or the FetchOpenApiSpec endpoint.

In the nRF Cloud APIs and portal:

  • Location anchor names are now limited to 32 characters to ensure devices can handle the anchor name provided to them.

Documentation

  • Corrections and additions to MQTT shadow topics.
  • Added character limit for Wi-Fi anchor names.
  • Changed nrf_cloud_provision.py script name to nrf_cloud_onboard.py.

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