• State Verified Answer
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 397 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 322111
Options

Resetted Node is still in the provisioned list after reset NRF Mesh Android App

Kamrans124

After Clicking on Reset then i wait for 2-3 seconds. The node gets reset and is unprovisioned, but it still shows in the android nrf app in the provisioned list. This Happend sometimes not every time when I reset. Normally after clicking on reset it unprovisioned and then removed from the android nrf app provisioned list.

Parents
  • +1

    Hi,

    If you reset the node, but the nRF Mesh app does not get confirmation of the reset, then you may end up in a situation where the node itself is reset, but the nRF Mesh app does not know (and therefore keeps the node in the database of current nodes.) This is related to the Two Generals' Problem; you cannot 100 % confirm an action in both ends, if there is a chance of packet loss.

    In this case: The node reset message is sent from the nRF Mesh app, received by the device and confirmed, but the confirmation is not received by the nRF Mesh app. The nRF Mesh app then doesn't know if the missing confirmation is due to the original message not reaching the node (in which case the node will not reset, but rather continuing communicating on the network) or if it is due to the confirmation getting lost (in which case the node will leave the network.) The safest action then, is to assume the node is still part of the network (and not remove it from the database.)

    In order to force remove the node from the network (either because it has been reset, otherwise lost, or you want to kick it out of the network,) in the nRF Mesh app you can swipe the node to either side. You will then be asked to confirm removing the node from the network.

    Please note that the unicast address of the node will not be reused before the network has been through two IV Updates. This is to avoid problems with there being two nodes using the same unicast address on the network. (The node isn't completely forced out of the network before the IV Index has increased by two.)

    Regards,
    Terje

Reply
  • +1

    Hi,

    If you reset the node, but the nRF Mesh app does not get confirmation of the reset, then you may end up in a situation where the node itself is reset, but the nRF Mesh app does not know (and therefore keeps the node in the database of current nodes.) This is related to the Two Generals' Problem; you cannot 100 % confirm an action in both ends, if there is a chance of packet loss.

    In this case: The node reset message is sent from the nRF Mesh app, received by the device and confirmed, but the confirmation is not received by the nRF Mesh app. The nRF Mesh app then doesn't know if the missing confirmation is due to the original message not reaching the node (in which case the node will not reset, but rather continuing communicating on the network) or if it is due to the confirmation getting lost (in which case the node will leave the network.) The safest action then, is to assume the node is still part of the network (and not remove it from the database.)

    In order to force remove the node from the network (either because it has been reset, otherwise lost, or you want to kick it out of the network,) in the nRF Mesh app you can swipe the node to either side. You will then be asked to confirm removing the node from the network.

    Please note that the unicast address of the node will not be reused before the network has been through two IV Updates. This is to avoid problems with there being two nodes using the same unicast address on the network. (The node isn't completely forced out of the network before the IV Index has increased by two.)

    Regards,
    Terje

Children
No Data
Related
Terms of service