Hi, Hi to all, I am trying to implement Generic_Delta_Server_Unack (Level Server) as follow ... void gen_delta_set(struct bt_mesh_model *model, struct bt_mesh_msg_ctx *ctx, struct net_buf_simple *buf)

#bluetoothmesh

Hi all, I wanna use #NVS to save #BluetoothMesh Models states. As per current implementation, #BluetoothMesh stack is using #FCB for persistent storage. If I use #NVS (with default setting) along with

#nvs #fcb #bluetoothmesh

Hi, I've created new PR https://github.com/zephyrproject-rtos/zephyr/pull/8101. It is basically modified version of samples/bluetooth/mesh as well as inspired from samples/boards/nrf52/mesh/onoff-app.

#bluetoothmesh

Hi Carles, Now get these FAULT/OOPS, ***** MPU FAULT ***** Executing thread ID (thread): 0x20001eb0 Faulting instruction address: 0x200006b8 Instruction Access Violation Fatal fault in thread 0x20001e

#bluetoothmesh

Hi, Assume 1) a company don't wanna go with any cloud service to store & upgrade #BluetoothMesh .json file for his products. 2) And no #OOB authentication during provisioning 3) On other side, user pr

#bluetoothmesh

Hi. I Think it will be possible – (but can’t be sure). At last Jehudi Maes (the NVS author) is considering right now ho to provide nvs-back-end for the setting (I’m in touch with him). Andrzej

#fcb #nvs #bluetoothmesh

Hi Vikrant, Mesh will work with any settings backend (currently FCB and NFFS, and in the future with NVS). Johan

#fcb #nvs #bluetoothmesh

Hi, will it be possible to choose between #FCB & #NVS for #BluetoothMesh persistence data storage using configuration options ? Thank You !!

#fcb #nvs #bluetoothmesh

Hi Johan, As per nrf52840_pca10056.dts file last 16KB is used for persistent data storage. To calculate FLASH life time, I have to understand what is going on at background (at #FCB layer). This is my

#bluetoothmesh

Hi, How to save (SIG or Vendor) Model states on SoC flash ? Is it going to be depend upon setting layer which is newly introduce concept or gonna completely independent as part of App layer ? --------

#bluetoothmesh

Hi Johan, Awesome, thanks for the info !!

#bluetoothmesh #lts

HI Aaron, This PDF may help developers who want to go with Zephyr #BluetoothMesh. https://www.zephyrproject.org/wp-content/uploads/sites/38/2018/03/openiot_zephyr_lts_what_and_why.pdf But following li

#bluetoothmesh #lts

Hi, It was bug from my side & I've resolved it. Now everything is working as expected. Excuse me for that !!

#bluetoothmesh

Hi to all, cd $(zephyr_base) git fetch origin pull/7283/head:BlueZMeshctl git checkout BlueZMeshctl I execute above commands & re-build samples/bluetooth/mesh & try to provision it using BlueZ 5.49 #m

#meshctl #bluetoothmesh

Vikrant and others, I was wondering here... Is there any way of using Bluetooth mesh by using the Nordic HAL (NRFX) instead of using the Zephyr's one? Thank you. Best regards, Rodrigo Peixoto.

#bluetoothmesh

Hello, I'm currently trying to implement a bluetooth mesh that includes not only relay nodes but low power nodes and their respective friends. So far I'm having a bit of trouble trying to do this. Is

#bluetoothmesh

Hi Vikrant, It's more of a provisioner issue than a Zephyr issue. On the Zephyr side all you need to do is make sure your configuration allows at least two network keys. Then you need to make your pro

#bluetoothmesh

Hi Johan, Some more detail. I added some instrumentation to parse_service_data and parse_mesh_service_data. The data type that gets passed to parse_mesh_service_data in data[0] is 0x00 while the funct

#bluetoothmesh #meshctl

Hi Vikrant, This is already supported using the "const char *uri" member of struct bt_mesh_prov. Johan

#bluetoothmesh

Hi, Is Zephyr going to introduce feature so that beacon will broadcast URI for unprovisioned #BluetoothMesh DEVICEs ? Or it is simply replacing DEVICE_NAME (means Zephyr ) to something like mentioned

#bluetoothmesh