Generic Web Export

introduction the export module "generic web export" is used to forward device updates to a web service multiple export instances can be created configuration the configuration is done via the "iot export" area of the web configuration or the bsc remote variables can be used to populate specific devices or channel data at runtime the "thing variables" can be used in templates or the url furthermore, the template to export the data can be fully customized thing template in the case of a device update, the variables are filled with the current values and the string generated in this way is sent as the body of the request variables variable description <\<gw id>> hardware id of the gateway <\<id>> device id <\<name>> device name <\<state>> device state <\<signal strength>> signal strength last signal <\<last modified>> last device change <\<channels>> placeholder for the channel template example configuration thing template { "node" "<\<gw id>>", "id" "<\<id>>", "name" "<\<name>>", "state" "<\<state>>", "signalstrength" <\<signal strength>> , "lastmodified" <\<last modified>> , "channels" { <\<channels>> } } channel template the channel template is used to iteratively generate a list of channels and their values this list can be used as a variable in the thing template the "channel separator" field is used to separate the elements in the generated string variables variable description <\<channel\ id>> id of the channel <\<channel\ value>> current channel value example configuration channel template "<\<channel\ id>>" "<\<channel\ value>>" authentication basic auth or authentication via header tokens is supported the basic auth credentials simply need to be entered into the appropriate fields header tokens can be added in the header field misc the request type, as well as custom header fields, can be added in the appropriate fields optionally, a filter based on thing id's can be activated