multicast only received by CoAP server not client

RE: multicast only received by CoAP server not client

ToasTer86 — Mon, 18 Dec 2017 10:58:22 GMT

I erased the flash on the device and am now receiving the coap messages. Thanks Hung

RE: multicast only received by CoAP server not client

ToasTer86 — Mon, 18 Dec 2017 09:55:01 GMT

Hey Hung,

I erased the flash on the client side that seems to have helped. The client is now receiving the messages. Although it is warning me that the messages are not of the right format:

<info> app: Received CoAP message that does not match any request or resource

I added my coap messages in thread_coap_utils.c & .h and compiling both versions with the same files. Will hook up the sniffer and see if I can find what is going wrong.

RE: multicast only received by CoAP server not client

ToasTer86 — Fri, 15 Dec 2017 12:11:43 GMT

Hey Hung, Thanks for the response I will take a look at this tomorrow. Today I will be working on other stuff. Will post an update here tomorrow.

RE: multicast only received by CoAP server not client

Hung Bui — Fri, 15 Dec 2017 10:08:57 GMT

You would need to double check the log to see if rx-on-when-idle is set to "disabled" or enabled because it maybe saved in flash. I suspect it's a bug that we don't reconfigure thread inside thread_init() in thread_utils.c if the role = RX_ON_WHEN_IDLE.

Please try to do a chip eraseall before testing, and make sure rx-on-when-idle= enable in the RTT log.

ff03::1 should be able to get to all MED devices in the network, you shouldn't need to use unicast address. If you still have trouble, we would need to debug deeper why it didn't receive the message. One easy test you can do is to let it as end device, then kill the leader (and maybe kill other routers also) so that it change to leader/router role and then check if by that change it can receive the multicast packet.

RE: multicast only received by CoAP server not client

ToasTer86 — Thu, 14 Dec 2017 17:50:15 GMT

Hey Hung Bui,

Thanks for your reply, they way I have set it is now :

thread_configuration_t thread_configuration =
{
    .role                  = RX_ON_WHEN_IDLE,
    .autocommissioning     = true,
    .poll_period           = 2500,
    .default_child_timeout = 10,
};

Checking the definition that should be a powered device:

typedef enum
{
    RX_ON_WHEN_IDLE = 0,  /**< Powered device */
    RX_OFF_WHEN_IDLE,     /**< Sleepy End Device */
} thread_role_t;

Can I use multicast messages to reach end devices, or should I use unicast messages for that ?

But it would kind of combat the general idea of a mesh network if I would always need to unicast a message to an end node. So shouldn't it be possible to reach endnode's using a multicast message?

If not, what way could I force the client to not take a end-device role?

Thanks again Hung

RE: multicast only received by CoAP server not client

Hung Bui — Thu, 14 Dec 2017 17:43:22 GMT

@toaster: Are you sure you didn't set the rx-on-when-idle to "disabled" ? If you set that it will acts a sleepy end device and can't receive the packet.

As you already pointed out ff03::1 is mesh local and should be received by all FTDs and MEDs meaning if it's an end device it should receive the packet.

My test here the server with role 2 can receive the packet, turn on/off the light, no problem.

RE: multicast only received by CoAP server not client

ToasTer86 — Wed, 13 Dec 2017 11:16:57 GMT

Is there a way I can force a unit into role 3 as a router, or make sure that my end devices also receive my multicast messages?

RE: multicast only received by CoAP server not client

ToasTer86 — Wed, 13 Dec 2017 11:16:02 GMT

Hmm in retro spect I do not think it has to do with the client/server role, but if a node is specified as a end device.

I just ran my ble_thread_dyn_template (server) on all 3 available boards and it seems that the unit that is designated a role 2: end device is not receiving the multicast messages but it is sending the multicast messages.