No I am missing something…
I looked at this THING business most likely a year ago. Read the docs. I didn’t get the concept at the time. And didn’t bother to change… as my set-up was and is working fine.
With this OH update and the following issue of OH not talking to mosquitto, panic and a steep learning curve set it.
Now that I have actually created a few things, and was pointed to the docs, which I didn’t read recently, and which have been updated containing for more info now than a year ago, I now get the THING thing.
I have not looked at what is modifications are required for rules, where I publish directly to controller. My assumption is, if I change to channels, my publish command must be different to what I have now.
Rich has provided me with an example what a rule needs to look like with mqtt v1 and v2.
It is one thing seeing it, and another to write your own.
This is the propagated truth. However, when it was pointed out to me that installing v2 and then v1 would work, and my system did not work after an update of OH; I removed the mqtt v1 action and binding; installed the v2 and then v1.
No errors occurred, the v1 connected straight to mosquitto, all was working again.
Yes, being time poor, as in when you work, migrating the amount of controllers I have to things, updating rules, etc. takes significant time (and maybe I am not the fastest).
Having this migration path now, where I can change one controller at the time, even “half” the ‘channels’ of a thing; yes, I have now a half migrated controller; e.g. I thing’ed the easy bits (string, switch, number; and not participating in rules), and will do the ones needing transformation or rule updates tonight or tomorrow.