• State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 69 subscribers
  • Views 2760 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 233202
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Mesh not finding proxy node

bluetooth_mdw

Hi

I have a test mesh network, with several devices provisioned using nRF Mesh and.... a proxy node which has been provisioned using an alternative method but with the same netkey, appkey and so on as the other nodes. In other words it is part of the same mesh network, albeit not listed in the nRF Mesh provisioning database. nRF Mesh cannot find the proxy to connect to it though. It is advertising using network identity, so I think that should be sufficient to identify it as a proxy which belongs to this network. Does nRF Mesh ignore nodes which are not in its database though, maybe using the BD_ADDR?

nRF Connect can see the node fine:

Any ideas why I can't use this proxy from nRF Mesh?

Thanks

Martin

Parents
  • 0

    Hi Martin,

    It's highly unlikely that it's not found if the net key are the same. Could you check if the network id values match  with another node in the network? You can do this with nRF Connect. 

    nRF Mesh does not filter out devices that's not in the database. Let us know how it goes.

  • 0 in reply to Roshan Rajaratnam

    Hi Aleksander and Roshan,

    apologies for the time it's taken me to respond.... my excuse is called "vacation" :-)

    Thanks for the information you've provided. That's very helpful in itself. Now... you're going to think I'm a little mad (which is fine by me) but nRF Mesh is not showing the network key value I was expecting it to. And...I have a network of 49 nodes and 33 of them were provisioned by hard coding keys in their source. The binaries in those devices have not changed in a long time either (months), so I am 100% confident of the keys they are using. 16 of my devices were provisioned using nRF Mesh. All of the nodes except one are servers and subscribe to the same group address. All these server nodes respond to client messages sent by the 49th device (a generic on/off client), which should prove that they are all using the same network and application keys. I ran my last set of tests involving this network only about a week ago, so I am certain of this.

    I also have a backup of the provisioning schema from about a week ago. This has the expected network key value in it (I won't repro it here). However, if I look in the Network settings of nRF Mesh, I see a different value. I haven't recreated my network in the last week so this is a puzzle.

    The most likely explanation for all of this is, of course..... user error. And if those 16 devices I provisioned with nRF mesh were not responding to the messages sent by my test client, with its hard coded netkey and appkey, I would conclude that this was the case. But.... the whole network functions as expected. So... it's weird. And..probably still user error! But... is there any possibility the app could corrupt network key values somehow? An unlikely long-shot, I know.

    If I find myself doing any more mesh testing work in the near future, I'll perhaps start again and RESET in nRF Mesh and then re-provision those 16 devices, test and generally keep an eye on whatever's going on.

    Again, thanks for the response.

    Martin

Reply
  • 0 in reply to Roshan Rajaratnam

    Hi Aleksander and Roshan,

    apologies for the time it's taken me to respond.... my excuse is called "vacation" :-)

    Thanks for the information you've provided. That's very helpful in itself. Now... you're going to think I'm a little mad (which is fine by me) but nRF Mesh is not showing the network key value I was expecting it to. And...I have a network of 49 nodes and 33 of them were provisioned by hard coding keys in their source. The binaries in those devices have not changed in a long time either (months), so I am 100% confident of the keys they are using. 16 of my devices were provisioned using nRF Mesh. All of the nodes except one are servers and subscribe to the same group address. All these server nodes respond to client messages sent by the 49th device (a generic on/off client), which should prove that they are all using the same network and application keys. I ran my last set of tests involving this network only about a week ago, so I am certain of this.

    I also have a backup of the provisioning schema from about a week ago. This has the expected network key value in it (I won't repro it here). However, if I look in the Network settings of nRF Mesh, I see a different value. I haven't recreated my network in the last week so this is a puzzle.

    The most likely explanation for all of this is, of course..... user error. And if those 16 devices I provisioned with nRF mesh were not responding to the messages sent by my test client, with its hard coded netkey and appkey, I would conclude that this was the case. But.... the whole network functions as expected. So... it's weird. And..probably still user error! But... is there any possibility the app could corrupt network key values somehow? An unlikely long-shot, I know.

    If I find myself doing any more mesh testing work in the near future, I'll perhaps start again and RESET in nRF Mesh and then re-provision those 16 devices, test and generally keep an eye on whatever's going on.

    Again, thanks for the response.

    Martin

Children
Related