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 Vikrant, The currently implementation is purely based on settings, so you can just register your own settings subpath to store app-specific information. I'd advise to use something else than "bt/"

#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 Kai, The idea is to avoid excessive flash writes (or worse, flash erases). There's a variable that's set with CONFIG_BT_MESH_SEQ_STORE_RATE. It controls that only the Nth sequence number increment

#bluetoothmesh

Hi Johan, Following your suggestion, I just did a test on it after git fetch 7428. After compiling and running "mesh_demo", at least, sequence number store and restore work well on my side. I use micr

#bluetoothmesh

Hi Kai, Please check the PR I referenced earlier. I've added a patch there to convert mesh_demo to use settings. It was actually the other way around that it made sense to do the calls: first settings

#bluetoothmesh

Thanks for the reply! The problem I suffered is that: when I run mesh_demo on microbit, I can't restore SEQ after a reset, when means that if a GenericOnOff client reset unexpected, I need to make thi

#bluetoothmesh

Hi Kai, Also note that the remaining state storing is coming as part of the following PR: https://github.com/zephyrproject-rtos/zephyr/pull/7428 Essentially everything is in place there now, but I sti

#bluetoothmesh

Hello, I noticed that zephyr start to support persistent storage for provisioning data like: { "Net", net_set }, { "IV", iv_set }, { "Seq", seq_set }, { "RPL", rpl_set }, { "NetKey", net_key_set }, {

#bluetoothmesh

Hi Johan, Awesome, thanks for the info !!

#bluetoothmesh #lts

Hi Vikrant, There has been discussion of doing a qualification listing (perhaps two, one for the core host stack and another for Mesh) for LTS releases under the name of the Linux Foundation, but as f

#bluetoothmesh #lts

Hi Kai, bt_mesh_model_publish() is (like the name suggests) for model publication. bt_mesh_model_send() is for everything else that falls outside of that use case. This could be e.g. a server model's

#bluetoothmesh

Hello, I'm trying to know the difference between two APIs, they are: * int bt_mesh_model_publish(struct bt_mesh_model *model) * int bt_mesh_model_send(struct bt_mesh_model *model, struct bt_mesh_msg_c

#bluetoothmesh

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

#lts #bluetoothmesh

Hi, We all look forward that the zephyr project bluetooth mesh can be used on a real project. Before that, we want to know those question's answer. Thanks. vikrant8051 <vikrant8051@...> 于2018年5月

#lts #bluetoothmesh

Hi, What will be status of #BluetoothMesh in #LTS v.1.12.0 release ? Will it be released as #Qualified stack ? As of now, we can't save Provisioning, Configuration & other real time data (eg. message

#lts #bluetoothmesh

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

Hi Steve, Thanks for testing. Could you also please add some sort of "tested to be working" comment in the PR to help it get merged? It'd indeed be interesting for someone to analyze the difference. E

#meshctl #bluetoothmesh