Hi, i use MDEK and PANS2,
Can i update Mosquitto in my bridges to the latest version or if i update mosquitto the bridge can have issues?
Regards
Ivan
Hi, i use MDEK and PANS2,
Can i update Mosquitto in my bridges to the latest version or if i update mosquitto the bridge can have issues?
Regards
Ivan
Hi Ivan
I can’t completely advise regarding this, it may break the gateway functionality. I guess the best is to try and revert to the previous image if you see poor performance with the new mosquitto version.
Thanks
Yves
Hi Ivan,
newer version of Mosquitto should work also.
Any MQTT v3.1.1 Broker or Mosquitto version 1.5.1 or newer should be fine.
Cheers,
TDK
Hi, following this thread, could/should a Mosquitto upgrade just be done via apt-get on the Pi or another means or was it installed using an alternative approach?
Hi @richb
the Mosquitto on the RPi was compiled from source code because the default one did not had turned on the websocket interface. The current versions of MQTT should support websocket out of box so you can try it via apt-get.
Best regards,
Jiri
Hi @jk-leapslabs - thank you. I’d seen that mosquitto wasn’t in dpkg
so thought it must have been from source, but couldn’t figure out why. Nice to know.
I’ve done the following:
apt-get update
apt-get install mosquitto=1.5.7-1+deb10u1
/usr/local/bin/dwm-daemon: error while loading shared libraries: libmosquittopp.so.1: cannot open shared object file: No such file or directory
sudo ldconfig
.-v 6
appended to the command in the init.d script to help any debugging.INFO [5479] [leaps::core::mq_looper@302] Client decac414c5a55582 reconnect
(over and over)
So, what do I think I know from this:
Any answers to any of my questions much appreciated. Any suggestions of config or things I should be doing also hugely appreciated.
And for context, here’s why I’m doing this: I would like to write an ansible playbook/module that automates the build of gateways.
I’ve seen that dwm.ko is compiled against 4.14.50-v7+ so I realise that’s a hard and fast dependency that won’t budge. And I’m cool with using that as the base OS for ansible to run against.
I had hoped I could :
That got me poking at mosquitto and before i knew it, I was up to my neck in it
If you can think of an easier way for me to achieve the same result, then groovy. Any advice about how the dwm-daemon works with mosquitto that might help me would be massively appreciated too.
Hi @richb
The mosquitto provides the broker and the client library (used by dwm-daemon) which can be installed separately. If the daemon is running, to see why the daemon is not connecting to the broker, I would run the broker manually with verbose debug log and see why is it so. It might give you some useful hits.
Jan.
@leapslabs - ah, cool. Obvious now you say it - it’s the client library for the daemon, makes sense. That was the bit I was missing from my understanding when I wrote:
I’ll try running mosquitto manually and with verbose debug and see what I find. Thank you again