Go deeper
Transports, other install paths, variables, Community, fanout, Home Assistant, troubleshooting.
This section assumes Meshloom is already running. It takes what used to live in the advanced READMEs so you do not have to open the repo for a setting.
Project terms appear directly: transport, fanout, flood scope, path hash mode, and secure context. If one is unclear, start with What is it and Around messages.
Read Variables and settings first to separate startup configuration from database-backed settings. Meshloom Community is on for new installs unless you opt out. Security explains what Meshloom does not protect.
Radio transports
USB serial, TCP, or Bluetooth — configured in the web UI.
Other install paths
Docker, systemd, Portainer, and a checkout for development.
HTTPS
Local TLS, WebGPU, and Meshloom behind a reverse proxy.
Variables and settings
What lives in the environment, what lives in the database.
Radio, contacts, and channels
What Meshloom loads onto the radio, flood scope, and hop width.
Fanout
MQTT, bots, webhooks, Apprise, SQS — whatever Meshloom hears can leave again.
Meshloom Community
Join, bind an IATA code, publish overheard packets, and share hashtag names.
Home Assistant
MQTT Discovery, devices, automations, and the topics that break.
Push notifications
Notifications even when the tab is closed. HTTPS required.
Troubleshooting
DEBUG logs, /api/debug, and the radio cases that come back often.
Security
Basic auth, turning bots off, exporting a key. None of this invents accounts.