FIRE DEPARTMENT

StationCommand Changelog

Current beta version: B.3.4.26

Version B.3.4.26

Certification entitlement key correction

Aligned Certification Tracker & Verification with licensing v0.4.11 entitlement key cert_tracker_verification.
Retained compatibility with earlier certification entitlement aliases.
Fixes the module showing DISABLED while the license server reports cert_tracker_verification: Enabled. Public QR verification continuity and licensing protections remain unchanged.

Version B.3.4.25

Apparatus-aware response counts

Active incident ARRIV, RESP, AVAIL, and UNLV totals now count personnel only; apparatus no longer inflate responder totals.
Apparatus remain listed in their current response status and are highlighted with a distinct blue row and APPARATUS label.
Incident-announcement responder counts/names are also personnel-only. No database migration is required.

Version B.3.4.24

Certification module production licensing hardening

Completed entitlement protection across private credential/certification management APIs, badge issuance, certification notification settings, scheduled jobs, and future private credential/certification/badge export routes.
Certification reminder and Michigan EMS sync jobs now fail closed when the Certification Tracker & Verification module is not licensed.
Certification-management navigation and pages are hidden/blocked when unavailable, while Administration → StationCommand License reports the module state and resolved entitlement key.
Existing public QR and verification links intentionally remain available after module disablement, expiration, or revocation, and all credential data is retained for later reactivation.
Added regression coverage for enabled, disabled, expired, revoked, grace, unlicensed, and temporarily-offline cached-license states. No database migration is required.

Version B.3.4.23

Category-controlled EMS sync + admin certification ordering

Michigan EMS expiration sync now appears only for categories Administrators mark as sync-capable; the built-in EMS category defaults to enabled.
The sync reuses the certification's existing Issuer Verification Link instead of requiring a duplicate Michigan registry URL.
Administrators and Training Administrators can move a member's certifications up/down using the same saved order used by My Credentials and public verification.
No database migration is required.

Version B.3.4.22

Nearby-jurisdiction CAD GPS tolerance

Added a per-CAD-agency Nearby GPS tolerance (default 10 miles) so neighboring-municipality and mutual-aid calls can still use CAD coordinates just outside the configured service boundary.
Wrong-state coordinates remain rejected, and points beyond the configured nearby tolerance still show CAD GPS rejected.
Accepted nearby coordinates show a warning with their distance outside the nearest service jurisdiction, while still plotting the incident.
When CAD supplies a nearby city/township, StationCommand tries that municipality first for private geocoding. No database migration is required.

Version B.3.4.21

Certification ordering, categories + Michigan EMS sync

Members can control certification display order, and Training Admins/Admins can assign category labels.
Administrators can add credential categories and choose label colors.
Verified Michigan EMS credentials can opt into daily public-registry expiration synchronization before reminder processing.

Version B.3.4.20

Credential decision emails

Member-submitted certification approvals and denials now send immediate decision emails to the member.
Decision-email failures do not roll back the credential review and are recorded in the audit trail.

Version B.3.4.19

Member QR analytics containment + overall statistics

Fixed per-badge analytics tiles on My Credentials overflowing into neighboring QR cards.
Added an Overall QR Analytics summary across all of a member's physical badge QR codes.
Overall statistics include badge counts, all-time/30-day/7-day opens, and first/last QR-open timestamps. No database migration is required.

Version B.3.4.18

Nodemailer mail engine + advanced delivery diagnostics

Replaced the custom SMTP/MIME sender with Nodemailer 7, matching the transport approach used by Fera Poker.
All StationCommand email flows now use Nodemailer, including invitations, certification approval requests, expiration warnings, test emails, and scheduled reminder deliveries.
Added an Advanced Email Delivery Diagnostic that sends one traceable message and shows message ID, accepted/rejected/pending recipients, envelope addresses, final SMTP response, message size, and timing.
Test reminder results now say the SMTP relay accepted messages rather than claiming inbox delivery, and show per-recipient diagnostics. No database migration is required.

Version B.3.4.17

Database-backed administrative settings

Fixed PostgreSQL/MySQL persistence for Email & Notifications, including saved SMTP configuration.
Generated Railway reminder-key state and Session Security settings now survive database-backed deployments/restarts.
Active weather-test state is also stored in the database for persistence parity with JSON mode.
No database schema migration is required; the existing cc_state table stores the added settings keys.

Version B.3.4.16

SMTP diagnostics + recipient previews + QR admin cleanup

Added a Test SMTP Connection action that validates the SMTP server, TLS/STARTTLS, authentication, and From Address without sending a message.
Added expandable recipient previews for test emails, certification approval reviewers, department expiration summaries, and personal member warnings.
Generated Railway reminder keys can now be revealed/copied later by authorized administrators; older hash-only keys must be rotated once.
Collapsed the Physical Badge QR Codes manager by default and widened the responsive admin badge cards to prevent squeezed controls. No database migration is required.

Version B.3.4.15

Credentials personnel counts + standard personnel ordering

Added an Active Personnel count to Administration → Credentials & Certifications.
The credential personnel directory now uses the department-wide Personnel Display Order: rank first, then Personnel Number or alphabetical order according to the Personnel setting.
Inactive personnel are kept at the bottom, sorted by the same rank/secondary rules, with a clear Inactive Personnel divider.
Pending approval badges remain visible without overriding the configured personnel order. No database migration is required.

Version B.3.4.14

Personnel device assignment + dedicated Credentials/Apparatus administration

Inactive members are hidden from the Active Members list by default and can be expanded with Show Inactive Members.
Active911 device assignment now lives directly on Personnel cards and supports multiple devices per member; assigned devices disappear from other member/apparatus pickers until unlinked.
Added an Active911 device-directory Resync Devices from API action under Administration → Integrations → Active911, with CSV import retained as a fallback.
Moved Credentials & Certifications and Apparatus into their own Administration pages; Apparatus now selects from available Active911 devices rather than requiring a typed ID. No database migration is required.

Version B.3.4.13

Fixed-time Railway reminders + inactive member retention

External certification reminder cron calls are now authoritative; use Railway cron 0 12 * * * for one daily run at 8:00 AM EDT / 7:00 AM EST.
Email & Notifications can generate/rotate a Railway cron key. The full key is displayed once and only a SHA-256 hash is retained by StationCommand.
Personnel can be deactivated/reactivated without deleting historical call information, certifications, credential profiles, or physical badge QR codes; inactive members cannot sign in and are removed from current assignment selections.
Public credential verification for retained inactive members remains available and clearly shows that the person is not currently affiliated. No database migration is required.

Version B.3.4.12

Daily Railway certification reminders

Added a protected Railway cron endpoint for certification expiration warnings using CRON_SECRET.
CERTIFICATION_REMINDER_SCHEDULER=external disables the web process hourly reminder loop so expiration warnings can be scheduled externally once per day.
The cron endpoint only performs the sweep during the configured department-local Daily Reminder Hour and retains same-day de-duplication.
Added a ready-to-copy Railway Function and deployment guide for an 8 AM Eastern schedule that follows daylight-saving time. Approval-request emails remain immediate. No database migration is required.

Version B.3.4.11

Certification approval-request email

Member certification submissions and pending verified-certification updates now immediately email enabled Administrators and Training Admins for review.
Approval emails identify the member/certification, summarize proposed verified-record changes, and link directly to Administration → Credentials & Certifications.
The existing Email & Notifications SMTP configuration powers approval requests; the optional additional department mailbox remains an expiration-warning recipient only.
Email delivery failures are audited without rolling back the saved certification submission, and Email & Notifications now shows separate expiration-recipient and approval-reviewer counts. No database migration is required.

Version B.3.4.10

Verified certification revisions + approval queue

Redesigned My Certification Records to mirror the clean verified-certification rows on the public verification page; add/edit forms stay hidden until requested.
Member edits to an already verified certification now create a separate Verified / Pending Update revision, keeping the current approved values visible publicly until review.
Credential managers can approve or reject pending revisions; approval promotes the proposed values and preserves the prior verified metadata in history, while rejection leaves the current verified record unchanged.
Added shared pending-approval counts/notices for certification reviews and pending Station Display pairings, with certification queues sorted to show pending work first. No database migration is required.

Version B.3.4.9

My Credentials permissions + responsive badge layout

Fixed the My Credentials profile/QR layout so summary cards and physical badge QR cards do not overlap at desktop and smaller widths.
Members can mark certifications Let expire to suppress expiration reminder emails; preference-only changes preserve an already verified certification.
Members can create managed physical badge QR codes and rename their friendly labels while the immutable badge URL code remains locked.
Credential managers can lock an individual member from self-service badge QR changes and/or profile-photo changes; the server enforces both locks. No database migration is required.

Version B.3.4.8

Immutable badge QR URLs + confirmed deletion

Physical badge URL codes are permanently locked after QR creation; server-side validation prevents later URL changes.
Friendly names and revocation messaging remain editable without changing the printed QR identity.
Added permanent badge deletion with explicit confirmation that the printed QR and badge-specific verification access will stop working.
Badge deletion is distinct from reversible revocation and is recorded in the Application Audit Trail. No database migration is required.

Version B.3.4.7

Unified Personnel, invites, and custom rank hierarchy

Combined People and Login into one Personnel record; login email is optional and can be added later.
Added StationCommand invite emails and resend-invite status using the existing Email & Notifications SMTP configuration.
Added a drag-and-drop custom Rank Hierarchy with editable rank names, abbreviations, public names, and tied peer levels.
Ranks sharing a hierarchy level are treated equally for operational sorting and rank-based hierarchy checks, while application access roles remain separate.
Members can view analytics for their own managed physical badge QR codes from My Credentials.
No database schema migration is required.

Version B.3.4.6

Email notifications + Training Admins + Member rank

Added a dedicated Email & Notifications administration page with persisted SMTP settings, global enable/disable controls, department recipient policy, and environment-variable fallback.
Added Training Admin as a limited account permission for certification/credential management and department-wide expiration alerts without full administrator access.
Certification expiration digests can notify all Admins, all Training Admins, and an optional department mailbox; members can independently opt out or select only the reminder milestones they want.
Added a neutral Member rank below the operational/probationary ranks for department members without a Firefighter or EMS role.
No database migration is required.

Version B.3.4.5

Certification email reminders + optional revoked warning

Added department certification reminder emails at 90, 60, 30, 14, 7, 6, 5, 4, 3, 2, and 1 day before expiration, on expiration day, and daily afterward for active members.
Added a Department Branding reminder-email recipient, generic server-side SMTP delivery, test/send-now controls, and per-certification Let Expire suppression.
Inactive members are skipped and successful reminders are de-duplicated per certification per department-local day and audited.
Revoked physical badges can now omit the red warning after Continue to Credentials while still showing the full revocation reason on the revoked-badge page.
No database migration is required.

Version B.3.4.4

Friendly badge URLs + revoked credential workflow

New badge QRs use friendly managed paths such as /q/MFR45-BADGE1, with badge-specific /verify/MFR45/BADGE1 and /verify/MFR45/BADGE1/revoke routes.
Revoking a physical badge now requires a public full revocation reason and a short warning message; scans open the revocation reason page before offering Continue to Credentials.
Continuing from a revoked badge shows the normal responder credentials with the configured red warning banner, while active badges remain warning-free.
The printed QR path remains stable through responder Public Verification ID and badge-code changes, and legacy B.3.4.3 opaque QR URLs remain compatible. No database migration is required.

Version B.3.4.3

Managed badge QR codes + verification analytics

