Ayyoob,
Could you tell me which piece of code in the Raspberry Agent store the client
information of the device type?
And if I create my new device plugin with "cdmf-devicetype-archetype”, does the
result codebase will include my device type client information in the agent
codes?
Thanks.
Hi Jason,
Device does not require a username/password to refresh the token rather it
requires a client Id and client secret[1]. For our sample use cases we can
either create a clientId and client secret per device or per device type.
In the raspberry pi example the client information will be
Hi Ayyoob,
Thanks. I am testing to change the AccessTokenDefaultValidityPeriod to 84600
seconds (about one day). I want to confirm with you whether my understanding of
the following configuration attributes is correct.
is used when user login in the
application and get the client_id and
Hi Jason,
This happens when the OAuth token is expired for the device. In the IoTS
alpha we have not implemented the renewing the token with refresh token
part, however this has been implemented in the master. One way of having a
continuous connection for the samples in alpha pack would be to
I got the following error logs from IoTS:
==
[2016-08-05 08:57:06,466] ERROR - MessageMetricsHandler Connection reset by peer
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at
Hi all,
I downloaded a raspberry pi agent from IoTS 1.0.0 alpha, ran the raspberry pi
agent and uploaded the temperature data successfully. But after I disconnected
the agent for a while, the MQTT connection could not be setup again. Can anyone
help me for this? Thanks.
MQTT_LISTENER:
