GeoPulse 1.23.1

New Features

External MQTT over TLS (OwnTracks): You can now connect GeoPulse to external TLS-secured MQTT brokers, including
support for private/self-signed cert setups and optional client certificates (mTLS). See #410
Documentation: https://tess1o.github.io/geopulse/docs/system-administration/configuration/owntracks-mqtt-external-tls
Geofences: one rule for multiple people/devices: A single geofence rule can now target multiple subjects.
Simplified and improved UX. See #401
Geofence Events upgrade: Events view now includes stronger filtering (date/subject/event), sorting, pagination,
better mobile layout, and faster actions to mark events as seen. See #401
Geofence Templates redesign: Creating/editing templates is easier, with clearer defaults, preview support, and
external destination connection testing. See #401
Home page redesign: The home page now gives a clearer start experience with quick actions and daily at-a-glance
stats like latest GPS update, distance today, and time moving.

More resilient geocoding: Reverse geocoding now handles temporary provider instability better (fewer failed
lookups during provider/API issues). See #411
Clearer geocoding provider behavior in UI: The app now explains that switching primary/fallback providers affects
new lookups, while existing cached locations remain until reconciliation is run. See #411
Geofence notifications sync: Seen/unseen status handling between geofence events and notifications is more
consistent.
Container/deployment improvements: Docker image/build flow was optimized for smoother self-hosted deployments.
Docker image size was reduced by 180MB (was 467MB, now 286MB) Thanks to @duhow
Improved integration tests - they are running 5x faster now.

Timeline large-range fix: Resolved an issue where forcing load on very large timeline ranges could fail to refetch
correctly.
Notification panel layout fixes: Improved notification bell/panel positioning and overlap behavior, especially on
mobile and map-heavy views.