WebQuery HTTP response code

[makedir]

Hello,

I am using a ESP32-C3 here with default firmware. I want to make two simple rules to send a WebQuery on a SSerial Event

Rule2 ON SSerialReceived#Message DO WebQuery http://URL POST %value% ENDON

and send back a SSerial message, that the WebQuery was delivered. But I cant find any documentation how to parse if WebQuery was successfully delivered. ChatGpt told me to use this:

Rule3 ON WebQuery#Status=200 DO SSerialSend "WebQuery sent" ENDON

But it seems there is no "Status" at all implemented. I found this example here to use something like this:

Rule3 ON WebQuery#Data=Done DO SSerialSend "WebQuery sent" ENDON

This gets parsed, but it always is parsed no matter what.

There is always a RESULT = {"WebQuery":"Done"} sent, no matter if the message was delivered.

You could even do a bogus command like this:

WebQuery http://THIS_URL_DOES_NOT_EXIST POST test

and you still get a :

RESULT = {"WebQuery":"Done"}

---

What is the right way to do this and get a proper HTTP reponse code like 200, or something else to notice the server responded?

[sfromis]

I already answered about what you can do. #13209 (comment)

[makedir]

@sfromis Hello, thanks for answering, but like I already said, this doesnt work. Tasmota always sends back

{"WebQuery":"Done"}

no matter what. if you do a bogus command like WebQuery https://thisurldoesnotexist POST test it also respons with

{"WebQuery":"Done"} and not with {"WebQuery":"Connect failed"}

There is never a error message sent back. is this a bug?

I dont know how to use Berry, the documentation is sadly not really good. If youd like to post a simple Berry example for this if it is just a few lines, I would appreciate that. But I would more like to use Rules because how simple they are for this.

[sfromis]

Well, there are situations where you can get {"WebQuery":"Connect failed"}, that was a copy/paste from a test I did. And editing your question with significant change after getting a response is not a great way to communicate.

Still, you are right that you cannot get a reasonable indication of reachability this way. But what I saw as the main question was about getting a status code. This is not available using the WebQuery command. No way around that.

If you enable the mentioned USE_WEBSEND_RESPONSE, a workable approach is to check your server response to validate it to be consistent with what you expected.

When it comes to Berry, here's a simple example illustrating getting a 404 status code, as my test server does not have a robots.txt file.

def wctest(url)
  var wc = webclient()
  wc.begin(url)
  var status = wc.GET()
  var response = wc.get_string()
  wc.close()
  print(f'{status=} {response=}')
end
wctest('http://192.168.xx.xx/robots.txt')

BTW. While rules work ok for quite simple things, it tends to get complex with various contortions to get a bit more complex.

[makedir]

Thank you very much. I just compiled a version with USE_WEBSEND_RESPONSE active and thats mostly all I need, so I get a json response now back and can do something like this:

Rule3 ON WebQuery#var=value DO SSerialSend "WebQuerySent" ENDON

[makedir]

@sfromis I think there is some kind of bug. I have tested the past hour with this, and it doesnt work reliable for some reason, example:

22:49:32.938 CMD: WebQuery https://ntfy.sh/MYTOPIC POST test
22:49:33.944 RSL: RESULT = {"WebQuery":"Done"}

=> no response

Repeating a 2nd time suddenly, a response with same input:

22:50:12.715 CMD: WebQuery https://ntfy.sh/MYTOPIC POST test
22:50:14.077 RSL: RESULT = {"WebQuery":{"id":"____","time":1741125014,"expires":1741168214,"event":"message","topic":"MYTOPIC","message":"test"}}
22:50:14.086 RUL: WEBQUERY#TOPIC=MYTOPIC performs 'SSerialSend "WebQuerySent"'
22:50:14.090 RSL: RESULT = {"SSerialSend":"Done"}

Also, if you do after rebooting, rules wont trigger it:

22:54:24.523 CMD: Rule1
22:54:24.526 RSL: RESULT = {"Rule1":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":63,"Free":448,"Rules":"ON System#Boot DO Backlog SerialLog 0; SSerialSend2 ready ENDON"}}
22:54:26.227 CMD: Rule2
22:54:26.230 RSL: RESULT = {"Rule2":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":89,"Free":422,"Rules":"ON SSerialReceived#Nachricht DO WebQuery https://ntfy.sh/MYTOPIC POST %value% ENDON"}}
22:54:28.134 CMD: Rule3
22:54:28.137 RSL: RESULT = {"Rule3":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":67,"Free":444,"Rules":"ON WebQuery#topic=MYTOPIC DO SSerialSend "WebQuerySent" ENDON"}}

But logs wont show Rule3 being triggered via Rule2, just if you do it manually:

22:41:04.775 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST'
22:41:06.131 RSL: RESULT = {"WebQuery":{"id":"_____","time":1741124466,"expires":1741167666,"event":"message","topic":"MYTOPIC","message":"TEST"}}
22:41:14.806 RSL: RESULT = {"SSerialReceived":{"Nachricht":"TEST"}}

[sfromis]

Not a bug, but a quirk. As explained in the docs, "When the JSON payload response is produced by a command executed by a rule .... the trigger will not fire unless the command is wrapped in backlog"
https://tasmota.github.io/docs/Rules/#examples-of-available-triggers

[makedir]

So I need to change Rule2 to use a Backlog even it is just one command, why? Do I need to use Backlog also for Rule3?

Rule1 ON System#Boot DO Backlog SerialLog 0; SSerialSend2 ready ENDON
Rule2 ON SSerialReceived#Nachricht DO Backlog WebQuery https://ntfy.sh/MYTOPIC POST %value% ENDON
Rule3 ON WebQuery#topic=MYTOPIC DO SSerialSend2 WebQuerySent ENDON

also what about the issue that it doesnt work as seen doing a manual command, not working, then repeating, suddenly working?

Also there is another weird "quirk" as seen here, that if you do sending SSerial in a row, randomly, there is "no" response where it doesnt work and sends back a DONE with no json, as seen here:

23:05:17.005 RSL: RESULT = {"SSerialReceived":{"Nachricht":"test"}}
23:05:17.013 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST'
23:05:19.035 RSL: RESULT = {"WebQuery":{"id":"","time":1741125919,"expires":1741169119,"event":"message","topic":"MYTOPIC","message":"TEST"}}
23:05:27.031 RSL: RESULT = {"SSerialReceived":{"Nachricht":"test"}}
23:05:27.039 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST'
23:05:28.417 RSL: RESULT = {"WebQuery":{"id":"","time":1741125929,"expires":1741169129,"event":"message","topic":"MYTOPIC","message":"TEST"}}
23:05:37.057 RSL: RESULT = {"SSerialReceived":{"Nachricht":"test"}}
23:05:37.065 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST'
23:05:38.481 RSL: RESULT = {"WebQuery":{"id":"","time":1741125939,"expires":1741169139,"event":"message","topic":"MYTOPIC","message":"TEST"}}
23:05:47.081 RSL: RESULT = {"SSerialReceived":{"Nachricht":"test"}}
23:05:47.090 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST
23:05:48.096 RSL: RESULT = {"WebQuery":"Done"} <---- DIDNT WORK
23:05:57.107 RSL: RESULT = {"SSerialReceived":{"Nachricht":"test"}}
23:05:57.115 RUL: SSERIALRECEIVED#NACHRICHT performs 'WebQuery https://ntfy.sh/MYTOPIC POST TEST'
23:05:58.498 RSL: RESULT = {"WebQuery":{"id":"","time":1741125959,"expires":1741169159,"event":"message","topic":"MYTOPIC","message":"TEST"}}