Added multiple independently managed physical-badge QR codes per responder using StationCommand-controlled /q/<token> redirects.
Each badge can be named, downloaded, revoked/reactivated, and tracked independently while continuing to follow the responder's current public verification ID.
QR exports contain the scan-ready QR plus only the badge friendly name underneath.
Added per-badge analytics and department-wide Analytics & Security reporting that separates QR opens from direct verification-page visits.
No database migration is required.

Version B.3.4.2

Probationary ranks + verification titles

Added Probationary Firefighter and Probationary MFR to personnel, account, and responder-device rank controls.
Both probationary ranks sort below Firefighter and MFR and use PFF/PMFR operational abbreviations.
Public credential verification now spells out rank titles such as Medical First Responder and Probationary Medical First Responder.
No database migration is required.

Version B.3.4.1

Credential photo crop + proof controls

Added drag/zoom/crop profile-photo editing for responder self-service and administrator credential management.
QR downloads now export only the scan-ready QR image in a rounded bordered white square with scan-safe spacing; no title, verification ID, or URL text is added.
Issuer verification links and uploaded certificate/PDF evidence now have independent public visibility controls, allowing either proof source, both, or neither.
Public APIs enforce the new proof controls independently. No database migration is required.

Version B.3.4.0

Credential & Certification Verification

Added Personnel-linked credential profiles with human-readable public IDs such as FF45 and public /verify/<ID> pages.
Added QR generation/scanning, responder photos, current/not-current affiliation status, certification expiration tracking, issuer verification links, and image/PDF evidence.
Members can submit certifications and renewals; administrators can verify/reject them, manage public visibility, and explicitly approve evidence for public viewing.
Private certificate files stay private by default, public verification omits certificate/license numbers, verification lookups are rate limited, and credential actions are added to the existing audit trail.

Version B.3.3.13

Respond API audit trail

Added successful and denied Station Command Home Respond API access to Analytics & Security → Application Audit Trail.
Entries identify the Home integration, endpoint, optional incident ID, source IP, user agent, outcome/status, and credential source without recording bearer tokens.
Frequent successful tracking polls are coalesced into five-minute audit windows; repeated denied requests from the same IP/endpoint are coalesced into one-minute windows.
Respond API entries use the existing audit retention, search, action, and time filters. No database migration is required.

Version B.3.3.12

Station Command Home shared mapping API

Added bearer-token protected /api/v1/respond/mapping so Station Command Home can retrieve the same browser-safe StationCommand map source list and priority order.
The response includes default map features, aircraft/overlay settings, satellite priority, and Multiview/Street View configuration plus a short revision hash for caching.
Server-only ArcGIS geocoders and road-snap configuration remain private and are not returned.
Home incident payloads/webhooks advertise the mapping endpoint, and the Integrations page displays the complete Mapping API URL. No database migration is required.

Version B.3.3.11

Department time zone

Added a Department Time Zone setting to Administration → Department Branding, defaulting to Eastern Time (America/New_York).
Department statistics, reports, period filters, station-display clocks, calendar day grouping, and shared timestamps now follow the saved department time zone rather than a hard-coded Detroit/Eastern zone.
Common U.S. zones plus UTC are available and daylight-saving changes are handled automatically. No database schema migration is required.

Version B.3.3.10

Department Statistics month-label correction

Fixed an Eastern-time rollover bug that shifted month labels backward by one in Department Statistics comparison tables.
January through December now label correctly in weekday, time-of-day, day-of-month, and call-type month comparisons.
Incident grouping/counts were already correct; this release fixes the displayed month labels. No database migration is required.

Version B.3.3.9

Department Statistics table + ranking polish

Wide comparison tables now scroll inside their own panel instead of widening the entire page.
Calls by Time of Day is stacked below Calls by Day of Month.
Impossible month/day combinations such as Feb 31 display — instead of 0.
Top addresses use competition ranking and include every address tied at the 10th rank.

Version B.3.3.8

Department Statistics redesign

Redesigned Department Statistics with higher-contrast operational cards and panels.
Added Month, Full Year, and Overall modes. Full Year compares patterns across months; Overall compares patterns across years.
Top-address breakdowns now use StationCommand call type/classification rather than CAD/Active911 call titles.
Current-year forecasting remains available in Full Year mode. No database migration is required.

Version B.3.3.7

Department statistics + data-aware period filters

Added an authenticated Department Statistics dashboard with specific-year or overall views, Department Ops Center summary metrics, monthly/weekday/day-of-month/time-of-day trends, average calls per day, call categories, mutual aid, and top-10 building addresses with call-type breakdowns.
Current-year statistics include a full-year call projection blending year-to-date pace with the recent 90-day trend; completed years show their final actual total.
The Department Statistics page intentionally contains no maps.
Incident History and Incident Records default to the current month/year, then remove empty periods after the user changes selection. Selecting a year resets the month to All months.
Report period selectors now use only months/years that contain included statistical data after the initial current-period default.

Version B.3.3.6

Public address generalization + display/edit polish

Fixed overly broad public location suppression for common CAD address formats while preserving nearest-100-block/intersection privacy.
Explicit BLOCK notation, facility-prefixed numbered streets, road-only locations, and safe cross-street road fallbacks can now be generalized; provider-supplied suppressed/withheld addresses remain protected.
Changed the internal station-display hamburger to an overlay dropdown so opening it no longer pushes the page down.
Incident Edit now persists before reporting success, supports repeated saves while staying open, refreshes its current incident/timeline state, and shows a visible “Changes have been saved” toast.

Version B.3.3.5

Manual incident creation

Added Incident Records → Add Incident so administrators can create calls that were not captured through Active911.
Manual calls use collision-safe StationCommand IDs, are visibly marked Manual, and can retain an optional CAD/incident number.
Incidents can be created live for 30 minutes or as historical-only records and then use the normal map, classification, statistics, address-history, EOC, participation, edit, and reactivation workflows.
Configured local ArcGIS geocoding/road snapping is attempted automatically before the normal Incident Edit screen opens for map-pin verification. No database schema migration is required.

Version B.3.3.4

Configurable session security

Added Analytics & Security → Session Security with separate Member and Admin/EOC Manager maximum session lifetimes.
Added a configurable inactivity timeout, enabled by default at seven days, while retaining a 30-day default absolute session lifetime.
Added configurable recent-sign-in protection for sensitive administrator actions, enabled by default with a 60-minute window.
Sensitive account, session-revocation, license, incident-purge, and stored-integration-credential changes can require Google/Microsoft reauthentication and return to the page that requested it.
Existing Sign Out, Sign Out of All Sessions, and administrator Revoke Sessions behavior is preserved. No database schema migration is required.

Version B.3.3.3

30-day sessions + sign out everywhere

Extended authenticated member sessions from 12 hours to 30 days.
Opening /login while already authenticated now goes directly to the member menu, so Member Login does not restart OAuth unnecessarily.
Normal Sign Out now ends only the current browser session.
Added My Settings → Session Security → Sign Out of All Sessions to invalidate every existing StationCommand session for the current account.
Added Personnel → Accounts → Revoke Sessions so administrators can force any authorized user to sign in again on every browser/device.
Global revocation is persisted before success is returned. No database migration is required.

Version B.3.3.2

Mobile map, scrolling, display-dot, and section-collapse cleanup

Widened automatic map fits on phone-width screens so short routes and single-point maps do not zoom in excessively.
Restored normal mobile document scrolling on public/admin pages and incident-edit overlays.
Collapsed Incident Activity Log by default, added selectable idle-screen dots to the internal display header, and completed shared Administration section collapse behavior.

Version B.3.3.1

Managed local GeoLite2 + collapsible Administration sections

Added managed local MaxMind GeoLite2 City downloads and updates using the installation's MaxMind account ID/license key; normal IP lookups stay local.
GeoLite2 City defaults to the StationCommand data directory, can be updated manually from Analytics & Security, and checks for updates automatically when credentials are configured.
MaxMind web-service fallback is now opt-in and disabled by default; retained security-event IPs can be backfilled with the local database.
Made top-level settings panels throughout Administration collapsible/expandable while keeping them expanded by default, including consistent open behavior for existing details-style admin panels.
Added MaxMind attribution and approximate-location warnings. No database migration is required.

Version B.3.3.0

Administration canonical-home cleanup

Made every persistent setting have one intended administration home and stopped license checks from re-showing unrelated panels on Call Classification or other admin pages.
Integrations is now the sole UI home for Active911, Station Command Home, Google Workspace/Groups, and Google Photos; legacy direct integration URLs redirect to the matching section.
Consolidated People, Accounts, Active911 Devices, Apparatus, Display Order, and Merge People under Personnel; legacy Roster, User Access, and Device Directory URLs redirect to the appropriate Personnel section.
Fixed stale account/person/device links and apparatus-device changes that could recreate phantom apparatus entries. No database migration is required.

Version B.3.2.8

CAD classification organization + version consistency

Moved CAD prefix/agency classification (for prefixes such as COF, ALF, and CSF) from Active911 Integration to Administration → Call Classification.
Kept CAD agency, mutual-aid, service-jurisdiction, and boundary-verification behavior unchanged; only the administration location and wording changed.
Centralized HTML version rendering on the server so login, menu, station display, public display, changelog header, and asset cache keys use the running application version.
Removed stale hard-coded version fallbacks from display JavaScript and added regression checks for version consistency and CAD-classification placement.

Version B.3.2.7

Startup initialization hotfix

Fixed a PostgreSQL startup crash introduced in B.3.2.6 where incident-history mode constants were referenced before initialization.
Moved the bulk-mutation startup guard ahead of startup persistence so normalized state can be saved safely during application initialization.
No database migration or data repair is required; the B.3.2.6 incident-history settings remain compatible.

Version B.3.2.6

Apartment/unit-aware incident history

Added department-level incident-history matching controls for exact-unit, building-wide, or selected-building behavior.
Selected buildings can share prior-call history across apartments, units, suites, rooms, and lots while other addresses continue to match exact units.
Unit identifiers are recognized from both Active911's Unit field and common unit labels embedded in the address.
The policy applies consistently to both category counts and detailed address-history records and persists across JSON, MySQL, and PostgreSQL.

Version B.3.2.5

Full-height incident response layout

Fixed the active incident screen leaving a large unused band beneath the Last Updated / Last Checked footer when weather and lightning alerts were not visible.
Incident header, alert slots, response content, and status footer now use explicit grid rows so hidden alert rows collapse and the route/detail area expands to consume all remaining display height.
Weather and lightning alert banners still reserve space only while visible; 720p and 1080p kiosk layouts continue to use the adaptive compact sizing rules.

Version B.3.2.4

Clean route map and opt-in diagnostics

Moved station response distance and ETA into one compact bar below the route map so routing is no longer covered by status tags.
Normal incident-map mode now suppresses permanent station/tracking labels and aircraft/lightning status badges; map markers and operational overlays remain available without the diagnostic text.
Added Show diagnostic map labels under Administration → Mapping → Default Map Features → Incident / response map.
Diagnostic mode restores tracking freshness/counts, station labels, aircraft/provider status, lightning status, and route origin/source troubleshooting; on-map diagnostic labels are translucent.

Version B.3.2.3

Lower-cost Static Street View with optional Dynamic mode

Street View now defaults to the Street View Static API for incident detail, reducing billable usage while retaining the existing satellite fallback.
Administration → Mapping adds a Street View mode selector: Static image (recommended) or Dynamic interactive panorama.
Static images use the configured radius, outdoor imagery, automatic camera direction toward the incident, and are reused while the incident coordinate/radius remain unchanged.
The Street View diagnostic follows the selected mode and identifies the API that must be enabled on the restricted browser key.

