Getting status messages from Mesh to Phone

Question

Hi I'd like to know how to get status messages into Mesh Proxy Data out. I have a Light Switch Server, and a Light Switch Client. They publish/subscribe to each other, and I've set up a timer to call app_onoff_status_publish every 1 second. I get the Present OnOff value and the source address in each status publish message and it is printed in the logs for the Client every second. 
 I'd like to know how I can put the present OnOff value and source address into Mesh Proxy Data Out (0x2ADE) on the Client. 
 
 I have a Proxy Client that connects to the Light Switch Client, acting as a Proxy Server. I am able to enable notifications on 0x2ADE, Proxy Data Out, but nothing is being written to 0x2ADE. I would like for the present on off value and src address in a status message to be written to 0x2ADE every time the Light Switch Client receives a status publish message.

qmorrison · Accepted Answer

That's okay Bjorn I was able to figure it out. I remembered using sd_ble_gatts_value_set() to programmatically write to a characteristic a few months ago. I was able to slightly modify an existing function, renaming it mesh_gatt_value_update(), which used sd_ble_gatts_value_set(). 
 By adding mesh_gatt_value_update to mesh_gatt.h and mesh_gatt.c, the function would have access to m_gatt, which has the 0x2ADE characteristic. 
 Then I was able to call mesh_gatt_value_update in main.c by including mesh_gatt.h at the top of main.c. I call mesh_gatt_value_update inside of app_onoff_status_publish_cb, which takes the incoming status message and prints it (Nordic's code) but then also sends the src address and payload to mesh_gatt_value_update, which passes it to sd_ble_gatts_value_set. 
 It is working now, and anytime the servers publish status messages, they end up in 0x2ADE on the proxy node, where I can read them through notifications in my cross platform mobile application.

Getting status messages from Mesh to Phone

Top Replies