Skip to content

v2.1.3 - Timestamp Tracking Default Configuration (2026-01-01)

What Changed?

This release makes ENABLE_TIMESTAMP=1 the default configuration in source code and updates all related documentation to reflect the new default status. Relative timing information (uptime since boot and inter-event duration) is now included by default in all detection events, enabling users to analyze event rates and detector responsiveness monitoring out of the box.

What's New

Configuration Update: Timestamp Tracking Now Default

What it does:

Establishes ENABLE_TIMESTAMP=1 as the standard default in include/config.h and updates all related documentation. This formalizes the shift toward relative timing as a core feature for v2+ firmware, enabling event rate analysis and multi-detector synchronization by default.

Documentation Updates:

  • Updated docs/develop/enable-timestamp.md with current defaults and complementary features
  • Clarified relationship between ENABLE_TIMESTAMP (relative timing) and ENABLE_RTC (absolute timing)
  • Updated CLAUDE.md optional fields section to reflect new defaults across all v2+ profiles
  • Verified consistency across all codebase documentation

Fields Provided:

  • uptime_ms - Milliseconds elapsed since device boot
  • timedelta_us - Microseconds since the previous detection event

Installation

Quick Start

# Get the release
git checkout v2.1.3

# Build and upload
task upload

# Verify timestamp tracking is working
task monitor

Timestamp tracking is automatically enabled. All detection events will include uptime_ms (time since boot) and timedelta_us (time since last detection) fields.

What's Different from the Last Version?

✅ Added

  • Comprehensive timestamp tracking documentation in docs/develop/enable-timestamp.md
  • Clarified complementary features section explaining relationship between ENABLE_TIMESTAMP and ENABLE_RTC

🔧 Changed

  • include/config.h: ENABLE_TIMESTAMP default changed to 1 (was 0)
  • platformio.ini: Removed -DENABLE_TIMESTAMP=0 override from v1 profile (now inherits base default)
  • docs/develop/enable-timestamp.md: Completely updated with current defaults, fields, and use cases
  • CLAUDE.md: Updated optional fields section to reflect new defaults for v2+ profiles

ℹī¸ No Breaking Changes

  • Timestamp functionality is identical to v2.1.2
  • All existing code, APIs, and command interfaces remain unchanged
  • Configuration change (ENABLE_TIMESTAMP default) does not affect v0 profile (explicitly overridden)
  • This is purely a configuration and documentation update

Is It Safe to Upgrade?

Backward Compatible: Yes

  • No functional changes - timestamp tracking behavior is identical to v2.1.2
  • Configuration change (ENABLE_TIMESTAMP default) does not affect v0 profile (explicitly overridden)
  • All v1 and v2 profiles automatically use timestamp tracking (same as before)
  • Existing command interfaces and responses remain unchanged
  • Safe for all existing deployments

Tests Passed

  • ✅ Builds without errors (v0, v1, v2 profiles)
  • ✅ Pre-commit checks pass (trailing whitespace, YAML/JSON, merge conflicts)
  • ✅ Timestamp functionality unchanged from v2.1.2
  • ✅ Documentation consistency verified across all files
  • ✅ Configuration inheritance verified (base defaults, profile overrides)

Release Details

  • Date: 2026-01-01
  • Version: v2.1.3
  • Files Changed: 4
  • include/config.h - ENABLE_TIMESTAMP default changed to 1
  • platformio.ini - Removed -DENABLE_TIMESTAMP=0 override from v1 profile
  • docs/develop/enable-timestamp.md - Complete documentation update
  • CLAUDE.md - Updated optional fields section
  • Commit Hash: b1c64b4 (bump: version 2.1.2 → 2.1.3)
  • Type: PATCH (Configuration/documentation update)

Next Steps

  • Continue maintaining timestamp tracking as a core feature for v2+ firmware
  • Monitor for any edge cases in event rate analysis and detector responsiveness tracking
  • Consider future enhancements to timestamp precision coordination with ENABLE_RTC for complete temporal context