MQTT availability #15

New Issue

2026-10-27T09:28:33+01:00

adam commented

2026-10-27 09:28:33 +01:00

Excellent software. I was just wondering has the MQTT logging been fully implemented? I have enabled it in the config but the logging just reports that its still disabled or not available. Thank you

Excellent software. I was just wondering has the MQTT logging been fully implemented? I have enabled it in the config but the logging just reports that its still disabled or not available. Thank you

adam closed this issue

2026-10-27 09:28:33 +01:00

adam commented

2026-10-27 09:28:34 +01:00

Hey there! And thank you, the mqtt broker needs to be over web sockets, which should be better documented for sure!

Hey there! And thank you, the mqtt broker needs to be over web sockets, which should be better documented for sure!

adam commented

2026-10-27 09:28:35 +01:00

Thanks for the fast response. The example shows port 1883, should that be over web sockets? I have enabled web sockets on the broker and it still doesn't want to work.

MOSQUITTO LOG

1767460936: mosquitto version 2.0.21 starting
1767460936: Config loaded from /etc/mosquitto/mosquitto.conf.
1767460936: Opening websockets listen socket on port 1883.
1767460936: mosquitto version 2.0.21 running

sudo systemctl status mosquitto

mosquitto.service - Mosquitto MQTT Broker
Loaded: loaded (/usr/lib/systemd/system/mosquitto.service; enabled; preset>
Active: active (running) since Sat 2026-01-03 17:22:16 GMT; 14min ago

config.yaml

MQTT publishing configuration (optional)

mqtt:
# Enable/disable MQTT publishing
enabled: true
# MQTT broker settings
broker: "localhost"
port: 1883

# Authentication (optional)
username: null
password: null

# Base topic for publishing
# Messages will be published to: {base_topic}/{node_name}/{packet|advert}
base_topic: "meshcore/repeater"

Log message

[17:33:11]
MQTTHandler INFO MQTT disabled or not available

Thanks for the fast response. The example shows port 1883, should that be over web sockets? I have enabled web sockets on the broker and it still doesn't want to work. MOSQUITTO LOG 1767460936: mosquitto version 2.0.21 starting 1767460936: Config loaded from /etc/mosquitto/mosquitto.conf. 1767460936: Opening websockets listen socket on port 1883. 1767460936: mosquitto version 2.0.21 running sudo systemctl status mosquitto mosquitto.service - Mosquitto MQTT Broker Loaded: loaded (/usr/lib/systemd/system/mosquitto.service; enabled; preset> Active: active (running) since Sat 2026-01-03 17:22:16 GMT; 14min ago config.yaml # MQTT publishing configuration (optional) mqtt: # Enable/disable MQTT publishing enabled: true # MQTT broker settings broker: "localhost" port: 1883 # Authentication (optional) username: null password: null # Base topic for publishing # Messages will be published to: {base_topic}/{node_name}/{packet|advert} base_topic: "meshcore/repeater" Log message [17:33:11] MQTTHandler INFO MQTT disabled or not available

adam commented

2026-10-27 09:28:36 +01:00

Yes that's the correct port and how I have it setup using web sockets if you enable debug in config yaml it might point you in the correct direction 👍

Yes that's the correct port and how I have it setup using web sockets if you enable debug in config yaml it might point you in the correct direction 👍

adam commented

2026-10-27 09:28:36 +01:00

Also have you tested pub to the broker with something else?

Also have you tested pub to the broker with something else?

adam commented

2026-10-27 09:28:37 +01:00

I have discovered the issue. The mqtt section in the config file was indented by two spaces. I removed them and then it connected to the mqtt broker without issue. I think that your example config also has it indented. Thanks again for your help

I have discovered the issue. The mqtt section in the config file was indented by two spaces. I removed them and then it connected to the mqtt broker without issue. I think that your example config also has it indented. Thanks again for your help

adam commented

2026-10-27 09:28:37 +01:00

Great, thank you for letting me know. I’ll review the configuration example you brought to my attention. This will eventually be available in the web UI.

Great, thank you for letting me know. I’ll review the configuration example you brought to my attention. This will eventually be available in the web UI.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#15