Re: BT mesh sample : sdu_recv: No matching AppKey

Johan Hedberg

Hi Steve,

On Thu, Sep 07, 2017, Steve Brown wrote:
I'm using bluez' meshctl to provision a redbear ble nano2 running
zephyr at commit 637087cc56040b7b3c4a81d0707723fb68e17895.

I've also applied unsupp_slave_feat_req.diff from Vinayak's email of

I add appkey 1 and bind 0 1 1000, but get the above warning when trying

I looked at the code around the warning. Could a "return 0" be missing
after host/mesh/transport.c:531 ?
I think you're right. Previously the code would do a
"return bt_mesh_model_recv(rx, sdu);", but after the function was changed
to return void adding a separate return statement was overlooked. The
warning itself is harmless but good to get fixed either way since it's
confusing. Do you want to try to submit a patch for that?


Join { to automatically receive all group messages.