Re: meshctl cannot parse its own config file

["Stotland, Inga" <inga.stotland@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]

Hi Michal,

On Mon, 2017-11-20 at 19:19 +0100, Michał Hobot wrote:
> Hi,
> I'm testing meshctl of bluez 5.47 with a lighting device with Silvair
> mesh stack.
> I am able to provision a device using a following sequence of
> commands:
> 
> provision a9d8....(UUID follows)
> add-appkey 1
> bind 0 1 1000
> 
> Im then able to turn the light on and off using onoff 1 / onoff 0.
> Get also works.
> 
> When I'm leaving meshctl and start it once again, it fails while
> parsing provisioner_db.json
> 
> I found out that the problem was caused by:
> 
> "bind":[
>   1
> ]
> 
> in nodes/elements/models
> When I remove "bind" element, everything seems to work fine.
> 
> Is it a bug in the software or am I doing something wrong?
> 
> Attaching configuration files.
> 
> Regards,
> Michal Hobot
> 
Looks like you discovered a loophole: the provisioner
should not try to issue any configuration commands that require
knowledge of model/element setup on the node without first getting node
composition. The result is a malformed database.

I submitted a patch: "[PATCH BlueZ] mesh: validate configuration
target" to address this issue.

Meanwhile, I suggest calling "get-composition" command prior to any
config command that deals with models.

Thanks,

Inga

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3266 bytes --]