mqtt

What problem does it solve?

Synchronet BBS administrators and operators lack a unified, remote way to monitor real-time operations across multiple BBS hosts and execute safe control tasks without manual local server access, leading to delayed response to issues and cumbersome administrative workflows.

Core Features & Use Cases

• Correct MQTT Configuration Discovery: Eliminate the common mistake of checking the wrong configuration file by retrieving MQTT settings (enabled status, broker address, port, authentication, TLS mode) directly from the correct ctrl/main.ini location.
• Cross-Host Real-Time Monitoring: Subscribe to live MQTT topic streams to track server status, spy on node terminal output, monitor failed login attempts per IP, view log streams, and capture BBS-wide action events for full situational awareness across all connected hosts.
• Safe Remote BBS Control: Execute production-impacting operations like server recycling, pausing/resuming listeners, clearing failed login lists, injecting input or messages into active nodes, and setting node flags via MQTT control topics, with built-in guardrails to avoid accidental disruption.
• Use Case Example: A sysop can remotely identify a single IP launching brute-force login attempts, clear that IP's failed login strikes across all hosts, and recycle only the affected web server without disrupting active terminal users.

Quick Start

Use the mqtt skill to verify if MQTT is enabled for your Synchronet BBS and retrieve the correct broker address, port, and authentication details required to connect a monitoring client.