Mesh SDK light switch example combining client and server

RE: Mesh SDK light switch example combining client and server

MLai — Mon, 15 Jun 2020 03:57:42 GMT

Yes, with add this in models_init_cb, the code works well.

static void models_init_cb(void)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initializing and adding models\n");

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
        m_clients[i].settings.p_callbacks = &client_cbs;
        m_clients[i].settings.timeout = 0;
        m_clients[i].settings.force_segmented = APP_CONFIG_FORCE_SEGMENTATION;
        m_clients[i].settings.transmic_size = APP_CONFIG_MIC_SIZE;

        ERROR_CHECK(generic_onoff_client_init(&m_clients[i], i + 1));
    }
    ERROR_CHECK(app_onoff_init(&m_onoff_server_0, APP_ONOFF_ELEMENT_INDEX));
}

RE: Mesh SDK light switch example combining client and server

tesc — Fri, 12 Jun 2020 13:48:18 GMT

Hi,

It looks like you never instantiate the onoff server. This is done using the function app_onoff_init() in the light switch server example. Among other things, this function is responsible for setting up the onoff server callbacks.

Regards,
Terje

RE: Mesh SDK light switch example combining client and server

MLai — Wed, 10 Jun 2020 01:48:56 GMT

Thank you for your answer. In my case, the switch itself is also a light bulb. The devices I have are some nordic dk boards. I want the boards can control and respond to other boards. I know that server can send back a status message, but in my case, I am not asking for a status message. What I want is to light up the dk led when button is pressed from another boards, and all boards support this function.

RE: Mesh SDK light switch example combining client and server

tesc — Tue, 09 Jun 2020 13:49:19 GMT

Hi,

I am not sure if you are looking for the same thing as the creator of that other thread. What does the communication between your devices look like? What do you need a device that is both client and server for?

If you have a light bulb device (on/off server) and several light switches (on/off clients), then the communication between server and clients goes like this:

One client is sending an on/off message, to turn the server on or off.
The server gets the on/off message, turns on or off, then publish a status message.
All clients receive the status message, and now they know that the server state has changed.

Notice how in this example, while the true state is only in the server, communication goes first from client to server, then from server to clients. All clients gets notified when the state of the server is changed, and the clients can store a copy of this server state. (But the only way for clients to actually change the state, is to send a message to the server, asking the server to change the state. The server is always in charge of keeping and updating the state.)

The key to Bluetooth mesh communication is often how you configure the nodes. What address each model publish to, and what addresses each model subscribes to. In the above example, the server needs to publish to a group address that all of the clients subscribe to.

So, what is your use case? What kind of devices do you have, and what kind of communication do you need between them?

Regards,
Terje