Some troubles in creating groups

RE: Some troubles in creating groups

Hung Bui — Mon, 12 Nov 2018 17:28:37 GMT

Hi Zhengrui,

Have you tried to increase CLIENT_MODEL_INSTANCE_COUNT ?

When you increase CLIENT_MODEL_INSTANCE_COUNT, the ACCESS_ELEMENT_COUNT will be increased accordingly.

You would need to increase ACCESS_MODEL_COUNT (=2+CLIENT_MODEL_INSTANCE_COUNT) as well.

After that you should have the number of client model to match with what you need.

RE: Some troubles in creating groups

zhengrui — Thu, 08 Nov 2018 02:33:29 GMT

em, I have changed some code on the client to add them but it seems like invalid for the client.Can you tell me where and how to add extra client and extra element on the client side? So that I can change the codes correctly.

Thanks.

RE: Some troubles in creating groups

Hung Bui — Fri, 02 Nov 2018 22:02:13 GMT

Hi Zhenrui,

I'm sorry for the late response, I am on vacation.

Please make sure you have created extra client model and extra element on the client side. I strongly suggest you to play with either the phone app (if you have proxy) to do provisioning or the PyACI to make sure you have all you need on the client and server side, and then can start to modify the provisioner to do provisioning instead of using the app/PyACI

RE: Some troubles in creating groups

zhengrui — Fri, 26 Oct 2018 09:12:29 GMT

I tried it ,when I input 4 or 5 in RTT Viewer to control the group3, it shows Publication not configured for client 4 or 5.I don't think that there is client 4 or 5.

If I configure 3 servers for the address of 0x1004,0x1005,0x1006, two of them can act to the client,but the third have no action when I send 4/5 to the server.

Did I have some understanding for it ?Or some codes lost in the client?

RE: Some troubles in creating groups

Hung Bui — Wed, 24 Oct 2018 11:05:06 GMT

Hi Zhengrui,

I don't see an issue with your code. You would need to debug and check:

- If your client can actually send packet to the address of group 3. You can check on access layer the actual packet sent when you press the button.Please check packet_tx() function in access.c

- If your server is actually subscribe to the Group 3 address. You can test this by using the python PyACI to send dummy packet to that address.

It's worth to try using the PyACI to setup some nodes with the publication/subscription address to the group address that you are testing.

I would suggest you to try playing with the provisioner on the phone app, and the PyACI to get to know more about the address, it's make it easier when you want to try to automate it with the code of the provisioner. For the app you can have a look at this video. For the PyACI, you should follow this guide.

RE: Some troubles in creating groups

zhengrui — Fri, 19 Oct 2018 11:49:32 GMT

Hi Joakim,

Thanks for your reply.

yes , I 've asked in the other case about creating groups,but they're different in vision of Mesh SDK. And the codes and the functions changed a lot so that I don't think it's the same problem and I have tried to be successful in grouping these servers,I need your help in this problem.

RE: Some troubles in creating groups

Joakim Jakobsen — Fri, 19 Oct 2018 11:22:53 GMT

Hi.

Sorry for the lates response.

I can see that you asked similar questions before.
I suggest that you continiue the discussion in one thread until your issue is resolved, instead of creating new ones.

There is also several other threads on devzone regarding this topic.
Did you try searching for the solution?

Best regards,
Joakim

RE: Some troubles in creating groups

zhengrui — Wed, 17 Oct 2018 02:28:31 GMT

Hi Bjorn，I don't know if you had tried to do something for this problem ,I think it's the element on client that I didn't add to and the pub address didn't bind to the element,can you tell me some methods to solve it ?

RE: Some troubles in creating groups

zhengrui — Fri, 12 Oct 2018 03:40:49 GMT

