Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ondrej Tomcik
    @ondrejtomcik
    @jkralik can he changed it using env variable from test to plgd?
    Wouter van der Beek
    @WAvdBeek
    ok, i just pressed the big red thing which is a device reset button.
    something happend on the device: cloud manager status: Failed
    but it also says that it installed successfully the PKI certificate chain.
    Ondrej Tomcik
    @ondrejtomcik
    yes. problem is on our end. Already created MR
    Build takes pretty long, I will give you new plgd cloud image in 40 mins.
    Wouter van der Beek
    @WAvdBeek
    ok, let me know when i can download it with docker
    Ondrej Tomcik
    @ondrejtomcik
    I will give you a new tag.
    Wouter van der Beek
    @WAvdBeek
    pretty cool by the way...:)
    Ondrej Tomcik
    @ondrejtomcik
    your satisfaction can be reflected in opencollective :-D
    https://github.com/plgd-dev/cloud
    https://opencollective.com/plgd-cloud
    Ondrej Tomcik
    @ondrejtomcik
    OR even better, contribute with documentation - how to start with secure and unsecure device together with bundle and plgd mobile app! That would be awesome!
    Ondrej Tomcik
    @ondrejtomcik
    @WAvdBeek plgd/bundle:v2next-d55f695
    let me know if it works
    you need to reinit your mob app
    Wouter van der Beek
    @WAvdBeek
    image.png
    i am still debugging the update.. it looks like that plgd is checking the input and somehow this is failing the input check?
    Ondrej Tomcik
    @ondrejtomcik
    Hm. Could you please go to developer console of your browser and check full response for that update request? If there are more information about the error.
    Wouter van der Beek
    @WAvdBeek
    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)
    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.
    Wouter van der Beek
    @WAvdBeek
    ok, this was not a plgd issue... issue is solved, e.g. update is working nicely from plgd to the device.
    i am OoO tomorrow, so i will try the security solution next week.
    Ondrej Tomcik
    @ondrejtomcik
    @WAvdBeek I was able to replicate your issue with update as well - such an error is returned when such a property is not editable - or simply when IoTivity-Lite rejests the request.
    Enjoy your time off and hear you on Monday.
    Kyle Haefner
    @khaefner
    @ondrejtomcik regarding documentation, Clarke and I are working on an article for embedded, which will be pretty much a user guide on how to do all of this, it should not be a huge lift to update the documentation.
    Soneca-ii
    @Soneca-ii
    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?
    Ondrej Tomcik
    @ondrejtomcik
    @Soneca-ii do you mean with plgd mobile app? CLOUD=0 has nothing to do with ownership transfer. It enables capability to onboard device to the cloud.
    Wouter van der Beek
    @WAvdBeek
    Hi Ondrej, the onboarding securely to the cloud now works.. I tried it out with a fresh instance of docker & device and it worked seamlessly!
    i can now control the device securely from the cloud.
    the app can't control the device?
    Ondrej Tomcik
    @ondrejtomcik
    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 :)
    Wouter van der Beek
    @WAvdBeek
    Ok thanks, I hoped I missed something. I agree that the app is simple and works correctly and simple for onboarding.
    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)
    Ondrej Tomcik
    @ondrejtomcik
    @WAvdBeek could you please describe the flow, what needs to be done to onboard devices that are talking to the cloud proxy? How are these devices discovered? Are they onboarded separately or is it enough to onboard cloud proxy itself?
    I didn’t track this topic in the OCF, so feel free to point me to some sequence diagram in the KAVI.
    Wouter van der Beek
    @WAvdBeek
    It is CR2599
    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.
    Ondrej Tomcik
    @ondrejtomcik

    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

    Soneca-ii
    @Soneca-ii
    @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?
    Ondrej Tomcik
    @ondrejtomcik
    @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.
    Ondrej Tomcik
    @ondrejtomcik
    @WAvdBeek are you around?
    Wouter van der Beek
    @WAvdBeek
    Hi Ondrej, i am around, but not working on this right now.
    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.
    Ondrej Tomcik
    @ondrejtomcik
    @WAvdBeek have a different topic. IoTivity Lite MRs. Any idea when somebody will find some time to review them?
    @WAvdBeek small wrapping in main will make it running in console.
    Wouter van der Beek
    @WAvdBeek
    hopefully next week, I have asked Kishen to find time tomorrow to release 2.2.2. that will unblock quite a bit of that backlog.