Android NRF Mesh Library Versions Save

The Bluetooth Mesh Provisioner and Configurator library.

v3.1.7

2 years ago

What's Changed

This release includes the following changes.

  • Fixes #432
  • Fixes #438
  • Fixes #441
  • #448 Adds support for Scheduler, Generic Transition time, PowerUpBehaviour, GenericProperties (Admin, User, Manufacturer) and Time Messages
  • #456 maintains consistency.
  • Fixes #457
  • Fixes #458, where the provisioner's sequence number seems to get reset when sending a message to 0xFF
  • Fixes #461 and fixes #462 that was causing the app/library to crash when de-obfuscating a received message.
  • #464 adds support for Android 12 BLUETOOTH_SCAN, BLUETOOTH_CONNECT permissions and splash screen. The app now includes the neverForLocation flag for Android S and onwards.
  • Fixes #466
  • #470 fixes #469
  • Fixes #471
  • #474 Fixes #473
  • #475 adds support for Energy32, Power and Electric Current characteristics.
  • #476
  • Library improvements
  • Deleting a network key that is bound to an application should not be allowed. Before deleting a network key, the user must unbind the application key from the network key or delete that application key bound to it.
  • Sample app improvements
    • Migrate to ActivityResultContract.
    • Migrate to AsyncListDIffer and ListAdapter in the adapter implementations.
    • Display the last modified date in the app based on the user's default time zone.
    • Add the mime type of the JSON file for ActivityResultContracts.CreateDocument()

New Contributors

Thank you for all your contributions.

Full Changelog: https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/compare/v3.1.6...v3.1.7

v3.1.6

2 years ago

This release brings the following changes

  • Specify the address of the element instead of the node address when sending message from the SensorServerActivity.java
  • Fixes #423, #418, #333 related to database migration
  • Fixes #354 an invalid GATT level segmentation issue. The lib was considering the MTU size instead of the SAR bits in the proxy PDU
  • Fixes #427, #406 where segmented messages to be retransmitted being get cleared. This should improve the retransmissions
  • Fixes #433 where the app was crashing on Android 6.0 devices due incorrect time stamp formatting.
  • Migrates from JCenter to MavenCentral and other improvements.

v3.1.5

3 years ago

This release introduces the following changes.

  • Fixes #416 where scenes that are listed not displayed correctly. This most probably broke when migrating from ButterKnife.
  • Cleans up a few deprecated functionality from the mesh library.

v3.1.4

3 years ago
  • This release brings the following changes
    • Fixes a crash when selecting to create a group address. This was introduced in version 3.0 when migrating from ButterKnife to viewBinding

v3.1.3

3 years ago

This release brings the following changes

  • Fixes version formatting on network json and some minor improvements.
  • Update network timestamp when editing the network.
  • Fix timestamp parsing when importing a mesh network.
  • Fix scene number parsing when importing a mesh network.
  • Disable deleting a scene that's already in use and only scene names should be editable.
  • Fixes a crash related to missing @HiltViewModel annotation.

v3.1.2

3 years ago
  • This release brings the following changes.
    • Fixes a crash in the app when invalid Marshalled Sensor Data is received via the SensorStatus message.
    • Improvements to dependency injection using Hilt.

v3.1.1

3 years ago
  • This release brings the following changes
    • Fixes #406: Related to broken block acknowledgements in the Lower Transport Layer.
    • Fixes #407 : Adds a check to confirm the old identity key is not null as a Key Refresh Procedure may have not taken place causing the old identity key to be null.

v3.1.0

3 years ago
  • This release brings the following changes
    • Adds support for sensor messages and 68/179 device properties.
    • Adds support for all Light LC messages.

v3.0.3

3 years ago

This release brings the following changes.

  • Fixes issue #400.

v3.0.2

3 years ago
  • This release brings the following changes.
    • Feature #395 which allows re-importing an existing network and continue sending messages from the last known sequence number stored in the DB. This should allow users to re-use already stored network information and start sending messages without having to change a provisioner address on the same device. Closes #371.
    • #396
    • #397