<t:          0>, main.c,  561, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
<t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
<t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
<t:        607>, main.c,  499, Initializing and adding models
<t:        618>, main.c,  542, Setup defaults: Adding keys, addresses, and bindings 
<t:        784>, provisioner_helper.c,  335, netkey_handle: 0
<t:        797>, main.c,  591, <start> 
<t:       1218>, main.c,  114, Flash write complete
<t:       1220>, main.c,  404, Mesh evt: FLASH_STABLE 
<t:       1222>, main.c,  578, Starting application ...
<t:       1224>, main.c,  580, Provisoned Nodes: 0, Configured Nodes: 0 Next Address: 0x0100
<t:       1228>, main.c,  581, Dev key : FB7646B013718CA9382C9930541489B7
<t:       1231>, main.c,  582, Net key : FFDC51E83D68B83AD76CA4F0390AADCC
<t:       1235>, main.c,  583, App key : 18FA155D5F6D8791AB2ED6DCFDFF7D1C
<t:       1237>, main.c,  584, Press Button 1 to start provisioning and configuration process. 
<t:       1241>, main.c,  404, Mesh evt: FLASH_STABLE 
<t:     625873>, main.c,  459, Button 1 pressed
<t:     625875>, main.c,  364, Waiting for Client node to be provisioned ...
<t:     630638>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices
<t:     673902>, provisioner_helper.c,  143, UUID seen: 0059CCAA000000000D10EC4F9C0BA8D1
<t:     673906>, provisioner_helper.c,   95, UUID filter matched
<t:     675111>, provisioner_helper.c,  263, Provisioning link established
<t:     821573>, provisioner_helper.c,  258, Static authentication data provided
<t:     964300>, provisioner_helper.c,  196, Provisioning completed received
<t:     964303>, provisioner_helper.c,  201, Adding device address, and device keys
<t:     964309>, provisioner_helper.c,  218, Addr: 0x0100 addr_handle: 0 netkey_handle: 0 devkey_handle: 2
<t:     964417>, main.c,  404, Mesh evt: FLASH_STABLE 
<t:     967950>, provisioner_helper.c,  159, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:     967955>, main.c,  285, Provisioning successful
<t:     967957>, provisioner_helper.c,  185, Provisioning complete. Node addr: 0x0100 elements: 4
<t:     967961>, provisioner_helper.c,   95, UUID filter matched
<t:     967963>, node_setup.c,  683, Configuring Node: 0x0100
<t:     967967>, node_setup.c,  573, Config client setup: devkey_handle:2 addr_handle:0
<t:     967970>, node_setup.c,  344, Getting composition data
<t:     967980>, access.c,  408, TX: [aop: 0x8008] 
<t:     967982>, access.c,  409, TX: Msg: 00
<t:     968039>, main.c,  114, Flash write complete
<t:     968042>, main.c,  404, Mesh evt: FLASH_STABLE 
<t:     968635>, main.c,  419, Unhandled Mesh Event: 1 
<t:     987919>, access.c,  241, RX: [aop: 0x0002]
<t:     987922>, main.c,  335, Config client event
<t:     987924>, node_setup.c,  354, Adding appkey
<t:     987941>, access.c,  408, TX: [aop: 0x0000] 
<t:     987944>, access.c,  409, TX: Msg: 00000018FA155D5F6D8791AB2ED6DCFDFF7D1C
<t:     987947>, main.c,  419, Unhandled Mesh Event: 0 
<t:     990148>, main.c,  419, Unhandled Mesh Event: 1 
<t:     990889>, access.c,  241, RX: [aop: 0x8003]
<t:     990892>, main.c,  335, Config client event
<t:     990894>, node_setup.c,  259, opcode status field: 0 
<t:     990897>, node_setup.c,  365, App key bind: Health server
<t:     990906>, access.c,  408, TX: [aop: 0x803D] 
<t:     990908>, access.c,  409, TX: Msg: 000100000200
<t:     990911>, main.c,  419, Unhandled Mesh Event: 0 
<t:     991462>, main.c,  419, Unhandled Mesh Event: 1 
<t:     991748>, access.c,  241, RX: [aop: 0x803E]
<t:     991752>, main.c,  335, Config client event
<t:     991754>, node_setup.c,  259, opcode status field: 0 
<t:     991756>, node_setup.c,  433, Setting publication address for the health server to 0x0001
<t:     991772>, access.c,  408, TX: [aop: 0x0003] 
<t:     991775>, access.c,  409, TX: Msg: 0001010000001E81010200
<t:     991778>, main.c,  419, Unhandled Mesh Event: 0 
<t:     994975>, access.c,  241, RX: [aop: 0x8019]
<t:     994978>, main.c,  335, Config client event
<t:     994980>, node_setup.c,  259, opcode status field: 0 
<t:     994983>, node_setup.c,  399, App key bind: 0x1001 client on element 0x0101
<t:     994993>, access.c,  408, TX: [aop: 0x803D] 
<t:     994996>, access.c,  409, TX: Msg: 010100000110
<t:     994999>, main.c,  419, Unhandled Mesh Event: 0 
<t:     996425>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1021218>, access.c,  408, TX: [aop: 0x803D] 
<t:    1021220>, access.c,  409, TX: Msg: 010100000110
<t:    1021794>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1047430>, access.c,  408, TX: [aop: 0x803D] 
<t:    1047432>, access.c,  409, TX: Msg: 010100000110
<t:    1047477>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1048300>, access.c,  241, RX: [aop: 0x803E]
<t:    1048304>, main.c,  335, Config client event
<t:    1048306>, node_setup.c,  259, opcode status field: 0 
<t:    1048309>, node_setup.c,  399, App key bind: 0x1001 client on element 0x0102
<t:    1048319>, access.c,  408, TX: [aop: 0x803D] 
<t:    1048321>, access.c,  409, TX: Msg: 020100000110
<t:    1048324>, main.c,  419, Unhandled Mesh Event: 0 
<t:    1048844>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1049207>, access.c,  241, RX: [aop: 0x803E]
<t:    1049210>, main.c,  335, Config client event
<t:    1049213>, node_setup.c,  259, opcode status field: 0 
<t:    1049215>, node_setup.c,  288, Set: on/off client: 0x0101  pub addr: 0xC003
<t:    1049231>, access.c,  408, TX: [aop: 0x0003] 
<t:    1049233>, access.c,  409, TX: Msg: 010103C000001E00010110
<t:    1049237>, main.c,  419, Unhandled Mesh Event: 0 
<t:    1051034>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1058063>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1071232>, access.c,  241, RX: [aop: 0x8019]
<t:    1071235>, main.c,  335, Config client event
<t:    1071237>, node_setup.c,  259, opcode status field: 0 
<t:    1071240>, node_setup.c,  288, Set: on/off client: 0x0102  pub addr: 0xC002   //there are something lost
<t:    1071255>, access.c,  408, TX: [aop: 0x0003] 
<t:    1071258>, access.c,  409, TX: Msg: 020102C000001E00010110
<t:    1071261>, main.c,  419, Unhandled Mesh Event: 0 
<t:    1073898>, main.c,  419, Unhandled Mesh Event: 1 
<t:    1075305>, access.c,  241, RX: [aop: 0x8019]
<t:    1075308>, main.c,  335, Config client event
<t:    1075311>, node_setup.c,  259, opcode status field: 0 
<t:    1075313>, main.c,  250, Configuration of device 0 successful
<t:    1075316>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices
<t:    1075319>, main.c,  419, Unhandled Mesh Event: 0 
<t:    1075380>, main.c,  114, Flash write complete
<t:    1075382>, main.c,  404, Mesh evt: FLASH_STABLE 
<t:    1209176>, main.c,  419, Unhandled Mesh Event: 4 
<t:    1320743>, access.c,  241, RX: [aop: 0x0004]
<t:    1320746>, main.c,  314, Node 0x0100 alive with 0 active fault(s), RSSI: -40
<t:    1320749>, main.c,  419, Unhandled Mesh Event: 0 
<t:    1867180>, main.c,  419, Unhandled Mesh Event: 4

