nRF Mesh v2.3.0

This version brings the following changes

• Adds dark theme support which will depend on the Android theme settings.

nRF Mesh v2.2.0

This release brings the following changes.

• Removes the duplicate sequence number field in the provisioner table.

  • If needed to change the sequence number of a provisioner, select the provisioner node from the nodes list using the provisionerUuid and use node.setSequenceNumber(sequenceNumber)
• • Fixes #293 - Improvements to how the Vendor model opcode is constructed. Now the ser may or or may not enter the opcode in the UI with the 3-octet opcode bits set. This is to make both implementations look similar to a certain extent.

• Fixes #287 by improving how the opcode is being parsed.

• Fixes #301

• Fixes #244 IV Index related Improvements:

  • IV Index and IV Update state has been merged in to an object that contains all iv related properties.
  • IV Index updates fixed. The library will now handle the Secure Network beacon with isIvUpdateActive flag set or high IV Index. The spec-defined time requirements are checked, so at least 96h need to pass in IV Index Normal Operation state and at least 96h in IV Index Update In Progress. The node will not execute more than one IV Index Recovery within a period of 192 hours.
  • IV Index Test Mode added: see MeshManagerApi.isIvUpdateTestModeActive flag.
  • A flag to disable limit of 42 when doing IV Recovery. This allows to connect to a network after IV Index changed by more than 42, which can happen at least in 48 weeks since last connection.

  Note I: The IV Index changes only when a Secure Network beacon is received. This happens usually when you connect to a Proxy Node, but the Proxy may also relay a SNB sent by another Node.
  Note II: To test IV Index Update enabled IV Test Mode. A switch has been added to Settings screen in the sample app. Test Mode allows you to transition IV Index by 1, or change the IV Index Update flag from true to false without the need to wait 96h. It will, however, not allow to transition to higher IV Index without passing the min-time requirement.
  Note III: The library will not send Secure Network beacons. It fully relies on other Nodes to initiate the process of updating IV Index. In most applications it will not be a case, as other nodes will reach half sequence number before the app, unless it's constantly connected to the network and sends messages in a loop, which doesn't seem to be probable scenario.

nRF Mesh v2.1.4

This release introduces the following changes

• Scanning started in loop when observing live data
• Additional checks for Network ID and Node Identity beacons
• Improved logging for handling secure network beacon length errors

nRF Mesh v2.1.3

This version introduces the following changes

• Set MTU to default value of 23 upon disconnectoin. This is a work around to avoid BLE Library v2.1.1 not resetting the MTU value for the same Ble library instance upon disconnection.

nRF Mesh v2.1.2

This version introduces the following changes

• Fixes a bug causing the maximum packet size to be calculated incorrectly this was introduced while migrating to BLE Library 2.1.1.
• Validate provisionee public key length during provisioning process.

nRF Mesh v2.1.1

This release brings the following changes

• Example firmwares updated.
• Request fine location instead of coarse location as mention in Android documentation.
• Migrated to Ble Library 2.1.1
• Fixes issue 270.
• Set default sequence number received for a node to -1. This fixed where the first segment received from a newly provisioned node to be not discarded.

nRF Mesh v2.1.0

This release brings the following changes.

• Fixes #258, #260 and this was happenning due to an incorrect validation of Unicast Address which is
• Fixes #257
• Fixes #262, the library does not use TAI anymore.
• Fixes #254
• Fixes #245
• Fixes some UI inconsistencies in the group controls activity

nRF Mesh v2.0.5

• Fixes an issue causing the Network import/export to fail in Android 10. Please note exporting to json will return a String json which must be handled on the application level in order to save to a file.

nRF Mesh v2.0.4

Issues Fixed

• Invalid timeout message being displayed for unacknowledged vendor model messages
• Vendor model messages getting sent twice unintentionally

nRF Mesh v2.0.3

• Improvements to the scanner, when enabling/disabling bluetooth
• Fixes an issue causing editing network/application keys to be not reflected properly. P.S. Any network key, application key that is in use can be changed except for the key name.
• Fixes parcelable implemenation for PublicationSettings and Groups