You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a screenshot for simple-pt-example device:
As you can see there's only one Device deregistered, and that's 1h after the first one, probably because:
#defineMBED_CLOUD_CLIENT_LIFETIME 3600
The same stands true for pt-examples 3 devices.
The text was updated successfully, but these errors were encountered:
It's true that the device will not be deregistered until the Edge lifetime end up, the cloud is informed of the de-registered devices in the update register message, which occurs with the lifetime interval. So, it's behaving as documented as far as I can tell.
de-registers the device in Device Management Portal.
So, the plain client has support for this, and it works. Edge does not do it. Why?
We need to keep live tracking of our devices in our Webapp, and querying Pelion portal is the way to go, in my opinion.
Since this is not working in Edge, the workaround would be to send a heartbeat, at a few seconds interval, to know if a/every device is active or not. This would consume(/bill) Pelion Portal transactions, which is not convenient.
Hi,
Using
pt-example
orsimple-js-examples/simple-pt-example.js
from https://github.com/ARMmbed/mbed-edge-examples, will not make devices deregistered in Pelion Portal.Here is a screenshot for

simple-pt-example
device:As you can see there's only one Device deregistered, and that's 1h after the first one, probably because:
The same stands true for
pt-example
s 3 devices.The text was updated successfully, but these errors were encountered: