It does. If the response has a body.
As Pete, suggested, “/pin/” should be replaced with “{device_pinValue}”. But “test webhook” still may not work for this use case. We’ll fix it in the next release. But real value should work as expected.
It does. If the response has a body.
As Pete, suggested, “/pin/” should be replaced with “{device_pinValue}”. But “test webhook” still may not work for this use case. We’ll fix it in the next release. But real value should work as expected.
Apologies, I missed that in the 10.02.2022 release announcement.
I looked at the documentation and it want really clear how to use these parameters. Maybe the documentation needs refreshing with the info about the webhook now returning the values, and some examples of how to embed the virtual pin values into the API call?
Pete.
Agree. Checked the doc, it’s very unhelpful.
Good day,
I have the same problem, where can I find the current documentation.
“/pin/” should be replaced with “{device_pinValue}”
it didn’t help me.
Thank you Pavel
Good day,
so i managed to write one value
https://api.thingspeak.com/update?api_key=xxxxxxxxxxxx&field1={device_pinValue}
in the old Legacy, I sent 4 values to the port at once and then wrote them like this
I can’t use this url in nove Iot
does the new blynk support writing multiple values at once?
If so, can you send me what the correct chain for writing should look like?
Thank you Pavel
Hello, is there some new update?
I created more webhooks to update values on ThingSpeak but it’s not good way, I wan’t to send all values in one GET response as it was possible in legacy Blynk…