Bluetooth ® Mesh SDK 8.1.0.0 GA Simplicity SDK Suite 2024.12.3
August 6, 2025
Bluetooth Mesh is a new topology available for Bluetooth Low Energy (LE) devices that enables many-to-many (m:m) communication. It's optimized for creating large-scale device networks, and is ideally suited for building automation, sensor networks, and asset tracking. Silicon Labs' software and SDK for Bluetooth development supports Bluetooth Mesh and Bluetooth functionality. Developers can add mesh networking communication to LE devices such as connected lights, home automation, and asset tracking systems. The software also supports Bluetooth beaconing, beacon scanning, and GATT connections so Bluetooth Mesh can connect to smart phones, tablets, and other Bluetooth LE devices.
This release includes features supported by the Bluetooth Mesh specification version 1.1.
These release notes cover SDK versions:
- 8.1.0.0 released August 6, 2025
- 8.0.2.0 released April 1, 2025
- 8.0.1.0 released February 5, 2025
- 8.0.0.0 released December 16, 2024
Bluetooth
KEY FEATURES
- Support added for Micrium and FreeRTOS.
- Bug fixes and minor enhancements.
Compatibility and Use Notices
For more information about security updates and notices, see the Security chapter of the Platform Release Notes installed with this SDK or on the Silicon Labs Release Notes page. Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Silicon Labs Bluetooth Mesh SDK, see Using This Release.
Compatible Compilers:
IAR Embedded Workbench for ARM (IAR-EWARM) version 9.40.1
- Using wine to build with the IARBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result in incorrect files being used due to collisions in wine's hashing algorithm for generating short file names.
- Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefully verify that the correct files are being used.
GCC (The GNU Compiler Collection) version 12.2.1, provided with Simplicity Studio.
- Link-time optimization feature of GCC has been disabled, resulting in a slight increase of image size.
1 New Items
1.1 New Features
Added in release 8.0.0.0
New examples:
- Support for RTOS (Micrium and FreeRTOS) has been added for several examples.
- Micrium and FreeRTOS variants were made for the following applications:
- btmesh_ncp_empty
- btmesh_soc_empty
- btmesh_soc_nlc_basic_scene_selector
- btmesh_soc_nlc_dimming_control
- btmesh_soc_switch_ctl
- FreeRTOS variant was made for the following applications:
- btmesh_soc_nlc_sensor_ambient_light
- btmesh_soc_nlc_sensor_occupancy
- btmesh_soc_sensor_client
- btmesh_soc_sensor_thermometer
Note that Device Firmware update is not yet supported in RTOS variant applications.
New components:
btmesh_solicitation_config_client: A component was added for Proxy Service Solicitation.App_rtaandApp_btmesh_rta: Application runtime adaptor layer for bare metal and RTOS related services.Btmesh_lcd_server: A component for Large Composition Data Models Metadata Page 0 generation.
Other new features:
- Models Metadata Page 0 is supported and automatically generated for the examples.
App_button_presssupports software debouncing.- Mesh Configurator tool supports generating Composition Data Page 1 and Page 2 for Vendor Models.
- Network Analyzer tool supports Bluetooth Mesh 1.1 specification.
1.2 New APIs
Added in release 8.1.0.0
- Added APIs to provide control over BLOB transfer and DFU model message sending rate:
sl_btmesh_fw_dist_server_configure_throttle,sl_btmesh_fw_standalone_updater_configure_throttle, andsl_btmesh_mbt_client_configure_throttle. - Added APIs to provide a new way of handling BLOB transfer block start:
sl_btmesh_mbt_server_enable_block_start_req, andsl_btmesh_mbt_server_block_start_rsp.
Added in release 8.0.0.0
Changes in application components:
Sli_sensor_server_cadence.cwas renamed toSl_sensor_server_cadence.c.
2 Improvements
Changed in release 8.0.0.0
API documentation for OOB authentication data handling on provisioner and provisionee has been corrected and clarified.
3 Fixed Issues
Fixed in release 8.1.0.0
| ID # | Description |
| 1406862 | Fixed an unintended deactivation of LC mode when entering standby mode. |
| 1413864, 1425025, 1451316, 1452212, 1452213 | Multiple fixes and improvements to make Firmware Update model operation more robust in a high-load environment. |
| 1427300 | Corrected Mesh BLOB Transfer Server model pull mode transfers completion. |
| 1434214 | DFU distributor server message sending corrected to handle all values of SL_BTMESH_CONFIG_APP_TXQ_SIZE correctly. |
| 1439194, 1453067, 1453189 | Fixed a number of issues in lighting and generic model state updates stemming from using generic level move operation. |
| 1449114 | Corrected minor issues in Configuration Client BGAPI: - Now uses the intended network key specified by enc_netkey_index to transmit sl_btmesh_config_client_get_model_pub() request; - Does not allow removing the network key used to transmit sl_btmesh_client_remove_netkey() request, as a response would not be sent after the removal; - Corrected publication retransmission reporting. |
| 1451726 | Fixed a problem in restoring generic model state on power up. |
| 1455257 | Returned at most 255 bytes of statistics data even if more are requested by application. |
| 1456429 | Fixed issues with migrating an embedded provisioner from SDK version 1.x. |
| 1470416, 1473472 | Corrected issues related to Mesh BLOB Transfer Server model timeout and state transition handling. |
| 1470419, 1470424 | Fixed issues with Mesh BLOB Transfer models and application communication, as well as with Device Firmware Update models and application communication; unreliable event to the application caused issues in high load conditions. |
Fixed in release 8.0.2.0
| ID # | Description |
| 1418409, 1151586 | Fixed a number of test BGAPI commands that were not working on provisioner because of a flawed system state check; also fixed sl_btmesh_lpn_init and sl_btmesh_node_get_rssi that were failing on provisioner for the same reason. |
| 1417649 | Fixed an issue with segmented messages transmitted over local loopback. |
| 1401801 | Fixed Scene Server model initialization when the server was on something other than the primary element. |
Fixed in release 8.0.1.0
| ID # | Description |
| 1285133 | Fixed a problem in Friend acknowledging segmented data it received directly from its LPN. |
Fixed in release 8.0.0.0
| ID # | Description |
| 348529 | Replay protection checks to discard messages were too strict for a corner case related to segments arriving out of order. |
| 1337570 | Fixed a potential null pointer reference in DFU Client model. |
| 1339163 | Removed stale outgoing advertisements from Tx queue to help manage overload situations. |
| 1345085, 1345650 | Fixed synchronization and thread safety issues with BGAPI command and event handling when RTOS is in use. |
| 1356050 | Improved the previous fix by eliminating unnecessary GATT service setup operations that could potentially fail. |
| 1378339 | Fixed a periodic task running issue that affected embedded provisioners with GATT functionality. |
| 1378639 | Fixed DFU Standalone Updater deinitialization sequence. |
4 Known Issues in the Current Release
Issues in bold were added since the previous release.
| ID # | Description | Workaround |
| 401550 | No BGAPI event for segmented message handling failure. | Application needs to deduce failure from timeout / lack of application layer response; for vendor models an API has been provided. |
| 454059 | A large number of key refresh state change events are generated at the end of KR process, and that may flood NCP queue. | Increase NCP queue length in the project. |
| 454061 | Slight performance degradation compared to 1.5 in round-trip latency tests was observed. | |
| 624514 | Issue with re-establishing connectable advertising if all connections have been active and GATT proxy is in use. | Allocate one more connection than is needed. |
| 841360 | Poor performance of segmented message transmission over GATT bearer. | Ensure that the underlying BLE connection's Connection interval is short; ensure that ATT MTU is large enough to fit a full Mesh PDU; tune the minimum connection event length to allow multiple LL packets to be transmitted per connection event. |
| 1121605 | Rounding errors may cause scheduled events to trigger at very slightly different times than expected. | Restart the host provisioner app before provisioning the second node. |
| 1226127 | Host provisioner example can be stuck when it starts to provision a second node. | Don't run self FW update and FW upload in parallel. |
| 1204017 | Distributor is not able to handle parallel self FW Update and FW Upload. | |
| 1412121 | Currently, only one Scheduler Server model is permitted, and it has to be located on the primary element. |
5 Deprecated Items
Deprecated in release 8.0.0.0
None.
6 Removed Items
Removed in release 8.0.0.0
None.
7 Using This Release
This release contains the following:
- Silicon Labs Bluetooth Mesh stack library
- Bluetooth Mesh sample applications
If you are a first-time user, see QSG176: Silicon Labs Bluetooth Mesh SDK v2.x Quick-Start Guide.
7.1 Installation and Use
The Bluetooth Mesh SDK is provided as part of the Simplicity SDK (GSDK), the suite of Silicon Labs SDKs. To quickly get started with the Simplicity SDK, install Simplicity Studio 5, which will set up your development environment and walk you through Simplicity SDK installation. Simplicity Studio 5 includes everything needed for IoT product development with Silicon Labs devices, including a resource and project launcher, software configuration tools, full IDE with GNU toolchain, and analysis tools. Installation instructions are provided in the online Simplicity Studio 5 User's Guide.
Alternatively, Simplicity SDK may be installed manually by downloading or cloning the latest from GitHub. See https://github.com/SiliconLabs/simplicity_sdk for more information.
Simplicity Studio installs the Simplicity SDK by default in:
- Windows: C:\Users\<NAME>\SimplicityStudio\SDKs\simplicity_sdk
- MacOS: /Users/<NAME>/SimplicityStudio/SDKs/simplicity_sdk
Documentation specific to the SDK version is installed with the SDK. Additional information can often be found in the knowledge base articles (KBAs). API references and other information about this and earlier releases is available on https://docs.silabs.com/.
7.2 Security Information
Secure Vault Integration
This version of the stack is integrated with Secure Vault Key Management. When deployed to Secure Vault High devices, mesh encryption keys are protected using the Secure Vault Key Management functionality. The table below shows the protected keys and their storage protection characteristics.
| Key | Exportability on a node | Exportability on Provisioner | Notes |
| Network key | Exportable | Exportable | Derivations of the network key exist only in RAM while network keys are stored on flash |
| Application key | Non-exportable | Exportable | |
| Device key | Non-exportable | Exportable | In Provisioner's case, applied to Provisioner's own device key as well as other devices' keys |
Keys that are marked as "Non-exportable" can be used but cannot be viewed or shared at runtime. Keys that are marked as "Exportable" can be used or shared at runtime but remain encrypted while stored in flash.
For more information on Secure Vault Key Management functionality, see AN1271: Secure Key Storage.
Security Advisories
To subscribe to Security Advisories, log in to the Silicon Labs customer portal, then select Account Home. Click HOME to go to the portal home page and then click the Manage Notifications tile. Make sure that 'Software/Security Advisory Notices & Product Change Notices (PCNs)' is checked, and that you are subscribed at minimum for your platform and protocol. Click Save to save any changes.
7.3 Support
Development Kit customers are eligible for training and technical support. Use the Silicon Labs Bluetooth Mesh web page to obtain information about all Silicon Labs Bluetooth products and services, and to sign up for product support.
Contact Silicon Laboratories support at http://www.silabs.com/support.
7.4 SDK Release and Maintenance Policy
For details, see SDK Release and Maintenance Policy.
Simplicity Studio
One-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!
Disclaimer
Silicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the information supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications.
Trademark Information
Silicon Laboratories Inc. ®, Silicon Laboratories ®, Silicon Labs ®, SiLabs ® and the Silicon Labs logo ®, Bluegiga ®, Bluegiga Logo ®, EFM ®, EFM32 ®, EFR, Ember ®, Energy Micro, Energy Micro logo and combinations thereof, "the world's most energy friendly microcontrollers", Redpine Signals ®, WiSeConnect, n-Link, EZLink ®, EZRadio ®, EZRadioPRO ®, Gecko ®, Gecko OS, Gecko OS Studio, Precision32 ®, Simplicity Studio ®, Telegesis, the Telegesis Logo ®, USBXpress ®, Zentri, the Zentri logo and Zentri DMS, Z-Wave ®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.
