How to include field value in ThingHTTP URL GET Request

I am trying to include a field value in a ThingHTTP GET request but have not been successful.

For example, I have have successfully used

https://myurl.com/site?value=12.34

to send a specifice value to an external site, but was unsuccessful when I tried to send a ThingSpeak channel field value in a similar way. I used the %% method, which works for ThingTweet, but that didn't seem to work here. e.g.

https://myurl.com/site?value=%%channel_1234567_field_1%%

Am I doing something wrong, or is there an alternative method for doing this?

[paul]

Did you ever find a fix to this? Unless I'm missing something trying to save a thinghttp containing a url with placeholders in now results in a generic error...

"Please try again!

There were some problems creating your ThingHTTP:

Provide a valid URL for your ThingHTTP."

[Warren Stanley]

I used a 'Matlab Analysis' instead of 'ThingHTTP', and wrote a short code to read my channel value and send it in a GET request URL. There are some examples on ThingSpeak on how to do this and it seems to work fine.

[paul]

Thank you @Warren Stanley That's exactly the pointer I needed, this approach certainly is the way forward!

Answer 1

[Sachin Lodhi]

Hi Warren,

It looks like you are on the right track, but there are some things that need to be considered when using ThingHTTP for GET requests with dynamic data from ThingSpeak channels. The %% notation is indeed used for placeholders, but the setup must be done correctly in ThingHTTP.

Here is a step-by-step guide to help you set this up:

1. Click Apps > ThingHTTP, and then click New ThingHTTP.
2. The next step is to configure the ThingHTTP. See the following section to properly configure ThingHTTP. https://www.mathworks.com/help/thingspeak/thinghttp-app.html#bvtzy2y-1:~:text=New%20ThingHTTP.-,Specify%20settings,-.%20Not%20all%20settings
3. Finally, test the ThingHTTP url. Once saved, You can use POSTMAN to try out your HTTP requests using the RESTful API for ThingSpeak.

If the above steps are correctly followed, the placeholder `%%channel_1234567_field_1%%` should be replaced with the actual value from the specified ThingSpeak channel and field.

Please note that if this does not resolve your query, then following these troubleshooting steps can help -

1. Check Channel ID and Field Number: Ensure that the channel ID and field number are correct.
2. Public or Private Channels: Replacement requests to private channels not owned by the same user as the ThingHTTP request return blank values.
3. URL Encoding: Make sure the URL is properly encoded if it contains special characters.

If you follow these steps and ensure all configurations are correct, you should be able to successfully include a ThingSpeak channel field value in your ThingHTTP GET request.

I hope this helps!

[Warren Stanley]

Hi Sachin,

Thank you for your very detailed answer. I wonder if my issue is something to do with your troubleshooting step 2, as it seems my attempt to pass a value via ThingHTTP GET request works if I just try to pass a fixed number

e.g. https://myurl/site?value=12.34

but not if I try to use a place holder

e.g. https://myurl/site?value=%%channel_1234567_field_1%%

which just passes a blank. I've tried other place holders like %%datetime%% and %%day%%, but get the same problem, so I don't think it's because of a mistake in my channel/field information..

Anyway, the requests I've been trying to send are to a MacroDroid webhook, where I can't really see what gets through. I will try sending the request to a different site of my own, where I can hopefully get a look at the full text of the request at the receiving end, and see what comes through.

Many thanks again.

Warren.

[Warren Stanley]

Hi again,

I've observed the full text of the URL that comes through on a server I set up. It seems the place holders don't get changed to the required value and the url text just comes through with the %%channel_1234567_field_1%% text exactly as I typed it originally. I double checked the channel and field information, and that seems ok, so not sure what else to try. Maybe the place holder code doesn't work when included in the URL itself, perhaps only when put in a message body or something?

Thanks again,

Warren.