Bluetooth: Mesh: Convert no opcode error to debug log
This error message may confuse when `CONFIG_BT_MESH_ACCESS_LAYER_MSG` is enabled and all messages are processed by the callback anyway. This error message also confuses when a node is subscribed to the same address as it publishes to, which makes it generating the error message every time it publishes a message. Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
This commit is contained in:
parent
bcd2aba4d7
commit
ef1f2d1336
1 changed files with 1 additions and 1 deletions
|
@ -1424,7 +1424,7 @@ static int element_model_recv(struct bt_mesh_msg_ctx *ctx, struct net_buf_simple
|
|||
|
||||
op = find_op(elem, opcode, &model);
|
||||
if (!op) {
|
||||
LOG_ERR("No OpCode 0x%08x for elem 0x%02x", opcode, elem->rt->addr);
|
||||
LOG_DBG("No OpCode 0x%08x for elem 0x%02x", opcode, elem->rt->addr);
|
||||
return ACCESS_STATUS_WRONG_OPCODE;
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue