ed to load resource: the server responded with a status of 503 ()
utils.js:65 Uncaught (in promise) TypeError: t is not a function
at ft (utils.js:65)
at things-details-page.js:107
at u (runtime.js:63)
at Generator._invoke (runtime.js:293)
at Generator.throw (runtime.js:118)
at r (asyncToGenerator.js:3)
at l (asyncToGenerator.js:29)
utils.js:65 Uncaught (in promise) TypeError: t is not a function
at ft (utils.js:65)
at things-details-page.js:107
at u (runtime.js:63)
at Generator._invoke (runtime.js:293)
at Generator.throw (runtime.js:118)
at r (asyncToGenerator.js:3)
at l (asyncToGenerator.js:29)
the 503 is intentional..
not sure yet if this is a plgd problem. trying to debug with devicespy and i also see things that are weird.
i am OoO tomorrow, so i will try the security solution next week.
Hi, a quick question. If creating an iotivity-lite server with CLOUD=1 ( secure and pki also) and placing the certificate from the PLGD I manage to onboard the device. Is there some workflow that I can do the same with an iotivity-lite server created with CLOUD=0 and configure it during the onboard?
i can now control the device securely from the cloud.
the app can't control the device?
Hey @WAvdBeek
No, the application is just transfering the ownership to the authenticated user and setting the coapcloudconf resource. The API of the plgd.mobile supports it, but UI would have to be developed. To have at least easy onboarding we did this simple one button plgd app :)
No, the application is just transfering the ownership to the authenticated user and setting the coapcloudconf resource. The API of the plgd.mobile supports it, but UI would have to be developed. To have at least easy onboarding we did this simple one button plgd app :)
the issue that i have now is that I have to onboard devices that are talking to the cloud proxy, hence I need an OBT that does cloud setup and onboarding.. reading the email of Kishen that does not yet exist. So i will add that code in the iotivity OBT (commandline).
to make this work I need to have the data to onboard the plgd cloud, e.g. what is the security information (I only supplied the unsecure info as work around in the device that talks to the plgd cloud)
I didn’t track this topic in the OCF, so feel free to point me to some sequence diagram in the KAVI.
the cloud proxy (my own code, not yet released) can be onboarded to plgd with plgd app.
the issue is then that the client of the cloud proxy that talks to the OCF devices needs to be configured, hence the plgd app is not doing that.
reading Kishens email (you are cc'ed) Kishen indicates that this code does not yet exists.
You could extend mobile app, or write your own console app which does the same as mobile app + additional required requests. It's fairly simple, but not sure if you want to use our OCF CoAP Client.
This is the library (for now we call it SDK but it will be sooner or later renamed) - https://github.com/plgd-dev/sdk
and here is the simple client using that SDK, which methods are invoked by the mobile app.
https://github.com/plgd-dev/plgd.mobile/blob/master/ocfclient/OCFClient.go
@ondrejtomcik Hi, thanks for the answer. Sorry for the late reply but had some trouble with the local setup. I have successfully connected the cloud device (non-secure and secured). Meantime I have another question, could you please share some example where it would be possible to use cloud2cloud between two PLGD bundle deployments? Is this even possible using the test bundle provided?
@Soneca-ii Hello. C2C is not part of the bundle. Currently the priority is pretty low to include it there as we are working on another topics.If you want to speed it up rapidly, you can contribute or we can assign one developer to this task, but this would be considered as paid support.
I have created the mediator in lite (obt) as preliminary code. however I still have issues with having the correct access and something else is wrong (e.g. code crashes)
does the go code work somehow in command line mode? adapting the android app is currently too much work to proof that the full chain : local device - cloud proxy - plgd can be set up. we know that all individual components already can be set up.
@WAvdBeek small wrapping in main will make it running in console.
if we merge now, then we need to do a full run of CTT tests again, hence there is order involved to avoid creating work.
Hello, I'm starting to develop an app and was looking at using plgd with the esp32. I set the OC_DEBUG flag in order to see if I could find any information on why PKI certificates were not working. However, once I turned on OC_DEBUG, the plgd mobile phone app couldn't discover the device (while the OTGC app did). Could it have something to do with timeouts (since while debugging it's writing a lot of stuff in the serial port, so it wastes more time) or do you think it's something else?
Discovery is in the mobile app hardcoded to 5seconds - https://github.com/plgd-dev/plgd.mobile/blob/master/lib/services/ocfClient.dart#L87 .
What you can try is to build a simple go client to call the discovery on your own with bigger timeout.
What you can try is to build a simple go client to call the discovery on your own with bigger timeout.
This can help you. Just create your own go file and do some copypasting.
https://github.com/plgd-dev/plgd.mobile/blob/master/ocfclient/OCFClient.go#L29-L87
https://github.com/plgd-dev/plgd.mobile/blob/master/ocfclient/OCFClient.go#L29-L87
