Simple EnOcean MQTT Client

introduction the export module "simple enocean mqtt client" establishes the connection to an mqtt broker and publishes messages under different topics multiple export instances can be created, but only one instance per broker url messages are always transmitted as strings and are usually formatted as json objects configuration in the iot export area of the web configuration or the bsc remote, the export connection can be created and the parameters configured tcp/ssl and web socket (http/https) connections are supported authentication is possible by username and password or client certificate the corresponding certificates or access data can be stored during configuration there is a possibility to customize the basic topics for publishing news parameter true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type data model base data of messages all messages are transferred as json objects basic information for message assignment is available in all objects base fields true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type sensors / actuators in addition to the basic fields, the following fields are available in the device object true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example data fsb 14 { 	"nodeid" "acdbda5906ee", 	"timestamp" 1689865668, 	"name" "fsb 14", 	"eurid" "2a3df3d", 	"refid" "enocean eltako fsb14", 	"channels" { 	 "jalousieslat" "unknown", 	 "jalousie" 65 0, 	 "priority" "off", 	 "jalousiestate" "unknown" 	} } fsr 14 { 	"nodeid" "acdbda5906ee", 	"timestamp" 1689865842, 	"name" "fsr14", 	"eurid" "c23df34", 	"refid" "enocean eltako fsr14", 	"channels" { 	 "switch" "on", 	 "priority" "off" 	} } gateway status in addition to the basic fields, the following fields are available in the gateway status object true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example data gateway status object { 	"nodeid" "acdbda5906ee", 	"timestamp" 1689864643, 	"version" "3 5 1", 	"online" true } mqtt topics the used topic structure is divided into data and command t data topics the gateway sends its status messages and the status messages of the connected devices via the data topics sensors / actuators the topic stored in the configuration under "enocean topic prefix" serves as the basis this path is extended by the eurid of the device and the device message is published there example topic enocean/513659d gateway the topic stored in the configuration under "gateway topic prefix" serves as the basis this path is extended by the hardware id of the device and the status message is published there example topic gateway/acdbda4512e0 command topics a simple way of controlling the gateway is implemented via the command topics actuators the topic stored in the configuration under "enocean topic prefix" serves as the basis and enables actuators to be switch this path is extended by the eurid of the device and the channel id as payload the new value is expected as string example topic enocean/513659d/switch example payload on off gateway the topic stored in the configuration under "gateway topic prefix" serves as the basis this path is extended by the hardware id of the device and the command to be executed a json object with the corresponding parameters is expected as payload available commands true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example topic gateway/acdbda4512e0/pairing gateway/acdbda4512e0/delete example payload on=90 off 513659d