2ff98636a5
Until now the OOB info and URI fields in unprovisioned beacons were generally ignored by the implementation. Add fields for these to bt_mesh_prov and make sure to take them into account when encoding advertising data, both for PB-ADV and PB-GATT. For PB-ADV the URI goes out in a separate beacon, whereas for PB-GATT it is placed in the scan response data. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
23 lines
565 B
C
23 lines
565 B
C
/* Bluetooth Mesh */
|
|
|
|
/*
|
|
* Copyright (c) 2017 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
void bt_mesh_pb_adv_recv(struct net_buf_simple *buf);
|
|
|
|
bool bt_prov_active(void);
|
|
|
|
int bt_mesh_pb_gatt_open(struct bt_conn *conn);
|
|
int bt_mesh_pb_gatt_close(struct bt_conn *conn);
|
|
int bt_mesh_pb_gatt_recv(struct bt_conn *conn, struct net_buf_simple *buf);
|
|
|
|
const struct bt_mesh_prov *bt_mesh_prov_get(void);
|
|
|
|
int bt_mesh_prov_init(const struct bt_mesh_prov *prov);
|
|
|
|
void bt_mesh_prov_complete(u16_t net_idx, u16_t addr);
|
|
void bt_mesh_prov_reset(void);
|