I have added bt_mesh_model_publish( ) in thread which starts to execute after getting interrupt from button. But when I click button multiple times in very short period of time then only thread execut

Hello Sir, I have attached my main.c with this email. (from Zephyr Mesh Demo) This main.c is mostly inspired from information provided by Steve Brown. Please check it. Here, root_models[2] is BT_MESH_

Thank you for the clarification. Could you please tell me, what should I do next ? I need agenda to deeply understand concept of #BluetoothMesh.

how to subscribe dynamically to heartbeat of any node (using meshctl) ? I've enable CONFIG_BT_MESH_CFG_CLI=y this in prj.conf Added "Configuration Client Model" into list of models supported by root_m

Hi to all, Need proper sequence of all commands to start working with #mesh_shell [ to activate Model 1000 (which subscribe to 0xC000) as well as 1001 (which publish to 0xC000) ] #meshctl take care of

1) Download this --> https://git.kernel.org/pub/scm/bluetooth/bluez.git/snapshot/bluez-5.48.tar.gz 2) tar -xvf bluez-5.48.tar.gz 3) mv bluez-5.48 bluez 4)cd bluez 5)./bootstrap-configure 6)make 7)make

Glad to hear it!

Hello, Currently I have been doing provisioning of #BluetoothMesh DEVICEs using #meshctl utility. But I've to individually makes connection with each device over PB-GATT for provisining & configuratio

#bluetoothmesh

Hello World !! ----------------------------------------------------------------------------------------------------------------------------- { "$schema":"file:\/\/\/BlueZ\/Mesh\/schema\/mesh.jsonschem

#bluetoothmesh

Hello World !! https://blog.bluetooth.com/provisioning-a-bluetooth-mesh-network-part-1 By reading this link, I understood that netKey, appKey, dveKey are AES-128 symmetric keys which are exchanged ove

#bluetoothmesh

Hi Johan, Thanks for your reply. https://blog.bluetooth.com/provisioning-a-bluetooth-mesh-network-part-1 https://blog.bluetooth.com/provisioning-a-bluetooth-mesh-network-part-2#_ftn2 I've been further

#bluetoothmesh

Hi Johan, Many many thanks Johan, for your in detail explanation. I don't want to use static public-private key pair for DEVICE & happy with current implementation. It is inherently more secure since

#bluetoothmesh

Hello World !! My question is related to this link's requirement, https://lists.zephyrproject.org/pipermail/zephyr-devel/2017-July/007888.html Is Zephyr going to add support for NFFS file system in up

#include <fs.h> void main( ) { fs_file_t *my_zfp; unsigned char ptr[32]; fs_open(my_zfp,"mesh.prv"); fs_write(my_zfp,"Hello World !! ",16); fs_read(my_zfp,ptr,32); fs_close(my_zfp); printk("%s",ptr);

>> How provisioner will understand from where to received/read DEVICE >> public key out of *Bluetooth-Link* or *OOB* channel ? >I believe this is out of scope for the specification, since any OOB >cha

#bluetoothmesh

I copied & pasted $zephyr/ext/fs/nffs directory into $zephyr_base/include ---------------------------------------------------------------------------------------------------------------------- & edit

Hi Vinayak, it works !! I make following changes ..... fs_file_t my_zfp; unsigned char ptr[32]; for(cntr=0;cntr<=31;cntr++) { ptr[cntr]='@'; } fs_open(&my_zfp,"mesh.prv"); fs_write(&my_zfp,"0123456789

fs_open( ) returns -19 instead of 0.

Hello World !! https://devzone.nordicsemi.com/blogs/1235/nrf-blinky-compatible-firmware-using-zephyr-blueto/ I modified $zephyr_base/sample/bluetooth/peripheral/src/main.c as mentioned above. Using nR

Thanks Michael !! Now I can access flash of nRF52840 using NFFS file system APIs. I request Zephyr OS maintainer to create & add following attached main.c under $zephyr_base/samples/boards/nrf52/nffs/