Unicast message failed to reach client

Hi,

We have a blue tooth mesh application similar to light and light-switch setup.

server nodes: light

client nodes: light-switch

We expand the light-switch node to send multicast message to all server nodes. Upon receiving the message, server (light) nodes reply with some information such as version number or node name via unicast message back to the caller (client node - the light switch).

This works well so far.

However, after a while, the client node won’t receive message from some server nodes any more. It can receive from some nodes, but not from all nodes. It can still send multicast message to these server nodes, but it won’t see the response message. We know that the server nodes (light) receive the message.

I’ll pull some log data and update this ticket, but please let me know what I need to look for.

Since this is now in production stage, we need to resolve this quickly. One way to work around I found is to reset the client node (light-switch) and re-provision and configure it back to the network again. This seems to work, but, it is not what we want to do since the problem seems to happen so often.

Thank you for your help.

Parents
  • Hello,

    Did you have any logs from the nodes when the issue occurs? Preferably also the network core logs, to see if anything is happening there when the node starts acting weird.

    How long does it usually take before the issue starts to occur?

    Is there some way for me to reproduce the issue with a handful of DKs, or does it require a large test-rig?

    Best regards,

    Edvin

Reply
  • Hello,

    Did you have any logs from the nodes when the issue occurs? Preferably also the network core logs, to see if anything is happening there when the node starts acting weird.

    How long does it usually take before the issue starts to occur?

    Is there some way for me to reproduce the issue with a handful of DKs, or does it require a large test-rig?

    Best regards,

    Edvin

Children
No Data
Related