Adding functionality to the Nordic Thingy Mesh Demo; enabling nodes to send to each other.

[Jan]

Hi all,

I'm currently working on adapting this example to fit my needs for testing a Bluetooth Mesh network. 

I want to add the functionality for nodes to send to each other (in the example, only the bridge can send to nodes).

I want the nodes to send to a hardcoded address from the other nodes without an acknowledge. I am wondering if I need a new model for this functionality. 

I have tried a few things but I keep getting errors from the underlying libraries so I could use some pointers on what steps to take in order to achieve this. 

Many thanks in advance!

Jan

[Mttrinh]

Hi,

You will need to make the nodes publish to other nodes using unicast address(hardcoded address). You should send unreliable messages if you don't want acknowledgement.

Have you looked at the light switch client/server examples?

[Mttrinh]

You would need a model for each node you want to send to. Unless you want to send the same message to many nodes, then you can just use a group address. While using group address you won't get an ACK either.

[Jan]

So if I want 30 nodes who all need to be able to send to each other. The provisioner needs to provision all of these 30 x 30 models? 

Is there a way to have a single model for each node in which can be sent to a hardcoded address?

[Mttrinh]

You will need to provision each node/device once, but need to configurate 30 models for each node.

Jan said:

Is there a way to have a single model for each node in which can be sent to a hardcoded address?

If I understood this question correctly, you are asking if it is possible to have a 30 models in one node, and each model can send to a hardcoded address? Yes, it should be possible. 

Can you give me more details about your use-case, perhaps there is other solutions?

[Jan]

Hi,

I'm building this mesh network for my graduation internship with which I can test the throughput for different configurations and network sizes. 

Therefore, a laptop will configure the nodes to send to one of the other nodes via the proxy/bride nodes once the nodes receive the "start test" command. Ideally, I would like the configure method to simple have one address which the node can store and simply send to. Because of the fact that a lot of different test cases need to be done. It would be ideal if the address to send to can be easily adapted by a configure method from the proxy. 

I hope this will shed some light on my goal, any tips are very welcome. 

Best regards, 

Jan 

[Jan]

Hi,

I managed to get it working. All the nodes can be configured to send to one of the other nodes with just one model. I don't know if I am doing everything the "official" way but this working version is fine for my testing purposes!

Thanks for your insight!