Skip to content

Fix Waveshare Box V2 volume mapping - #39

Merged
eirabie merged 2 commits into
mainfrom
fix/waveshare-volume-control
Oct 10, 2026
Merged

eirabie merged 2 commits into
mainfrom
fix/waveshare-volume-control

Conversation

@eirabie

@eirabie eirabie commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Waveshare Box V2 inherited a 60% output ceiling that drove the ES8311 far below its normal output level, leaving playback quiet even at high slider settings. Keep the codec at fixed 0 dB and use ESPHome software attenuation over the full volume range; failed gain or unmute writes keep the amplifier off.

Hardware impact

  • No new required hardware
  • Adds optional hardware
  • Changes the required reference BOM

The change applies to Waveshare Box V2. The reference Voice Pyramid volume mapping remains unchanged. Existing saved percentages produce louder output, so attended testing should start at low volume.

Standalone impact

Volume control remains device-local and works offline. Settings/API formats, prayer history, shared recordings and partition layout are unchanged.

Testing

Automated: 18 UBSan CTests and 107 Python tests passed. Generated configuration checks cover all Waveshare profiles and the reference volume route. All three Waveshare builds passed pinned dependency, partition and capacity inspection; OTA growth is +96 bytes for audio and +80 bytes for display/diagnostics. See the dated build report.

Hardware: attended installation, loudness/distortion, sustained playback, concurrent network/display runtime memory and cold-restart validation remain pending. Automated builds do not establish physical acceptance.

Licensing/media

  • No new third-party media or dependency licensing concerns
  • Licensing/attribution details are documented in this PR

@eirabie
eirabie marked this pull request as ready for review October 10, 2026 14:37
@eirabie
eirabie merged commit 96670c1 into main Oct 10, 2026
11 checks passed
@eirabie
eirabie deleted the fix/waveshare-volume-control branch October 10, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant