Lines Matching +full:1 +full:- +full:a

1 .. zephyr:code-sample:: nrf_bluetooth_mesh_onoff
3    :relevant-api: bt_mesh
5    Control LEDs on a mesh network using the Bluetooth Mesh OnOff model.
10 This is a simple application demonstrating a Bluetooth Mesh multi-element node.
11 Each element has a mesh onoff client and server
15 a unique UUID. It is obtained from the device address set by Nordic in the
19 The models for button 1 and LED 1 are in the node's root element.
20 The 3 remaining button/LED pairs are in elements 1 through 3.
27 If a LED server is provided with a publish address, it will
30 If a button is pressed only once within a 1 second interval, it sends an
34 previous is discarded. This might seem a little clumsy, but the alternative of
41 This sample has been tested on the Nordic nRF52840-PDK board, but would
47 This sample can be found under :zephyr_file:`samples/boards/nordic/mesh/onoff-app` in the
52 .. zephyr-app-commands::
53    :zephyr-app: samples/boards/nordic/mesh/onoff-app
62 binds button 2 and LED 1 to application key 1. It then configures button 2
63 to publish to group 0xc000 and LED 1 to subscribe to that group.
65 .. code-block:: console
67    discover-unprovisioned on
71    appkey-add 1
72    bind 0 1 1000                # bind appkey 1 to LED server on element 0 (unicast 0100)
73    sub-add 0100 c000 1000       # add subscription to group address c000 to the LED server
74    bind 1 1 1001                # bind appkey 1 to button 2 on element 1 (unicast 0101)
75    pub-set 0101 c000 1 0 0 1001 # publish button 2 to group address c000
77 The meshctl utility maintains a persistent JSON database containing
85 root element's unicast address as it is the only one that has a
91 The meshctl utility also supports a onoff model client that can be used to
100 See :zephyr:code-sample-category:`bluetooth` samples for details.