Version B.3.2.2

Response map HUD safe zone

Moved route distance and drive-time information above Leaflet attribution so it remains readable on station displays.
When live tracking is visible, the route ETA pill stacks above the tracking-status pill instead of overlapping the bottom edge.
Added responsive placement for smaller display sizes.

Version B.3.2.1

Street View diagnostic correction

Fixed the Street View administration test using the geographic weather center for multi-station departments, which could legitimately be far from any Street View road.
The test now checks configured station locations, supports an optional geocoded/road-snapped test address, and distinguishes Google API/configuration failures from local panorama coverage.
If the selected radius has no result, the diagnostic probes up to 250 m and can recommend a larger radius instead of reporting a false failure.

Version B.3.2.0

Street View, satellite priority, and all-agency alert activation

Added optional Google Street View to the incident response detail panel, with a configurable search radius and automatic full-satellite fallback when no usable panorama is available or the call is an intersection.
Street View initially faces the incident coordinate and does not re-query unchanged incident locations on every normal display refresh.
Added an independent Satellite priority order under Administration → Mapping; the Kent preset starts with Kent Aerial 2026 → Kent Aerial 2023 → Esri World Imagery.
Active911 webhook payloads with usable incident data now activate immediately regardless of agency ownership; API enrichment remains asynchronous.
Active911 polling can also fall back to a usable alert-list record when a cross-agency detail endpoint is unavailable, so CAD/department mapping classifies calls without filtering them from the active display.

Version B.3.1.5

Active-station route focus and station labels

The normal station response map now fits only the assigned display station, that station's route, and the incident destination.
Other configured stations no longer force the route map to zoom out, but their markers may still appear when they naturally fall inside the fitted viewport.
Station markers use persistent map labels so incidental station pins remain identifiable without hover.

Version B.3.1.4

Adaptive route/satellite split

Changed incident Multiview from a satellite overlay into a true adaptive sibling panel beside the route map.
Wide TVs show route map and satellite side-by-side; narrower layouts can stack them so neither map covers the other.
The close satellite panel uses the same category-colored incident marker, coordinate, and pointed-tip anchor as the main response map.

Version B.3.1.3

Configurable address-history lookback

Added an Address History Lookback setting for station displays with 1 month, 3 months, 6 months, 1 year, 2 years, 3 years, 5 years, 10 years, and Indefinite options.
Address-history category counts and detailed fallback history use the selected rolling lookback window.
Paired TV/browser display profiles retain their own address-history window and persist it with the rest of the display profile.
Removed live responder-location sharing controls from the Station Display settings modal; those privacy controls remain available under My Settings.

Version B.3.1.2

Adaptive response screen and full-bleed satellite Multiview

Reworked the active-response screen around available viewport width and height so the operational map and information panels fit more reliably on 720p/1080p TV browsers.
Combined the former bottom history/check panels into a compact status strip showing only Last Updated and Last Checked.
The close satellite image fills the entire Multiview area, with title and provider/status labels floating over the imagery.
ArcGIS ImageServer NoData is transparent and lower-priority satellite providers remain underneath the preferred source, allowing fallback imagery to fill uncovered areas.
Fixed the CSS rule that cancelled Leaflet icon anchors so marker tips represent the actual geographic coordinate.

Version B.3.1.1

Kent aerial imagery and point-anchored markers

Added ArcGIS ImageServer sources using exportImage in Web Mercator for county/state-plane aerial imagery.
Multiview can now select satellite sources automatically by priority with provider failover before zoom fallback.
The Kent County preset now prefers Kent Aerial 2026 → Kent Aerial 2023 → Esri World Imagery for the close satellite inset.
Rebuilt station, incident, weather, and location pins so the visible marker tip is the actual map coordinate; the Multiview location marker uses the same point anchor.
Corrected the Kent BaseMap preset close-zoom limit while retaining OpenStreetMap as the permanent foundation.

Version B.3.1.0

ArcGIS dynamic mapping and address matching

Added ArcGIS Dynamic MapServer rendering through the ArcGIS export endpoint in Web Mercator, allowing local/state-plane county GIS services to align with Leaflet.
Added prioritized ArcGIS GeocodeServer providers with minimum match scores for private incident and station address resolution before the existing Nominatim fallback.
Added optional ArcGIS road-centerline validation/snap with automatic polyline-layer discovery, maximum snap distance, and OSRM fallback.
Added a one-click Kent County GIS Preset for Courtland plus an Administration → Mapping Test Address workflow.
Server-side geocoder/road-provider settings remain private and persist with the existing non-destructive Mapping configuration.

Version B.3.0.12

Same-origin Leaflet reliability

Leaflet 1.9.4 became a pinned StationCommand runtime dependency served from the StationCommand domain instead of depending on browser-side CDN availability.
Public Weather & Active Alerts retained external Leaflet CDNs only as emergency fallbacks.

Version B.3.0.11

Leaflet SRI correction

Corrected the Leaflet 1.9.4 JavaScript Subresource Integrity hash to the exact official value (...B9co0q...).
Updated the public weather fallback loader and map-page integrity checks while preserving weather-data/map-failure isolation.

Version B.3.0.10

Public weather map loading reliability

Fixed the public Weather & Active Alerts page failing with L is not defined when the primary Leaflet CDN did not load.
Added Subresource-Integrity-protected Leaflet fallback loading through jsDelivr and cdnjs for the public weather page.
Current conditions and active alerts now remain visible even if the radar map library or map layer fails; map failure is isolated to the radar panel instead of marking all weather data unavailable.
Corrected the Leaflet 1.9.4 JavaScript SRI hash on the other StationCommand map pages and strengthened the security self-check to verify the exact official hash.

Version B.3.0.9

Public Weather & Active Alerts

Moved Weather & All Alerts from the authenticated station display to the public-facing StationCommand site.
Added public route /weather with current NWS conditions, current NOAA/NWS radar, every active alert, and available NWS alert polygons, with no forecast content.
The public alert area now offers Weather & All Alerts whenever active alerts exist; each individual alert continues to use the concise View NWS Alert action.
Station display alert banners return to View NWS Alert only. Public weather and alert links remain high-contrast instead of browser-default blue.

Version B.3.0.8

Weather & active alerts view

Added a Weather & All Alerts action anywhere the private Station Display shows an active weather alert, including idle Weather, active incidents, and EOC mode.
The new full-screen weather detail view shows current conditions, current radar, every active NWS alert, alert polygons, and the configured aircraft overlay without showing forecast cards.
Each alert in the detail view keeps its own View NWS Alert action to the specific NWS product.
NWS alert action text across station display surfaces is explicitly forced to inherit the alert surface color instead of browser-default blue. The public page action remains the concise View NWS Alert label with explicit high-contrast text.

Version B.3.0.7

Station display rotation, TV fit, and alert-link polish

Moved Mutual Aid / Department Assistance into the normal Station Display idle rotation with per-display enable/disable control.
Made /display the canonical TV/browser pairing URL; /tv and /pair-display remain compatible aliases.
Reworked the kiosk shell around the browser's actual visible viewport, with compact low-height TV layouts and overscan-safe padding to reduce clipping on 720p and TV-browser canvases.
Public NWS alert actions now read View NWS Alert, and NWS alert links across station, radar popup, admin, and public views inherit the alert surface color instead of browser-default blue.

Version B.3.0.6

Automatic mutual aid tracking and reporting

Added report short names and an Our Department marker to CAD agency mappings.
Monthly report Mutual Aid counts are generated from incident data. Aid given is detected from the CAD prefix; unmapped CAD prefixes report as Unknown.
Incident Records include a collapsed Mutual Aid / Department Assistance editor where administrators can override who was helped and mark one or more departments that helped us.
Added YTD, last-month, and current-month assistance summaries by department short name for both aid given and aid received.
Excluded incidents are omitted from mutual aid statistics. Manual report adjustments remain available for publication-only corrections.

Version B.3.0.5

Specific NWS alert links

NWS alert banners and polygons now link to the appropriate human-readable NWS office/hazard product instead of the generic alerts page.

Version B.3.0.4

Persistent mapping configuration

Mapping settings and paired display configuration now persist correctly in PostgreSQL/MySQL across Railway restarts and deployments; new mapping defaults merge without overwriting saved values.

Version B.3.0.3

Station display pairing workflow and persistent pairing codes

Moved TV/browser pairing and per-device display settings from Administration → Mapping into Administration → Station Displays, alongside physical station configuration.
Denied pairing requests are now deleted from the active device collection immediately. Revoked/removed paired displays are also deleted immediately, so inactive devices no longer remain in the pairing list.
Pairing denial and device revocation/removal are retained as dedicated Security Log events with the administrator, display/device ID, display name, assigned station, source IP, and prior status.
Fixed /pair-display refresh behavior. A short-lived HttpOnly pairing-continuation cookie now restores the same pending request and six-digit confirmation code after a browser refresh instead of creating or losing the request.
The high-entropy pairing continuation secret is no longer stored in page JavaScript. Pairing status is authenticated by the HttpOnly continuation cookie, while the long-lived paired-display credential remains a separate HttpOnly device cookie.
Refreshing after administrator approval but before activation resumes the approved request and completes activation automatically. Expired, denied, or removed requests show a clear restart state.

Version B.3.0.2

Permanent fallback basemap and aircraft-on-radar correction

Leaflet now keeps a permanent OpenStreetMap foundation underneath every StationCommand map. ArcGIS, Google, custom XYZ/ArcGIS, and WMS sources render above it, so transparent/no-data areas and failed upper tiles reveal the fallback instead of a blank map.
The same foundation/failover runtime is shared by incident, EOC, Current Radar/weather, heat maps, analytics, admin, and public map surfaces.
Fixed the Weather/Current Radar aircraft toggle: aircraft is now actually requested and rendered on that map when Weather Map → Aircraft is set to All Aircraft or Helicopters Only.
Aircraft overlays now use map-instance state so Incident, EOC, Weather, and both heat maps can update independently without overwriting one another.
Aircraft feed failures now show the upstream error detail directly in the map status rather than silently appearing as an empty overlay.
Multiview now keeps the OpenStreetMap foundation beneath its satellite source and automatically steps down the satellite zoom when a provider does not have tiles at the requested level.

Version B.3.0.1

Aircraft visibility, unified map sources, and working satellite Multiview

Reworked the private incident/EOC aircraft overlay into transparent tactical labels: yellow directional aircraft/rotorcraft symbols, callsign, type, speed, altitude, and distance remain readable without an opaque label tile covering the map.
Aircraft retrieval now fails over server-side across ADSB.lol, Airplanes.live, and ADSB.fi, retains a short stale cache during provider outages, and shows an on-map status for loading, no nearby aircraft, provider name, cached data, or feed failure.
Unified map-source behavior across StationCommand. The same enabled sources, priority order, and failover list now drive incident, EOC, weather, heat-map, admin, analytics, and public map surfaces.
Converted Multiview from configuration-only groundwork into a working close-up satellite inset on incident and EOC maps. Incident Multiview centers on the mapped call; EOC centers on the most recently received mapped incident.
Added configurable satellite zoom (15–22) and per-source maximum zoom. The selected Multiview satellite source is automatically enabled when Multiview is saved so the inset cannot silently reference an unavailable source.
The satellite inset is deliberately non-interactive so it cannot steal TV/touch input from the operational map; it displays source attribution and a clear source/zoom status.

