I’m here on the mailing list as well, but I don’t have much knowledge of the “black boxes” of proprietary Mesh products that Vikrant was referring to.
toggle quoted messageShow quoted text
On 18 Jan 2019, at 7.34, wxzzzh <firstname.lastname@example.org> wrote:
You can go here: https://zephyrproject.slack.com/messages/C18PLHN8H/convo/C18PLHN8H-1547649579.774500/?cdn_fallback=1
in general channel, talk to Johan Hedberg by @jhe, who's the leader of this project and should can help you.
签名由 网易邮箱大师 定制
On 1/17/2019 21:01，vikrant8051<email@example.com> wrote：
Available Bluetooth Mesh App layers (which are based on resp. Semiconductor
manufacture BLE Mesh stack) are black boxes. So we can't mimic what they
So is there anyone(developer) who is behind those black boxes to optimise zephyr/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app further?
(Please refer Bluetooth Mesh Model Specification Table 6.128 for details .
From my point of view, current implementation is pretty much stable or Okay
& that makes me biased for it).
Is there any one who has successfully implemented
- Light HSL Server/Client models using Zephyr Mesh stack
- which has clear all PTS test rquirements 😃
- and have used something indigenous/superior way than proposed implementation
in mentioned app ?
Thanks & regards,