MQTT Bridge for Luup

This is a MQTT Bridge for Openluup and Mios'Vera Platform (Luup engine). This could help integration with other ecosystems (Tasmota, Shelly, Home Assistant) with an external process, running indendpently from your Vera/Openluup installation.

Vera early beta. Use at your own risk.

Installation and minimal requirements

The broker runs on .NET 5. Linux, Windows or macOs are OK. See Microsoft docs for more information on running it on Linux. Raspberries are perfectly supported, as well as Docker. You can build it directly from source. Just download the files, install .NET SDK and then run, inside the directory:

dotnet build
dotnet publish -c Release -r linux-x64

Remove -r linux-x64 if you want to build a portable app. It's completely fine to build it on Windows and publish on Linux, or macOs, or whatever combination you like.

If you want to build a single file with .NET installed, simply run

dotnet publish -c Release -r linux-x64 -p:PublishSingleFile=true --self-contained true

The application binary will be published under bin\Release\net5.0\linux-x64\publish\.

All the files here can be copied to your machine. The executable name is Luup.MqttBridge (.exe on Windows) and needs permissions to execute.

You can run the application directly (ie from another process).

Refer to your own preferred operating system on how to transform and run this at startup or as service. Systemd under Linux is supported.

First configuration

Here's an example of configuration:

{
	"MQTT": {
		"Username": "luup",
		"Password": "openluup",
		"Port": 1883
	},

	"Luup": {
		"ipAddress": "127.0.0.1",
		"port": 3480
	},

	"Devices": [
		{
			"ClientID": "sonoff-pool",

			"TopicName": "tele/tasmota/SENSOR",
			"TopicPath": "DS18B20.Temperature",

			"AlternateTopicName": "stat/tasmota/STATUS8",
			"AlternateTopicPath": "StatusSNS.DS18B20.Temperature",

			"DeviceID": 501,
			"Service": "urn:upnp-org:serviceId:TemperatureSensor1",
			"Variable": "CurrentTemperature"
		},

		{
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "ON",

			"DeviceID": 486,
			"Service": "urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
			"Variable": "ModeTarget",
			"Value": "HeatOn"
		},

		{
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "OFF",

			"DeviceID": 486,
			"Service": "urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
			"Variable": "ModeTarget",
			"Value": "Off"
		},

		{
			"ClientID": "tasmota-dehum",

			"TopicName": "tele/tasmota/SENSOR",
			"TopicPath": "DS18B20.Temperature",

			"DeviceID": 486,
			"Service": "urn:upnp-org:serviceId:TemperatureSensor1",
			"Variable": "CurrentTemperature"
		},

		{
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "OFF",

			"DeviceID": 499,
			"Service": "urn:upnp-org:serviceId:SwitchPower1",
			"Variable": "Status",
			"Value": "0"
		},

		{
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "On",

			"DeviceID": 499,
			"Service": "urn:upnp-org:serviceId:SwitchPower1",
			"Variable": "Status",
			"Value": "1"
		}
	]
}

It's self explanatory. Go to MQTT section and put in your credentials. These will be used by your client devices as well. In Luup section specify your Vera/Openluup IP and port.

Devices section has your mappings. You can map a message to different devices, use a part of the payload, or mix and match.

Standard configuration must include:

• ClientID: the broker filters the messages by this value. Be sure to set the device client ID, as set in your device. Use * if you want to only search for a topic.
• TopicName: the MQTT topic (case insensitive).
• DeviceID: Vera/Openluup deviceID.
• Service: Luup service ID.
• Variable: The variable to update with the computed value.

If your device send a fixed value, you should specify:

• TopicValue: if your device send a fixed value (ie on), specify the value. It's case insensitive.
• Value: The value to be sent as the computed value.
• AlternateTopicValue: same as above, but will check for an alternate topic.

If your device send a dynamic value, you should specify:

• TopicPath: specify the path, in JSONPath format. i.e. "DS18B20.Temperature" will search for DS18B20 then get the value from Temperature node.
• AlternateTopicPath: same as above, but will look for a second path.

Use one or another. If both are specified, the first (fixed value) wins.

Virtual HTTP Devices plug-in for Vera

If you need to represent virtual devices that performs HTTP calls, you need my other plug-in. This is 100% compatible with Vera UI/Altui, mobile apps and act as a standard control in that sense.

More info

Logging

By default, verbose logging is enabled. Logs are rotated daily in _logs. If you want to disable verbose logging, just uncomment the latest lines from the default config file.