Version B.3.0.0

Mapping platform, aircraft overlays, and paired station displays

Added a dedicated Administration → Mapping page for department-wide map configuration and paired station-display management.
Leaflet remains StationCommand's rendering engine while administrators can prioritize and fail over among OpenStreetMap/XYZ, cached ArcGIS MapServer tiles, WMS, Google roadmap/satellite/hybrid/terrain, and other configured HTTPS map services.
Mapping defaults now apply across incident, EOC, weather, heat-map, analytics, public, station-editor, weather-location, and incident-editor map surfaces.
Added a live aircraft overlay to private incident and EOC maps with server-side provider failover. Each supported map can default to Off, All Aircraft, or Helicopters Only, with configurable radius and refresh interval. Aircraft now render as transparent tactical labels with callsign, type, speed, altitude, and distance, plus an on-map feed status.
Added temporary EOC-session controls for Weather, Aircraft mode, and map controls. EOC overrides reset when EOC mode is disabled, so the next activation starts from department Mapping defaults.
Added paired station-display device authentication. The TV only needs /pair-display; pending requests appear automatically in Administration → Mapping with the same six-digit code shown on the TV for visual Approve/Deny confirmation.
Pairing approval and the paired-device panel can set or later change the TV name, assigned station, enabled idle screens, rotation speed, calendar layout, and responder-scroll delay. Active TVs receive changes through StationCommand state updates without re-pairing.
The short-lived visual confirmation code is retained only while a request is pending and is deleted on approval, denial, or expiration. The separate high-entropy pairing secret and long-lived device token are HMAC-SHA256 hashed. Paired displays cannot use StationCommand admin/member write APIs.
Already-paired browsers that revisit /pair-display are recognized and redirected to their assigned station instead of creating a duplicate pairing request.
Added the configuration foundation for a future map multiview with a close satellite view and Street View provider without enabling the unfinished split-panel UI yet.
Carried forward B.2.4.3 multi-day calendar behavior and corrected beta-version references.

Version B.2.4.3

Multi-day calendar events and beta version-reference correction

Calendar-grid events now appear on every local calendar day they occupy on both the station display and authenticated member Events calendar.
Google Calendar all-day events retain explicit all-day metadata so Google's exclusive end date is handled correctly. An event with start September 1 and end September 4 appears on September 1, 2, and 3 only.
Timed events spanning midnight expand across each occupied America/Detroit calendar day. An event ending exactly at midnight is not repeated on the following day.
Multi-day calendar cells identify continuation context with labels such as Day 1 of 3, Continues, and Ends, while list views continue to show each event once with its full range.
Corrected StationCommand beta notation throughout source comments, historical changelog entries, and documentation so beta builds consistently use B.#.#.#.
Renamed the B.2.3.6 compliance documentation files to use the corrected B. prefix.

Version B.2.4.2

Multiple CAD jurisdictions and public map reliability

CAD Agency / Township Mapping now supports multiple service jurisdictions per CAD prefix. Administrators enter one city/township/jurisdiction per line for an agency.
Each configured service jurisdiction is resolved and stored separately. CAD GPS is considered inside the agency service area when it falls inside any resolved jurisdiction.
Private address/intersection geocoding tries the configured jurisdictions in order, preferring a jurisdiction whose name matches the CAD city field. This supports agencies responsible for both a city and surrounding township(s).
Partial boundary verification no longer falsely rejects CAD GPS that may belong to an unresolved configured jurisdiction; state validation remains in effect until all configured service areas are verified.
Strengthened public intersection mapping. StationCommand tries multiple named-intersection geocoder formats and, when needed, uses CAD GPS only as a server-side search anchor to find the crossing of both named OpenStreetMap roads. The returned public point is the named intersection, not raw CAD GPS.
Fixed hidden Leaflet map sizing in the public carousel by invalidating all public map viewports after every slide transition instead of relying on exact slide-title wording.
Current-month and year-to-date heat maps now load independently with Promise.allSettled, so a failure or timeout on one map can no longer prevent the other from rendering.
Bulk heat-map requests no longer synchronously geocode every uncached no-GPS/intersection location. This avoids long map requests that could make both heat-map screens appear blank.
If a heat map still has unmapped generalized locations while the background cache is warming, the public display retries after 15 seconds rather than waiting for the normal five-minute refresh.

Version B.2.4.1

Public incident-tracker and heat-map coverage fix

Fixed the public Incident Tracker so the map again displays all non-excluded calls received today, not only incidents that are still active.
The Active Incidents text list remains limited to currently active incidents, while earlier calls today remain visible as subdued map markers.
Added aggregate mapped today / awaiting usable location diagnostics to the public tracker so missing-location issues are visible instead of silently disappearing.
Fixed another public heat-map omission path: uncached intersections and incidents without usable CAD GPS now attempt their generalized 100-block/intersection geocode immediately on the first map request.
Calls with usable CAD GPS continue to use the server-side privacy-shifted temporary marker while the preferred generalized road point is cached, keeping large heat-map requests responsive.
StationCommand now proactively warms the generalized public coordinate cache whenever an incident is received or updated.
The public incident object remains strict-whitelisted to call type, generalized location, half-hour-rounded time, and privacy-safe map geometry. No incident/CAD IDs were added to support the today/active split.
False Alarm incidents remain intentionally excluded from monthly/yearly heat maps, and administratively excluded incidents remain excluded. They are not counted as heat-map mapping failures.

Version B.2.4.0

Adaptive call classification and public-map regression fix

Replaced the fixed call-classification function with configurable call categories while retaining the existing seven categories as the default configuration.
Added a local adaptive similarity model that compares new call title/narrative/priority/unit context against historical calls. Administrator-reviewed/reclassified calls receive full weight; legacy pre-B.2.4.0 classifications can bootstrap the model at reduced weight.
False Alarm calls are always excluded from the adaptive learning corpus. False Alarm can still be automatically recognized through its deterministic rule hints.
Each category now has independent Automatic Classification and Learn From Reviewed Calls controls. A category can remain available for manual classification while being completely excluded from automatic calculation.
Administrators can add categories, rename categories, change colors, edit rule hints/keywords, enable/disable categories, and adjust learning thresholds from Administration → Call Classification.
New automatic results record their source, confidence/similarity, and explanation. Incident Records shows the automatic suggestion and whether the call was manually reviewed.
The adaptive model does not recursively train on its own new automatic classifications. New model output becomes a strong training example only after administrator review/reclassification.
Added a classification test tool and a Recalculate Unreviewed Calls action. Manually reviewed calls are preserved during recalculation.
Configured category names/colors now flow into private displays, public statistics/maps, Incident Records, and report category data.
Fixed the B.2.3.23–B.2.3.25 public-map regression where an empty generalized-location cache could make all incident markers disappear. Active incidents resolve the generalized 100-block/intersection immediately; heat maps use a privacy-shifted temporary marker while the preferred generalized road cache warms.
The temporary public-map fallback never serializes raw CAD GPS. It independently displaces both north/south and east/west by roughly 525–1,000 feet and is replaced by the preferred generalized-block/intersection location when available.

Version B.2.3.25

CAD GPS township/state validation

Added independent CAD GPS sanity validation for private response and EOC incident mapping.
When a CAD prefix has an expected township/jurisdiction, CAD GPS outside that resolved boundary is treated as suspect and is no longer allowed to veto a valid address geocode inside the expected jurisdiction.
Suspicious/outside-jurisdiction CAD GPS is reverse-checked for its state. If it resolves to a different state than the CAD agency mapping expects, StationCommand classifies it as outside-state and rejects it as a map fallback.
A CAD GPS point outside the expected township is also rejected as a final fallback even when it remains in the correct state.
If CAD GPS is rejected but the exact address resolves inside the expected jurisdiction, the private map uses the address/intersection result instead.
If both address mapping fails and CAD GPS fails jurisdiction/state validation, StationCommand shows no misleading incident marker and reports CAD GPS rejected rather than plotting the bad coordinates.
Private response and EOC displays now show a clear warning when CAD GPS is outside the expected jurisdiction/state or is still being validated.
Private map cache version was advanced so previously cached incident locations are revalidated under the new GPS rules.

Version B.2.3.24

Private street locking and CAD agency jurisdictions

Restored configured fire-station street addresses to public station records and public map station popups. The strict incident-address privacy rules remain unchanged.
Private response and EOC incident maps now attempt to lock incident markers to the geocoded street or named intersection instead of always plotting raw CAD GPS.
Private map address results are rejected when they are far from CAD GPS, outside a configured CAD agency jurisdiction, or cannot be reliably associated with the requested street. CAD GPS remains the operational fallback.
Added persistent CAD Agency / Township Mapping under Active911 Administration. Administrators can map prefixes such as COF to an agency name, township/jurisdiction, and state.
CAD-prefix matching uses the longest enabled matching prefix and attaches the matched agency/jurisdiction to private incident/EOC state and Incident Records.
Added Verify / Refresh Township Boundaries, using Nominatim administrative boundaries to constrain private address geocoding to the configured jurisdiction.
Private incident map routing now routes to the street/intersection-locked point when available and clearly labels whether the point is intersection-locked, street-locked, GPS-road-snapped, pending, or using CAD GPS fallback.
EOC map markers and focused bounds use the same private locked coordinates.

Version B.2.3.23

Public map privacy hardening and persistent navigation

Fixed mobile public-display navigation by pinning Previous, slide selectors, Next, and Pause Rotation to the bottom of the viewport on every public screen.
Added explicit Previous/Next controls on desktop public displays as well; existing slide dots and Pause Rotation remain available.
Public incident street addresses now round to the nearest 100 block. Named intersections remain intersections and receive no random displacement.
Public map coordinates are now derived only from the generalized 100-block/intersection geocode. Exact CAD latitude/longitude is no longer passed into the public geocoding worker.
For non-intersections, StationCommand applies a privacy displacement and accepts a road snap only when it is close to the generalized block and identifies the same street.
If a reliable same-street road snap cannot be produced, the marker receives independent stable pseudo-random north/south and east/west offsets of roughly 525–1,000 feet from the generalized block geocode.
All public incident times on active and heat-map APIs are rounded server-side to the nearest 30 minutes; the browser independently re-applies half-hour rounding before display.
Public active-map incident records are strict-whitelisted to call type, generalized location, rounded time, and the privacy-safe geometry required to draw the marker. IDs, exact addresses, unit/apartment, CAD codes, narratives, responders, response states, notes, timelines, and exact coordinates remain private.
Public heat-map call records expose only call type and rounded time inside a generalized location point. Exact station street addresses were also removed from public map/dashboard responses.

Version B.2.3.22

Colored month comparison trends

Updated the private station-display Calls by Day of Month chart so every previous month has its own distinct color instead of all prior-month lines being gray.
Previous-month colors are intentionally rendered at reduced opacity/saturation so they remain visible as comparison context without competing with the bright current-month line.
The legend now shows an individual colored key for each previous month while keeping the current month clearly identified as the highlighted series.
The current month retains the bright cyan line, points, glow, and highlighted current-day marker.

Version B.2.3.21

Station Command Home live tracking and report bar labels

