Reply to myself, additional information. Making it even more confusing.
I have tested the mote against another gateway and it showed up (ttn hilversum angry bytes). Coming home i issued another uplink packet and that did show up on the node api and the gateway api (ttn hilversum zeeheldenkwartier)
"gateway_eui": "FFFEB827EB5939CD",
"data_raw": "QAEA4AIANABNa8/JtsxVp/nTX3Lc",
"data_plain": "984008\u0000\u0000",
"rssi": -71,
"time": "2016-03-25T15:39:55.025Z",
"datarate": "SF8BW125",
"snr": 11.2,
"node_eui": "02E00001",
"data": "OTg0MDA4AAA=",
"frequency": 868.3
and on the gateway api it showed following (little time-difference??)
"datagramsreceived": 0,
"ackratio": 100.0,
"rxforwarded": 1,
"datagramssent": 0,
"time": "2016-03-25T15:40:09.574Z",
"altitude": 6.0,
"eui": "FFFEB827EB5939CD",
"rxok": 1,
"latitude": 52.20985,
"longitude": 5.15226,
"rxcount": 1
Strangely now it showed in the packet logs as a CRC_BAD?? Or not even at all, which is quite strange since something came through the gateway and became visible on the API, but not on the packet log?
I assume that in the packet log it is the first line (of selected text) as there is mentioned the SF8 datarate. (as the node api also tells me it was a sf8 communication). The rest of packet log shows SF7.
Anyone?
