[Solved] OH2: upgrade from 2.5.6 to 2.5.9-1; OH no longer talks to mosquitto

Setup, Configuration and Use Installation
1

Version: 2.5.9 (Build)
System: Host: rpi3ohv2 Kernel: 4.19.66-v7+ armv7l (32 bit) Console: tty 2
Distro: Raspbian GNU/Linux 9 (stretch)

I am using mqtt v1.
Machine was working nicely.
Upgraded via apt-get, which upgraded OH 2.5.6 to 2.5.9-1
Restarted; heaps of errors; OH could not load bindings
stopped OH service
clean-cache
started OH service
started as expected; however, it does not talk to mosquitto

mosquitto -v shows connections from a bunch of other machines, but not openHAB.

mosquitto -v
1603266054: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1603266054: Using default config.
1603266054: Opening ipv4 listen socket on port 1883.
1603266054: Opening ipv6 listen socket on port 1883.
1603266054: New connection from 192.168.1.62 on port 1883.
1603266054: New client connected from 192.168.1.62 as mosqpub|506-rpi33 (c1, k60).
1603266054: Sending CONNACK to mosqpub|506-rpi33 (0, 0)
1603266055: Received PUBLISH from mosqpub|506-rpi33 (d0, q0, r0, m0, 'ArgyleCourt/Property/AcuRite5in1', ... (173 bytes))
1603266057: New connection from 192.168.1.9 on port 1883.
1603266057: New client connected from 192.168.1.9 as rPiPy_BMS (c1, k60).
1603266057: Sending CONNACK to rPiPy_BMS (0, 0)
1603266062: New connection from 192.168.1.54 on port 1883.
1603266062: New client connected from 192.168.1.54 as Arduino_BorePump (c1, k15).
1603266062: Sending CONNACK to Arduino_BorePump (0, 0)
1603266062: New connection from 192.168.1.58 on port 1883.
1603266062: New connection from 192.168.1.78 on port 1883.
1603266062: New connection from 192.168.1.52 on port 1883.
1603266062: New connection from 192.168.1.74 on port 1883.
1603266062: New connection from 192.168.1.61 on port 1883.
1603266062: New connection from 192.168.1.60 on port 1883.
1603266062: New connection from 192.168.1.76 on port 1883.
1603266062: New connection from 192.168.1.55 on port 1883.
1603266062: Received SUBSCRIBE from Arduino_BorePump
1603266062: 	ArgyleCourt/Property/Hub/BorePump/Demand (QoS 0)
1603266062: Arduino_BorePump 0 ArgyleCourt/Property/Hub/BorePump/Demand
1603266062: Sending SUBACK to Arduino_BorePump
1603266062: New client connected from 192.168.1.58 as arduino_MainGate (c1, k15).
1603266062: Sending CONNACK to arduino_MainGate (0, 0)
1603266062: New client connected from 192.168.1.78 as UNO_OutsideShellSensors (c1, k15).
1603266062: Sending CONNACK to UNO_OutsideShellSensors (0, 0)
1603266062: New client connected from 192.168.1.52 as arduino_AmbientLight_1 (c1, k15).
1603266062: Sending CONNACK to arduino_AmbientLight_1 (0, 0)
1603266062: New client connected from 192.168.1.74 as arduino_PumpStation1 (c1, k15).

Karaf shows

openhab> bundle:list | grep MQ                                                                                                                                                                  
230 │ Active │  80 │ 1.14.0                  │ openHAB MQTT Binding
237 │ Active │  80 │ 1.14.0                  │ openHAB MQTT Transport Bundle

bundle:stop both
bundle:start both

… no difference in behaviour.

Now I’m stuffed!

While typing this up, I rebooted the rPi. No difference. mosquitto is running and receiving the expected messages. OH does not ‘talk’ to mosquitto.

Any ideas?!

[edit/update]: What springs to mind…
I tried to run mqttv2 in parallel yesterday; installed the binding, created a broker thing and one generic thing, all via PaperUI. I removed all three, after finding out v1 and v2 do not want to run at the same time.
Could there be a residual config somewhere I need to get rid of?

2

OK…

What I have done…

I used PaperUI to uninstall the mqqt1 action and v1 binding.
Then installed the v2 binding.
Created a broker thing and one generic mqtt thing.

2020-10-21 19:03:24.635 [hingStatusInfoChangedEvent] - 'mqtt:broker:mymosquitto' changed from UNINITIALIZED to INITIALIZING
2020-10-21 19:03:24.743 [hingStatusInfoChangedEvent] - 'mqtt:broker:mymosquitto' changed from INITIALIZING to OFFLINE
2020-10-21 19:03:26.993 [hingStatusInfoChangedEvent] - 'mqtt:broker:mymosquitto' changed from OFFLINE to ONLINE

2020-10-21 19:03:26.385 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '127.0.0.1' with clientid ffa76501-e5fe-474a-9625-425487824e8b

2020-10-21 19:08:39.432 [hingStatusInfoChangedEvent] - 'mqtt:topic:56873dfe' changed from UNINITIALIZED to INITIALIZING
2020-10-21 19:08:39.485 [hingStatusInfoChangedEvent] - 'mqtt:topic:56873dfe' changed from INITIALIZING to ONLINE

This alone would not make my items/rule with mqtt involved work… but…

I then installed the v1 action and binding… and in that order mqtt2 then mqtt1 both work at the time time; and I can now start to change items and rules and add things.
And once done, can remove the mqtt1 action and binding.

I will report back here, once finished. :slight_smile: