I have a test application in the office that uses Data Storage as it’s primary retrieval means, it calculates the timespan relative to its last retrieve so I know this works. As I use a calculation, I always request a number of seconds, so you may want to try 3600s or 604800s
Usually I find people (clients) get a 204 when the device id isn’t quite right.
In the first instance, can you COPY and paste what you are using, then change the key AND tell us what environment you are using - OS, programming language etc
And whilst we are looking at that, can you confirm you have tried using the Swagger online tool linked from the integration for testing? If you go in to the Data Storage integration there is a link called “go to platform”
Hey Nick, thanks responding. I can confirm I have been using the Swagger online tool, which provided me with the curl command for a device with ID dl-pr26_5100
That’s weird. Any chance your payload format decoder is outputting an attribute called device_id? Or, if that is actually outputting device_id_1, then it seems the device id in TTN Console is simply 5100? What if you use 5100 in the URL?
I can’t tell if ruchir_dl-pr-26_5100 is some very specific application name or a combination but it definitely fails my sniff test.
And 5100 is clearly wrong, it should be dl-pr26_5100
PS, if you follow the go to platform link from the integration, it would setup most of this in Swagger, all you have to do is hit the authenticate button and add your key.
You could also use the access key you’ve got for the Storage Integration, to subscribe to the uplink data using an MQTT client. That will show you what is in the JSON attribute payload_fields. (And I’m quite sure you’ll see a field device_id that confuses the Data Storage query.)
Hey Arjan, I used your example to setup an MQTT client. When I use your command and my access
the program waits without receiving any uplink data even though the sensor sends data every 10 minutes. I confirmed with the Swagger UI that data is still being sent for the sensor. Do I have to update the topic field of the command to something other than -t '#'? I’m currently trying to get access to the console to look at the decoder as well. Thanks!
That # is a wildcard that will show you all messages. So no, no change needed for that. I cannot explain why it doesn’t work; it really should work the correct application id and access key, assuming you’re using EU868. If not, then the server name needs changing too.