The cloud API doesn’t seem to parse DOUBLE values correctly. Here’s a quick sample app that demonstrates the problem: double test = 0.5; void setup() { Spark.variable("test", &test, DOUBLE); } When I request this variable through the cloud API, the response is: { "cmd": "VarReturn", "nam…

Not that long ago the double type wouldn’t even compile properly, so there is some progress there :wink: However last I heard the only Spark.variable type officially supported was INT. I’m sure that’s in process of changing as well!

It seems that strings work pretty well: char mystr[6]; void setup() { Spark.variable(“mystr”, &mystr, STRING); } void loop() { sprintf(mystr, “%.2f”, 12.34); }

Yep, I’m using that as a workaround in the meantime, but it would be nice to not waste cpu/memory sprintf()ing the double value into a string buffer every cycle, especially since the cloud API does have a field for double values, it just doesn’t work :stuck_out_tongue:

I believe @Dave and @zachary are working on the parsing issue. I would confirm with them here.

Hey All, @mohit is right, @zachary and I are working on this and I think the plan is to try and rollout a fix this week. When that happens the “temporary” fields will disappear from the API responses, and the result type should just accurately reflect what you returned. I’m guessing “double” is f…

Hey all, Is it possible that there are also problems with the strings at the moment ? I just received my core and i tried a few simple things like accessing the variables … and by using the following code i just tested a few things : double temperature = 0.0; int intTemperature =0; char mystr…

@enicky String variables were working just a couple days ago… and INT should work! I tried your code… all seemed broken at first… no more Kegerator on Friday at Spark!!! xD But then I remembered something about length of funcKey length max 12 characters…and even though the docs don’t say the same f…

@BDub Thanks!! the int’s worked indeed. But i was trying to pass some floats, doubles, … nothing seemed to work … But I’ll keep that in mind : maxLength = 12 ;o) Really thanks for the info!!

oh my bad, I was using “temperature” instead of “temperatures” for your INT. So only varKey’s greater than 12 break, not all of them.

would love to hear if you manage to pass a float through the API. I just get garbage as it seems now. INT works nicely though.

Cloud API incorrectly parsing DOUBLE values

Cloud

sjunnesson January 8, 2014, 2:02am 12

found a temporary solution here

Topic		Replies	Views
Trouble reading DOUBLE in javascript sdk Cloud	0	815	July 5, 2015
Strange results using and returning doubles [SOLVED] Troubleshooting	9	1651	February 15, 2014
GET reads all return same variable value Cloud	7	3745	January 5, 2014
Spark.variable() STRINGS larger than 9 chars issue [SOLVED] Cloud	33	9237	July 15, 2014
Function doesn't return correct values? Firmware	12	4872	December 31, 2013

Cloud API incorrectly parsing DOUBLE values

Related topics