Station Command Home can now retrieve eligible apparatus/responder Active911 locations through the existing bearer-token Respond API.
Outbound HMAC Home webhooks remain coordinate-free and now advertise tracking availability/Respond API metadata only.
Respond API tracking respects the same privacy rules as StationCommand: responders require department enablement, member opt-in, a linked device, and RESP/ARRIV; apparatus requires apparatus tracking to be enabled.
Respond API tracking includes position timestamp, accuracy, freshness, age, configured icon, and configured color so Home can render the same resource markers.
Inactive/cleared incidents do not expose live tracking positions through the Home Respond API.
Report bar charts now reserve headroom and place the numeric value above every bar, including the tallest and zero-value bars.

Version B.2.3.20

Public carousel fix and admin page load reliability

Fixed the public-display desktop carousel indicators so they render as true circles again while retaining 44-pixel accessible button targets.
Fixed an initialization race affecting admin pages where Personnel or Incident Records could occasionally finish authentication before the page registered its data-load handler, leaving the page empty until refresh.
Admin and member shared page loaders now support late-registered ready handlers and use no-store authenticated GET requests.
Personnel and Incident Records now automatically retry one failed initial data request instead of requiring a manual browser refresh.
Added a Device Directory link to the Personnel page navigation and a prominent Open Device Directory / Import Devices button in the Unassigned / Apparatus Devices section.
Added Device Directory to Incident Records navigation and versioned Personnel/Incident page assets to avoid stale browser JavaScript after upgrades.

Version B.2.3.19

Public mobile Call Trends overhaul

Reworked the public Call Trends slide for phone-sized screens so charts and cards no longer force desktop-width content off the right side of the viewport.
The monthly call chart now renders to the actual mobile viewport instead of forcing a 720-pixel-wide SVG; month/value labels are compacted on phones.
Calls by Day of Week now fits all seven weekdays and all three comparison series within the mobile card using smaller bars, labels, and a wrapping legend.
Public analytics cards now use min-width:0, full-width single-column stacking, compact headings, and vertical slide scrolling on mobile to prevent clipping.
Average Calls per Day remains three-column on phones but uses compact responsive cards.
Public header, metrics, statistics panels, carousel controls, and footer were tightened for mobile while retaining touch-friendly controls.
Public analytics and maps re-render after meaningful orientation/viewport changes.
Desktop/kiosk public-display behavior is unchanged.

Version B.2.3.18

Member My Settings page

Added a dedicated authenticated My Settings page for every StationCommand member.
Members can update their display name, review their account role/rank, see whether department responder tracking is enabled, and understand exactly when location sharing is allowed.
Members can opt in or out of Active911 responder location sharing directly from My Settings without needing to open a station display.
Members can select their personal tracking icon and color, or independently inherit the Device/Admin default icon and/or color.
My Settings lists the member's linked Active911 devices and shows each device's administrator-configured default icon/color.
The page clearly explains that personnel locations are requested only while RESP/ARRIV, are restricted to authenticated incident/EOC maps, and are never exposed on the public display.
Added My Settings to the customizable member menu and to the private station-display navigation menu.

Version B.2.3.17

Custom tracking icons/colors and audible incident announcements

Added administrator-selectable map icons and colors for Active911 devices and standalone apparatus records.
Added responder-selectable icon and color overrides in Display Settings, with independent Use Device/Admin Default fallbacks.
Expanded vehicle icons to include Fire Engine, Ladder Truck, Ambulance/Rescue, Command Vehicle, Tanker/Tender, Utility Vehicle, Car, SUV, Pickup, and Van.
Fresh/aging tracking markers now preserve each configured color; stale locations continue to turn gray after 30 minutes.
Added optional Audible Incident Announcement (Text-to-Speech), disabled by default, for private station displays.
Added a configurable spoken-message template with insertable screen fields including department, incident type/title/address, cross streets, narrative, station, time received, CAD code, responders, address-history counts, and weather alerts.
Added private custom start-tone upload (MP3/WAV/OGG/WebM/M4A/AAC, up to 4 MB) that plays before browser speech synthesis.
New calls are announced once per running browser session; calls already active when a display starts are not replayed in bulk.
Public displays remain isolated from Active911 tracking coordinates and private audible-announcement configuration.

Version B.2.3.16

Active911 tracking on private EOC map

Extended the optional Active911 device-location overlay to the authenticated EOC map while EOC mode is active.
Apparatus follows the same department setting as the normal response map and remains eligible regardless of Active911 response status.
Opted-in responders appear in EOC only when their linked Active911 device is RESP or ARRIV on at least one active EOC incident.
EOC markers use the same freshness rules: bright red through 2 minutes, faded red from 2–30 minutes, and gray after 30 minutes.
Responder EOC labels include the qualifying incident context. Stale resources stay visible but do not drive focused EOC map bounds.
Fresh/aging tracked resources are considered when the EOC map initially fits or when the tracked device set changes. Routine GPS movement updates markers in place so the map does not continuously jump.
Tracking remains private: no tracked coordinates are added to the public display/API, analytics, incident history, or persistent database storage.

Version B.2.3.5

Read-only Google access, device import, and branding consistency

Reduced Google Calendar authorization to the least-privilege read-only scopes calendar.events.readonly and calendar.calendarlist.readonly. StationCommand no longer requests the broad Calendar read scope.
Google Group announcements continue using gmail.readonly, which is read-only and is required to read the delivered message body displayed by StationCommand. No Calendar or Gmail write scopes are requested.
Added Active911 Device CSV import to Device Directory. Device Code suffixes are discarded so values such as 2151534-YHQQ are stored as numeric device ID 2151534.
Device import maps the CSV Name as the device alias and can automatically link exact personnel/account name matches and configured apparatus names. Apparatus matching ignores spaces/punctuation so names such as Rescue71 can match Rescue 71.
Completed a branding pass across StationCommand pages: every HTML page now uses the configured department logo as its favicon, shared department branding is applied to administration top bars, and previously hard-coded login/legal branding now follows Department Branding settings.
OAuth failure/unauthorized pages now use the same department-branded StationCommand error experience.

Version B.2.3.4

Branded error pages

Replaced plain browser-style HTML error screens with StationCommand-branded pages using the configured department name and uploaded logo.
Added branded access-denied, page-not-found, invalid-request, request-too-large, unexpected-error, and unavailable sign-in configuration pages.
API endpoints continue returning structured JSON errors so integrations are not affected.
Error pages are responsive and provide clear Return and Retry actions.

Version B.2.3.3

Report branding and chart corrections

Monthly and yearly reports now use the currently configured StationCommand department name and configured/uploaded department logo, with cache-busting so a newly uploaded logo is not replaced by a stale browser image.
Incident-type report colors now use the same category color mapping as the StationCommand station and public displays.
Fixed report Time of Day calculations by including the America/Detroit incident hour in the shared date-part helper.
Improved report layout so Total Calls remains inside the Incident Type panel and the Time of Day legend is easier to read.

Version B.2.3.2

Report period selector fix

Fixed the Monthly & Yearly Reports page failing to initialize because its client script conflicted with shared Administration JavaScript globals.
The report year now defaults to the current America/Detroit year, including when switching to Yearly Report.
The Month selector is now populated with January through December in the HTML as a fallback and is automatically set to the current month when Monthly Report is selected.

Version B.2.3.1

PostgreSQL + MySQL database support

Added PostgreSQL as a first-class StationCommand persistence backend while retaining full MySQL and JSON support.
PostgreSQL uses JSONB payload storage, native TIMESTAMPTZ incident/announcement timestamps, indexed operational columns, and automatic schema creation/upgrades.
Added Railway-friendly POSTGRES_URL/DATABASE_URL configuration. StationCommand permits only one live database backend at a time to prevent split writes.
Added manual JSON → PostgreSQL and MySQL → PostgreSQL migration tools with record summaries and normalized full-store digest verification.
PostgreSQL startup never imports existing data automatically. Administrators must explicitly run the migration/import command before switching production.
Added PostgreSQL connectivity testing and post-migration verification commands; source MySQL/JSON data is never deleted by migration.

Version B.2.3.0

Reports, Address Notes, integrations, and public privacy

Added printable Monthly and Yearly Reports modeled on department statistics sheets, with incident-type distribution, historic volume, day-of-week, time-of-day, and monthly/day-of-month trends.
Added persistent Address Notes with Information, Caution, High Priority, and Critical / Responder Safety urgency levels. Matching notes automatically appear above the dispatch narrative on private incident displays.
Added Address Notes administration with search, edit, delete, optional expiration, normalized address matching, and audit logging.
Consolidated Active911, Station Command Home, Google Calendar/Groups, Google Photos, and manual synchronization controls under a single Integrations administration item. Weather remains separate.
Public heat-map incident times are now rounded to the nearest hour on the server before being returned to the browser. Earlier non-active calls on the Public Active Incidents map are also server-rounded; active calls retain their normal live received time.

Version B.2.2.19

Personnel access-level editing

Personnel linked to a StationCommand login now have an editable Access Level field directly on their Personnel Directory card.
Access can be changed between User, EOC Manager, and Admin when saving the person.
Accounts not linked to personnel also have an editable Access Level and Save Access control in the Personnel Directory.
Existing administrator self-protection remains enforced, so an administrator cannot accidentally remove their own administrator access.

Version B.2.2.18

Personnel Directory display fix

Fixed the Personnel Directory failing to render after last-login information was added in B.2.2.17.
The page now loads StationCommand's shared time-format helper before rendering linked-account login timestamps.
Added a defensive date formatter so a formatting-helper problem can no longer blank the entire personnel list.

Version B.2.2.17

Account login visibility and readable audit logs

Personnel linked to StationCommand accounts show the linked account and last successful login directly on the personnel record.
Personnel Directory includes authorized accounts that are not tied to a personnel record, including role, account status, and last successful login.
Security Events is now collapsible and retains its readable filters for event type, time range, search, and result limit.
Application Audit Trail is now collapsible, searchable, filterable by action and time range, and formatted into readable labeled fields instead of raw JSON.

Version B.2.2.16

Account activity and security-log usability

Personnel linked to a StationCommand login now show the linked account name/email, access role, enabled/disabled state, and last successful login time directly on their personnel card.
Added an Accounts Not Linked to Personnel section listing authorized accounts that do not currently belong to a personnel record, including role, status, and last login.
Security Events now use readable event names and structured account/request/source details instead of raw JSON.
Added Security Event filters for free-text search, event type, time range, and result limit, plus Refresh and Clear Filters controls.
Security events visually distinguish successful logins, denied/failed events, privileged actions, and general activity for faster review.

Version B.2.2.15

Apparatus editing fix

Fixed apparatus editing on Personnel Directory and User Access. The apparatus list now loads on the initial page load instead of only appearing immediately after creation.
Apparatus remain editable after refreshing or revisiting the page, including apparatus created without an Active911 Device ID.
Improved apparatus edit cards with clear Save Changes/Delete Apparatus controls and alphabetical ordering.

Version B.2.2.14

EOC Quick Reference cleanup

EOC Quick Reference now hides apparatus that have no personnel assigned.
Assigned apparatus remain listed alphabetically and continue to show their assigned crew.
If no apparatus have personnel assigned, the section shows a simple empty-state message.

Version B.2.2.13

Personnel numbers and resource sorting

Added an optional Personnel Number to each canonical personnel record and made it editable from Personnel Directory.
Added a global Personnel Display Order setting: personnel remain grouped by rank, then can be sorted alphabetically or by Personnel Number.
When apparatus and personnel are shown together, apparatus are always listed first alphabetically; personnel follow in rank order using the configured alphabetical/number secondary sort.
Applied the resource ordering to EOC crew data, responder/device ordering, Incident Management personnel choices, and Personnel Directory.
EOC Quick Reference apparatus cards are now always alphabetical, and crew members follow the configured personnel sort. Personnel numbers are shown there when available.

