|
Can not get any call back when bluetooth connect fail
Hi guiwu gue, Is this the same issue you've outlined here: https://jira.zephyrproject.org/browse/ZEP-2005 If so, does the attached patch help? Johan
Hi guiwu gue, Is this the same issue you've outlined here: https://jira.zephyrproject.org/browse/ZEP-2005 If so, does the attached patch help? Johan
|
By
Johan Hedberg
· #28
·
|
|
qemu_x86 zephyr bluetooth beacon sample error
Hi Priyanka, What version of Zephyr is this with? I've noticed that sometimes there seems to be some garbage data inserted to the virtual UART between btproxy and qemu, and restarting qemu usually hel
Hi Priyanka, What version of Zephyr is this with? I've noticed that sometimes there seems to be some garbage data inserted to the virtual UART between btproxy and qemu, and restarting qemu usually hel
|
By
Johan Hedberg
· #146
·
|
|
Mesh provisioning w/ SILabs Android Mesh app
Hi Steve, At least some versions of the SiLabs app had a bug with OOB handling that was causing similar results as above. A simple solution was to disable OOB provisioning support from the Zephyr side
Hi Steve, At least some versions of the SiLabs app had a bug with OOB handling that was causing similar results as above. A simple solution was to disable OOB provisioning support from the Zephyr side
|
By
Johan Hedberg
· #185
·
|
|
[Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards
Hi Vikrant, The API is documented with the usual doxygen syntax. I'm not sure how frequently documentation in the master branch gets generated onto the website, so it might be better for you to genera
Hi Vikrant, The API is documented with the usual doxygen syntax. I'm not sure how frequently documentation in the master branch gets generated onto the website, so it might be better for you to genera
|
By
Johan Hedberg
· #261
·
|
|
[Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards
Hi David, Thanks, I suppose the right place should then be: http://docs.zephyrproject.org/api/bluetooth.html#mesh-profile However, that seems to be broken/incomplete at the moment, since it only lists
Hi David, Thanks, I suppose the right place should then be: http://docs.zephyrproject.org/api/bluetooth.html#mesh-profile However, that seems to be broken/incomplete at the moment, since it only lists
|
By
Johan Hedberg
· #263
·
|
|
How & what to save provisioning configuration set by meshctl utility into flash memory of NRF52840-PDK ??
Hi Vikrant, Good to see that you're making progress with this. Note that you'll also need to send an OnOff Status response when receiving this message, as section 3.3.1.2.2 in the Mesh Model Specifica
Hi Vikrant, Good to see that you're making progress with this. Note that you'll also need to send an OnOff Status response when receiving this message, as section 3.3.1.2.2 in the Mesh Model Specifica
|
By
Johan Hedberg
· #268
·
|
|
Help needed to setup 6loble using IPSP sample
Hi Vakul, Have you verified that the handle value 32 is valid, i.e. the controller gave that in a prior LE Connection Complete event? It would help investigate the issue if you could get the entire lo
Hi Vakul, Have you verified that the handle value 32 is valid, i.e. the controller gave that in a prior LE Connection Complete event? It would help investigate the issue if you could get the entire lo
|
By
Johan Hedberg
· #272
·
|
|
Help needed to setup 6loble using IPSP sample
Hi Vakul, The connection handle is completely local to the device, so what you have on the Linux side has no relevance to Zephyr (i.e. the handles can, and often will be different). I don't see any co
Hi Vakul, The connection handle is completely local to the device, so what you have on the Linux side has no relevance to Zephyr (i.e. the handles can, and often will be different). I don't see any co
|
By
Johan Hedberg
· #274
·
|
|
Help needed to setup 6loble using IPSP sample
Hi Vakul, This looks like fairly reasonable fix to me. Would you be able to submit it as a pull request? Note that there's a minor coding style issue: the split line needs to be aligned with the first
Hi Vakul, This looks like fairly reasonable fix to me. Would you be able to submit it as a pull request? Note that there's a minor coding style issue: the split line needs to be aligned with the first
|
By
Johan Hedberg
· #281
·
|
|
About publish & subscribe mechanism in Bluetooth Mesh
Hi Vikrant, You can find the answer in the Mesh Profile Specification. E.g. section 4.2.2.1 states: "The publish address shall be the unassigned address, a unicast address, a Label UUID, or a group ad
Hi Vikrant, You can find the answer in the Mesh Profile Specification. E.g. section 4.2.2.1 states: "The publish address shall be the unassigned address, a unicast address, a Label UUID, or a group ad
|
By
Johan Hedberg
· #296
·
|
|
About publish & subscribe mechanism in Bluetooth Mesh
Hi Vikrant, Mesh application payloads always start with a model-specific OpCode, which is 1-3 bytes long. So if you want to send valid data you'd need to do that in the context of a model, and in that
Hi Vikrant, Mesh application payloads always start with a model-specific OpCode, which is 1-3 bytes long. So if you want to send valid data you'd need to do that in the context of a model, and in that
|
By
Johan Hedberg
· #300
·
|
|
Error while publishing from one node to another node in Bluetooth Mesh
Hi Vikrant, It looks like the sender has been reset without restoring its earlier state, whereas the receiver has continued running all the time. This will cause the sender to send using an "old" sequ
Hi Vikrant, It looks like the sender has been reset without restoring its earlier state, whereas the receiver has continued running all the time. This will cause the sender to send using an "old" sequ
|
By
Johan Hedberg
· #316
·
|
|
Discarding Netwok PDU
Hi Ashish, There are too many conditions to start listing them here. I recommend you look at net.c and transport.c under subsys/bluetooth/host/mesh/ and trace through the code starting with bt_mesh_ne
Hi Ashish, There are too many conditions to start listing them here. I recommend you look at net.c and transport.c under subsys/bluetooth/host/mesh/ and trace through the code starting with bt_mesh_ne
|
By
Johan Hedberg
· #318
·
|
|
about success rate of publish-subscribe mechanism of Zephyr Bluetooth Mesh
Hi Vikrant, Note that strictly speaking this isn't publishing. For publishing you'd use the bt_mesh_model_publish() API. The bt_mesh_model_send() is primarily intended to be used for responding to mes
Hi Vikrant, Note that strictly speaking this isn't publishing. For publishing you'd use the bt_mesh_model_publish() API. The bt_mesh_model_send() is primarily intended to be used for responding to mes
|
By
Johan Hedberg
· #320
·
|
|
understanding of logic behind address used in Publish-Subscribe mechanism for Bluetooth Mesh
Hi Vikrant, What do you need this for? If you need to access the element it's right there in model->elem. That's just some group address the provisioner has apparently configured this model to publish
Hi Vikrant, What do you need this for? If you need to access the element it's right there in model->elem. That's just some group address the provisioner has apparently configured this model to publish
|
By
Johan Hedberg
· #325
·
|
|
Publishing user data
Hi Ashish, The "all relays" group address is 0xfffe and not 0xffe. In most cases it's unwise (inefficient) to have all nodes of a mesh network acting as relays, so you may want to rethink your setup.
Hi Ashish, The "all relays" group address is 0xfffe and not 0xffe. In most cases it's unwise (inefficient) to have all nodes of a mesh network acting as relays, so you may want to rethink your setup.
|
By
Johan Hedberg
· #328
·
|
|
[Zephyr-devel] mesh: relay traffic when relay state is 0x02 (not supported)
Hi Vikrant, Please try to avoid top-posting, especially if the existing thread is using inline quoting. Are you talking about adv-adv relaying or GATT-adv relaying (or vice-versa)? Steve seemed to con
Hi Vikrant, Please try to avoid top-posting, especially if the existing thread is using inline quoting. Are you talking about adv-adv relaying or GATT-adv relaying (or vice-versa)? Steve seemed to con
|
By
Johan Hedberg
· #334
·
|
|
[Zephyr-devel] mesh: relay traffic when relay state is 0x02 (not supported)
Hi Vikrant, For the record, I just did a quick test with the LigthBlue app (similar to nRFConnect) and it correctly shows that the Provisioning service (UUID 0x1827) gets replaced by the GATT Proxy se
Hi Vikrant, For the record, I just did a quick test with the LigthBlue app (similar to nRFConnect) and it correctly shows that the Provisioning service (UUID 0x1827) gets replaced by the GATT Proxy se
|
By
Johan Hedberg
· #335
·
|
|
[Zephyr-devel] mesh: relay traffic when relay state is 0x02 (not supported)
Hi Vikrant, I took a second look at the logic in bt_mesh_net_relay() and indeed it was still buggy. Thanks for catching this. The following pull request (which I'm still doing a bit of testing on) sho
Hi Vikrant, I took a second look at the logic in bt_mesh_net_relay() and indeed it was still buggy. Thanks for catching this. The following pull request (which I'm still doing a bit of testing on) sho
|
By
Johan Hedberg
· #336
·
|
|
Complete Sample Demo for BluetoothMesh like Nordic Semiconductor "Light_Switch"
Hi Vikrant, This is not really useful information without some more details. What Publish Retransmit and Network Transmit states does the Nordic SDK use? What are the values of these states on the Zep
Hi Vikrant, This is not really useful information without some more details. What Publish Retransmit and Network Transmit states does the Nordic SDK use? What are the values of these states on the Zep
|
By
Johan Hedberg
· #339
·
|