• State Verified Answer
  • Replies 9 replies
  • Subscribers 64 subscribers
  • Views 5254 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 207605
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

provisionning using nRF Mesh

Mickael Marty

hi,

I tried to provision the light example using the nRF Mesh app.

So far, I succedded in provisionning the device but i couldn't set the publish suscribed addresses, and therefore use the example.

From my understanding of the spec, the client should publish to the server element's address which in turn should suscribe to  the client element address. I also assumed that publishing status would require the server to publish to an address suscribed by the client(eg it's element unicast address).

I can set the publish address corectly but i didn't succed in setting the suscribed one. Any idea why?

Also, where can i find documentation about the app? It is not referenced here or in the info center

Also, i noticed that writting an address of less than four digits causes the app to crash.

Thank you,

best regards,

Mickael

Parents
  • +1

    Hi Mickael, thanks for testing nRF Mesh for iOS!

    First of all, let's try things out to make sure we're on the same page,

    1. Download the latest version from the app store (v1.0)
    2. Provision your node (needs to have a GenericOnOff Server model so you can test the LED)
    3. Go to the GenericOnOff Model's view
    4. Bind the app key
    5. Press the toggle switch and observe the LED turning On/Off (This will use the unicast address of the model's element)
    6. Add a subscription group address, let's say `0xCEEF`, note that this will support only Group addresses, not the Unicast.
    7. Press the toggle switch and observe the LED turning OnOff/ (This will now be using the group address instead)

    Repeat all of the above for as many nodes as you like, as long as you set the same subscription address `0xCEEF` in that case, all the nodes will turn on/off when you toggle the switch.

    Note: Node control through the app will only work with the `GenericOnOffServer` model, any other models are not implemented, don't confuse it with `SimpleOnOffServer` if you see it.

Reply
  • +1

    Hi Mickael, thanks for testing nRF Mesh for iOS!

    First of all, let's try things out to make sure we're on the same page,

    1. Download the latest version from the app store (v1.0)
    2. Provision your node (needs to have a GenericOnOff Server model so you can test the LED)
    3. Go to the GenericOnOff Model's view
    4. Bind the app key
    5. Press the toggle switch and observe the LED turning On/Off (This will use the unicast address of the model's element)
    6. Add a subscription group address, let's say `0xCEEF`, note that this will support only Group addresses, not the Unicast.
    7. Press the toggle switch and observe the LED turning OnOff/ (This will now be using the group address instead)

    Repeat all of the above for as many nodes as you like, as long as you set the same subscription address `0xCEEF` in that case, all the nodes will turn on/off when you toggle the switch.

    Note: Node control through the app will only work with the `GenericOnOffServer` model, any other models are not implemented, don't confuse it with `SimpleOnOffServer` if you see it.

Children
  • 0 in reply to Mostafa Berg

    Hello Mostafa,

    Thanks for your answer, I just saw it and tried.

    I am using the App v1.01, build 7.

    I want to provision and use the simple light example from sdk 2.0.1.

    I provisioned and bound the AppKey without problem.

    i did two tests: I set publication adress of my client to my server's unicast and i tried again with a group address

    On the server side, the publication address is my client unicast and the subscription one is the same group address.

    I tried setting the leds on and off from the client but i get: "Ignored. Node is not configured." when pressing the buttons.

    What am I doing wrong?

    Also, does your step 6 means that I can't send any message to unicast address to control a single element? or is it implementation specific?

    Thanks in advance

    Mickael

    edit: My bad, the example just required all the client to be configured to work.It's ok now.

  • 0 in reply to Mickael Marty

    Yes, that's correct, I'm not sure why the client demo is setup that way but all models needs to be configured for it to work :)

    glad things worked out !, please remember to mark the answer as accepted so this gets updated for future users, and if you have any questions don't hesitate opening a new ticket ! :)

Related