1. Instantly
2. No (but will be soon. Server holds 10 min interval data, with only the last measurement being recorded, while the devices send data every 1 min. Instead of holding only the 10th measurement, an average will be implemented for all 10 values).
3. Yes
I suspect this is related to the other issue you’ve observed. I’ll need to investigate it further and report back.
I found that some city names have bad encoding in the JSON data published here:
“id”:”1100000E”, “city”:”Timi?oara” (this also occurs for other ids)
“id”:”12000045″,”city”:”KC4%97dainiai”.
Hi Radu, I’m trying to figure out the actual time of the timestamp in data reports… For example I downloaded data at 08:49 on 25 March 2017 and it reads:
At 09:49 I’ll do another download to help me figure out the time correlation… but, I’ll probably still need some guidance, not knowing at what time the data capture is in relationship to the download time… thought I could help myself by capturing the joined date/time, but it reflect today’s info… 25 March.. my uptime is 253080s (that’s seconds, right?)
Those are standard Unix timestamps (seconds from the beginning of Unix calendar, 1970-01-01T00:00:00Z).
Using this online converter the timestamp 1490410770 translates to 03/25/2017 @ 2:59am (UTC).