Version 1.1.0

The built-in catalog now follows the Bluetooth specifications more closely, and scripts get new tools for streams and control points.

Changes since 1.0.1

• Closer to the standards. Every built-in peripheral and composed device was reviewed against its Bluetooth SIG specification, and the differences were corrected: data formats, control points, stored records, and how each one behaves when a central connects, subscribes or leaves.
• Delivery you can see. When a notification or indication cannot be delivered, the session feed says so instead of the value disappearing quietly.
• Stream data and control points in scripts (Pro). Send one message as ordered chunks with notifyChunks, answer just the central that asked with indicate(value, centralId), and mark a characteristic as a control point so the Studio checks and acknowledges each write before your handler runs. Scripts can also declare secondary and included services and static descriptors, and are told when a delivery fails. The JavaScript API page has the details.
• Corrected guides. The JavaScript API, developer guide and BLE protocols reference were checked against the code and the specifications and corrected where they disagreed.

What works differently

• Indoor Bike and Rower no longer include a resistance level in their data, because fitness apps read that field at two different sizes. Setting a resistance target still works.
• Beacon settings are checked more strictly. A value saved in 1.0.1 may need editing before a beacon starts; the message names the field to fix.
• Nordic UART answers a write straight away and sends its echo afterwards, in order.

Known limits

• The corrections were verified in software against the specifications; this is not a Bluetooth SIG certification, and real fitness and health apps can still differ in what they accept.
• The Remote Script Editor is unencrypted and is for trusted networks only.