Device OS 3.0.0-rc.2 is the second release candidate on non-LTS feature development branch (3.x). To learn more about our new LTS release line, read our blog post.
Note: This is a Release Candidate and is not intended for production yet.
You can view information about Device OS versions, upgrades and downgrades here.
3.0.0-rc.2
Highlights
[Cellular] Battery presence detection when charging is disabled
Increased maximum payload sizes for cloud primitives (publishes, variables, functions)
Improved cold and warm boot behavior on B5 SoMs and Trackers
This is a release candidate (RC) on non-LTS feature development branch (3.x). To learn more about our new LTS release line, read our blog post.
Note: This is a Release Candidate and is not intended for production yet.
You can view information about Device OS versions, upgrades and downgrades here.
3.1.0-rc.1
Highlights
[Gen 3] (Argon, Boron, B SoM, B5 SoM, Tracker) maximum application size has been increased from 128KB to 256KB#2322. A few important aspects of this change:
Compatibility with 128KB applications built with < Device OS 3.1 versions is maintained. Devices can still run them even if other parts have been upgraded to Device OS 3.1+.
Upgrade process OTA (including product-based upgrades) is transparent.
When upgrading locally (using DFU or Serial), make sure to update the bootloader first, as it has some logic managing compatibility between 128KB and 256KB application types. See this page on steps how to perform the update.
If using standalone Particle CLI installation, make sure it’s updated to >= 2.12.0 version, which includes support for 256KB applications.
A compiler will trigger an error when a function does not return a value, but was declared with a non-void return type #2323
This is a release on non-LTS feature development branch (3.x). To learn more about our new LTS release line, read our blog post.
Note: This is a Release and may be used for production.
You can view information about Device OS versions, upgrades and downgrades here.
3.1.0
Highlights
[Gen 3] (Argon, Boron, B SoM, B5 SoM, Tracker) maximum application size has been increased from 128KB to 256KB#2322. A few important aspects of this change:
Compatibility with 128KB applications built with < Device OS 3.1 versions is maintained. Devices can still run them even if other parts have been upgraded to Device OS 3.1+.
Upgrade process OTA (including product-based upgrades) is transparent.
When upgrading locally (using DFU or Serial), make sure to update the bootloader first, as it has some logic managing compatibility between 128KB and 256KB application types. See this page on steps how to perform the update.
If using standalone Particle CLI installation, make sure it’s updated to >= 2.12.0 version, which includes support for 256KB applications.
A compiler will trigger an error when a function does not return a value, but was declared with a non-void return type #2323
This is the second Release Candidate for the upcoming Device OS release 2.2.0 (LTS) with critical bugfixes and backports from 3.x release line.
To learn more about LTS release line, read our blog post.
You can view information about Device OS versions, upgrades and downgrades here.
2.2.0-rc.2
Highlights
This Release Candidate contains a set of critical bugfixes and backports from 3.x release line
DTLS session is not cleared on socket errors (e.g. caused by cellular network deregistration), reducing network data required to re-established cloud connection #2335#2337
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
[Boron / B SoM / Electron] SARA R410 05.12 modem firmware support #2317#2319#2318
A compiler will trigger an error when a function does not return a value, but was declared with a non-void return type #2323
DTLS session is not cleared on socket errors (e.g. caused by cellular network deregistration), reducing network data required to re-established cloud connection #2335#2337
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
[Gen 3] BLE: extended advertisement support with Coded PHY #2331
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
[Gen 3] BLE: extended advertisement support with Coded PHY #2331
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
Note: This is a Beta Pre-Release for testing only. API’s may change before a Release Candidate is created.
This is the first Device OS Release in the 4.x LTS line, based on new Feature/Enhancements/Bugfixes and Breaking Changes from the 3.x release line.
Note: If you are upgrading from 2.x, please review the changelogs highlights for 3.0.0/3.1.0/3.2.0/3.3.0 below.
Note: Critical Bugfixes from 3.x will already be backported in the latest 2.3.0, and some other Bugfixes may only apply to previous 3.x releases. Internal changes are omitted in the 3.x changelog list below, however the full changelog may be found at the Device OS repo.
To learn more about LTS release line, read our blog post.
You can view information about Device OS versions, upgrades and downgrades here.
4.0.0-beta.1
Breaking changes
Deprecate/remove the PRODUCT_ID macro #2446. Users may now use the same binary for multiple Products that share the same device Platform and Functionality. Including this macro will cause a build error and show the following message:
The PRODUCT_ID macro must be removed from your firmware source code.
The same compiled firmware binary may be used in multiple products that share the same platform and functionality.
[Gen 3] BLE: extended advertisement support with Coded PHY #2331
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
[Gen 3] HAL - Only skip modules that fail integrity check from module info #2387
3.1.0
Highlights
[Gen 3] (Argon, Boron, B SoM, B5 SoM, Tracker) maximum application size has been increased from 128KB to 256KB#2322. A few important aspects of this change:
Compatibility with 128KB applications built with < Device OS 3.1 versions is maintained. Devices can still run them even if other parts have been upgraded to Device OS 3.1+.
Upgrade process OTA (including product-based upgrades) is transparent.
When upgrading locally (using DFU or Serial), make sure to update the bootloader first, as it has some logic managing compatibility between 128KB and 256KB application types. See this page on steps how to perform the update.
If using standalone Particle CLI installation, make sure it’s updated to >= 2.12.0 version, which includes support for 256KB applications.
A compiler will trigger an error when a function does not return a value, but was declared with a non-void return type #2323
Note: This is a Release and may be used for production.
This is the first Device OS Release in the 4.x LTS line, based on new Feature/Enhancements/Bugfixes and Breaking Changes from the 3.x release line.
Note: If you are upgrading from 2.x, please review the changelogs highlights for 3.0.0/3.1.0/3.2.0/3.3.0 below.
Note: Critical Bugfixes from 3.x will have already been backported in the latest 2.3.0, and some other Bugfixes may only apply to previous 3.x releases. Internal changes are omitted in the 3.x changelog list below, however the full changelog may be found at the Device OS repo.
To learn more about LTS release line, read our blog post.
You can view information about Device OS versions, upgrades and downgrades here.
4.0.0
Breaking changes
Deprecate/remove the PRODUCT_ID macro #2446. Users may now use the same binary for multiple Products that share the same device Platform and Functionality. Including this macro will cause a build error and show the following message:
The PRODUCT_ID macro must be removed from your firmware source code.
The same compiled firmware binary may be used in multiple products that share the same platform and functionality.
[Gen 3] BLE: extended advertisement support with Coded PHY #2331
[Argon / Tracker] Avoid power leakage through ESP32 ESPBOOT pin #2342
Fixes parsing of JSON strings with more than 127 tokens #2348
Reset scheduled module updates performed by the bootloader in case a second OTA update happens before they are applied (e.g. if System.disableReset() is used to postpone a pending device reset) #2346
[Gen 3] HAL - Only skip modules that fail integrity check from module info #2387
3.1.0
Highlights
[Gen 3] (Argon, Boron, B SoM, B5 SoM, Tracker) maximum application size has been increased from 128KB to 256KB#2322. A few important aspects of this change:
Compatibility with 128KB applications built with < Device OS 3.1 versions is maintained. Devices can still run them even if other parts have been upgraded to Device OS 3.1+.
Upgrade process OTA (including product-based upgrades) is transparent.
When upgrading locally (using DFU or Serial), make sure to update the bootloader first, as it has some logic managing compatibility between 128KB and 256KB application types. See this page on steps how to perform the update.
If using standalone Particle CLI installation, make sure it’s updated to >= 2.12.0 version, which includes support for 256KB applications.
A compiler will trigger an error when a function does not return a value, but was declared with a non-void return type #2323
Be sure to read the full collection of release notes Particle Device OS Updates Thread.
Be sure to read the full collection of release notes 
Be sure to read the full collection of release notes