Version B.2.2.12

Standalone apparatus creation fix

Fixed Personnel Directory so a standalone apparatus can be created directly from the main Create Person or Apparatus form by selecting the Apparatus rank.
Creating an Apparatus rank entry no longer requires an Active911 device, Google account, or participation setting; the device can be linked later.
Hardened apparatus create/update/delete persistence so standalone apparatus records are written immediately to persistent storage.

Version B.2.2.11

Personnel and apparatus management

Added Delete Person controls to Personnel Directory. Deleting a person releases linked devices, removes current EOC assignments, and optionally removes their StationCommand login authorization when one exists.
Added apparatus creation and management directly to User Access and Personnel Directory, including apparatus that do not yet have an Active911 Device ID.
Changed apparatus classification from a separate checkbox to the Apparatus device rank. Existing checked apparatus devices are migrated automatically to the Apparatus rank.
Unassigned Active911 devices can now be given any responder rank directly from Personnel Directory without being attached to a StationCommand account.
Device Directory now uses the Rank field as the single source of truth for apparatus classification while retaining backwards compatibility with existing saved device profiles.

Version B.2.2.10

In-app dialogs

Replaced browser-native confirmation and warning popups with StationCommand-styled in-app dialogs.
Confirmation dialogs now support Confirm/Cancel actions, keyboard Escape/Enter behavior, focus trapping, mobile sizing, and background locking while open.
Updated Administration, Incident Management, EOC Management, roster/personnel, announcements, device/apparatus, station settings, and member quick actions to use the same consistent dialog experience.

Version B.2.2.9

EOC map switching fix

Fixed automatic EOC map switching between the focused calls/stations view and the regional weather view.
Routine StationCommand display refreshes no longer restart the EOC switching timer, which previously prevented the configured interval from completing.
Switch mode now begins on the focused operational view, alternates at the configured interval, and resets cleanly when leaving EOC mode or changing map modes.

Version B.2.2.8

Map behavior, EOC map views, and EOC Manager

Weather radar now centers on the average configured station location when stations exist and automatically fits a regional approach-weather view around that center.
Private and public heat maps now tightly fit all mapped calls plus configured stations, with no township-specific map center. With no calls, station locations determine the view.
Public active-incident maps use the same tighter operational bounds around stations and today’s incident locations.
Improved mobile line graphs by keeping labels/points readable inside a horizontally scrollable chart area instead of compressing the entire graph to phone width.
Stopped the EOC map from rebuilding markers and redrawing radar on every routine state refresh, reducing visible flashing.
Added EOC map modes: Zoomed In (calls and stations), Zoomed Out (regional approaching weather), or automatic switching between the two at a configurable interval.
Added the EOC Manager access role. EOC Managers can open EOC Management and use all EOC controls without receiving access to the rest of StationCommand Administration.

Version B.2.2.7

Mobile public display

Reworked the public statistics site for phones and small tablets without changing the desktop/kiosk layout.
Public slides now use normal vertical page flow on mobile, eliminating horizontal clipping and allowing the active slide to scroll naturally.
Made the department header, login button, statistics cards, charts, Time of Day view, heat maps, active incidents, weather alerts, and footer controls responsive to narrow screens.
Active-incidents information now remains visible below the map on mobile instead of being hidden.
Wide charts use contained horizontal scrolling where necessary so they no longer force the entire public page wider than the phone viewport.

Version B.2.2.6

Google Calendar and Groups reliability

Separated Google Calendar and Google Groups refresh handling so a failure in one integration no longer prevents the other from updating.
Persisted the last known-good Google Calendar events and Google Group announcements so a restart or temporary Google API/token error does not blank the displays.
Calendar now serves the last known-good event cache during a temporary Google API failure instead of returning an empty display when cached data exists.
Expanded Google Group discovery to match either direct group delivery or Gmail List-ID/list delivery.
Google workspace sync now runs every 15 minutes and reports Calendar and Google Groups errors separately for easier troubleshooting.

Version B.2.2.5

Menu stability fix

Fixed a navigation-layout feedback loop that could continuously reorder menu cards and make the Menu or Administration pages appear frozen or unresponsive.
Dynamic menu items, including EOC Quick Reference, now trigger a single layout refresh after the menu has finished loading instead of using a DOM mutation observer.
Preserves alphabetical defaults, favorites-first behavior, saved manual ordering, and Reset Layout behavior from B.2.2.4.

Version B.2.2.4

EOC assignment and display refinements

Changed the EOC display to a flex-based full-height layout so the map and Active Incidents board consume the full remaining station-screen height.
Combined apparatus and direct-person incident assignment into one repeatable dropdown with a separate Enroute/On Scene status for each assignment.
Apparatus and direct personnel can now be assigned to only one active EOC call at a time, and personnel riding an apparatus are removed from direct-person choices.
Made Apparatus Crews collapsible and prevents a person from being placed on more than one apparatus crew.
Menu and Administration cards default to alphabetical order, favorites always display first, manual reordering remains persistent, and Reset Layout restores alphabetical order and clears favorites.

Version B.2.2.3

EOC full-screen layout correction

Fixed the EOC station display so the map and Active Incidents board occupy the full remaining viewport beneath the station header instead of collapsing to their content height.
Pinned the EOC operational view to the station-display viewport and made the map fill its grid cell absolutely, removing the circular percentage-height calculation that caused the short map/list panels.
Added a second non-panning Leaflet size validation after layout settles so radar and base-map tiles fill the enlarged map without changing the incident/station viewport.

Version B.2.2.2

EOC reactivation handling

Reactivated incidents now return to the active EOC board whenever EOC Mode is active.
Reactivated EOC incidents return unassigned so apparatus and direct personnel can be assigned again, with automatic device-status handling reset to off.
The reactivation and return to the EOC board are recorded in the incident activity log.

Version B.2.2.1

EOC display and crew-management refinements

Made the EOC map and active-incident board adapt to the station display viewport and extend to the bottom of the available screen area.
Condensed the EOC display heading into a single line and automatically shortens a trailing “Fire Department” to “FD” to preserve space.
Moved Active EOC Calls above apparatus crew assignments in EOC Administration.
Replaced large personnel checkbox grids with compact personnel dropdown rows per apparatus. Use Add Person to add as many crew positions as needed, then Save Crew.

Version B.2.2.0

Emergency Operations Center Mode

Added EOC Mode for private station displays and administration. EOC Mode suppresses private display timers and routing, shows all EOC-held incidents on a single radar/map board, and displays the highest-severity active weather alert.
Added EOC call management with call reclassification, full narrative visibility, apparatus assignment, direct-personnel assignment, Enroute/On Scene state, per-incident Active911 device-status override, and manual clear.
Added EOC apparatus crew management. Assigning an apparatus to a call snapshots its current crew into incident participation credit automatically.
Added standalone apparatus records in the Device Directory so apparatus can exist before an Active911 device ID is assigned and can be linked later.
Added incident-level EOC activity history to Incident Management, including assignments, status changes, reclassification, crew credit, mode transitions, and clear actions with actor and timestamp.
Added an EOC Quick Reference menu item while EOC Mode is active, showing active calls followed by apparatus/crew assignments.
Public display behavior remains unchanged by EOC Mode; public active-incident timing continues to use normal display-window rules. Manual EOC clear removes the incident from public active incidents.
Tightened the dedicated weather radar default view while keeping it centered on the configured weather point.

Version B.2.1.30

StationCommand Home multi-instance reliability

Fixed StationCommand Home webhook/settings persistence on MySQL-backed installations.
Added support for multiple StationCommand Home instances with independent names, webhook URLs, HMAC signing secrets, Respond API bearer tokens, enable/disable state, delivery status, and test buttons.
Respond API authentication accepts the token assigned to any configured Home instance, so one Home installation can be revoked without affecting the others.
Existing single-instance StationCommand Home settings are migrated automatically into the new multi-instance configuration.

Version B.2.1.29

Stable response map & radar visibility

Response maps no longer tear down, refit, and reroute on every Active911 state refresh when the incident location is unchanged, eliminating the repeated map bounce.
Route bounds are applied once per incident/location change with map animations disabled for a steadier station display.
Response-map radar opacity is reduced so street names and road geometry remain easier to read beneath precipitation imagery.
The dedicated weather radar is also slightly more transparent while retaining its regional view.

Version B.2.1.27

Webhook reliability & Station Command Home settings

Fixed Active911 webhook status reporting so a saved secret correctly shows as configured instead of being overridden by stale persisted status fields.
Active911 “Other” integration URLs are now generated from the public request origin and prefer HTTPS for hosted installations.
Admin API/webhook tests no longer inflate the live webhook Processed counter; tests have their own counter.
Station Command Home webhook and Respond API settings are now available directly on the Active911 Integration settings page, including generated signing secrets, generated bearer tokens, endpoint display, and a test delivery button.

Version B.2.1.26

Heat map false-alarm filtering

FALSE ALARM incidents are excluded from private and public heat-map points and no longer affect automatic heat-map bounds/zoom.
False alarms remain available in incident history and normal department statistics.

Version B.2.1.26

Station Command Home Respond API support

Added the read-only StationCommand Respond API endpoint used by Station Command Home to retrieve full incident data by incident ID.
Respond API requests use a dedicated bearer token configured with STATIONCOMMAND_RESPOND_API_TOKEN.
The incident payload includes operational incident details and the display-safe responder list needed by Station Command Home.
Preserved the existing signed Station Command Home webhook integration for real-time incident created, updated, and cleared events.

Version B.2.1.24

Beta version naming & public weather test

Changed the StationCommand beta display version format to B.#.#.#, beginning with B.2.1.24.
Standardized current version labels across the station display, public display, API status, and changelog.
StationCommand test weather alerts now appear on public pages so the public alert banner can be fully tested.
Public test alerts are unmistakably labeled TEST — NOT A REAL NWS ALERT and do not link to a fabricated NWS alert product.

Version 2.1.20

Public display layout hotfix

Fixed the public-display grid so the conditional NWS alert banner no longer pushes the rotating slides/footer into the wrong rows.
Kept the alert banner in its own reserved row; when no alert exists that row collapses to zero height.
Moved entitlement/error notices to a fixed overlay so they cannot disrupt the public display layout.

Version 2.1.19

Public NWS alert banners

Public statistics pages now show a persistent banner near the top for every active National Weather Service watch, warning, advisory, or other alert affecting the configured weather point.
Each public alert banner shows the alert type, NWS headline/area, expiration time, and a direct link to the official NWS alert resource.
Public alert data excludes StationCommand local TEST alerts so internal display testing is never presented to the public as real weather information.
A lightweight NWS alert check now runs once per minute globally, allowing newly issued alerts to be discovered much sooner than the normal 15-minute full forecast refresh.

Version 2.1.17

Weather payload & warning takeover fix

Fixed NWS weather and test-alert payloads being serialized as empty objects even when NWS requests returned valid forecast data.
Hourly, seven-day, observation, and alert availability can now be evaluated from the actual NWS payload returned to StationCommand.
Interrupt-level weather alerts, including the local TEST Tornado Warning, now take over the station display even while an incident is active.
Clearing or expiring the test warning immediately returns the display to the active incident or normal rotation.

Version 2.1.16

Customizable Admin & Member menus

Administration is now a launcher page instead of one long crowded page.
Each major Administration section has its own URL/page.
Admin and member menu cards can be favorited to pin them first and dragged to reorder.
Menu layout preferences are stored server-side per user and follow the account across devices.

