Skip to content

Feat: Allow max timeout values to become zero, since zero means default.#10570

Open
h3lix1 wants to merge 1 commit into
meshtastic:developfrom
h3lix1:power-timeout-zero-sentinel
Open

Feat: Allow max timeout values to become zero, since zero means default.#10570
h3lix1 wants to merge 1 commit into
meshtastic:developfrom
h3lix1:power-timeout-zero-sentinel

Conversation

@h3lix1
Copy link
Copy Markdown
Contributor

@h3lix1 h3lix1 commented May 28, 2026

Add a zero-sentinel timeout helper for config fields where 0 means default. Use it for PowerFSM screen_on_secs, min_wake_secs, and wait_bluetooth_secs so UINT32_MAX/MAX_INTERVAL can request immediate transitions to low power state.

Apparently the codebase treats both UINT32_MAX and MAX_INTERVAL as different values that mean maximum due to Apple cleints.

This is part of the ESP32 Power Saving series of diffs.

🤝 Attestations

  • I have tested that my proposed changes behave as described.
  • I have tested that my proposed changes do not cause any obvious regressions on the following devices:
    • Heltec (Lora32) V3
    • LilyGo T-Deck
    • LilyGo T-Beam
    • RAK WisBlock 4631
    • Seeed Studio T-1000E tracker card
    • Other (please specify below)
      Seed Xiao Wio esp32-s3

Add a zero-sentinel timeout helper for config fields where 0 means default. Use it for PowerFSM screen_on_secs, min_wake_secs, and wait_bluetooth_secs so UINT32_MAX/MAX_INTERVAL can request immediate transitions.

This change intentionally does not alter WiFi or Bluetooth runtime gating.
@github-actions github-actions Bot added needs-review Needs human review enhancement New feature or request labels May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request needs-review Needs human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant