Mqtt parsing with transformation

[kriznik]

I think this question was already in place but can’t really find an answer.

I do have this as example device

Type dimmer : roses "Roses" [ stateTopic="home/climate/diningroom/table/stat/RESULT",   commandTopic="home/climate/diningroom/table/cmnd/Dimmer", transformationPattern="JSONPATH:$.Dimmer" ]

but TASMOTA is reporting to RESULT manytimes different data and OH is freaking out everysingle time when “Dimmer” is missing in the MQTT (which is quite often)

2021-11-07 12:02:16.378 [WARN ] [t.generic.ChannelStateTransformation] - Executing the JSONPATH-transformation failed: Invalid path '$.Dimmer' in '{"If":"Done"}

Is there a way how OH may ignore MQTT message if it is not containing Path in transformation instead of reporting Warning?

(yes I can disable WARN messages in log, but that’s not the point)

[rossko57]

See

MQTT 2.5 M1+ How to implement the equivalent to MQTT1 REGEX filters

Problem In the MQTT1 binding there was a feature that let us filter messages published to a given topic and only pass those that match a given REGEX to the transformation and/or on to the Item. This was useful to handle devices that publish messages to a single well known topic for all their devices. For example, the official firmware from the vendor of Shelly devices have a request/response protocol over MQTT to get meta data about the devices (IP address, MAC address, firmware version, whethe…

[kriznik]

Thanks for pointing me there. Not sure if that I’ll be able to adapt to my issue as that is about group mqtt topic and regexing name of the device.
In here I don’t have anything like it…

hmm maybe I’ll try to regex “Dimmer” word and let’s see what happends

[hafniumzinc (T)]

@kriznik

hmm maybe I’ll try to regex “Dimmer” word and let’s see what happends

That’s exactly what I do. It will work.

transformationPattern="REGEX:(.*Dimmer.*)∩JSONPATH:$.Dimmer"

[kriznik]

Thank you! seems to be fine.

Thous would be nice “auto” feature so it will regex JSON path directly itself