Version 2.1.16

Responder visibility & mobile public display

My Statistics now includes a complete year-to-date responder leaderboard from the department roster, including responders without Station Command accounts or linked Active911 devices. Responders marked No Stats remain excluded.
Read-only incident details now show every responder recorded on the call, not only whether the signed-in user was counted.
The public Time of Day screen is now scrollable on mobile, with horizontally scrollable donut panels/legend details instead of shrinking the content to an unreadable size.

Version 2.0.16

Agency identity in license validation

License validation now sends the configured Station Command agency/department name as agencyName.
License validation now sends the Station Command installation URL as url.
The URL is derived from the incoming request/proxy host and protocol; APP_BASE_URL can be used as a fallback for scheduled validation checks.
Administration diagnostics show the non-secret agency name and URL included in the validation request.

Version 2.0.15

License validation contract correction

Validation now sends the documented minimal request: licenseKey, product, and version.
Stopped sending the client-generated installation ID during normal hosted-license validation.
Removed unrelated station-count and public-usage fields from the validation request.
Structured license-server errors now display their actual code/message instead of [object Object].
Administration shows which non-secret fields were sent in the validation request.

Version 2.0.14

Entitlement enforcement audit

Audited every current licensable feature against the license server's entitlements object.
Added server-side gates for responder/incident displays, department statistics, advanced analytics, calendar events, display customization, and the public portal.
Member and Admin interfaces now hide matching unavailable sections instead of showing controls that the server will reject.
Administration now lists every entitlement returned by the license server with enabled/disabled state and any limit.
Plan names remain informational only; entitlement booleans and limits are authoritative.

Version 2.0.13

Direct entitlement pass-through

Removed Station Command plan/type translation from license enforcement.
The complete license-server JSON response is now stored unchanged and treated as the source of truth.
Features are enabled directly from entitlements.<feature>.enabled.
Station limits come directly from stations.licensed / stations.unlimited.
Public monthly traffic comes directly from entitlements.public_stats_monthly_views.limit.
Expiration/grace behavior comes directly from expiresAt, licenseState, and outageGraceUntil.

Version 2.0.12

End-to-end license state repair

Schema 3 responses now use a dedicated deterministic parser and never merge with stale cached legacy data.
MySQL now persists the complete Station Command license object, including the admin-entered key, cached entitlements, instance ID, and validation timestamps.
Added Administration diagnostics showing the license server's returned schema/plan/status/public-display value and whether a normalized entitlement is actually cached.
Added asset cache-busting to prevent stale Admin/Public JavaScript after rapid deployments.

Version 2.0.11

Schema 3 validation parser correction

Fixed the remaining null cached-license dereference that caused Cannot read properties of null (reading 'limits') after a successful HTTP 200 validation.
License validation now recognizes schema 3 data whether returned at the response top level or under payload.
Fresh validation responses no longer depend on an existing cached license.

Version 2.0.10

License persistence & schema null-safety

Fixed schema 3 validation when optional objects such as limits are null.
Admin-entered license keys now persist through the active database backend, including MySQL.
Cached license state and validation timestamps are persisted through the database backend after each validation.
Administration now indicates when the entered license key is saved persistently.

Version 2.0.9

Public Portal entitlement fix

Fixed schema 3 validation caching so Station Command retains the complete license response instead of caching only the nested entitlements object.
Public Portal now correctly recognizes features.public_display=true from the license server.
Enterprise plan, unlimited stations, public-traffic limits, organization, and validation state now remain intact after validation.

Version 2.0.8

License schema 3 support

Added native parsing for license-server schema 3 responses.
Enterprise and unlimited station licenses now display correctly from stations.licensed=-1 / stations.unlimited=true.
Maps snake_case license features such as public_display, advanced_analytics, department_stats, and responder_display into Station Command entitlements.
Uses nextValidationAt and outageGraceUntil from the licensing server.
Corrected Admin license diagnostics to display full attempted URLs and removed duplicate/undefined endpoint output.

Version 2.0.7

Absolute license URL diagnostics

License validation now uses absolute external URLs only; no relative validation path is passed to fetch().
The primary target is https://license.stationcommand.app/api/license/validate.
If that endpoint returns 404, Station Command tries the licensing service's advertised canonical endpoint https://license.stationcommand.app/api/v1/license/validate.
Administration now displays the complete absolute URL actually used for the most recent validation attempt.

Version 2.0.6

Direct license validation endpoint

Station Command now validates licenses directly against https://license.stationcommand.app/api/license/validate.
Removed fallback attempts against pluralized or alternate validation paths that could obscure the actual licensing request.
The licensing host remains hard-coded and cannot resolve back to the Station Command application itself.

Version 2.0.5

Hard-coded licensing service

Station Command now always sends production license validation requests to https://license.stationcommand.app.
Removed LICENSE_SERVER_URL and LICENSE_VALIDATE_PATH as deployment overrides so a Station Command installation cannot accidentally validate against itself.
The Administration license status now reports the fixed licensing service address.

Version 2.0.4

License endpoint compatibility

License validation no longer assumes only /api/v1/licenses/validate.
Added automatic fallback across known StationCommand license validation routes.
Added optional LICENSE_VALIDATE_PATH to explicitly configure the server route.
Added compatibility request fields for older license-server schemas.
Administration now shows the validation endpoint used and every attempted route when validation fails.

Version 2.0.3

License server connectivity fix

Corrected the default license server hostname to https://license.stationcommand.app.
Updated the application, environment example, and licensing documentation to use the correct hostname.
Corrected all current-version labels across the member menu, login page, public display, station display, and changelog.

Version 2.0.2

Licensed public portal fallback

When a license is not ACTIVE or GRACE, or does not include the Public Portal entitlement, the root page now shows a generic StationCommand member login instead of public statistics.
Public statistics, heat-map, analytics, and active-incident APIs now enforce the same Public Portal entitlement.
Authorized members and administrators can still sign in to repair or update licensing.

Version 2.0.1

License key management & public display repair

Added license-key entry, replacement, clearing, and immediate validation in Administration.
Saved license keys remain server-side and are returned to the browser only as a masked confirmation.
Changing a license key clears the old cached entitlement before validating the replacement.
Repaired public display department branding and logo loading through the reliable /department-logo endpoint.
Public display API failures now show a clear licensing/service message instead of silently rendering blank information.

Version 2.0.0

Microsoft sign-in & station licensing

Added Microsoft Entra ID sign-in alongside Google sign-in.
Added StationCommand license validation through the configurable license server at license.stationcommnd.app.
Licensing now limits physical station locations while allowing unlimited display devices at every licensed station.
Added license status and manual validation controls to Administration.
Updated 2.0 licensing so physical station locations are the licensed resource while displays at each station remain unlimited.
StationCommand now consumes generic feature entitlements and limits instead of hard-coding Basic/Intermediate/Pro behavior.
Added monthly public-portal traffic usage reporting and 80%/100% administrative warnings without automatically disabling the public portal.
License validation now preserves the last valid cached entitlement set during license-server outages.
Removed Home Station and per-user saved home routing from the web application; responder-origin routing is reserved for the responder app.
Removed individual annual/YTD call-total overrides. Participation totals are calculated from incident history.
Prepared feature entitlements for responder display, core statistics, individual portal, and public display licensing.
Added first-party public analytics with no retained public source IP, GPC/DNT reduction, page/slide usage, session duration, referrer and coarse network-supplied geography.
Added security logging for successful and failed Google/Microsoft logins, authorization denials, logout and protected write actions; security events can retain full source IP under the configured retention policy.
Added Analytics & Security administration and a public privacy notice at /privacy.
Disabled browser GPS/geolocation permission for StationCommand.

Version 1.7.0

Annual responder call-total overrides

Admins can now set an exact annual/YTD call total for an individual person from the Personnel Directory.
Overrides are stored by calendar year, so a 2026 correction does not affect 2027 or other years.
The overridden YTD value is used on Personnel Participation, Personal Stats, and the YTD responder leaderboard.
Month-to-date, Last Month, monthly charts, incident participation, and the underlying incident history remain calculated from actual incident records.
Leaving the annual override blank removes it and immediately returns that person to the automatically calculated YTD total.

Version 1.6.9

Google Photos OAuth/device recovery fix

Fixed Google Photos showing authorization failed after Google had already confirmed the device/account connection.
OAuth refresh tokens are now persisted immediately before Ambient device creation, so StationCommand never re-polls a consumed one-time device code.
Ambient device creation/recovery can now be retried independently without reconnecting the Google account.
Added recovery for devices created during an earlier partial setup and for ALREADY_EXISTS responses.
The Choose Albums button is now hidden until a real external Google settingsUri exists; it can no longer open the StationCommand Admin page through a placeholder # link.
Added a Finish Device Setup control when Google authorization succeeded but Ambient device creation still needs to complete.

Version 1.6.8

Google Photos Admin hotfix

Fixed ReferenceError: savePhotosConfig is not defined when using the Google Photos Collage controls.
Restored the shared Photos settings-save helper used by Save and Connect Google Photos.
Admin now reloads the saved non-secret Google Photos OAuth Client ID.
Leaving Client Secret blank preserves the existing secret instead of overwriting it.
Leaving Client ID blank during an unrelated update no longer erases the stored client ID.

Version 1.6.7

Display settings persistence & overview fit fix

Fixed Display Settings not saving after the Google Photos slide was added; the Photos checkbox was missing from the modal while the save code expected it.
Added the missing Google Photos collage rotation checkbox and hardened preference saving so a missing future control cannot abort the entire save.
User display settings now wait for MySQL persistence to complete before StationCommand reports success, and the browser reads the preferences back to verify the save.
Existing user preference records are normalized against current defaults so newly added display options do not reset older accounts.
Public display-screen administration now also waits for persistent storage confirmation.
Rebuilt the internal Statistics Overview layout so hero, metric cards, and Call Activity by Type share the actual viewport instead of fixed heights that overflow below the screen.
Call-category columns can scroll internally only when necessary, preventing the overall station display from being cut off.

Version 1.6.6

Google Photos setup-flow fix

Changed Google Photos Ambient authorization to Google's standard two-step flow instead of depending on the streamlined automatic redirect.
After Google account authorization, StationCommand creates and stores the Ambient device and exposes its exact Google-provided settingsUri as a Choose Albums button.
Added automatic polling of devices.get using Google's recommended pollingConfig.pollInterval until mediaSourcesSet becomes true.
Added a Change Albums action that reuses the existing device/settings URI rather than creating another Ambient device.
Added recovery logic that can reuse the newest matching Ambient device if a prior connection attempt created one.

Version 1.6.5

Clean announcements & Google Photos collage

Removed Google Groups subscription, unsubscribe, and discussion-link boilerplate from Gmail-sourced announcements.
Added internal-only Google Photos collage support using the Google Photos Ambient API.
Admins can connect Google Photos and select specific albums/photo collections for the StationCommand ambient device.
Added an adaptive Google Photos collage slide and per-user rotation toggle.
Google Photos metadata refreshes hourly and image bytes are proxied through authenticated StationCommand endpoints.

Version 1.6.4

Internal date & military time labels

Added the current Eastern date next to the internal station-display clock.
Kept the internal header clock in 24-hour military time.
Changed internal Calls by Time of Day labels themselves to military ranges such as 1500–1800 instead of 3–6 PM.
All eight internal time-of-day periods now use 0000–0300 through 2100–2400 consistently.

Version 1.6.3

Time-of-day kiosk fit fix

