I tried again now and I still get calls every second in the get callback
By the way, maybe it's unrelated, but should I develop my devices using the plgdev branch for iotivity-lite? I found that since I updated iotivity-lite with the lastest version in master the plgdev app stops discovering my device (I fixed it by just reverting the merge)
There are some new breaking changes which we didn’t integrate yet to our sdk.
@DavidMarquezF From logs I see that the device
b4fead3a-72af-4043-56e8-90590de03c92 doesn't send response for the PING requests. So cloud close connection. After that device reconnects again to the cloud and then cloud start obsere all resources of the device. This is why you see lot's of GET requests.
I digged a bit deeper into it (I'm still not done) but I wanted to share what i found. Apparently I don't get a call from the server each second, it's the device that has the internal periodic observation setup. When the device is initialized oc_ri_invoke_coap_entity_handler is called for each resource (as you pointed out). However, since these resources are set up as periodic observables (every second), iotivity polls internally every second the resources. These send their info to the cloud.
I tried using wireshark to debug the connections (I set up a local docker as explained in https://plgd.dev/guide/getting-started/1-deploy.html#bundle) but I can't seem to make it decrypt the connection with the private key. However, I tried setting some debug points and it does look like it responds with a PONG.
If I remove the periodic observation every second from the resources this won't happen. But then I'm curious as how you would be able to set a periodically observable resource in the cloud conditionally (let the user decide if the resource should be updated every second or not), with the notification switch in the web UI for example.
@DavidMarquezF For cloud it is expected that all resources are observable. It means when any change occurs on any property of any resource, devices sends a notification to the cloud with that resource. You can trigger it via
oc_notify_observers(). Pulling mechanism is inefficiency so we don't want to support it.
I had to make a change to IoTivity, there was a compiling error, please take a look at iotivity/iotivity-lite#34 and make a better fix that actually compiles
I have asked to shut down gitlab asap, because I think it is overwriting github.
nope, only Kishen, VTM and Rami
@Dr_rami_twitter
Commit something to gitlab if it will be mirrored, or vice-versa (if it will be again overwriten by gitlab - lost).
not sure if gitlab does another sync that it might get lost again..
I just remove account which probably does the sync.
(but he is not awake just yet)
anyway the first part of building otgc on linux is working again
and the master is now building correctly, although we need a fix for at link error to reinstate that part of the cloud code
there is now a CI job on iotivity that checks linux otgc build
<<<<<<< jakarta
oc_cloud_clear_context(ctx);
cloud_store_initialize(&ctx->store);
cloud_manager_stop(ctx);
ctx->last_error = 0;
ctx->store.cps = 0;
cloud_store_dump(&ctx->store);
master
hi, I'm a newbee and just tried setup this https://plgd.dev/quickstart/deploy-plgd-cloud/ in my aws cloud
I'm trying open the browser acter run the docker but nothing happen
really appreciate for the advice. thank you
hi, I'm a newbee and just tried setup this https://plgd.dev/quickstart/deploy-plgd-cloud/ in my aws cloud
Hello. Are you deploying this bundle image in the AWS? Bundle is supposed to be deployed on your local PC. Of course you can deploy it in AWS but then this deployment guidline won’t help you with set up of load balancer and so on. Do you have all your ports open? Can you telnet to 5684 5683 and 443 ?
1 reply