prefixkit Ask an engineerAsk Support RU

Smart home

Mosquitto config generator

Build a mosquitto.conf for Mosquitto 2.x: password login, per-user permissions (ACL), WebSocket for browsers and TLS for connections from the internet, plus the mosquitto_passwd commands.

Users

Everything is built in the browser: passwords and addresses are not sent anywhere.

Why the broker refuses

Since 2.0, Mosquitto with no config listens on localhost only and refuses anonymous clients. That is why you need listener 1883 and a password file. Code 5 (not authorised) means a bad login or ACL; a connection error means the port is closed or the broker listens elsewhere.

Test the broker from the browser (needs WebSocket, and wss on 8884 from an HTTPS page): MQTT client. Get a Let’s Encrypt certificate as for a website; restart Mosquitto after renewal.

More tools: smart home

Home Assistant tools newEverything for the smart home section in one place.Remote access to Home Assistant newCloudflare Tunnel, nginx, Caddy, WireGuard configs.ESPHome generator newBoard and sensors to a ready YAML with keys.Zigbee coordinator picker newWhich stick for ZHA, Zigbee2MQTT and Thread.Zigbee device catalog new5,400 devices: features, MQTT, automations.ESP32 pinout newWhich GPIOs are safe: ESP32, C3, S3, ESP8266.MQTT discovery generator newConfig topic and JSON for Home Assistant.Zigbee channel vs Wi-Fi newPick a Zigbee channel clear of your Wi-Fi.Camera RTSP URL newHikvision, Dahua, Reolink, Tapo stream URLs.Frigate config generator newCameras, go2rtc, Coral or OpenVINO.Zigbee2MQTT config newAdapter, port, MQTT, channel.Home Assistant Docker Compose newHA, Mosquitto, Zigbee2MQTT, ESPHome stack.MQTT client newTest a broker over WebSocket in the browser.Home Assistant YAML checker newAutomations and configuration.yaml mistakes.
Idea?