RE: Apache-Mynewt/Zephyr mesh receiving a String

Petter Myhre — Wed, 03 Jan 2018 10:26:53 GMT

I'm not too familiar with Apache Mynewt, but the nRF5 SDK for Mesh documentation describes how you can create new models, see this.

RE: Apache-Mynewt/Zephyr mesh receiving a String

Adityaxavier — Fri, 29 Dec 2017 05:37:05 GMT

Actually, the question was more towards technical feasibility. From what I understand in BLE Mesh, we have to stick to one of the listed models.

Implementing a custom model would require changing core mesh implementation. Is this even possible in nRF SDK ?

RE: Apache-Mynewt/Zephyr mesh receiving a String

leonwj — Thu, 28 Dec 2017 17:36:25 GMT

Hello Adityaxavier,

You will be better served asking MyNewt/Zephyr related questions in their respective communities, both of which are very active and provide excellent support...

The relevant links are provided below:

MyNewt

subscribe to: dev-subscribe@mynewt.incubator.apache.org

search archives at: mail-archives.apache.org/.../

Zephyr

subscribe to: zephyr-devel@lists.zephyrproject.org

search archives at: lists.zephyrproject.org/.../

Hope this helps,

regards

[update - dec 30th 2017]

Hello Adityaxavier,

In Bluetooth Mesh, there are certain models that are mandatory and are included in so-called Foundation Models. These include Configuration Server & Health Server. Config/Health Client(s) are Foundation models but are optional.

Additionally, there are standard/generic models Generic-xxx, such as GenericOnOff etc. which provide template actions/responses to standard devices, as well as models for sensors, lighting etc. These are all documented in the Bluetooth SIG Mesh Model specification (not to be confused with the Mesh Profile specification which provides insight into the internal communications and message handling of a Bluetooth SIG Mesh stack).

Finally, in the Nordic and Zephyr (as well as other) implementations of Bluetooth Mesh, it is possible to implement custom/vendor models in order to bring specialized functionality to the fore. The following link provides details of Nordics specific handling of that process. By following the Mesh specification, interoperability across implementations should exist even for custom/vendor models.

This concept of custom models is further demonstrated within the Nordic Mesh SDK via the Simple OnOff custom model and (as it alludes to) should not be confused with the GenericOnOff SIG model.

Please let us know, should you require any additional insight.

regards,