Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 18599

Re: IoTKit activaction failed: "could not be updated  Unauthorized"

$
0
0

Just tried on Edison

# configure_edison --version
68
# iotkit-admin -V
1.5.0

 

activation worked fine - I did

iotkit-admin initialize
iotkit-admin reset-components
id=$(iotkit-admin device-id | awk '{print $(NF)}')
echo $id

 

add device with the given ID, i.e. [$id below meaning value of that variable]

ID = $id

Gateway = $id

Name = Edison

 

activation code: goto "Account" -> "Activation Code"

 

then with that code

iotkit-admin activate <activation code>

 

No issues with activation on my side

 

Now the board should be displayed "active" on dashboard.us.enableiot.com.

afterwards:

systemctl enable iotkit-agent
systemctl start iotkit-agent
# systemctl status iotkit-agent
● iotkit-agent.service - iotkit-agent
   Loaded: loaded (/lib/systemd/system/iotkit-agent.service; enabled)   Active: active (running) since Thu 2014-09-25 19:32:15 UTC; 22min ago
Main PID: 343 (node)   CGroup: /system.slice/iotkit-agent.service           └─343 node /usr/bin/iotkit-agent


Sep 25 19:32:15 edison systemd[1]: Started iotkit-agent.
Sep 25 19:32:17 edison iotkit-agent[343]: 2014-09-25T19:32:17.946Z - info: Sending attributes...
Sep 25 19:32:19 edison iotkit-agent[343]: 2014-09-25T19:32:19.920Z - info: Starting listeners...
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.056Z - info: MQTT listener started on port:  1884
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.061Z - info: TCP listener started on port:   7070
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.067Z - info: UDP listener started on port:  41234

 

I initially created the board with wrong device id. Activation worked as well but I couldn't register components and hence wasn't able to send data. Also got a message like "Authorization failed". After correct activation of the board registering components and sending data works fine - in the example belo

 

# systemctl status iotkit-agent
● iotkit-agent.service - iotkit-agent
   Loaded: loaded (/lib/systemd/system/iotkit-agent.service; enabled)   Active: active (running) since Thu 2014-09-25 19:32:15 UTC; 22min ago
Main PID: 343 (node)   CGroup: /system.slice/iotkit-agent.service           └─343 node /usr/bin/iotkit-agent


Sep 25 19:32:15 edison systemd[1]: Started iotkit-agent.
Sep 25 19:32:17 edison iotkit-agent[343]: 2014-09-25T19:32:17.946Z - info: Sending attributes...
Sep 25 19:32:19 edison iotkit-agent[343]: 2014-09-25T19:32:19.920Z - info: Starting listeners...
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.056Z - info: MQTT listener started on port:  1884
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.061Z - info: TCP listener started on port:   7070
Sep 25 19:32:20 edison iotkit-agent[343]: 2014-09-25T19:32:20.067Z - info: UDP listener started on port:  41234
Sep 25 19:32:41 edison iotkit-agent[343]: Attributes sent
Sep 25 19:32:57 edison iotkit-agent[343]: 2014-09-25T19:32:57.758Z - info: Submitting:  n=temp, v=45
Sep 25 19:32:59 edison iotkit-agent[343]: 2014-09-25T19:32:59.466Z - info: Response received:  response=none detail, status=0

 

"attributes sent" is the registration of the temperature.v1.0 component "temp" via iotkit-agent. Afterwards data (temp = 45) has been sent.

 

Data accessible ok in dashboard

 

So in summary: works for me right now


Viewing all articles
Browse latest Browse all 18599

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>