Richard Kuo
This is a simple mbed client example demonstrating, registration of a device with mbed Device Connector and reading and writing values as well as deregistering on different Network Interfaces including Ethernet, WiFi, 6LoWPAN ND and Thread respectively.
Fork of
mbed-os-example-client
by 
mbed-os-examples
Diff: README.md
- Revision:
- 9:dcc4b552c03a
- Parent:
- 7:9a1ee269650b
- Child:
- 12:7da135488950
diff -r d28429119e05 -r dcc4b552c03a README.md --- a/README.md Wed Aug 03 07:30:28 2016 +0100 +++ b/README.md Wed Aug 03 12:00:18 2016 +0100 @@ -275,3 +275,15 @@ For information on how to get notifications when resource 1 changes, or how to use resources 2 and 3, take a look at the [mbed Device Connector Quick Start](https://github.com/ARMmbed/mbed-connector-api-node-quickstart). + +## Known Issues + +If you are using MESH_THREAD as the network interface, once your client device joins the Thread Border Router and you hard reset the client device using reset button, the client device will not be able to join the network again and you will see a warning: + +``` +[WARN][mleS]: dropping packet because mle frame counter is not higher +``` + +Border router will start dropping packets because of MLE frame counter mismatch. For more information about MLE frame counter feature see the [MLE-05 RFC](https://tools.ietf.org/id/draft-kelsey-intarea-mesh-link-establishment-05.html#rfc.section.7.6). +After 240 seconds, the default link timeout triggers the Border router to unregister the lost end device and the BR drops all the counters for that particular device. +Now your should should be able to join the network again.