ThingSpeak charts and widgets displaying incorrect data
For the past several days I have been experiencing a problem with data visualization on two of my ThingSpeak channels.
The data appears to be uploaded and stored correctly, and new entries are still being added to the channels. However, the visualizations are not working correctly.
The standard Field Charts show only a very small number of data points instead of the normal continuous measurements. Most of the points are compressed on the left side of the chart, while one or a few points appear far to the right and are connected by long straight lines. The time axis is also incorrect and sometimes shows repeated dates such as “01 Jan”.
The numeric widgets are affected as well and display incorrect values. Some custom visualizations also remain blank or fail to load.
The problem appeared suddenly and affects two separate channels which had previously been working correctly. I did not make any significant changes to the channels before the problem started.
This seems somewhat similar to the ThingSpeak chart/timeline issue reported in June 2026, when charts were displaying incorrect time ranges and the DAYS/RESULTS settings were not working correctly. However, my current problem also affects numeric widgets and custom visualizations, and the charts show incorrect dates and strangely positioned data points.
Could this be a regression or a similar issue with the ThingSpeak visualization system?
Has anyone else experienced the same problem recently?
7 Comments
Time Descending
Sorry to hear things arent working so great. I checked one of my channels, and the field charts thre seem to be working fine. Sucessfully changed the days setting. Is your channel public? If so can you share it? Is anyone else seeing this issue?
I think I see the issue. Somehow your channel has been updated with data very far in the future. For example, the latest point I see in your chart is labelled from the year 2054. I've done this accidentally myself before. Presumably, you are updating your channel using "created at" parameter instead of using the system timestamp provided when you update without this parameter.
Perhaps your microprocessor had an overflow and placed odd digits in the timestamp.
There are a few fixes that I can think of.
- Download the data, then delete the channel feed and start clean
- Download the data, delete the offending points, clear the channel feed, and upload the old cleaned data.
- Leave the data as is, but use the start and end parameters from the charts api in your call. You can delete the field charts on you channel view and replace them with custom visualizations that use the charts API or another custom MATLAB visualization.
- Start writing to a different channel.
Unfortunately, there is no selective delete available in ThingSpeak.
i have checked csv file, fpund couples line wigh wrong year. dont use 'created at'. my microcomputer send package to thingspeak wothout time stamps.
sorry for confiusing. i check the latest version and fpund out tjat i was mistalen earlier. l am actually using tjr created at parametr when sending data to Thingspeak. Each measutement are stotrd with ots time stamp and that timr stamp is later semt to Thingspeak. So the incorrect dates in the channel may indeed originated from the timestamp gemerated by the device befor the data are uploaded.
I am now cheking tjr code responsible for generating and formatting these timestamps to find out why occasionaly dates such as 2010, 2037, 2053 or 2054 appear in the data
can you share the code that is running on your microprocessor? we may be able to provide insights based on that .
Sign in to participate
Tags
