Why in thingspeak you only read data as multiple fields?

Hi Team

Who can explain to me as to why in thingspeak, you only have limited option to chose either read one field? But your data format on JSON or CSV show all feeds not one you wish to see? I am having that issue now with my CSV file format, on my URL i am passing correct request as field 1.json format. But the file format seem to give me all feeds.

Temperature

Illuminance

Button-State

// Downloading file into csv/json format.

$(document).ready(function() {

$("#download").click(function() {

var count = 0;

if($('#temperature').prop('checked')) count++;

if($('#illuminance').prop('checked')) count++;

if($('#button-state').prop('checked')) count++;

if(count > 1) {

window.location.href ='https://api.thingspeak.com/channels/899906/feeds.json?start=2019-11-14%2019:11:14&end=2019-11-18%2019:11:18';

}else{

// checking for one field being checked.

if($('#temperature').prop('checked')) count--;

if($('#illuminance').prop('checked')) count--;

if($('#button-state').prop('checked')) count--;

if(count < 1) {

window.location.href = ' https://api.thingspeak.com/channels/899906/fields/1.json?start=2019-11-15%2019:11:15&end=2019-11-18';

}

});

Hi Team

I had a discussion with team from thingspeak, so they gave me an idea to this issue yesterday. Well perhaps its quite plausible to share amongst the team here so if one mate may, likely to experience such issue as this to their problem. Well the issue was double, see the code below for solution and please note the code was amended by me after follow their documentation which i still argue is still not enough.

// checking for one field entry to read.

$(document).ready(function() {

$('#temperature').click(function() {

var xcount = 0;

if($('#temperature').prop('checked')) xcount--;

if(xcount < 1) {

window.location.href ='https://api.thingspeak.com/channels/899906/fields/1.csv';

}

});

// checking for two field entry to read.

$(document).ready(function() {

$('#download').click(function() {

var ncount = 0;

if($('#illuminance').prop('checked')) ncount--;

if(ncount < 1) {

window.location.href = 'https://api.thingspeak.com/channels/899906/fields/2.csv';

}

});

NB: the URL is changed simply because thingspeak API in REST has to read this constraint as a content, whether you passing this parameter as GET or POST. So i was looking for this issue, the code is working and seem to follow a bit about this platform REST API.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Guest User6y ago
Hi Team

I had a discussion with team from thingspeak, so they gave me an idea to this issue yesterday. Well perhaps its quite plausible to share amongst the team here so if one mate may, likely to experience such issue as this to their problem. Well the issue was double, see the code below for solution and please note the code was amended by me after follow their documentation which i still argue is still not enough.

// checking for one field entry to read.
$(document).ready(function() {
$('#temperature').click(function() {
var xcount = 0;
if($('#temperature').prop('checked')) xcount--;
if(xcount < 1) {
window.location.href ='https://api.thingspeak.com/channels/899906/fields/1.csv';
}
});
});

// checking for two field entry to read.
$(document).ready(function() {
$('#download').click(function() {
var ncount = 0;
if($('#illuminance').prop('checked')) ncount--;
if(ncount < 1) {
window.location.href = 'https://api.thingspeak.com/channels/899906/fields/2.csv';
}
});

});
NB: the URL is changed simply because thingspeak API in REST has to read this constraint as a content, whether you passing this parameter as GET or POST. So i was looking for this issue, the code is working and seem to follow a bit about this platform REST API.
0