Hmm... indeed something is amiss with generation of the mesh API documentation.
toggle quoted messageShow quoted text
I'm heading out for Thanksgiving vacation, so for now, indeed the header files should be consulted. I'll submit a github issue and look into this more when I return, unless someone else wants to look into this before then.
From: Johan Hedberg [mailto:email@example.com]
Sent: Thursday, November 16, 2017 11:43 PM
To: Kinder, David B <firstname.lastname@example.org>
Cc: Vikrant More <email@example.com>; zephyr-
Subject: Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation
on nRF52840-PDK boards
On Fri, Nov 17, 2017, Kinder, David B wrote:
The documents from the master branch (including the doxygen APIThanks, I suppose the right place should then be:
material) are published nightly to
However, that seems to be broken/incomplete at the moment, since it only
lists the doxygen group bt_mesh but doesn't provide any links to its
subgroups (there are many of them). If I tracked this down right the page
gets generated from doc/api/bluetooth.rst, so that likely needs fixing.
Meanwhile, it seems the best source for Mesh documentation right now is to
look at the header files directly.