Ratio between Bluetooth Mesh server and clients?

[SørenHN]

When making a bluetooth mesh network, what is a good rule of thump for the ratio between servers and clients?

I am thinking of implementing the server-client-model scheme seen on this figure:

The arrows denote message direction. Status messages, obviously, moves the opposite direction.

Does it make sense to have one B server for handling messages from all the B clients? Or should i have one server for each client?

Is it possible to have one A client for all the A servers instead of one for each?

And are there any disadvantages with either design?

[ketil]

Hi,

It is difficult to answer your questions without knowing more about the application you are building since Bluetooth Mesh is very flexible.

You could however build it the way you have specified in your diagram by setting the middle node as a Control model. More information is available in the Mesh Profile Specification 1.0 Section 2.3.6 Models.

If you feel there is anything confidential about your application you could create a My Page account and ask your question there.

Ketil

[SørenHN]

Hi Ketil, thank you for the answer. I think that I will stick with the design on the diagram, but it is nice to know that Bluetooth Mesh flexible. I don't think it would be beneficial to combine the A clients and B server in to one controller, as their responsibility does not overlap and in the future, they might not be in the same device.

But if I were to combine them into a controller, how would i go about that? Is there an example somewhere I could look at?

I was not aware that I could ask confidential questions on the "My Page"-page, so thank you for that also.

[ketil]

We currently do not have an example of a Control Model. You can make one yourself by combining Server and Client Models. If/when we make an example I will try to remember this case and let you know.