v1.13.0

Summary

Add MQTT notifications for Significant Connections.

TapMap 1.13.0 can publish new Significant Connections to an existing MQTT broker. MQTT is optional, and the connection can be set up with tapmap --configure-mqtt. It supports TLS and optional authentication on Windows, macOS, Linux and Docker.

Notifications use the existing Significant Connections detection and do not affect event history. By default, notifications start after 7 active Insights days to avoid sending events while TapMap is still building its initial history.

Features

• Add MQTT notifications for Significant Connections
  • Set up the MQTT connection with tapmap --configure-mqtt
  • Support TLS and optional authentication
  • Reconnect automatically after connection loss
  • Support Windows, macOS, Linux and Docker
• Add notification learning period
  • Start notifications after 7 active Insights days by default
  • Configure the learning period with TAPMAP_NOTIFICATION_LEARNING_DAYS
  • Continue recording Significant Connections during the learning period

Fixes

• Handle Significant Connections when the process PID is unavailable

Testing

MQTT was manually tested on Windows, Linux, macOS, and Docker, including configuration and persistence, TLS and authentication, message delivery and payloads, learning-period behavior, connection loss and reconnection, unavailable brokers, authentication rejection and recovery, invalid configuration, and clean shutdown.

The automated test suite and Ruff checks pass.

Documentation

• Add MQTT documentation
• Update Help, About, Docker, environment variables, Privacy and architecture documentation

Notes

• MQTT delivery uses QoS 0 and messages are not retained
• MQTT delivery is best effort and does not affect Significant Connections history
• No persistence-format changes

Full Changelog: v1.12.3...v1.13.0