[CLOSED] MQTT binding version 2.4 (Pre-release !)

[David_Graeff]

See here:

How to: MQTTv2 Eventbus rules

Hi everyone. As some of you, I was missing the mqtt eventbus feature in MQTTv2, so after reading across the forums and encountering quite some errors I finally managed to mimic the eventbus feature by using rules. I thought I would share this. I’m not a script or rule guru, so I’m sure this can be optimised. In PaperUI I created: MQTT broker: mqtt:broker:8ca384dd Publish Trigger channel: mqtt:broker:8ca384dd:pub The Publish Trigger listens to everything (#) and the delimiter is “#”. …

[matzR (Matthias Reinagl)]

So you mean to capture the MQTT message in a string item and then run a rule to extract the values?

[Karl-Heinz_Weidling1 (Karl Heinz Weidlinger)]

I would be interested in what folder and file the paperui stores the settings.

[meingraham (Michael Ingraham)]

in the userdata folder:
/srv/openhab2-userdata/jsondb (for openHABian)
OR
/var/lib/openhab2/jsondb

[sjcliffe (Steve Cliffe)]

@matzR I’m using the following to “bridge” between my phone sending Owntracks data via MQTT and the new GPSTracker binding:

val String gpsLoggerUrl = 'http://127.0.0.1:8080/gpstracker/owntracks'
val String json = (Mobile_Owntracks.state as StringType).toString
sendHttpPostRequest(gpsLoggerUrl, "application/json", json)

The Mobile_Owntracks item is bound to my phone’s MQTT topic using the 2.4 binding.

[Karl-Heinz_Weidling1 (Karl Heinz Weidlinger)]

yes there they are, thank you very much:grinning:

[Zippochonda]

@matzR

Hi,

I really like the new binding but struggle to use it for the Owntracks configuration I had set up with the 1.x binding.
I know there is the GPSTracker binding which could help, but I want to stick with MQTT for this.
The old item configuration I had was:

Switch  PresenceM_PhoneMqttHome "M @ Home" (gLOG)          { mqttitude="mosquitto:owntracks/Matthias/iPhone/event:Home" }

What I understood so far is, that I can transform the incoming value from MQTT, which looks like this:

‘{“t”:“c”,“tst”:1546182339,“acc”:65,“_type”:“transition”,“event”:“leave”,“lon”:XXXXXX,“lat”:YYYYY,“wtst”:1487837532,“tid”:“AA”,“desc”:“BB”}’

with JSONPATH to get out the different values. But the problem is, that I need three values to be checked:

• event
• tid
• desc

Only if these three match the target pattern, the switch should turn ON.
Is this solvable with JSONPATH?

Thanks
Matthias

Did you found a solution?

[vzorglub (Vincent Regaud)]

@Zippochonda

Only if these three match the target pattern, the switch should turn ON.
Is this solvable with JSONPATH?

No,
This is solvable with a JS transform

[tracstarr]

I’ve got the same error as this. I tried defining the actions above the rule and in the rule with the same result. I have my broker defined in a file and works fine receiving messages.

Bridge mqtt:broker:synology [ host="192.168.0.12",secure=false ]
{
    Thing mqtt:topic:alarm {
    Channels:
	    Type string : alarmstaterequest "Alarm State" [stateTopic="home/alarm/set", allowedStates="DISARM,ARM_HOME,ARM_AWAY"] 
    }
}

And this is my current rule:

import java.util.concurrent.locks.ReentrantLock

val ReentrantLock lock  = new ReentrantLock()
val actions = getActions("mqtt", "mqtt:broker:synology")

rule "Alarm Panel Action Received"
when
    Item alarmpanelRequest changed
then	
	lock.lock()
    try {
	
		switch(alarmpanelRequest.state.toString) {
			case "DISARM": {
				OhAlarmState.postUpdate("disarmed")
				actions.publishMQTT("home/alarm","disarmed")
				sendPushoverMessage(pushoverBuilder("Disarm").withTitle("Alarm Panel").withSound("falling"))
			}
			case "ARM_HOME": {
				OhAlarmState.postUpdate("home")				
				sendPushoverMessage(pushoverBuilder("Arm").withTitle("Alarm Panel").withSound("falling"))
				actions.publishMQTT("home/alarm","armed_home")
			}
			case "ARM_AWAY": {
				OhAlarmState.postUpdate("armed")
				actions.publishMQTT("home/alarm","armed_away")
				sendPushoverMessage(pushoverBuilder("Arm").withTitle("Alarm Panel").withSound("falling"))
			}
		}		
		
    } catch(Exception e) {
		logError("Error", "Alarm Panel Action Received: " + e.getMessage)
	} finally{
        lock.unlock()
    }
    
end

The actions.publishMQTT failes with
[ERROR] [eclipse.smarthome.model.script.Error] - Alarm Panel Action Received: Instance is not an MQTTActions class.

[David_Graeff]

It works for this guy:

openHAB2 MQTT2 binding - multiple brokers

The documentation on MQTT2 is decribing how to use actions with the new binding. When using this, I do get an unexpected behaviour when having more than one broker. Depending on the sequence in the code, the messages are send to the wrong broker. The following rule works as expected: // mqtttest.rules // https://www.openhab.org/blog/2018-12-16-mqtt-arrives-in-the-modern-openhab-2-x-architecture.html val String filename = "mqtttest.rules" //--------------------------------------------------…

[vzorglub (Vincent Regaud)]

Why are you using a lock?