VersionWarning by SteveMicroNova · Pull Request #1086 · micro-nova/AmpliPi

SteveMicroNova · 2026-02-25T20:04:04Z

What does this change intend to accomplish?

If you have a cached version of amplipi, or keep the site open in another tab / in the app before and after an update, your code is liable to be mismatched with the backend and have odd behaviors. This warning surfaces that issue to the user so they know that they're in need of restarting their browser/app or clearing their cache.

Desktop:

Mobile:

Checklist

Have you tested your changes and ensured they work?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?
If applicable, have you updated the CHANGELOG?
Does your submission pass linting & tests? You can test on localhost using ./scripts/test
If this is a UI change, have you tested it across multiple browser platforms on both desktop and mobile?

SteveMicroNova · 2026-02-25T20:05:26Z

                            set({ skipUpdate: false });
                        } else {
                            set({ status: s, loaded: true, disconnected: false });
+                            if(s.info.version != "0.4.11"){


I would like a more robust version pin than "Remember to update this line before every update"

Finding a way for react to store the poetry version would be ideal, but any way that doesn't require intentional manual upkeep is mandatory for this imo

#1086 (comment)
Updated this line to:

if(s.info.version != import.meta.env.VITE_BACKEND_VERSION){

SteveMicroNova · 2026-02-25T20:06:30Z

This PR also has a lot of changes to the various StatusBar style components, that's due to me waffling about which version I should use and wanting them all to have feature parity as I found upgrades I could easily build for my immediate needs

SteveMicroNova · 2026-02-25T21:04:29Z

 echo "Building web app"
 pushd ../web            # Change to web directory
 npm install             # Install nodejs dependencies
+echo "VITE_BACKEND_VERSION=$(poetry version -s)" > .env # Collect the version number and bake it into the frontend


I've learned that Vite can bake environment variables into the compiled webapp if you use a dotenv and prefix the vars with VITE_ so I dynamically grab the poetry version and put it in a .env at build time

linknum23 · 2026-03-02T19:10:38Z

This PR also has a lot of changes to the various StatusBar style components, that's due to me waffling about which version I should use and wanting them all to have feature parity as I found upgrades I could easily build for my immediate needs

Should these be at least in a separate commit? Maybe even a separate PR?

linknum23 · 2026-03-02T19:11:23Z

Is there a reason the bar on desktop is left aligned?

SteveMicroNova · 2026-03-02T19:13:40Z

This PR also has a lot of changes to the various StatusBar style components, that's due to me waffling about which version I should use and wanting them all to have feature parity as I found upgrades I could easily build for my immediate needs

Should these be at least in a separate commit? Maybe even a separate PR?

At least one batch of changes is useful and belongs in this PR, and given that those components are all slightly different takes on the same base thing* I feel like retaining feature parity without splitting that into multiple PRs could have value

(*) They're all notification things, they just have different levels of working out of the box vs granular control schemes

linknum23 · 2026-03-02T19:15:30Z

A standard way to do this is to stack the "upgrade" first and then to add the "feature"

SteveMicroNova · 2026-03-03T16:58:44Z

New versions:

linknum23

Looks good. Just change this specific message to a warning as discussed. Thanks for pushing this through.

SteveMicroNova · 2026-06-24T19:34:57Z

Looks good. Just change this specific message to a warning as discussed. Thanks for pushing this through.

This is the last thing to do on this PR, though due to changes made in the child PR it might be easier / cleaner to change the severity level another time if that's acceptible

Or I can cherry pick and wade through a slightly odd rebase situation, but changing that color in a different PR seems simplest

codecov-commenter · 2026-06-24T19:37:07Z

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.34%. Comparing base (7499989) to head (76370ce).
⚠️ Report is 97 commits behind head on main.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1086      +/-   ##
==========================================
- Coverage   50.67%   50.34%   -0.33%     
==========================================
  Files          40       41       +1     
  Lines        7154     7397     +243     
==========================================
+ Hits         3625     3724      +99     
- Misses       3529     3673     +144

Flag	Coverage Δ
unittests	`50.34% <ø> (-0.33%)`	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

SteveMicroNova · 2026-06-24T19:41:08Z

Or I can cherry pick and wade through a slightly odd rebase situation, but changing that color in a different PR seems simplest

OR I can remember that that PR is pointed at this one, so I can merge that and then change it here while having a sensible lineage and call it good

SteveMicroNova · 2026-06-24T19:57:52Z

Now for the moment of truth, "Do we like the warning version?"

… that notifies the user when the fix is unsuccessful

When the preamp microcontroller hangs it stops ACKing and every I2C write fails with OSError 121 (EREMOTEIO). The existing fallback only reopens the SMBus handle, which recovers a transient bus glitch but not a hung preamp - zone control stays dead until someone power-cycles the unit. Escalate: when the reopened-bus retry also fails, reset the preamps in place, re-assign I2C addresses, reopen the bus and re-flush all cached register values so zone state (mute/source/volume) survives, then retry the write. Rate-limited to once per 20s so a benign one-off glitch never resets audio. Observed live on our unit 2026-06-04 (zone control dead until manual reboot); with this patch the same wedge self-heals in under a second. Signed-off-by: Stamate Viorel <stamate.viorel@gmail.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SteveMicroNova commented Feb 25, 2026

View reviewed changes

SteveMicroNova requested a review from linknum23 February 25, 2026 21:04

SteveMicroNova marked this pull request as ready for review February 25, 2026 21:14

SteveMicroNova force-pushed the VersionWarning branch 3 times, most recently from 862f88e to e129535 Compare February 26, 2026 17:41

SteveMicroNova mentioned this pull request May 13, 2026

Reset Preamp Micro on Communication Failure #539

Open

SteveMicroNova force-pushed the VersionWarning branch 2 times, most recently from b5bb80e to 7077819 Compare May 19, 2026 19:16

SteveMicroNova force-pushed the VersionWarning branch from 8015464 to aa4c2ba Compare May 29, 2026 21:09

linknum23 reviewed Jun 15, 2026

View reviewed changes

Comment thread NEW_RELEASE.md Outdated

linknum23 reviewed Jun 15, 2026

View reviewed changes

Comment thread CHANGELOG.md

SteveMicroNova force-pushed the VersionWarning branch from 16ea23c to e859500 Compare June 15, 2026 18:14

SteveMicroNova force-pushed the VersionWarning branch 2 times, most recently from 688d861 to 76370ce Compare June 24, 2026 19:29

linknum23 approved these changes Jun 24, 2026

View reviewed changes

SteveMicroNova and others added 3 commits June 24, 2026 16:01

Add global alert bar, dynamic webapp version warning

3cc00d6

Add user alert flow to the backend, attemtp to fix an I2C error state…

721567e

… that notifies the user when the fix is unsuccessful

Add alert surfacing workflow to @stamateviorel 's I2C self-healing fix

c1b9da9

SteveMicroNova force-pushed the VersionWarning branch from 6b6e57f to c1b9da9 Compare June 24, 2026 20:02

SteveMicroNova merged commit 802fa30 into main Jun 24, 2026
3 checks passed

SteveMicroNova deleted the VersionWarning branch June 24, 2026 20:11

Uh oh!

Uh oh!

Conversation

SteveMicroNova commented Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this change intend to accomplish?

Checklist

Uh oh!

SteveMicroNova Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

SteveMicroNova Feb 26, 2026

Choose a reason for hiding this comment

Uh oh!

SteveMicroNova commented Feb 25, 2026

Uh oh!

SteveMicroNova Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

linknum23 commented Mar 2, 2026

Uh oh!

linknum23 commented Mar 2, 2026

Uh oh!

SteveMicroNova commented Mar 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linknum23 commented Mar 2, 2026

Uh oh!

SteveMicroNova commented Mar 3, 2026

Uh oh!

Uh oh!

Uh oh!

linknum23 left a comment

Choose a reason for hiding this comment

Uh oh!

SteveMicroNova commented Jun 24, 2026

Uh oh!

codecov-commenter commented Jun 24, 2026

Codecov Report

Uh oh!

SteveMicroNova commented Jun 24, 2026

Uh oh!

SteveMicroNova commented Jun 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

SteveMicroNova commented Feb 25, 2026 •

edited

Loading

SteveMicroNova commented Mar 2, 2026 •

edited

Loading