Lines Matching refs:will
35 This is done to ensure that all available log will be printed to the shell output.
41 time the device boots up, as the device will remember its provisioning data between reboots.
94 The message will be sent to the current destination address, using the current network and
96 the device will only send packets to itself. To change the destination address to the All Nodes
102 configured network and application keys will receive and process the messages we send.
169 Reset the local mesh node to its initial unprovisioned state. This command will also clear
216 Enable or disable Low Power operation. Once enabled, the device will turn off its radio and
279 …* ``FaultID``: If present, the given fault ID will be deleted. If omitted, all registered faults w…
317 beacons with the given UUID. Once found, the unprovisioned device will be added to the mesh
321 …* ``UUID``: UUID of the unprovisioned device. Providing a hex-string shorter than 16 bytes will po…
323 …* ``Addr``: First unicast address to assign to the unprovisioned device. The device will occupy as…
324 …* ``AttDur``: The duration in seconds the unprovisioned device will identify itself for, if suppor…
333 advertising for PB-GATT with the given UUID. Once found, the unprovisioned device will be
337 …* ``UUID``: UUID of the unprovisioned device. Providing a hex-string shorter than 16 bytes will po…
339 …* ``Addr``: First unicast address to assign to the unprovisioned device. The device will occupy as…
340 …* ``AttDur``: The duration in seconds the unprovisioned device will identify itself for, if suppor…
347 …orter than 16 bytes will populate the N most significant bytes of the array and zero-pad the rest.…
378 …mal value of the static OOB. Providing a hex-string shorter than 16 bytes will populate the N most…
388 …* ``Addr``: First unicast address to assign to the device. The device will occupy as many addresse…
440 …* ``Val`` - Static OOB value. Providing a hex-string shorter than 32 bytes will populate the N mos…
457 device. The beacon will run for 60 seconds before the node returns to normal Proxy beacons.
496 module (``mesh models cfg``) inside the ``mesh models`` subcommand list. This module will work on
510 it will only be able to configure itself and the mesh nodes it provisioned. The following steps are
552 Read a composition data page. The full composition data page will be printed. If the target
553 does not have the given page, it will return the last page before it.
642 …a 128-bit hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most…
651 …a 128-bit hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most…
675 …a 128-bit hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most…
684 …a 128-bit hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most…
774 …rtual address to publish to. Providing a hex-string shorter than 16 bytes will populate the N most…
821 …ual address to subscribe to. Providing a hex-string shorter than 16 bytes will populate the N most…
832 …remove the subscription of. Providing a hex-string shorter than 16 bytes will populate the N most…
854 …ed to the subscription list. Providing a hex-string shorter than 16 bytes will populate the N most…
901 * ``0``: Heartbeat subscription will be disabled.
902 …* ``1`` to ``17``: The node will subscribe to Heartbeat messages for 2\ :sup:`(period - 1)` second…
916 * ``1`` to ``17``: The node will periodically publish 2\ :sup:`(count - 1)` Heartbeat messages.
917 * ``255``: Heartbeat messages will be published periodically indefinitely.
922 * ``1`` to ``17``: The node will publish Heartbeat messages every 2\ :sup:`(period - 1)` seconds.
940 module (``mesh models health``) inside the ``mesh models`` subcommand list. This module will work on
946 By default, the module will choose the first Health Client instance in the model composition when
952 destination address is set to zero, the targeted Health Client will attempt to publish messages
1019 Server will start publishing is fault status with a reduced interval. The reduced interval
1030 Server will start publishing is fault status with a reduced interval. The reduced interval
1079 …hen communicating with Target nodes. If omitted, the BLOB Transfer Client will address each Target…
1086 Perform a BLOB transfer to Target nodes. The BLOB Transfer Client will send a dummy BLOB to
1093 …* ``BlockSizeLog``: Logarithmic representation of the BLOB's block size. The final block size will…
1095 …ating with Target nodes. If omitted or set to 0, the BLOB Transfer Client will address each Target…
1096 …Transfer Mode) or ``pull`` (Pull BLOB Transfer Mode). If omitted, ``push`` will be used by default.
1110 …ating with Target nodes. If omitted or set to 0, the BLOB Transfer Client will address each Target…
1143 receiving any BLOB data, but the implementation in the mesh shell will discard the incoming data.
1207 Add a virtual DFU image slot that can be transferred as a DFU image. The image slot will be
1259 Check whether the device at the configured destination address will accept a DFU transfer
1273 …mmunicating with the Target nodes. If omitted, the Firmware Update Client will address each Target…
1280 a Target node address is provided, the Firmware Update Client model will try to cancel the
1281 DFU procedure on the provided Target node. Otherwise, the Firmware Update Client model will
1339 mesh shell Firmware Update Server will discard the incoming firmware data, but otherwise behave as a
1394 this command will continue populating the receivers list until
1430 …ating with the Target nodes. If omitted, the Firmware Distribution Server will address each Target…
1431 …nal field that corresponds to the update policy. Setting this to ``true`` will make the Firmware D…
1537 …e used to generate the hash. Providing a hex-string shorter than 16 bytes will populate the N most…
1682 * ``ElemAddr``: Element address that will process the aggregated opcodes.
1714 … shorter than 16 bytes will populate the N most significant bytes of the array and zero-pad the re…
1722 …start extended scanning for. Providing a hex-string shorter than 16 bytes will populate the N most…
1762 …* ``UUID``: UUID of the unprovisioned node. Providing a hex-string shorter than 16 bytes will popu…
1764 … Address to assign to remote device. If ``addr`` is 0, the lowest available address will be chosen.
1771 … Address to assign to remote device. If ``addr`` is 0, the lowest available address will be chosen.
1902 …etwork key (NetKeyIndex=0). Providing a hex-string shorter than 16 bytes will populate the N most…
1921 ``mesh provision`` and ``mesh provision-adv`` will be added automatically if the
1924 …exadecimal UUID of the node. Providing a hex-string shorter than 16 bytes will populate the N most…
1928 …horter than 16 bytes will populate the N most significant bytes of the array and zero-pad the rest…
1949 …horter than 16 bytes will populate the N most significant bytes of the array and zero-pad the rest…
1969 …horter than 16 bytes will populate the N most significant bytes of the array and zero-pad the rest…
2008 …* ``Ackd``: This argument decides on whether an acknowledged or unacknowledged message will be sen…
2009 …iation RPL list. This parameter is optional; if absent, only a single SSRC address will be cleared.