This tutorial helped me lot to see ‘things’ and their syntax clearer:
… and it does include the broker.
So does the image I attached in my previous port, they all show the broker name in the Thing.
Yes, it does unlink/link on channel change…
In fact I had tried both methods.
MainGate did not have mymosquitto
{channel="mqtt:topic:maingate:mac"}
Zeva did have it.
{channel="mqtt:topic:mymosquitto:zevabms:mac"}
The examples in the link above have the broker in the channel.
{ channel="mqtt:topic:mosquitto:Aircondition:fanspeed" }
Both my items do not get updated by mqtt.
TRACE logging the binding shows no activity in picking up any topics.
Well, if it is changes to .things files only, then my statement holds true, as the tings I use are astro, logger, ntp which never changed since late 2018 when I created that thing file.
I think another issue with mqtt being in a thing file, whenever a change is made it disconnects and reconnects to the broker… thus interrupting message flow for that short period.
I am at the end of my wits.
… and basically reverted all changes; as in back to mqtt v1. It simply works…