Page 1 of 1
Unclear setup of ThingSpeak with mega-20180822
Posted: 24 Aug 2018, 22:06
by fjk
Dear folks!
Admittedly I am a total beginner both in ESPeasy and ThingSpeak.
Under certain circumstances my problem can be easily solved with a simple tip.
It is simply unclear to me what I have to enter under "ThingHTTP Name:". This parameter is not mentioned in the official "EasyProtocols".
- Screenshot 2018-08-24 22.04.23.png (80.51 KiB) Viewed 5931 times
thanks in advance
/FJK
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 25 Aug 2018, 03:22
by lyndondr
I don't use the "ThingHTTP Name:" but for some reason awhile back I had to stop using the Hostname and use the IP address. The IP address in your post is what I use.
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 25 Aug 2018, 11:33
by fjk
thank you ... I changed to IP ... I set the "ThingHTTP Name:" to label set for the data field on ThingSpeak, but if this relevant at all, I don't know
meanwhile I see some data, but receiving quite a lot of ThingSpeak related errors :
=> Timeout while reading input data!
/FJ
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 25 Aug 2018, 16:09
by TD-er
There is some issue with ThingSpeak in which it is changing it's IP.
So then you have to remove the controller and re-configure it.
I'm working on an issue and this morning I merged a pull request that may also fix this issue.
If you are having issues to even make the first setup, than this is not relevant to the issue you're experiencing.
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 26 Aug 2018, 10:11
by fjk
Thanks, so if I use one of the upcoming ESP builds I shouldn't have this problem with ThingSpeak anymore, right?
/FJK
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 26 Aug 2018, 12:21
by TD-er
Last build has the patch for connecting to a client. See this merged pull request:
https://github.com/letscontrolit/ESPEasy/pull/1672
In short, the result of the connect call was not checked properly, so regardless the result, it was considered successful.
There was already a mechanism to cache the DNS lookup (the IP-address) and on failed connect force an update of this cache. But if the result of the connect never "failed" (due to incorrect check of the return value), this mechanism never is triggered.
So this patch will address the problem of Thingspeak that it is changing IP every now and then, resulting in failed uploads to ThingSpeak.
If you cannot even make an initial connection, then there is another issue. (maybe not set DNS or gateway when using static IP)
Re: Unclear setup of ThingSpeak with mega-20180822
Posted: 26 Aug 2018, 12:28
by fjk
Understood, thank you very much.
/FJ