This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth Mesh Broadcast Package

The version used is nrf5_SDK_for_Mesh_v5.0.0_src.

nrf5_SDK_for_Mesh_v5.0.0_src\examples\light_switch\server.

Question 1: I want to turn off mesh broadcasting first, and then restart mesh broadcasting. How do I do this?
Question 2: The mesh broadcast has started, can I change the broadcast content?

Parents
  • Hi,

    I am not quite sure if I understand the use case here. The term "mesh broadcasting" is not defined in Bluetooth mesh, so you may refer to several concepts or use cases. Do you have a device that will publish regular status updates, where it sends the same status repeatedly, but sometimes the status changes so it starts to send out a new status message repeatedly?

    The way this is done in mesh, is that a device has a model, which is either a server model or a client model. The server model contains state. The client model can be used to ask the server model to change its state, or to ask the server model to publish its current state. The server can also publish its state automatically at a regular interval, and/or when the state changes. The publish address for messages from all models is configurable. Models can also subscribe to a number of group addresses, which means messages addressed to those group addresses will be read and handled by the model. Using this, you build up the mesh network and configure what models communicate with what other models, and in what fashion.

    For instance: For the light switch server, you can configure publication on the Generic On Off Server Model with a publish period. The device then publishes the status at that interval. It publishes the current status of the Generic On Off Server Model. If the status of that model changes (e.g. by sending on or off messages from a Generic On Off Client Model on a light switch client example), the new status is the one that gets published.

    Regards,
    Terje

Reply
  • Hi,

    I am not quite sure if I understand the use case here. The term "mesh broadcasting" is not defined in Bluetooth mesh, so you may refer to several concepts or use cases. Do you have a device that will publish regular status updates, where it sends the same status repeatedly, but sometimes the status changes so it starts to send out a new status message repeatedly?

    The way this is done in mesh, is that a device has a model, which is either a server model or a client model. The server model contains state. The client model can be used to ask the server model to change its state, or to ask the server model to publish its current state. The server can also publish its state automatically at a regular interval, and/or when the state changes. The publish address for messages from all models is configurable. Models can also subscribe to a number of group addresses, which means messages addressed to those group addresses will be read and handled by the model. Using this, you build up the mesh network and configure what models communicate with what other models, and in what fashion.

    For instance: For the light switch server, you can configure publication on the Generic On Off Server Model with a publish period. The device then publishes the status at that interval. It publishes the current status of the Generic On Off Server Model. If the status of that model changes (e.g. by sending on or off messages from a Generic On Off Client Model on a light switch client example), the new status is the one that gets published.

    Regards,
    Terje

Children
No Data
Related