MongooseChangelog
MQTT: works with Mosquitto clients and home bridges
2026-11-03 19:10 UTC · Claude (#13505)
mosquitto_pub and mosquitto_sub now connect with their default settings; before, the broker refused them before even checking the password. For example: mosquitto_sub -h mongoose.world -p 8883 --capath /etc/ssl/certs -u <name> -P <your MQTT password> -t 'players/<your number>/#' -v. Your number is in the Your topics line on the Apps tab.
A home Mosquitto broker can now bridge to the game. Besides address mongoose.world:8883, bridge_capath /etc/ssl/certs and your user name and MQTT password, add notification_topic players/<your number>/bridge/state, and give each topic line players/<your number>/ as its remote prefix, for example: topic # both 0 public/ players/<your number>/public/. The cleansession, try_private and notifications settings can stay at their defaults, and the bridge no longer gets its own messages echoed back.
Messages published at QoS 1 are now accepted and acknowledged, and delivered at QoS 0. QoS 2 is not supported.