4.2.3

✅ Bug fixes

• Fixed: The return type of convert.toUint8Array() no longer satisfies BufferSource¹

¹) The return type of the function is now Uint8Array<ArrayBuffer> instead of Uint8Array<ArrayBufferLike>.

Other

• Updated dependencies

4.2.2

✅ Bug fixes

• Fixed: Sourcemaps were not part of the NPM package (since version 4.0.0)

Other

• Updated depdencies

4.2.1

✨ Enhancements

Improved handling of reconnection attempts during device interface discovery

It can happen that there are errors thrown while discovering a device's Bluetooth interface, that instruct the user to "Reconnect the device" due to the device's GATT server being reported as disconnected.

When trying to validate this by checking the BluBluetoothRemoteGATTServer.connected status flag, it appears that sometimes, in some browsers, the status flag wrongly reports the device as connected. If that was the case, Blu previously did not attempt to reconnect the device.

Now, BluBluetoothRemoteGATTServer.connect() is called regardless of the status flag's current value.

Documentation

• Improved some TSDoc comments

✅ Bug fixes

• Fixed: Device connection timeout was not respected when it has been reached during the discovery of a device's Bluetooth interface

4.2.0

🚀 Features

Multiple device interface discovery attempts

Blu can now discover a device's Bluetooth interface multiple times in case of an error. This can be useful when a device's interface is not fully discoverable after connecting to it, e.g. due to communication interference or other disruptive factors.

You can define the number of available attempts with the new deviceInterfaceDiscoveryAttempts configuration option. By default, Blu will retry to discover a device's Bluetooth interface once in case of an error.

Additionally, you can control the delay between discovery attempts with the new deviceInterfaceDiscoveryAttemptDelay configuration option. By default, Blu will wait 100 milliseconds between subsequent discovery attempts.

✨ Enhancements

• Improved logging during device connection process

4.1.0

🚨 Breaking changes

• Blu no longer discovers services, characteristics, and descriptors that are not part of the device's described interface by default. To retain this functionality, you need to enable the new deviceInterfaceExtensiveDiscovery configuration option.

🚀 Features

Extensive device interface discovery option

A new configuration option (deviceInterfaceExtensiveDiscovery) has been added to control the discovery of services, characteristics, and descriptors that are not part of the device's described interface.

4.0.0

🚨 Breaking changes

Package

Important

The Blu NPM package is now named blutooth.
It will no longer be available under the former @blu.js/blu name.

API

• Blu's API has been refactored in a lot of places in this new major release.

3.0.3

✨ Enhancements

Advertisement scanning ⚠️

• Polyfilling via BluConfiguration.useBluetoothInterface is now supported
• Added a BluBluetoothAdvertisingEvent interface

BluDeviceAdvertisement

• Added a timestamp property
• device property now always returns a BluBluetoothDevice instead of a device constructed from the BluConfigurationOptions.deviceType

Documentation

• Improved various TSDoc comments

Other

• Updated dependencies

3.0.2

✅ Bug fixes

• Fixed: BluBluetoothState did not add event listeners in some cases when a Web Bluetooth polyfill was registered during runtime

Other

• Updated dependencies

3.0.1

✅ Bug fixes

• Fixed: BluBluetoothState did not update connectedDevices and connectedDevice
• Fixed: BluDevice could dispatch disconnection-related events more than once after connecting and disconnecting more than once

Other

• Updated dependencies

3.0.0

🚨 Breaking changes

API

• Blu's API has been refactored in a lot of places in this new major release.