I now just integrated the the mosquitto 2.0.17 package inside the firmware and removed the Mosquitto 2.0.18 package from the profile file. The i install the package after booting with the new firmware. So i just hope mosquitto will be fixed in the feature and i just can use the standard package again. If they didnt fix it i will go your way. Thx for your help, its a nice experience to get answers really soon in the onion community!

@crispyoz thanks a lot again. I'll post the result here after executing the above code.

I'm using golang, for MQTT over ssl. The solution in our code was to use tcps for the connector and port 8333. Granted, we're using certificates already in the ca-bundle (Amazon) for the upstream message broker, so we don't need to finagle self-signed certs. What language are you using?

@Alexandr-Didenko "Naturally" you didn't say anything about your Omega2+'s firmware (as usual;) Omega Firmware Changelog So - for example on a vanilla v0.2.0-b197 ... v0.3.2 b232 firmware - mosquitto has already installed. Run a top command even on your freshly installed Omega2+ please. # Omega2+ with v0.3.2 b232 firmware root@Omega-5BE1:/# opkg list-installed | grep -i mosquitto libmosquitto-ssl - 1.5.8-2 mosquitto-client-ssl - 1.5.8-2 mosquitto-ssl - 1.5.8-2 root@Omega-5BE1:/# opkg info mosquitto-ssl Package: mosquitto-ssl Version: 1.5.9-2 Depends: libc, librt, libuuid, libopenssl, libwebsockets-openssl Provides: mosquitto Status: unknown ok not-installed Section: net Architecture: mipsel_24kc Size: 76962 Filename: mosquitto-ssl_1.5.9-2_mipsel_24kc.ipk Description: Mosquitto is an open source (BSD licensed) message broker that implements the MQTT protocol version 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model. This package also includes some basic support for configuring via UCI This package is built with SSL support. TLS-PSK will be included (in both the client and broker) if OpenSSL is built with TLS-PSK support. Package: mosquitto-ssl Version: 1.5.8-2 Depends: libc, librt, libuuid, libopenssl, libwebsockets-openssl Provides: mosquitto Status: install user installed Architecture: mipsel_24kc Conffiles: /etc/mosquitto/mosquitto.conf cad5c6ae4ecf25e2709e88f2b92d75905ac4aedc622df6e9a536238c0b047856 /etc/config/mosquitto eaa6b71fbd8e5f7142d949432374017e4cb5d01cf5039b9cd4a65f8953126521 Installed-Time: 1566829837 root@Omega-5BE1:/# mosquitto -h mosquitto version 1.5.8 mosquitto is an MQTT v3.1.1 broker. Usage: mosquitto [-c config_file] [-d] [-h] [-p port] -c : specify the broker config file. -d : put the broker into the background after starting. -h : display this help. -p : start the broker listening on the specified port. Not recommended in conjunction with the -c option. -v : verbose mode - enable all logging types. This overrides any logging options given in the config file. See http://mosquitto.org/ for more information.

Did you ever figure this out? I think if you just want a server running, install the latest firmware, and you have one running. Connect your omega to a local wifi network, and you have a .local available address on your subnet. I do this as I use an Omega2 as my MQTT server for my local network. I changed my hostname to mosquitto and now through my network via the web console app and I can connect to this server using mosquitto.local from other hosts. It doesn't take a lot of setup. Or, was your question related to something else?

Apologies, I know this is an old thread but I have followed Paul Cousins instructions too and also have the "Connection refused" Error. I have tried to check that I have put the certificates over in a couple of different ways but as I am downloading them from Amazon to a mac and then uploading them to the onion, I'm not sure how I could be disturbing them. I have looked for others having this problem and I don't see anyone so I'm really confused to know what I might be doing wrong. Any chance you can say any more about why reinstalling the certificates worked for you? Many thanks Robin

I think it useful to understand how the build system works so you can always install any OpenWrt package you may need. If you search for the packages on OpenWrt.org you can download the build configuration file(s) and it lists the dependencies. Here is how you would use the build system to build mosquitto which also handles the dependencies. You run the scripts from the directory in which you install the build system: ./scripts/feeds update ./scripts/feeds install mosquitto make menuconfig Here's the output: Installing package 'mosquitto' from packages Installing package 'libwebsockets' from packages Installing package 'libuv' from packages Installing package 'c-ares' from packages I don't use Docker, I think it strangles performance.

I've just gotten my Omega 2 board today, and I'm thinking along very similar lines — I want my Onion boards to either send MQTT messages when something happens to their connected hardware, or do something with that hardware according to MQTT messages received. Like you (Sebastian), I see no point in running an MQTT broker on the device — the broker will be elsewhere; these are edge devices that should merely be MQTT clients. I see you solved it by using some clever files and shell scripting. But did you consider using Python? From other threads, it looks like paho-mqtt can be installed for python, which should make it pretty easy (and possibly more efficient) to subscribe to topics and do stuff in response (or conversely, to publish MQTT messages in reaction to anything you can sense in Python). Just wondering if I am somehow barking up the wrong tree, or whether this is a sensible way to do it.

Did you end up solving this? I am currently trying to cross compile mosquitto with websockets for the Omega2+ and NO luck. Thanks!

@mark-doutre Thanks - found that. Though I think it would still be good if there was a more direct method of stopping it. Regarding the running of the broker on the Omega, I agree with your comment. So far I have just been playing with MQTT and having a local broker under one's own control is a valuable part of getting to understand it all. In the real world, using a separate broker somewhere else is probably the way to go. Any way, thanks for your interest and comments