It seems that data is not recorded

Hello, since this morning (around 8h00 am, Paris time), data sent by my iots is not recorded. I have not changed any settings on my iots and my internet connection is OK. On the page with my channels, it seems that the channels are updated because I see that the "updated" times are evolving. Is there a problem today with Thingspeak?

[Roland Morla]

Hello, it seems that the problem has come again around 20h00 Paris time (12/152023).

[Christopher Stapels]

My channels seem to be fine, and some public ones I watch are ingesting normally up to now (23h49 paris time).

The status page indicates ThingSpeak is fine at present. Feel free to post again if you continue to see the issue. If we detect a system wide event Ill post an update.

[Roland Morla]

The problem is still present. 02h35 paris time. Data from 6 iots dispatched on 3 different channels are not updated on the servers. Some other iots using my own server are ok as well as my internet access (I could not write this comment if was not the case).

[Roland Morla]

Hello, I think I found the problem. In order to save battery on my iots I used a less secure set of cipher algorithms for TLS, but it seems that from yesterday thingspeaks servers demand more secure algorithms. I tried a patch suppressiong the "espClient.setCiphersLessSecure();" line in my code and my test iot can again connect. So it seems I will have to reprogram my iots.

Would you please confirm that you changed security requirements for TLS on your servers? Best Regards.

[Christopher Stapels]

What hardware and software are you using?

[Roland Morla]

Hello, I am using esp8266 microcontrolers and home made software using the arduino IDE and the librairies that go with it. Best Regards.

[Christopher Stapels]

Are you using the ThingSpeak library? It works nicely with ESP8266.

https://github.com/mathworks/thingspeak-arduino

[Roland Morla]

No, this is my own (dirty) code. My code is rather old and I did not know there were such a library at the time I wrote it. In fact maybe it even did not exist. As I told you before, I tried to save as much as battery power as I could, and I found a significant difference of execution time between the "normal" and the less secure version of cipher algorithms, so I decided to use the less secure version. ( more security is good, but who cares about the temperature of my freezer ? ). Anyway I took sometime this week-end to recompile my code and re flash my iots and everthing is alright now. Best Regards

Answer 1

[Christopher Stapels]

There was a short downtime for ThingSpeak on July 19 from approximentally 6 am UTC until 10am. You can always see the present status of MathWorks online services here.