-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question : Friend & Low power node with nRF52840 #31905
Comments
I've tried to change the config for the low power node as follow :
As I've seen it commented is some nrf config, without success. ==== EDIT : After some research, it seems there is a problem at the network layer. The method ==== EDIT 2 : The method
is always true and make the program reach the end, returning false. As I'm not an expert of Zephyr or Bluetooth mesh, I dunno why it's like that. ==== EDIT 3 :
==== EDIT 4 : From the LPN :
From the Friend :
==== EDIT 5 : |
Good morning,
I tried to setup a low power node and a friend with two nRF52840 and it doesn't seem to work. Any indication would be helpful.
For this, I used the onoff-app as base project, and changed the Kconfig as follow :
To Reproduce
For the low power node :
For the friend :
Logs and console output
Then I provisionned the low power node first, then the friend, with the nRF mesh app. The logs are as follow :
For the low power node :
Then the 8 last lines would repeat as he tries to find a friend. So far, it seems to work.
For the friend :
I tried to play a bit with Kconfig option, for example setting BT_MESH_LPN_RECV_DELAY at 150 but without success. The connexion between the LPN and Friend is never established as the LPN is always sending request packets.
Is there an example somewhere about LPN & Friend ?
Expected behavior
I expected the friend to see the low power node and establish a connexion with it.
Impact
I need the Friend-Low power node feature for a project.
Environment (please complete the following information):
52ad9a468c1a3ae9a00d1e5aac389c5bfcf087ec
.Best regards.
The text was updated successfully, but these errors were encountered: