Skip to content

nRF Mesh v2.2.0

Compare
Choose a tag to compare
@roshanrajaratnam roshanrajaratnam released this 30 Apr 08:18
0e691c3

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.