mosquitto | Eclipse Mosquitto - An open source MQTT broker

Solution!!

Since service is not executeable, instead of using service, i just executed mosquitto via mosquitto command.

https://forum.openwrt.org/t/mqtt-service-command-is-not-working-via-c-lua/116434/2

The code you've posted is not complete (missing closing } from your publish function) and you haven't shown were you are calling that function.

You also haven't followed the instructions in the answer to the question you took the code from, which clearly states that you should be calling client.subscribe(topic) in the on connect callback.

client.connected won't return true until after the on connect event handler has been completed.

Add a call to client.subscribe() to the on connect event handler so you actually have some messages to trigger the on message event handler

It looks like there is a sequence of things happening that is causing Connector to rerender and drop the connection, here's what I think is going on:

1. App is subscribing to store state, causing it to rerender every time a new message is received.
2. You're recreating your mqtt config object every time App renders, because you're passing an object literal {keepalive: 10}
3. In Connector.tsx line 48, the mqttConnect callback depends on the mqtt options object. React does a referential equality check, sees the options have changed, and causes the callback to be recreated.
4. In Connector.tsx line 59, this causes the useEffect to rerun because the callback changed, which calls its teardown function, which ends the mqtt connection.

To fix it, you should create your MQTT options outside of App so that they don't change.

Firstly the errors about not being able to open the pid or log files are because you are running mosquitto as a normal user (probably pi). This user does not have permission to read/write to file in /var/run or /var/log hence the failure when you try and run it "manually".

You've not said how you installed 2.0.11, as the default version bundled with Bullseys is still a 1.5.x build. Assuming you used the mosquitto.org repository then the mosquitto service will have been installed and configured. It will automatically pick up the default config file at /etc/mosquitto/mosquitto.conf as should be displayed with:

Mosquitto does not automatically load a configuration file, you must pass it one on the command line with the -c flag if you want to use anything other than the default values. When run as a service the service definition include the -c pointing to the default configuration file.

The default configuration file is normally stored in /etc/mosquitto/mosquitto.conf. This file includes the following line:

So after all, @hardillb answer helped me.

At first it didnt send the message even if I saved the client in a variable because I saved it before the client was connected.

Working code:

From the docs:

An optional array of null-terminated strings specifying the servers to which the client will connect. Each string takes the form protocol://host:port. protocol must be tcp or ssl. For host, you can specify either an IP address or a host name. For instance, to connect to a server running on the local machines with the default MQTT port, specify tcp://localhost:1883. If this list is empty (the default), the server URI specified on MQTTClient_create() is used.

Make sure your URL starts with ssl:// not just an IP address and port.

From the docker docs

When you use a bind mount, a file or directory on the host machine is mounted into a container. The file or directory is referenced by its absolute path on the host machine.

So you have to pass the full (absolute) path to the mosquitto.conf e.g. /home/jay/mosquitto/mosquitto.conf (see this issue for info on why). You can get your shell to help: