-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes Degu fail to update shadow, right after register Degu to AWS IoT Core. #41
Comments
This was referenced Mar 13, 2020
yoshidam-at
added a commit
to yoshidam-at/degu
that referenced
this issue
Mar 27, 2020
…gister Degu to AWS IoT Core.
yoshidam-at
added a commit
to yoshidam-at/degu
that referenced
this issue
Apr 1, 2020
… right after register Degu to AWS IoT Core. - set mutex degu_utils::degu_get_asset() - set mutex CoAP send and receive - add parameter zcoap_buf degu_utils::degu_coap_request() to reduce k_malloc() - if the size secured by k_malloc is less than level 3, round up to level 2.
yoshidam-at
added a commit
to yoshidam-at/degu
that referenced
this issue
Apr 13, 2020
…gister Degu to AWS IoT Core. set CONFIG_HEAP_MEM_POOL_SIZE 39936(Multiples of 256). delete get asset on callback thread link up. delete mutex.
yoshidam-at
added a commit
to yoshidam-at/degu
that referenced
this issue
Apr 13, 2020
…gister Degu to AWS IoT Core. - add parameter zcoap_buf degu_utils::degu_coap_request() to reduce k_malloc() - if the size secured by k_malloc is less than level 3, round up to level 2. - set CONFIG_HEAP_MEM_POOL_SIZE 39936(Multiples of 256).
yoshidam-at
added a commit
that referenced
this issue
Apr 13, 2020
fix #41 Sometimes Degu fail to update shadow, right after register De…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Sometimes Degu fail to update shadow, right after register Degu to AWS IoT Core.
To Reproduce
Expected behavior
reboot Degu.
Screenshots
none.
Version(please complete the following information):
Additional context
none.
The text was updated successfully, but these errors were encountered: