Since about 22:00 packets can not be delivered (ICMP destination unreachable messages), the Wiki and API respond with ‘504 Gateway Time-out’ and InfluxDB with ‘Could not connect to http://croft.thethings…’
Thanks for reporting - we were migrating from InfluxDB to MongoDB (because of missing packets).
It should be all up again.
When querying the API for packets from one node I’m getting results for all nodes:
Get for: http://thethingsnetwork.org/api/v0/nodes/02012902/
Result:
GET /api/v0/nodes/02012902/
HTTP 200 OK
Vary: Accept
Content-Type: application/json
Allow: GET, HEAD, OPTIONS
[
{
“_id”: “56451ff39180c305f11fbc24”,
“node_eui”: “02013101”,
“data_json”: {
“temperature”: 19.18,
“node”: “THINGSIO_1”
},
“data_raw”: “gAExAQIAAQAGYm6YGoug2hMN1MuDh/Sz8KF0sNeKLDNfA9vgRhtFdn5hfGuGwvdCfU+9Kp4v”,
“data”: “eyJub2RlIjoiVEhJTkdTSU9fMSIsInRlbXBlcmF0dXJlIjoxOS4xOH0=”,
“gateway_eui”: “1DEE15E85FA7DCEF”,
“data_plain”: “{“node”:“THINGSIO_1”,“temperature”:19.18}”,
“time”: “2015-11-12T23:25:39.572”
},
{
“_id”: “56451ff39180c305f11fbc23”,
“node_eui”: “5A480107”,
“data_raw”: “QAcBSFoA2wIBKaRG2ZM00joj/EsGNzk=”,
“data”: “dHRuLXpoLTgwMg==”,
“gateway_eui”: “FFFEB827EBF7E594”,
“data_plain”: “ttn-zh-802”,
“time”: “2015-11-12T23:25:39.428”
},
…
I see the same, its not filtering on the node_eui
Andrew
Now it seems to be filtering but is showing results for a different node.
nope, not yet filtering
fixed (renamed fields issue)
nice! it works now
*still the limit filter is giving a 500 error
I am testing this API with two Home Automation packages. On the call:
http://thethingsnetwork.org/api/v0/nodes/
I still do get Server Error (500), also for specific Node IDs
Yes it noticed it too, we are working on it.