Hi Jehudi, The local "OnOff Client" of meshctl is bound to Application Key 001, not 000 (see the local_node.json file). I am not certain the Zephyr supports the on/off opcode (even if the Composition data of Zephyr is claiming to support the model) but at a minimum, you should be sending appkey 001, and binding the on/off server to that key. > -----Original Message----- > From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth- > owner@xxxxxxxxxxxxxxx] On Behalf Of Laczen JMS > Sent: Tuesday, August 29, 2017 10:58 AM > To: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> > Cc: linux-bluetooth@xxxxxxxxxxxxxxx > Subject: Re: usage of meshctl with zephyr node > > Hi Luiz, > > Thanks for the reply. Zephyr does support the onoff model. Using the silicon > lab mesh program for android I can control the onoff server model on the > node. > > What I don't know is if I can use the onoff command in meshctl to control the > onoff server model on the node. I am trying to provision, configure and > control a node using meshctl. The provisioning works, I am doubting the > configuring and controlling. > > For the configuring I am using: configure nodeID, add-appkey, bind, is this OK > ? > > For the controlling I am using onoff nodeID, onoff 1/0, is this OK? > > Kind regards, > > Jehudi > > 2017-08-29 19:38 GMT+02:00 Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx>: > > Hi, > > > > On Tue, Aug 29, 2017 at 4:50 PM, Laczen JMS <laczenjms@xxxxxxxxx> > wrote: > >> Hi, > >> > >> I have tried to use meshctl with a zephyr node, but I can't figure > >> out how to use it. I have a zephyr node that is unprovisioned and I'm > >> doing the following: > >> > >> [meshctl] # discover-unprovisioned on -> works and gives a new > >> unprovisioned node (dddd000..) [meshctl] # discover-unprovisioned off > >> [meshctl] # provision dddd -> works [Zephyr Mesh-Node-0100] # > >> configure 0100 > >> [config: Target = 0100] # add-appkey 0 -> works: Node 0100 AppKey > >> Status Success > >> [config: Target = 0100] # bind 0 0 1000 -> works: Node 0100 Model App > >> Status Success Element 0100 AppIdx 000 > >> ModelId 1000 > >> Binding successful AppIdx 000 > >> [config: Target = 0100] # back > >> [Zephyr Mesh-Node-0100] # onoff 0100 > > > > I don't thing Zephyr supports onoff model, that might explain why this > > is failing. > > > >> [on/off: Target = 0100]# onoff 1 fails (does nothing) The debugging > >> on the node gives the following message: > >> [bt] [WRN] sdu_recv: No matching AppKey adding some extra debugging > >> lines in the node gives the following information: > >> (AID(&hdr) != keys->id): > >> [bt] [WRN] sdu_recv: Appkey IDs hdr:31 keys:46 > >> > >> Am I using meshctl incorrect ? I am doubting the bind command. > >> > >> Thanks, and kind regards, > >> > >> Jehudi > >> -- > >> To unsubscribe from this list: send the line "unsubscribe > >> linux-bluetooth" in the body of a message to > >> majordomo@xxxxxxxxxxxxxxx More majordomo info at > >> http://vger.kernel.org/majordomo-info.html > > > > > > > > -- > > Luiz Augusto von Dentz > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in > the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo > info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
