How to add simple on/off client to Provisioner

RE: How to add simple on/off client to Provisioner

Bjørn Kvaale — Fri, 07 Sep 2018 11:51:26 GMT

wangshuai Could you please open a new case. Thanks.

RE: How to add simple on/off client to Provisioner

wangshuai — Fri, 07 Sep 2018 03:39:53 GMT

hi Brent

I have opened Mesh V2.1.1 and have not seen Client to be integrated to provisioner.how did you do it？

Thinks

RE: How to add simple on/off client to Provisioner

brent_dong — Mon, 20 Aug 2018 18:31:51 GMT

Hi,

Too many misleads here, SDK 101 is not right way. file structure is changed a lot.

SKD 2.1.1 support Client to be integrated to provisioner.

RE: How to add simple on/off client to Provisioner

Jui-Chou (Rick) Chung — Thu, 10 May 2018 07:00:47 GMT

Hello AgathaKuan,

For working on nRF52840, I would like to suggest you compare the difference between nRF52840 SES workspace setting and also nRF52832 SES workspace.
But after the meeting in Leaderson office, I would suggest you to look into serial interface for your design, because you want to use an external MCU as host. If you found any issue related to serial interface, I would like to suggest you checking the mesh SDK document, searching the related threads in Devzone, or rising another ticket in Devzone for serial interface issue.

RE: How to add simple on/off client to Provisioner

agathaKuan — Thu, 10 May 2018 01:39:55 GMT

sorry , I means "program thingy project on nRF52840"

Because I have successfully program thingy project on 52832 pca10040,

(of course I disable many external sensors and the 3-color led),

and SDK 13 do support softdevice s140,

now I wonder if it is possible to program it on nRF52840 pca10056.

RE: How to add simple on/off client to Provisioner

Jui-Chou (Rick) Chung — Wed, 09 May 2018 07:20:15 GMT

Hello AgathaKuan,

No, we are not able to use nRF52840 SES workspace in Thingy 52, because Thingy is using nRF52832.

RE: How to add simple on/off client to Provisioner

agathaKuan — Wed, 09 May 2018 01:41:23 GMT

I see.

If it is possible to generate nRF52840 SES workspace in mesh SDK 1.0.1.

Is it possible to nRF52840 SES workspace in Thingy52 ?

RE: How to add simple on/off client to Provisioner

Hung Bui — Thu, 03 May 2018 07:48:17 GMT

@Agatha: I already explained what you need to do to configure the clients locally in my answer. You can follow what Rick suggested, refer to the light switch client in SDK v1.0.

RE: How to add simple on/off client to Provisioner

Jui-Chou (Rick) Chung — Thu, 03 May 2018 04:33:08 GMT

Hello AgathaKuan,

I would like to suggest you check the following link:

https://devzone.nordicsemi.com/f/nordic-q-a/30035/segger-embedded-studio-project-files-missing-in-mesh-sdk-v1-0-1/129630#129630

It is possible to generate nRF52840 SES workspace in mesh SDK 1.0.1

And you can take the reference from the light switch client to see how to run client model and provisioner in single node.

RE: How to add simple on/off client to Provisioner

agathaKuan — Thu, 03 May 2018 01:33:58 GMT

Exactly I need to implement on nRF52840,

so I CAN NOT use SDK1.0 because there isn't nRF52840 SES project file.

And, I need 4 simple on/off client on provisioner.

PLZ, describe more about "do configuration for the client locally"

RE: How to add simple on/off client to Provisioner

Hung Bui — Wed, 02 May 2018 12:20:22 GMT

Hi Agatha,

How exactly you want to integrate the lightswitch client into the provisioner ?

In SDK v1.x we have 4 elements on the lightswitch client node. One element is provisioner and the others are light switch client elements.

When you have the client integrated on the provisioner, you need to do configuration for the client locally.

If you only plan to have 1 client on the provisioner, it can be as easy as calling simple_on_off_client_init() because you only need one element. And then you assign the publication address of the client to the light server you want to control.

If you plan to have multiple elements, you would need to declare the local unicast address matches with the number of elements. I would suggest you to follow what we did in SDK v1.0