there are some replenish about configuring client ,I found that the GROUP_ADDRESS_333 (0xC004) (I added ) was not bonded to the client ,so I think something lost here.can you me?

RE: Some troubles in creating groups

zhengrui — Fri, 12 Oct 2018 03:20:49 GMT

0> <t:          0>, main.c,  309, ----- BLE Mesh Light Switch Client Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        531>, main.c,  276, Initializing and adding models
 0> <t:        566>, main.c,  341, Device UUID : 0059CCAA000000000D10EC4F9C0BA8D1
  < 0
 0> <t:      59538>, main.c,  177, Button 0 pressed
 0> <t:      59540>, main.c,  206, Sending msg: ONOFF SET 1
 0> <t:      60437>, main.c,  124, Acknowledged transfer success.
 0> <t:      60440>, main.c,  150, OnOff server: 0x0106, Present OnOff: 0, Target OnOff: 1, Remaining Time: 100 ms
 0> <t:      62174>, main.c,  150, OnOff server: 0x0106, Present OnOff: 1, Target OnOff: 1, Remaining Time: 100 ms
 0> <t:      65625>, main.c,  155, OnOff server: 0x0106, Present OnOff: 1
  < 1
 0> <t:      95574>, main.c,  177, Button 1 pressed
 0> <t:      95576>, main.c,  206, Sending msg: ONOFF SET 0
 0> <t:      96149>, main.c,  124, Acknowledged transfer success.
 0> <t:      96151>, main.c,  150, OnOff server: 0x0106, Present OnOff: 1, Target OnOff: 0, Remaining Time: 100 ms
 0> <t:     101202>, main.c,  155, OnOff server: 0x0106, Present OnOff: 0
  < 2
 0> <t:     125058>, main.c,  177, Button 2 pressed
 0> <t:     125060>, main.c,  206, Sending msg: ONOFF SET 1
 0> <t:     127633>, main.c,  150, OnOff server: 0x0104, Present OnOff: 1, Target OnOff: 1, Remaining Time: 100 ms
 0> <t:     131199>, main.c,  155, OnOff server: 0x0104, Present OnOff: 1
  < 3
 0> <t:     151266>, main.c,  177, Button 3 pressed
 0> <t:     151268>, main.c,  206, Sending msg: ONOFF SET 0
 0> <t:     156528>, main.c,  155, OnOff server: 0x0104, Present OnOff: 0
  < 4
 0> <t:     184026>, main.c,  177, Button 4 pressed
 0> <t:     184028>, main.c,  206, Sending msg: ONOFF SET 1
 0> <t:     184031>, main.c,  256, Publication not configured for client 4
  < 5
 0> <t:     226614>, main.c,  177, Button 5 pressed
 0> <t:     226616>, main.c,  206, Sending msg: ONOFF SET 0
 0> <t:     226618>, main.c,  256, Publication not configured for client 5

all of the log of debug.