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

Hello World !! By including NFFS support into #BluetoothMesh project, now I can access flash of nRF52. { Some useful links: http://docs.zephyrproject.org/api/file_system.html https://lists.zephyrproje

#bluetoothmesh

Hi Johan, Is SFCB better option than NFFS to save #BluetoothMesh's persistence data ? Will it help us in case of nRF51 series which has limited flash storage ? Thank You !! ---------- Forwarded messag

#bluetoothmesh

This is observation based on following configuration done by #meshctl. Two nRF52840-PDK boards has been used for it. For Board 1. after provisioning, I used following commands to configure it ********

#bluetoothmesh

Hello World !! This is observation based on following configuration done by #meshctl. Two nRF52840-PDK boards has been used for it. For Board 1. after provisioning, I used following commands to config

#bluetoothmesh

Hello to all, SoC like nRF52840 supports only 10k write cycles. Is that means, saving sequence no. as soon as NODE receives message, on flash could corrupt it after 500 days if it receives 20 messages

#bluetoothmesh

Hi Johan, In older version of Bluetooth, only 3 channels are used for advertising. But in Bluetooth 5 we can use data channels for advertising. Can we use data channels as ADV channel by configuring Z

#bluetoothmesh

Hi, If #BluetoothMesh DEVICE ECDH-public key (oob public key) is exchanged over OOB channel then what is further need of authentication using input-OOB or output-OOB or static-OOB ? Thanks,

#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

On Sat, Apr 14, 2018, 11:18 AM Vikrant More <vikrant8051@...> wrote: Hi Rodrigo, You can start with this, http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html You have to

#bluetoothmesh

Hi, I am not able to provision my Devices which is executing sample example at $/zephyr/samples/boards/nrf52/mesh/onoff-app/ http://docs.zephyrproject.org/samples/boards/nrf52/mesh/onoff-app/README.ht

#bluetoothmesh #meshctl

Hi, https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-faq As per this link, under the heading of #VisitorAttacks we could see : "Visitor attacks are prevented by giving gues

#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

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, I had a chance to look at this further. More at the bottom. It doesn't appear that bt_mesh_proxy_identity_enable() gets called in prov.c:proxy_data(). The earlier call to bt_mesh_provision() close

#meshctl #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

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 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