Combining Provisioner & Client role and Self Provisioning & Configuring client node

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

Mttrinh — Thu, 09 Sep 2021 11:47:45 GMT

Hi,

I suggest you open a seperate ticket with more details regarding the issue you are running into.

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

BilalChaudhary — Mon, 06 Sep 2021 11:05:06 GMT

Hi,

I am working on the same type of thing using Mesh Sdk5.0.0 where I am trying to add the light switch client in the provisioner.

As soon as I add generic_onoff_client_init before or after the provisioner setup example throws the error.

My question is how would I add the client to the provisioner. (Currently, I have added Client functions from client example to run side by side)

And also self-provision the client that is running in provisioner. (This one is for the later stage when the client successfully adds to the provisioner example).

Regards,

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

E.Sumathi — Fri, 23 Oct 2020 04:47:43 GMT

1. when I try to send on/off message from client to server generic_onoff_client_set() and then it returns mesh assert. I was able to trace upto nrf_mesh_packet_send() this function gets called.
2. Ok thanks I will try with PyACI provisioner.

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

Mttrinh — Mon, 19 Oct 2020 12:54:55 GMT

1. What function is returning this assert?

2. I don't think the Element Count is related to URI. URI is a kind of ID to tell which type of device it is. And the number of element is sent when the provisionee respond to the provisioning request, not when getting the compositioning data.

I suggest you to test out the PyACI provisioner to get a deeper understanding on how everything works.

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

E.Sumathi — Wed, 14 Oct 2020 05:06:07 GMT

1. I have set mesh irq priority as "NRF_MESH_IRQ_PRIORITY_LOWEST" and iam using uart interrupt, uart irq priority as " APP_IRQ_PRIORITY_LOWEST"
2. Yes I have made some modification. Actually I want to use light bulbs as sever node and also provision & configure light bulbs with static provisioner. Static provisioner uses URI to provision & configure a node so in order to provision light bulbs I modified code. Is element count in provisioner related to URI?
Without any modification in static provisioner it works fine. Instead of using URI I have hardcoded scenario (m_scenarios[i].p_cfg) since I know number of models in light bulb. And any other suggestion to use static provisioner to provision & configure light bulbs?

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

Mttrinh — Tue, 13 Oct 2020 12:23:37 GMT

Hi,

1. It seems it asserts at this line:

NRF_MESH_ASSERT_DEBUG(bearer_event_in_correct_irq_priority());

related to priority. You should go through this: Setting interrupt priority levels. Use the example I mentioned in the previous answer as a reference to see that everything is done correctly.

2. Not sure if this is related to this thread. Can you try provisioning and configuration with the nRF Mesh app for iOS/Android and the static provisioner example without modifications? Do you see the same issue? No modifications was made to the server except for Element Count?

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

E.Sumathi — Mon, 12 Oct 2020 12:16:51 GMT

1. Yes for provisioning I used prov_helper_provision_self() & app_default_models_bind_setup() and configuration I added and set group address (0xC001) as publish address. And have subscribed server to same group address.
I checked with address line tool error in timer_scheduler "/home/qmax02/Ble_Mesh/nrf5_SDK_for_Mesh_v4.2.0_src/mesh/core/src/timer_scheduler.c:214 (discriminator 1)".

2. This is another case - I used static provisioner, after combining provisioner and client role. Initially I had element count as 2 now I tried to provision a sever by this time I didn't get composition data, it went on retrying for three times and then configuration failed.

RE: Combining Provisioner & Client role and Self Provisioning & Configuring client node

Mttrinh — Mon, 12 Oct 2020 11:57:59 GMT

Hi,

1. Did you provision and configure the client successfully? You can use addr2line tool to see where the assert occurs, see this.

I suggest you take a look at the Client example from Mesh SDK v1.0.1. The provisioner and client was combined in this example. The SDK version is old but you can use the example as a reference. This post is also relevant.

2, What kind of error do you receive? What do you use to provision the device? Have you made any other modifications to the example other than changing the Element Count?