Improves OTA update reporting and process

[IDisposable]

Improves the OTA (Over-The-Air) update process by adding better reporting and handling of reboot requirements.

• More detailed logging, state management for reboots

[IDisposable]

@adamshiervani Not actually sure how to go about testing this...

[adamshiervani]

In the Makefile, you just set a low number and run ./dev_deploy.sh -i. If you check for updates with that, you should be able to get through the OTA process.

I'll try that out now.

[adamshiervani]

The OTA mechanism technically works. I was able to upgrade a device by lowering the version number in the Makefile. The code cleanup and the more granular state pushes to the client are great, but I have a few usability and robustness concerns.

The updated UI is confusing (I suspect flex-col is missing 😄). Despite the copy, it’s not immediately clear whether the reboot is automatic or requires the user to click “Reboot,” and it’s not obvious what happens if a reboot is already pending. All valid UX questions from the user’s perspective.

OTA Component

With the current implementation, if the reboot + IP assignment takes longer than the WebSocket reconnect policy allows, the “Reconnect” and “Reboot” buttons can lead the client to stale, lazy-loaded settings routes that break the app.

Stale settings pages

This PR aside, the only actual problem I noticed with OTA is the client-side state becomes desynchronized after a reboot: the client doesn’t perform a full refresh when the update completes. This is likely not caused by insufficient OTA-status events, but rather, the WebSocket reconnect threshold is being exceeded during the reboot/IP-assignment cycle (for example, DHCP can take a while). You can actually reproduce this by pulling the Ethernet cable during reboot -- the client hits the reconnect timeout and stops trying.

I would simply suggest extending the WebSocket reconnect threshold during updates to infinity. This way, the only thing that I can think of that could break the client-side part of the OTA mechanism is if DHCP assigned a different IP to the JetKVM, but that's fine for now.

[IDisposable]

@adamshiervani clean-up complete and added exponential backoff and 2000 retries (so effectively 5.5 hours)

[IDisposable]

This forces a page reload as soon as the navigation is registered

[IDisposable]

This forces a page reload as soon as the navigation is registered

[IDisposable]

DHCP assigned a different IP to the JetKVM, but that's fine for now.

In that case, we wouldn't be able to reconnect if they were using an IP, but if they were using a hostname or accessing through app.jetkvm.com it would eventually reconnect ;)

[IDisposable]

@adamshiervani This should be ready for retest/review

[Copilot]

Pull Request Overview

This PR improves the OTA (Over-The-Air) update process by adding better reporting and handling of reboot requirements, including enhanced logging, state management for reboots, and UI changes to indicate reboot status with reconnect functionality.

• Adds rebootNeeded and rebooting state management to track update progress through completion
• Implements UI changes to show reboot status and provide manual reconnect/reboot buttons
• Improves error handling and logging throughout the update process

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
ui/src/routes/devices.$id.tsx	Refactors authentication logic and improves WebSocket reconnection handling
ui/src/routes/devices.$id.settings.general.update.tsx	Adds reboot state UI with reconnect and manual reboot buttons
ui/src/routes/devices.$id.settings.general.reboot.tsx	Adds window reload on dialog close for proper state refresh
ui/src/routes/devices.$id.settings.access._index.tsx	Fixes grammar in comment
ui/src/main.tsx	Simplifies authentication check logic
ui/src/hooks/stores.ts	Adds rebootNeeded and rebooting state fields to OTA store
ui/src/components/Button.tsx	Adds reloadDocument prop support to LinkButton component
ota.go	Improves error messages, logging, and adds reboot state management
main.go	Enhances auto-update logic with better logging and timing

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[IDisposable]

Rebased and ready for review.

[tadic-luka]

@IDisposable I'm not familiar with react/tsx that much but your changes introduced compilation errors:

src/routes/devices.$id.settings.advanced.tsx:317:19 - error TS1308: 'await' expressions are only allowed within async functions and at the top levels of modules.

317                   await sleep(2000);
                      ~~~~~

  src/routes/devices.$id.settings.advanced.tsx:314:26
    314                 onClick={() => {
                                 ~~~~~~~
    Did you mean to mark this function as 'async'?

src/routes/devices.$id.settings.advanced.tsx:317:25 - error TS2304: Cannot find name 'sleep'.

317                   await sleep(2000);
                            ~~~~~

src/routes/devices.$id.settings.general.reboot.tsx:15:5 - error TS1308: 'await' expressions are only allowed within async functions and at the top levels of modules.

15     await sleep(1000);
       ~~~~~

  src/routes/devices.$id.settings.general.reboot.tsx:12:31
    12   const onClose = useCallback(() => {
                                     ~~~~~~~
    Did you mean to mark this function as 'async'?

src/routes/devices.$id.settings.general.reboot.tsx:15:11 - error TS2304: Cannot find name 'sleep'.

15     await sleep(1000);
             ~~~~~

src/routes/devices.$id.settings.general.update.tsx:27:5 - error TS1308: 'await' expressions are only allowed within async functions and at the top levels of modules.

27     await sleep(1000);
       ~~~~~

  src/routes/devices.$id.settings.general.update.tsx:24:31
    24   const onClose = useCallback(() => {
                                     ~~~~~~~
    Did you mean to mark this function as 'async'?


Found 5 errors in 3 files.

Errors  Files
     2  src/routes/devices.$id.settings.advanced.tsx:317
     2  src/routes/devices.$id.settings.general.reboot.tsx:15
     1  src/routes/devices.$id.settings.general.update.tsx:27
make: *** [Makefile:95: frontend] Error 2

I would say this is a regression and not an issue with the version of the npm or other build tool used to compile this code.

[IDisposable]

Yikes, sorry about that, the rebase broke that code (it was an old PR). Thanks for the reminder to recompile after doing rebases 😄