So you are using the version 1 MQTT binding, in this case nothing usefull will be shown on PaperUI and you don’t need to have or better won’t have any MQTT Thing.
If the broker is running as before and your items are created by the same file I’d would check with MQTTfx (or a similar program) whether mqtt messages are processed at all.
And for the sake of all the users trying to help, in the present situation ( MQTT version 2 being out 2 years AND OH3 ( to one with no version1 support) went public a week ago ) it would be a good idea to highlight the use of an deprecated binding.
Yes, as stated in the O.P.
Agree with what you’re saying.
However, the work involved to change will be significant.
… and I hope you’re not blaming me for having upgraded a minor and official release which broke the system.
mosquitto is up and running fine.
I can run commands, which are accepted by the controllers, but not processed by OH.
This is what puzzles the heck out of me. OH seems to connect, if I can assume that from the fact it states in the log that it it disconnecting from the mymosquitto broker.
… is what I get in openhab.log when shutting OH down.
When I try to change the clientId in mqtt.cfg, this is recorded in the openhab.log:
2020-12-26 19:37:40.458 [ERROR] [org.apache.felix.configadmin ] - Cannot use configuration org.openhab.mqtt for [org.openhab.io.transport.mqtt.MqttService, org.osgi.service.cm.ManagedService, id=381, bundle=237/mvn:org.openhab.io/org.openhab.io.transport.mqtt/1.14.0]: No visibility to configuration bound to mvn:org.openhab.action/org.openhab.action.mqtt/1.14.0
OK, you do use the binding and the action. I faintly remmber a problem with them, if I remember correctly the action needed to be loaded after the binding to solve the problem (will have to digg into old posts to verify).
and thanks for changing the title!
Such problem could be resolved by loading the mqtt action manually after the mqtt binding was installed. I think unloading the action (which is set in the addons.cfg) won’t work for you, so try to remove it from the addons.cfg, restart and load the mqtt action afterwards manually (if you still need it).
I proactively moved the mqtt1 entry to the front (as you suggested earlier), and restarted, and…
… mqtt is working again.
Phew… the “Haussegen hing schief” given the 'most-of-the-day" outage.
I am not sure, whether the action is required (was always there from years ago).
… but considering I hadn’t made the change you then suggested to remove the mqtt action and reboot… I think we have a fix.
Thank you so much for hanging in there! Much appreciated.