Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
Sensitivity: 
Importance: Normal
In-Reply-To: <e9577a1d890c83da99c8dcc2908fff680c9ecb7e.camel@intel.com>
References: <e9577a1d890c83da99c8dcc2908fff680c9ecb7e.camel@intel.com>,
        <OF2849A126.CB6B1F2C-ONC1258514.0028F058-C1258514.0028F05A@phytec.de>
Subject: Re: mesh-cfgclient Node is not attached
From:   Mahaboob Nazeer SK <nazeer.m@phytec.in>
To:     "Gix, Brian" <brian.gix@intel.com>
Cc:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Message-ID: <OFA1C38C14.B5366C1E-ONC1258515.00350A6C-C1258515.00350A6E@phytec.de>
Date:   Fri, 21 Feb 2020 10:39:20 +0100
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Brian,

That was helpful. Its working now,i am able to=20
discover the unprovisioned nodes.

Thank you.


-----linux-bluetooth-owner@vger.kernel.org wrote: -----
To: "nazeer.m@phytec.in" <nazeer.m@phytec.in>, "linux-bluetooth@vger.kernel=
.org" <linux-bluetooth@vger.kernel.org>
From: "Gix, Brian"=20
Sent by: linux-bluetooth-owner@vger.kernel.org
Date: 02/21/2020 12:25AM
Subject: Re: mesh-cfgclient Node is not attached

Hi Mr Nazeer,

On Thu, 2020-02-20 at 08:27 +0100, Mahaboob Nazeer SK wrote:
> Hi,
>=20
> I was trying to provision a node using a mesh-cfgclient.
>=20
> I have successfully ran create and i was able to get configuration=20
> files in the .config.
>=20
> [mesh-cfgclient]# create=20
> Mesh network configuration exists (/home/nazeer/.config/meshcfg/config=5F=
db.json)
>=20
> After that i have tried to discover the unprovisioned node but i get=20
> Node is not attached message.
>=20
> [mesh-cfgclient]# discover-unprovisioned on
> Node is not attached
> [mesh-cfgclient]#

The problem you describe is probably due to the daemon not finding an appro=
priate BT controller to attach to.=20
This led to the "Attach" failing after the "Create", and then none of the c=
ommands to the node are able to be
sent.


There are a couple of options here:

1. If you have a single BT Controller (v4 or newer) you will need to disabl=
e the main bluetooth daemon so that
the bluetooth-meshd daemon has access to it:
$ sudo systemctl disable bluetooth
$ sudo systemctl stop bluetooth

2. If you have *multiple* BT controllers, make sure the bluetooth daemon ha=
sn't automatically claimed them all:
In /etc/bluetooth/main.conf, make sure AutoEnable=3Dfalse (reboot may then =
be required)


In the future, we will be doing work to enable co-existance and controller =
sharing for single controller
systems. However, this will require some changes in the kernel.


>=20
> Could you please let me know if weather there are some=20
> more steps involved to discover and provision a node or if am missing som=
ethings.
>=20
> Thank you.

Regards,

--Brian Gix