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

Mesh Elements Subscribe of Proxy Light Switch Client can't receive 2nd Publish of Proxy Light Switch Server


Hi ~

   SDK: nrf5_SDK_for_Mesh_v2_0_1 's ligth switch proxy client & proxy server
   IDEs : SEGGER Embedded Studio for ARM
              Release 3.40  Build 2018052200.36079
              Windows x64

   SoftDevices : s132_nrf52_6.0.0_softdevice
   Computer platform : Windows10
   hardware revisions : PCA10040 V1.1.0

  Element 0x0004 can't receive Element 0x0002 As shown.

Parents
  • Hi,

    It shouldn't be a problem doing what you are trying to do, but there aren't much information to know what went wrong. Can you give me more details about your problem? how do you do provisioning and configuration?

  • Try another

    I use both Client&Server and Proxy's android APP (mobile app) with nRF Mesh.
    The hardware is PCA10040, and then use the mobile APP to configure the file "Question 001.png".
    Why do I use the Client subscription to not read the button status of the Server Publish(Element 0x0002)?
    The direction of the black arrow in the figure represents the normal transmission, and the red line represents the transmission failure.

    I made the second configuration test attachment image file ("question 002.png" file).
    After I changed the configuration of Element 0x0003 to 0x0002, Element 0x0002 can publish to the subscription of Element 0x0003.
    However, there is no way for the publish of Element 0x0001 to be received for the subscription of Element 0x0003.
    From the figure (question 001 & question 002) you can find:
    Client-side subscriptions can only be received if the Element itself has an Publish Address.
    The server-side subscription does not require the Element itself to have an Publish Address.

    How can I get the client-side subscription to receive the Address that I have not publish yet? (Like the server side)

Reply
  • Try another

    I use both Client&Server and Proxy's android APP (mobile app) with nRF Mesh.
    The hardware is PCA10040, and then use the mobile APP to configure the file "Question 001.png".
    Why do I use the Client subscription to not read the button status of the Server Publish(Element 0x0002)?
    The direction of the black arrow in the figure represents the normal transmission, and the red line represents the transmission failure.

    I made the second configuration test attachment image file ("question 002.png" file).
    After I changed the configuration of Element 0x0003 to 0x0002, Element 0x0002 can publish to the subscription of Element 0x0003.
    However, there is no way for the publish of Element 0x0001 to be received for the subscription of Element 0x0003.
    From the figure (question 001 & question 002) you can find:
    Client-side subscriptions can only be received if the Element itself has an Publish Address.
    The server-side subscription does not require the Element itself to have an Publish Address.

    How can I get the client-side subscription to receive the Address that I have not publish yet? (Like the server side)

Children
No Data
Related