http post not working?

[J V]

TLDR; the field "command for on" needs an entry.

Long version:

Just struggled a bit getting an http post from Loxone, and discovered something: the field "command for on" has to be filled out. I wanted to send a simple post to a webserver, and assumed I do not need it, but nothing was triggered and no packet could be seen on the network. I entered a dummy command, followed by \r, and now the webserver receives the http post commands. Not sure if this is documented behaviour or expected behaviour, but I lost quite some time because of it. So hopefully this helps others. :-)

[Christian Fenzl]

Hi,

afaik in the address of the virtual output you have to enter only the host, like http://myserver (or http://hostort), and in the command for on the rest of the URL, like /dosomething.html

Regards, Christian

[J V]

In "virtual output" yes. But if in "virtual output command" I just have values for the following
-
http post command for on: something
http method for on: post
http method for off: get
-
then my webserver does not receive anything and I thought there was no packet sent out.

If I however add a value for the field (in "virtual output command")
-
command for on: somethingelse\r
-
then the webserver receives "something"

I'm not sure why it behaves like this, but without "command for on" set, I do not receive anything...

[Christian Fenzl]

Ok, I understand. Might be a bug.

[J V]

It took me some time to figure out, so I thought I just post it here in case others have the issue.
I am still using 7.4.4.14, the web server is the built-in webserver of EventGhost.

[Gast]

TLDR; the field "command for on" needs an entry.

Long version:

Just struggled a bit getting an http post from Loxone, and discovered something: the field "command for on" has to be filled out. I wanted to send a simple post to a webserver, and assumed I do not need it, but nothing was triggered and no packet could be seen on the network. I entered a dummy command, followed by \r, and now the webserver receives the http post commands. Not sure if this is documented behaviour or expected behaviour, but I lost quite some time because of it. So hopefully this helps others. :-)

I know this is a bit late to the party but have you reported this to loxone?

[J V]

No... I did not report it: I noticed it after the new version came out and have been unable to test it on the new version (incompatibility with some older phones, so for now I stick with the older version).