This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Mesh App does not detect Proxy node while nRF Connect does.

I am trying to implement nRF52 Light Switch Proxy Server in nRF52832 boards. Everything works fine on behalf of board and it prints the Device UUID as well. Although I can observer Mesh Proxy Service in nRF Connect, no proxy nodes are detected by nRF Mesh app. I have tried the same of Android Phone as well as an iPhone.

Can someone please help me through this?

Parents Reply Children
  • Initially it was being detected (on and off) and I've configured my devices for about half a dozen times. But now it is not being detected at all. What I've observed that app detects when I use a new board but it does not detect them when they've been connected to once or twice. (but that should not be an issue as I've tried new phones and factory reset the previous phones as well.)

    Debugger outputs are normal:

    <t:          0>, main.c,  372, ----- BLE Mesh Light Switch Proxy Server Demo -----
    <t:        537>, main.c,  298, Initializing and adding models
    <t:        587>, main.c,  418, Device UUID : 005955AA000000004370AF64E52D2A66

    I'm using Segger Embedded Studio.

    Connecting and disconnecting with nRF Connect app gives the following output

    <t:          0>, main.c,  372, ----- BLE Mesh Light Switch Proxy Server Demo -----
    <t:        537>, main.c,  298, Initializing and adding models
    <t:        587>, main.c,  418, Device UUID : 005955AA000000004370AF64E52D2A66
    <t:   14151513>, main.c,  238, Successfully updated connection parameters
    <t:   14151516>, proxy.c,  575, Connected
    <t:   14629498>, proxy.c,  602, TX ready
    <t:   14635883>, proxy.c,  615, TX complete
    <t:   14803631>, proxy.c,  591, Disconnected

Related