メインコンテンツ

結果:

When making a ThingHttp request via POST, the server response header does not include: "Content-Length:". Instead it is using "Transfer-Encoding: chunked". This makes it dificult to confirm that the entire response has been recieved. Any way to change this?
21:09:55.812 -> POST /apps/thinghttp/send_request HTTP/1.1
21:09:55.812 -> Host: api.thingspeak.com
21:09:55.812 -> Content-Type: application/x-www-form-urlencoded
21:09:55.812 -> Content-Length: 60
21:09:55.812 ->
21:09:55.812 -> headers=false&api_key=[removed]&message=Arduino Reset
21:09:55.906 ->
21:09:57.040 ->
21:09:57.040 ->
21:09:57.040 -> HTTP/1.1 200 OK
21:09:57.040 -> Date: Thu, 15 Dec 2022 02:09:57 GMT
21:09:57.040 -> Content-Type: text/html; charset=utf-8
21:09:57.040 -> Transfer-Encoding: chunked
21:09:57.040 -> Connection: keep-alive
21:09:57.040 -> Status: 200 OK
21:09:57.040 -> Cache-Control: max-age=0, private, must-revalidate
21:09:57.040 -> X-Request-Id: 798bbb62-da97-4ff8-a15b-c60b68fd60d3
21:09:57.040 -> ETag: W/"408e73c03e9c23fc2318c396c21c09e8"
21:09:57.040 ->
21:09:57.040 -> 2d
21:09:57.040 -> Congratulations! You've fired the alert event
21:09:57.040 -> 0
21:09:57.040 ->
NHON NGUYEN
NHON NGUYEN
最後のアクティビティ: 2023 年 1 月 24 日

There is exactly the same tutorial for my topic but I couldn't make it work. It worked like a charm on SMS service but it wasn't on call. Authentication shouldn't be a problem cause it's similar to SMS configuration. The remaining information that I've doubt is the "Body" part. I filled it like:

From={+Twilio number}&To={+myNumber}&Body=CO2 concentration is exceeding the threshold value and being at :%%channel_1372010_field_3%%

And also, the API URL is:

https://api.twilio.com/2010-04-01/Accounts/{My AuthSID}/Calls.json

I replaced my own information on the above items but It didn't make a call at all even when the TimeControl app run it. Hope to get your help.

João Machado
João Machado
最後のアクティビティ: 2021 年 2 月 26 日

Hi guys,

I'm using Thingspeak to log data for my small weather station project. The data then gets sent to an Airtable using React and ThingHTTP. When I check the exported CSV from Thingspeak I can see the data being logged at regular intervals — every 5 minutes, 3 seconds in. However, something happens with React/ThingHTTP, because the Airtable log doesn't match. Every hour or so, the entry will have an added minute (13:01, 17:01, etc). Why does this happen? React is programmed to use ThingHTTP whenever Field1 is different from 0.