# \[Solved\] Upgrade from 2.5.10 to 2.5.11 resulted in missing MQTTv1 processing **URL:** \ **Category:** Installation\ **Created:** [December 26, 2020, 4:41am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334 "2020-12-26T04:41:01Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 4:41am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/1 "2020-12-26T04:41:01Z")
- Platform information: - Hardware: Raspberry Pi 3 Model B Rev 1.2\_ - System: Host: rpi3ohv2 Kernel: 5.4.51-v7+ armv7l bits: 32 Console: tty 2 - Distro: Raspbian GNU/Linux 10 (buster) - OpenJDK Runtime Environment (Zulu 8.31.1.122-linux\_aarch32hf) (build 1.8.0\_181-b122) - **Version: 2.5.10 (Build) (apt-get), text-based config** - binding = astro, exec, logreader, network, ntp, systeminfo, fritzboxtr0641, expire1, **mqtt1** , weather1 - ui = paper, basic, classic, restdocs - persistence = rrd4j, mapdb - action = mail, mqtt - transformation = map, javascript, xslt, scale, jsonpath I upgraded from 2.5.10 to 2.5.11 simply to be on the latest version of 2.5. After the upgrade MQTT messages were no longer processed. No changes were made to the config. Since all controllers in my place run on MQTT, pretty much every thing is non-functional. After unsuccessful attempts to troubleshoot the problem… I reverted back to 2.5.10… only to discover the problem persists. I am at a loss on how to fix this. The openhab.log does not give my any clues about mosquitto being loaded/started, but says `Stopping broker connection 'mymosquitto'` when stopping OH. I really need some help. Thanks. Steps undertaken so far: 1. initial upgrade to 2.5.11 2. restart; lots of errors 3. stop OH 4. clear cache 5. start OH; seemingly normal start 6. stop OH 7. start OH; seemingly normal start → still no MQTT processing 8. sudo apt install openhab2=2.5.10-1 9. clear cache 10. start OH → still no MQTT processing 11. stop and start OH; seemingly normal start → still no MQTT processing Non-MQTT stuff is working. However the mosquitto broker is installed and running and works for other things: ```auto sudo service mosquitto status ● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-10-26 14:04:07 AEST; 1 hour ago Docs: man:mosquitto.conf(5) man:mosquitto(8) Main PID: 10530 (mosquitto) Tasks: 1 (limit: 2184) CGroup: /system.slice/mosquitto.service └─10530 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf ``` ---
**Author:** ![denominator](https://community.openhab.org/user_avatar/community.openhab.org/denominator/32/37349_2.png) [@denominator](https://community.openhab.org/u/denominator)\ **Post date:** [December 26, 2020, 5:32am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/2 "2020-12-26T05:32:50Z")
If a couple of reboots won’t fix it then you can try clearing cache which will force everything to rebuild. ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 5:59am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/3 "2020-12-26T05:59:53Z")
Thanks… I will add what I have done in the original post. ---
**Author:** ![hafniumzinc](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/b9bd4f/32.png) [@hafniumzinc](https://community.openhab.org/u/hafniumzinc)\ **Post date:** [December 26, 2020, 6:53am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/4 "2020-12-26T06:53:12Z")
> [@Max\_G](#): > > The openhab.log does not give my any clues about mosquitto being loaded/started Mosquitto is a separate software, so the openHAB logs won’t show whether this is loaded or not. In a Linux command terminal (or over SSH), what does ```auto sudo systemctl status mosquitto ``` show? ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 7:13am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/5 "2020-12-26T07:13:12Z")
added to initial post: ```auto sudo service mosquitto status ● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-10-26 14:04:07 AEST; 1 hour ago Docs: man:mosquitto.conf(5) man:mosquitto(8) Main PID: 10530 (mosquitto) Tasks: 1 (limit: 2184) CGroup: /system.slice/mosquitto.service └─10530 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf ``` ---
**Author:** ![hafniumzinc](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/b9bd4f/32.png) [@hafniumzinc](https://community.openhab.org/u/hafniumzinc)\ **Post date:** [December 26, 2020, 7:24am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/6 "2020-12-26T07:24:40Z")
OK, that looks good! Next, we should check the Broker Thing within openHAB, and whether it’s successfully connected. Can you confirm that your Broker Thing is successfully connected when you look in PaperUI? What is your Broker Thing configuration? ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 7:53am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/7 "2020-12-26T07:53:27Z")
There is none. It is a text-based config. ---
**Author:** ![hafniumzinc](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/b9bd4f/32.png) [@hafniumzinc](https://community.openhab.org/u/hafniumzinc)\ **Post date:** [December 26, 2020, 7:56am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/8 "2020-12-26T07:56:49Z")
That’s not true: PaperUI will still show your Broker Thing, and whether it is connected (“ONLINE”) - you just can’t edit it. Should be somewhere like _Configuration_ → _Things_ Please also show your configuration of your Broker Thing. ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 8:44am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/9 "2020-12-26T08:44:33Z")
Well… it is a few minutes away, as the machine is booting and takes some 9 minutes. … I was using the rPi to build a new 2.5 system, but on a different drive… the system upgrade just finished; hence, the swap of drives and rebooting the system. * * * I have to say that this GUI config business is doing my head in. I tried to config the MQTTv2 version, but it is so much work given that all my controllers talk MQTT. * * * OK, back in business… … and yes, there is no MQTT broker in the PaperUI There is a services/mqtt.cfg: ```auto mymosquitto.url=tcp://localhost:1883 mymosquitto.clientId=openhab mymosquitto.retain=true ``` I have got the bindings: ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/6/0/600a9ffac8a589ad79d94fe731ebb5fefa250e55.png) ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/7/4/74c9715314c5d82ba87dd39ac656b78739e71f16.png) [edit\_1] for completeness: I had deleted the following file and it got recreated the same way (identical): ```auto cat /var/lib/openhab2/config/org/openhab/mqtt.config :org.apache.felix.configadmin.revision:=L"1" mymosquitto.clientId="openhab" mymosquitto.retain="true" mymosquitto.url="tcp://localhost:1883" service.pid="org.openhab.mqtt" ``` ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 9:14am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/10 "2020-12-26T09:14:50Z")
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. ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 9:21am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/11 "2020-12-26T09:21:46Z")
> [@opus](#): > > using the **version 1 MQTT** 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. ---
**Author:** ![denominator](https://community.openhab.org/user_avatar/community.openhab.org/denominator/32/37349_2.png) [@denominator](https://community.openhab.org/u/denominator)\ **Post date:** [December 26, 2020, 9:25am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/12 "2020-12-26T09:25:25Z")
I guess now you have a decision to make. Keep bashing away until you get the old one working or upgrading to mqtt2 on oh3 or goto OH3. GO with OH3 > [@YAML openHAB 3 MQTT TASMOTA SONOFF](https://community.openhab.org/t/yaml-openhab-3-mqtt-tasmota-sonoff/110003): > > Getting Tasmota working with OH3 using MQTT This is for someone that has installed openhabian and wants to use tasmota to control their device. Prerequisite SSH Access - I like and use [https://termius.com/](https://termius.com/) MQTT Broker - I Mosquitto as the Broker for all of my MQTT devices. I install using the openhabian config tool. Device - Tasmota installed on a device and be able to view webpage. MQTT Client - [http://mqtt-explorer.com/](http://mqtt-explorer.com/)SSH If you haven’t done so installed mosquitto using ssh login to … ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 9:26am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/13 "2020-12-26T09:26:40Z")
> [@Max\_G](#): > > and I hope you’re not blaming me All I tried to say was the use of MQTT1 should have been highlighted. ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 9:30am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/14 "2020-12-26T09:30:16Z")
> [@Max\_G](#): > > 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. If OH is disconnecting it is DISconnected! The reason for disconnecting is the culprit! Most times in such cases a non-unique clientID was the reason. ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 9:35am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/15 "2020-12-26T09:35:29Z")
```auto 2020-12-26 16:22:51.941 [INFO] [penhab.io.transport.mqtt.MqttService] - Stopping broker connection 'mymosquitto' ``` … 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: ```auto 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 ``` ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 9:45am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/16 "2020-12-26T09:45:17Z")
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! 👍 ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 9:50am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/17 "2020-12-26T09:50:14Z")
> [@opus](#): > > action needed to be loaded after the binding Not sure how this can be achieved… this is the addons.cfg ```auto grep "^[^#;]" /etc/openhab2/services/addons.cfg remote = true legacy = true binding = astro,exec,logreader,network,ntp,systeminfo,fritzboxtr0641,expire1,mqtt1,weather1 ui = paper,basic,classic,restdocs,habpanel persistence = rrd4j,mapdb action = mail,mqtt transformation = map,javascript,xslt,scale,jsonpath ``` There is no option to determine load order… [all I did was upgrade 2.5.10 to 2.5.11, stop, start and it should have been fine; no config changes of any sort were made; and the timestamps of the config files are all before the upgrade] ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 9:56am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/18 "2020-12-26T09:56:15Z")
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). ---
**Author:** ![Max\_G](https://community.openhab.org/user_avatar/community.openhab.org/max_g/32/64598_2.png) [@Max\_G](https://community.openhab.org/u/Max_G)\ **Post date:** [December 26, 2020, 10:07am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/19 "2020-12-26T10:07:32Z")
🙂 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. ---
**Author:** ![opus](https://community.openhab.org/user_avatar/community.openhab.org/opus/32/55801_2.png) [@opus](https://community.openhab.org/u/opus)\ **Post date:** [December 26, 2020, 11:07am UTC](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334/20 "2020-12-26T11:07:42Z")
Your welcome 🎄 My guess on your mqtt action usage is `Tasmota Admin`. [Next page](https://community.openhab.org/t/solved-upgrade-from-2-5-10-to-2-5-11-resulted-in-missing-mqttv1-processing/111334.md?page=2)