BLE Mesh Initialization

Can’t get the mesh demo working. We get the following in the debug console:

Mesh FW built at 14:43:29 on May 28 2018

SERVER

Clock = 26Mhz

UUID = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff

Random Address = ff:ff:ff:ff:ff:ff

Security = 1, current node state = 0, friend = 3

Generated Device public key (BE)

We can see the device in the nRF Connect BLE Android app, but not in the Toshiba mesh app, probably because the address is not initializing properly. We loaded the standalone beacon demo firmware just to make sure the board was ok, and it used the correct Bluetooth address and worked fine.

Is the problem that the mesh demo is designed for the Toshiba board pictured?

Thank you. I figured out how to set up one board as a mesh-client and one as a mesh-server and was able to provision and talk to the server board.

Is it possible with the server library to make the relay nodes also proxies? I tried modifying the server HCI script to enable the proxy_support bit in the sDevice_features struct, but I wasn't able to see the board directly through the app. My application requires users to be able to connect to a mesh network through any board without having dedicated proxy-server/mesh-client boards.