Can we see that, for avoidance of misunderstandings? Guessing you see someItem received Command XX
Item
channel= describes a link mqtt:topic:Brilliant:POWER gives the UID, the name, of the target channel.
As you can see, that is a hierarchal UID
mqtt says to look at MQTT binding for Things topic says to look amongst topic Things - other bindings can have different types of Things Brilliant says to look for the topic named Brilliant, obviously
That gets us to your topic Thing but that may have multiple channels POWER obviously selects the channel
That is usually a two-way link. Item commands get passed to the channel. Binding messages get passed via channel to Item state update.
So we can look at your Things, see if it matches …
channel type corresponds with your Item type, that’s a good start.
There’s not enough of your Things file on view here to see if the mqtt:topic:Brilliant part is correct, we can only see the channel name POWER
Channels:
Type switch : POWER "Light Power On/OFF" [
stateTopic="stat/Brilliant/POWER",
commandTopic="cmnd/Brilliant/POWER",
on ="ON",
off ="OFF"
]
Type string : reachable "Reachable" [
stateTopic = "tele/Brilliant/LWT"
]
Type dimmer:dimmer "Dimmer" [
stateTopic="stat/Brilliant/RESULT",
commandTopic="cmnd/Brilliant/Dimmer",
transformationPattern="JSONPATH:$.Dimmer"
]
Type colorHSB:color "Colour" [
stateTopic="stat/Brilliant/RESULT",
commandTopic="cmnd/Brilliant/HSBColor",
transformationPattern="JSONPATH:$.HSBColor"
]
Type switch:state "State" [
stateTopic="tele/Brilliant/STATE",
transformationPattern="JSONPATH:$.POWER",
on ="ON",
off ="OFF"
]
}
This topic Thing does not belong to the broker.
You can structure it this way, say if you defined broker in one file and topic in another. But you would need to tell the topic which broker it belongs to - there can be more than one.
Easier is to make the hierarchy implicit by using curly braces.
If you do it that way, you an allow parts of the topic Thing UID to default to the parent broker Bridge. Less to type, less to get wrong.
Bridge mqtt:broker:MosquittoMqttBroker "Mosquitto MQTT Broker" [
host=“192.168.0.20”,
secure=false,
]
{
Thing topic Brilliant "Light" {
Channels:
Type switch : POWER "Light Power On/OFF" [ ...
...
}
}
That topic Thing will have a UID of mqtt:topic:MosquittoMqttBroker:Brilliant, and to use in a channel= assingment you would need to give channel name as well mqtt:topic:MosquittoMqttBroker:Brilliant:POWER
Since I started with OH3 I have been wandering through the OH forum. Now I have to say that I have been helped a lot again. Thanks. Without this information it would be pretty complicated, being a MQTT/Tasmota newbie. Works great now.