All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: Testing Bluetooth Mesh with python
Date: Fri, 5 Jul 2019 08:59:32 +0200	[thread overview]
Message-ID: <OFA0EEF328.803EDE57-ONC125842E.002572A3-C125842E.002668F9@phytec.de> (raw)
In-Reply-To: <47E2CBA9-0E7D-46D7-AB94-E27B54AAE110@intel.com>

Hi Brian,

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

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

--
Thanks






-----linux-bluetooth-owner@vger.kernel.org wrote: -----
To: Mahaboob Nazeer SK <nazeer.m@phytec.in>
From: "Gix, Brian" 
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:
> 
> Hi,
> 
> 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.
> 
> But is there any other way to provision a node using a python script.I found a test-mesh script in the test folder 
> of bluez stack ,but i was unable to provision and test a node with it.Could you share a test procedure if any.

We are in the process of coding the Management1 D-Bus interface which includes many of the method calls required for Provisioner support.  The test-mesh python script does *not* work with the meshctl tool, which uses a GATT based architecture.

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

The methods required for the Provisioner side are not quite ready to be pushed out.


> 
> --
> Thanks
> 
> 
> 
> 
> 

      parent reply	other threads:[~2019-07-05  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  4:06 Testing Bluetooth Mesh with python Mahaboob Nazeer SK
2019-07-04 18:41 ` Gix, Brian
2019-07-05  6:59 ` Mahaboob Nazeer SK [this message]

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=OFA0EEF328.803EDE57-ONC125842E.002572A3-C125842E.002668F9@phytec.de \
    --to=nazeer.m@phytec.in \
    --cc=J.Remmert@phytec.de \
    --cc=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.