#705 - add LV Battery voltage tile to eFuses page#707
Draft
bracyw wants to merge 6 commits into
Draft
Conversation
… specs; drop orphaned card
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Redesigns the LV Battery presentation on the eFuses page as a reusable, read-only "Quick view" status bar pinned to the top-right of the page, out of the eFuse command zones. It is a right-edge sidebar pop-out that auto-opens, collapses to a small edge handle, and stays available (sticky) while the eFuse cards scroll beneath it.
On the bar sits an LV Battery chip: live voltage from VCU/LV/voltage with a status dot that turns red on the LV low-voltage fault (VCU/Faults/Non-Critical/LV_LOW_VOLTAGE_FAULT) and stays green otherwise. The warning is driven purely by the firmware fault flag, never a hardcoded voltage cutoff. This represents the physical low-voltage battery, distinct from the LV eFuse card (VCU/eFuses/LV/Voltage).
This is the foundation for #709 (customizable status bar for user-pinned topics): the bar projects chips and is built to hold more later.
Frontend-only: telemetry ingest is schemaless (Topic = DataType), so there is no scylla-server, Charybdis, or Siren change.
Notes
The status bar is a reusable component at src/components/status-bar (projects chips via ng-content), with the LV Battery chip at efuses-page/components/lv-battery-chip. Telemetry is read as signals through the existing storage seam under zoneless change detection, with no new services or backend contracts. The page host is set to display block so the sticky bar's containing block spans the full page.
Accessibility and theming: the fault is announced by an aria-label on the status dot rather than color alone, the collapse and re-open controls carry visible focus rings, focus moves to the successor control on toggle so keyboard users are not dropped to the page body, the slide-in animation respects prefers-reduced-motion, and all colors use the shared theme tokens. Both new components ship with co-located unit specs.
Test Cases
Screenshots
Quick View Tab (not popped out)

Quick View Popped out

Quick View Popped Out during scroll

Checklist
It can be helpful to check the
ChecksandFiles changedtabs.Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
package-lock.jsonchanges (unless dependencies have changed)Closes #705.