There seems to be a lot of conflicting information about this: The easy-setup wiki page shows a constrained device registering with an iotivity cloud without any other devices running iotivity besides the mediator The example easy-setup app shows a coap+tcp ip address being sent to the constrained device
None of the documentation on end points that I have read state that you are limited to your local network There are no TLS libraries in the iotivity-constrained repo Thiago Macieira said in a previous post that "I advise against making a constrained device talk directly to the Internet and the cloud." Can anyone confirm one way or another whether a constrained device can talk to the cloud? If it can't, is this a feature that may be included at some point in the future? ________________________________ CONFIDENTIALITY NOTICE: This is a transmission from Homedics, LLC, and the information contained herein, and all attachments are privileged, confidential and proprietary information intended only for the addressee. If you are not the addressee, you are hereby notified that any disclosure, dissemination, distribution, copying or use of the contents of this transmission and any attachments is not allowed and expressly prohibited. If you received this transmission in error, please destroy it and notify Homedics, LLC immediately at (248) 863-3000. CAUTION: Internet and e-mail communications are the property of Homedics, and Homedics reserves the right to retrieve and read any message created, sent and received. Homedics reserves the right to monitor messages by authorized Homedics' associates at any time without any further consent. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170531/cd6bf4ee/attachment.html>
