The following features are missing from Loxone Config and LOXONE

[Jan Reklamowy]

The following features are missing from Loxone Config and LOXONE:

1) With HTTP virtual input, to be parameterized by \ v the address in the URL:

  eg http://smartdom.eu/data/2021-05-19 now if the date is variable, it cannot be specified in the variable's URL. It should be done like this: http://smartdom.eu/data/v

and then input the value of / v in Loxone to the block

2) Unable to read text values from HTTP virtual input (HTTP virtual input - command)

Text must be converted to single characters.

No need to convert single ASCII characters.

With a modern system it should be possible to retrieve text values from 1 to 200 characters.

This is a much needed feature.

[Rob_in]

Don't tell us - tell Loxone!

FWIW, I use ioBroker for to interface our Loxone system with the other stuff it doesn't support and workaround such issues.

[Tico]

Regarding Point 1) -

Where a variable URL needs to be specified, you can use a Virtual Output with 'Save HTTP Reply' with the entry -

/user/common/answer.html

or

/user/common/answer.json

or

/user/common/answer.txt

 The 'Command for ON' becomes the URL appended with /<v>.

ie.   http://smartdom.eu/data/<v>

The Virtual Output can be triggered by any variety of options (pulse generator, time schedule etc.). The 'Save HTTP Reply' then stores the URL response on the Loxone SD card (with some consequences for SD card longevity). You then need to set up a Virtual HTTP Input that polls the internally saved file. 

The URL address for the internal file is now -

http://Username:Password@MiniserverIP:Port/dev/fsget/user/common/answer.html

The Virtual HTTP  Input command recognition will then need to have the search term set appropriately to find your data field.

Regarding Point 2) -

Text Input to the Miniserver is difficult but not impossible (read ugly work-around). The following link is to a wiki for 'Text Input to Miniserver'.

https://www.loxwiki.eu/display/LOXEN/Text+Input+to+Miniserver

I've successfully used these two processes ('Virtual Output with Save HTTP Reply' and 'Text Input to Miniserver') to retrieve tokens for device authentication requirements. It gets too unwieldy when the token gets too large, but for small tokens of ~50 characters, authentication is viable using just Miniserver resources.