From: "Gix, Brian" <brian.gix@intel.com>
To: "mike@mnmoran.org" <mike@mnmoran.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: mesh: Send mesh model message to group address
Date: Sat, 15 Feb 2020 19:50:44 +0000 [thread overview]
Message-ID: <e2f322b4ba3abb81b59a51d8bb5c3611b968cd4f.camel@intel.com> (raw)
In-Reply-To: <848c1b0b-83c6-41a3-fc66-1359fa9a72bb@mnmoran.org>
Hi Michael,
On Sat, 2020-02-15 at 13:20 -0500, Michael N. Moran wrote:
> I've been using meshctl to provision/configure a group of
> mesh nodes.
First off, don't use meshctl for work going forward, unless for some reason you *require* GATT support. Mesh
is designed to primarily be an Advertising based system, and so all current work is being done on the
bluetooth-meshd daemon, which does not yet have GATT support.
We currently have a pretty robust solution based on:
1. Run mesh/bluetooth-meshd as root
1.1 You may need to first install, *or* copy
mesh/bluetooth-mesh.conf --> /etc/dbus-1/system.d/bluetooth-mesh.conf
1.2 Make sure mesh/bluetooth-meshd has a dedicated v4.0 or
better controller. This can be done by stopping bluetoothd,
or by having a 2nd controller in the system and making sure
that in /etc/bluetooth/main.conf, AutoEnable=false
1.3 reboot
2. Run tools/mesh-cfgclient
> There does not seem to be a mechanism in meshctl to send
> model messages to group addresses or virtual addresses.
>
> As an example, consider the simple OnOff model. I can
> configure the subscription for an OnOff model with a group
> address. However, the meshctl onoff command will not work
> with a group address set for the onoff target.
>
> I have modified the cmd_set() function in onoff-model.c by
> removing the node_find_by_addr(target) check and this works
> fine. Obviously, that only works for the OnOff model. I'd
> happily submit a patch for that model, but that doesn't seem
> to be a very good general solution.
>
> So is meshctl the right (only) tool to use on Linux?
> Is there a newer tool that is planned or under development?
See above, and use the tip of the repository (currently at v5.53)
>
> regards,
> mike
next prev parent reply other threads:[~2020-02-15 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 18:20 mesh: Send mesh model message to group address Michael N. Moran
2020-02-15 19:50 ` Gix, Brian [this message]
2020-02-16 4:39 ` Michael N. Moran
2020-02-16 15:17 ` Gix, Brian
2020-02-16 22:32 ` Michael N. Moran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2f322b4ba3abb81b59a51d8bb5c3611b968cd4f.camel@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mike@mnmoran.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox