On Mon, Nov 20, 2017, Vikrant More wrote:
Now I able able to access, first byte send by *"onoff"* command afterGood 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 22.214.171.124.2 in the Mesh Model Specification states:
"If the received message is a Generic OnOff Set message, the Generic
OnOff Server shall respond with a Generic OnOff Status message"
Now I want to save configuration set by meshctl utilitty into flashThis is next on my to-do list for the mesh implementation. For now it's
left up to the application to store and restore the information it
wants. Most of the network state you'll be able to grab from the mesh
structs that the app defines but it's possible that for some you need to
hack the stack code itself.
Note that since we're now starting to have a Configuration Client Model
implementation as well, it opens another possibility for loading back
the values to the stack. I'm not sure if it's worth it, considering that
it involves encrypting & decrypting messages just to set some local
variables, however the benefit is reduced code duplication.