This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Light switch demo versus thingy52-mesh-provisioning-demo

Hello, developers! I am wondering if the Light switch demo and the thingy52-mesh-provisioning-demo serve the same purpose. I tried to run them combined: the first one on an nrf52840 and the second one on thingy52. But they do not exhibit the behaviour of the thingy52-mesh-provisioning-demo (i.e. the LED doesn't blink at the command of the switch). However, from my perspective, they achieve the same goal: publish-subscribe; light switch-light bulb.

Could someone confirm me if my understanding is correct? Maybe I could manage to make both work eventually. Thank you in advance.

Parents
  • Hi,

    However, from my perspective, they achieve the same goal: publish-subscribe; light switch-light bulb.

    Yes, you are correct. Both demo's are doing the same. meaning they both showcase how you can provision and configure a node to be a light switch or a light bulb. 

    The Thingy firmware is equiped with both Generic OnOff client and Generic OnOff Server, so it can be both a light switch and a light bulb. While the Light switch demo have two separate firmware: The light switch client(light switch) and light switch server(light bulb).

    I assume you want to run the nRF52840 as a light bulb/switch and the thingy52 as the other one?

  • Hi

    Thank you for the quick and very well-explained answer.

    un the nRF52840 as a light bulb/switch and the thingy52 as the other one?

    Yes - I try to achieve exactly what you said!

    Eventually, my reasoning is to place one Thingy in the middle as a relay. Because from what I read, in a mesh network, all nodes which are not destination will just forward the messages. Therefore, my first step would be:

    Step 1: [client (nRF52840)] ------> [server (Thingy:52)] - not working at this moment. Need to figure out.

    And after this is done, the next step would be:

    Step 2: [client (nRF52840)] ------> [server (Thingy:52), relay] ------> [server (Thingy:52), final destination] - final goal.

    If you have any suggestion how to achieve my first step, or if you think I can try something simpler and just do Step 2 directly, I am open for any suggestions Slight smile

    Thank you!

Reply
  • Hi

    Thank you for the quick and very well-explained answer.

    un the nRF52840 as a light bulb/switch and the thingy52 as the other one?

    Yes - I try to achieve exactly what you said!

    Eventually, my reasoning is to place one Thingy in the middle as a relay. Because from what I read, in a mesh network, all nodes which are not destination will just forward the messages. Therefore, my first step would be:

    Step 1: [client (nRF52840)] ------> [server (Thingy:52)] - not working at this moment. Need to figure out.

    And after this is done, the next step would be:

    Step 2: [client (nRF52840)] ------> [server (Thingy:52), relay] ------> [server (Thingy:52), final destination] - final goal.

    If you have any suggestion how to achieve my first step, or if you think I can try something simpler and just do Step 2 directly, I am open for any suggestions Slight smile

    Thank you!

Children
No Data
Related