https://devzone.nordicsemi.com/f/nordic-q-a/65865/multiple-switch-on-a-single-server-nodeHello, I had been looking at BLE mesh documentation as well as the examples on the SDK and looks every node should have a dedicated function. generic on/off server controlling one switch, sensor node reading one sensor and I think that&#39;s the BLE specificationen-USTelligent Community 13Tue, 15 Sep 2020 14:00:31 GMThttps://devzone.nordicsemi.com/thread/269688?ContentTypeID=1Tue, 15 Sep 2020 14:00:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:99bda641-7030-4855-a0cf-2b1b2bc611e0Lakay<p>Thank you for the inputs. I&#39;m progressing more quickly :D&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/269388?ContentTypeID=1Mon, 14 Sep 2020 13:13:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bfdf1da0-769c-47cd-88ba-334d0467bcf3Hung Bui<p>Hi Lakay,&nbsp;</p> <p>If you have a look at our light switch client example you can find that we have 2 elements on one node. Each element has a light switch client. It&#39;s initialized in&nbsp;models_init_cb() function.&nbsp;</p> <p>If you want to&nbsp;have multiple servers that control multiple light bulb you can choose to do the same thing. Note that on one element there should be only one server/client with the same model. This is the reason why we have multiple elements with one model on each element.&nbsp;</p> <p>If you plan to use a generic model to control multiple application/sensor you can define your own model (something similar to the UART service we have in Bluetooth LE). You can follow our simple on_off model in our SDK (models/) and instead of sending 1 byte you can send a byte array instead.&nbsp;</p><div style="clear:both;"></div>