Fixed the internal Calls by Time of Day screen overflowing below the bottom of 1080p and shorter kiosk displays.
Changed the layout to reserve separate responsive space for donuts and the full legend.
Donut size now scales down automatically on shorter displays instead of pushing legend rows off-screen.
Tightened headings and legend spacing while preserving larger sizing on taller station displays.
Mobile/tablet layouts continue to flow vertically and scroll rather than clipping content.

Version 1.6.2

Military header clock & interactive analytics

Changed the internal station-display header clock to explicit 24-hour military time with no AM/PM indicator.
Expanded Calls by Time of Day to use substantially more of the available station/public display area while retaining responsive mobile scaling.
Expanded Calls by Day of Month to use nearly the full public slide area.
The current month is now emphasized by default on the day-of-month graph.
Hovering or focusing another month temporarily highlights that month's line while fading the others; clicking a month makes it the selected month until another is selected.
Time-of-day labels use military ranges consistently on internal and public displays.

Version 1.6.1

Adaptive displays & readability

Redesigned the rotating Department Announcements screen with responsive cards, wrapping text, larger typography, and safe scrolling so long announcements no longer run off-screen.
Redesigned the rotating Upcoming Department Events screen for clearer event names, 24-hour start/end times, and locations.
Improved the authenticated Upcoming Events and Announcements pages with larger responsive cards and mobile layouts.
Changed the internal Calls by Time of Day labels to explicit military ranges such as 0000–0300 and 2100–2400.
Expanded kiosk content to use the available display area while using responsive clamp-based sizing to remain readable on smaller screens.
Added responsive overflow handling across analytics, personnel, heat-map, incident, calendar, and announcement screens to reduce clipping on unusual aspect ratios and mobile devices.

Version 1.6.0

Public display controls, calendar improvements & hourly Google sync

Added raw call counts beside each time-of-day percentage on public and private donut displays.
Confirmed internal StationCommand time formatting uses 24-hour / military time.
Added administrator controls to enable or disable individual public display screens.
Added a public Calls by Day of Month graph with each month of the current year plotted on the same line chart.
Calendar events now show start date/time, end time, end date when different, and location when supplied.
Added Upcoming Events and Announcements links/pages to the authenticated menu.
Google/Gmail announcements now use only the original message and ignore replies/forwards.
Google Calendar and Gmail synchronization now runs once per hour.

Version 1.5.3

Department logo persistence hotfix

Restored the missing /department-logo handler that serves the configured uploaded department logo to pages and favicons.
Uploaded department logos are served directly from the MySQL-backed department configuration with the correct image content type.
Logo uploads now wait for the persistent database write to complete before Administration reports a successful save.
Added no-cache headers/cache busting so replacing a logo is reflected immediately instead of showing an older browser-cached image.
Configured local or external logo URLs remain supported, with the StationCommand logo as a safe fallback.

Version 1.5.2

Time-of-day donut charts

Replaced the time-of-day percentage rows with donut charts on both public and private displays.
Added separate YTD, Current Month, and Last Month donuts.
Each donut uses the eight 3-hour call periods as slices and retains exact percentages in a shared legend.

Version 1.5.1

Google Account integration wording & 3-hour analytics

Renamed Google Workspace Integration to Google Account Integration so the feature accurately reflects support for normal Gmail/Google accounts.
Google Workspace is not required for the Calendar or Gmail integrations.
Changed Calls by Time of Day from four 6-hour periods to eight 3-hour periods.
YTD, Current Month, and Last Month continue to display percentages rather than raw call totals.
Kept backward compatibility with the previous Google integration authorization URL.

Version 1.5.0

Time-of-day analytics & Google Workspace APIs

Standardized visible current-version references to 1.5.0.
Added public/private Calls by Time of Day displays using YTD, Current Month, and Last Month percentages.
Added Google Calendar API support with persistent OAuth authorization.
Added Google Group announcements through Gmail API messages delivered to a configured mailbox.
Added Google Workspace settings, manual refresh, status, and disconnect controls in Administration.
Retained iCal calendar URL support as a fallback.

Version 1.4.2

Dynamic changelog branding

Removed the remaining legacy department-specific branding from the changelog.
The changelog now uses the department name and logo configured in StationCommand Administration.
Updated changelog navigation and visual styling to match the rest of StationCommand.
Kept the StationCommand marketing-site link in the footer.

Version 1.4.1

Persistent Active911 administration

Moved Active911 routine API configuration into the administrator dashboard and persistent database state.
Added administrator editing for API enable/disable, refresh token, polling interval, webhook enable/disable, and webhook secret.
Environment variables remain supported as first-run/fallback configuration, so routine Active911 changes no longer require Railway environment edits.
Persisted webhook usage counters, last received/processed times, alert/agency IDs, errors, and the latest 100 webhook events in MySQL-backed storage.
Added the exact Active911 “Other” integration URL to the admin dashboard and a one-click webhook-secret generator.
Persisted short-lived Active911 access-token state and expiration information across deployments/restarts.

Version 1.4.1

Version visibility & changelog

Added this public changelog page at /changelog.
Made visible StationCommand version numbers link directly to the changelog.
Added the running version to the public statistics dashboard footer.
Standardized current-version references throughout the application to 1.4.1.

Version 1.1.13

Responder analytics

Added Year-to-Date, Current Month, and Last Month calls-per-day averages prominently to the public Call Trends screen.
Responder Participation now shows the complete roster rather than stopping at the first group of responders.
Added a slow continuous-loop scroll for long participation lists.
Added per-user responder-scroll delay settings: 5, 10, 15, 20, 30, 45, 60, and 90 seconds; 10 seconds is the default.

Version 1.1.12

Call averages

Changed day-of-week charts from raw totals to average calls per occurrence of each weekday.
Added average calls per day for Year to Date, Current Month, and Last Month.

Version 1.1.11

Active911 CSV compatibility

Updated CSV import for the current Active911 agency export format.
Added correct parsing for America/Detroit timestamps.
Added historical responder-response parsing for RESP, ARRIV, UNLV, WATCH, and related events.
Improved large CSV import performance and row-level error reporting.

Version 1.1.10

Hotfix

Fixed an internal active-incident display regression that prevented route maps and elapsed timers from rendering.

Version 1.1.9

Officer controls

Moved Clear Incident and +30 Minutes controls off station displays and onto the authenticated menu page.
Restricted controls to Captain, Deputy Chief, Chief, and administrators while incidents are active.

Version 1.1.8

Profiles & participation

Added user self-service display-name editing.
Added officer incident controls for active calls.
Added admin participation review per incident and manual responder-count overrides.

Version 1.1.7

Analytics

Added public and private Call Trends displays.
Added monthly call line graph and day-of-week call graph.
Added private responder participation totals for Year to Date, Current Month, and Last Month.
Combined multiple Active911 devices mapped to one user and counted a person once per incident.
Participation counts RESP and ARRIV only; AVAIL and UNLV do not count.

Version 1.1.6

Authentication UX

Added a clear authorization-denied message for Google accounts not approved for StationCommand.
Added a direct return link to the Public Statistics page.

Version 1.1.5

Active911 webhook

Added the production Active911 third-party webhook receiver.
Webhook events trigger an immediate authoritative Active911 API refresh while scheduled polling remains as backup.
Added webhook status and testing information to administration.

Version 1.1.4

Reserved / superseded

The webhook build was originally numbered 1.1.4 and was reissued as 1.1.5 to keep the project version history aligned.

Version 1.1.3

Public map loading

Fixed public maps being blocked by synchronous geocoding and road-snapping work.
Public maps now render immediately using safe generalized locations while preferred road-snapped points resolve and cache in the background.

Version 1.1.2

Public location privacy

Strengthened public residential-location privacy using generalized 100-block locations.
Preferred road-snapped public points instead of points over homes.
Kept intersection incidents identifiable as intersections without residential jitter.

Version 1.1.1

Server-side public privacy

Moved public-location sanitization entirely server-side.
Stopped exposing exact CAD/Active911 coordinates and exact addresses through public API responses.
Added generalized public identifiers and protected public heat-map coordinates.

Version 1.1.0

MySQL production architecture

Migrated persistent application data from store.json to MySQL.
Added automatic database schema initialization and migrations.
Added JSON-to-MySQL migration and database-test utilities.
Persisted Active911 access-token state in MySQL.
Prepared StationCommand for continuously hosted production operation.

Version 1.0.13

Heat-map details

Updated heat-map popups to match the public incident-map style.
Displayed category, privacy-safe location, and date/time rounded to the nearest hour for historical calls.

Version 1.0.12

Mobile & map popups

Fixed mobile hamburger-menu behavior.
Updated public map marker popups to show category, privacy-safe location, and rounded date/time instead of generic call counts.

Version 1.0.11

Personnel & token persistence

Persisted the current Active911 short-lived access key and expiration.
Linked Active911 devices to Google users and added personnel ranks.
Added apparatus-first responder sorting and rank abbreviations.
Added transparent markers for completed calls from the current day.
Improved responder-column overflow behavior.

Version 1.0.10

Public incident display

Renamed the public incident slide to Active Incidents.
Fixed numbered-road intersections such as 12 Mile Rd being mistaken for house numbers.

Version 1.0.9

Incident classification

Changed public active-call labels to standardized categories rather than raw Active911 descriptions.
Made vehicle-accident wording override medical wording so crashes classify as MVA.

Version 1.0.8

Public Active Incidents

Added the public Active Incidents map and list as another homepage slide.
Added active-incident and calls-today counters.
Normalized MED/MEDICAL calls to RESCUE/EMS.
Reworked Leaflet marker handling to address disappearing points.

Version 1.0.7

Public homepage

Made the root homepage a public statistics and heat-map rotation.
Moved Google login and the member menu to separate pages.
Added slide dots, direct slide selection, pause/resume controls, and smoother screen rotation.

Version 1.0.6

Display settings

Added configurable idle-screen rotation speed with a one-minute default.
Added auto-hidden station navigation that can be revealed from the corner or with Ctrl+Shift+M.

Version 1.0.5

Display Settings hotfix

Repaired the Display Settings button and preference modal behavior.

Version 1.0.4

Station UI

Standardized station navigation around a single Home link.
Unified rounded incident panels, map containers, update boxes, inputs, and buttons.
Corrected an initial build regression so Home Station and per-user Display Settings remained available.

Version 1.0.3

Home Station

Added /sthome with routing from each user's saved home address.
Added per-user idle-display selection settings.
Added the department patch to statistics branding.
Added green Active911 Live and red Active911 Offline status badges.

Version 1.0.2

Branding & history

Replaced the generic CTFD circle with the department patch.
Expanded Last Change Detected into a visible incident-change history.

Version 1.0.1

Polling & category colors

Stopped routine Active911 polls from resetting the incident display timer when nothing changed.
Separated Last Change Detected from Last Checked.
Applied standardized incident-category colors to live station displays.

Version 1.0.0

First official release

Reset project versioning for the first official StationCommand release.
Replaced PIN authentication with Google OAuth.
Added Admin and User access levels and the /user administration page.
Established the official production baseline for Active911 incidents, station displays, statistics, weather, calendar, announcements, heat maps, and administration.

Pre-1.0 Development

Prototype period

Established the original Active911 ingest, station routing, responder status, incident timers, multiple-call rotation, weather, calendar, announcements, address history, incident editing, device aliases, historical imports, statistics, and heat maps.
Developed the 1080p station-display layout and the operational rules that became StationCommand 1.0.0.