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: <47E2CBA9-0E7D-46D7-AB94-E27B54AAE110@intel.com>
References: <47E2CBA9-0E7D-46D7-AB94-E27B54AAE110@intel.com>,
        <OFCEFD7E67.77A1AF25-ONC125842D.001694FD-C125842D.001694FE@phytec.de>
Subject: Re: Testing Bluetooth Mesh with python
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>,
        Jonas Remmert <J.Remmert@phytec.de>
Message-ID: <OFA0EEF328.803EDE57-ONC125842E.002572A3-C125842E.002668F9@phytec.de>
Date:   Fri, 5 Jul 2019 08:59:32 +0200
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Brian,

Thank you for that information.It's good to know.=20

Do you have any expected timeline like when this could=20
be pushed out.

--
Thanks


-----linux-bluetooth-owner@vger.kernel.org wrote: -----
To: Mahaboob Nazeer SK <nazeer.m@phytec.in>
From: "Gix, Brian"=20
Sent by: linux-bluetooth-owner@vger.kernel.org
Date: 07/05/2019 12:10AM
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Testing Bluetooth Mesh with python

Hello,

> On Jul 3, 2019, at 9:08 PM, Mahaboob Nazeer SK <nazeer.m@phytec.in> wrote:
>=20
> Hi,
>=20
> We are using Zephyr Mesh onoff example on nrf52 eval kit to test the Mesh=
 Functionality.For provisioning of the
> node we are using meshctl tool.
>=20
> But is there any other way to provision a node using a python script.I fo=
und a test-mesh script in the test folder=20
> of bluez stack ,but i was unable to provision and test a node with it.Cou=
ld you share a test procedure if any.

We are in the process of coding the Management1 D-Bus interface which inclu=
des many of the method calls required for Provisioner support.  The test-me=
sh python script does *not* work with the meshctl tool, which uses a GATT b=
ased architecture.

The D-Bus interface (as described in the doc/mesh-api.txt) works with the b=
luetooth-meshd daemon which is currently being built out, and it is entirel=
y built on Advertisement (non-GATT) based communication with other nodes.

The methods required for the Provisioner side are not quite ready to be pus=
hed out.


>=20
> --
> Thanks
>=20
>=20
>=20
>=20
>=20