Hi Vikrant, Advertising on Coded PHY needs the implementation of Extended Advertising feature of BT V5.0. This feature has not been implementation, only a initial effort was attempted. That said, any

#bluetoothmesh #ble

Hi, http://blog.bluetooth.com/exploring-bluetooth-5-going-the-distance Is concept of, LE Codded PHY present in current Zephyr implementation to increase range between two #BluetoothMesh Nodes ? What i

#bluetoothmesh #ble

Hi, MyNewt's is a good start point. But looks need more work to make zephyr bluetooth mesh be used in light. I am looking forward it. In the mean time, I can start sensor model coding on zephyr when t

#bluetoothmesh

Hi to all, I solved my own issue. Please refer this ... https://github.com/vikrant8051/zephyr/blob/mesh_demo/samples/boards/nrf52/mesh/onoff_level_app/src/mesh/doer.c Thank You !!

#bluetoothmesh

Hi, I forgot to mentioned about struct server_state *state_ptr = model->user_data; ---------------------------------------------------------------------------------------- struct server_state { int cu

#bluetoothmesh

Hi Vikrant, At the moment the default settings for NVS and FCB are indeed overlapping; you cannot use them at the same time. To use NVS and FCB together my advice would be to look at the board dts fil

#nvs #fcb #bluetoothmesh

Hi Andy, commit 43553da9b2bb9e537185695899fb5184c3b17ebe Author: Andy Ross <andrew.j.ross@...> Date: Thu May 31 11:13:49 2018 -0700 kernel/sched: Fix preemption logic The should_preempt() code w

#bluetoothmesh

Hello World !! Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh [bt] [ERR] hci_tx_thread: assert: 'err == 0

#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 Vikrant, Mesh will work with any settings backend (currently FCB and NFFS, and in the future with NVS). Johan

#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 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, Awesome, thanks for the info !!

#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

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, 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, answering inline. Ok. I really need that. Do you need help on that? I am a little bit confusing. I was willing to create the sample related to OTA and mesh. But if there is other sample as yo

#bluetoothmesh

Hi, This was already identified as a bug in meshctl by Steve, a week ago or so. However, I haven't seen a patch submitted to BlueZ yet. Johan

#bluetoothmesh #meshctl

Hi Diana, Yes, that's correct. The 'frnd' variable can also be controlled through the configuration model (normally operated from the provisioner device). If you set CONFIG_BT_MESH_LPN_AUTO=y then you

#bluetoothmesh