Versions & Updates
이 콘텐츠는 아직 번역되지 않았습니다.
Every Xisom build carries a version. Knowing which version is running — and whether all parts of the system agree — is the first thing to check after an update or when something behaves unexpectedly.
The About panel
Section titled “The About panel”Open Settings → About. It shows the running version of the platform, along with
the build identity. The version follows the standard MAJOR.MINOR.PATCH format (for
example v1.5.0).
You can also confirm the backend version from the health endpoint:
curl -s https://your-device-ip/api/system/health# → { "version": "v1.5.0", "commit": "...", "buildTime": "..." }What version drift means
Section titled “What version drift means”The About panel shows both the frontend version (the dashboard in your browser) and the backend version (the running service). When they differ, the panel highlights the mismatch.
Operationally:
- Stale browser tab — the most common, harmless cause. Hard-refresh the dashboard (or close and reopen it) to load the current version.
- Partial update — one service was redeployed and another wasn’t. Re-run the update so all parts land on the same version. See Offline Bundle Install → Update.
When in doubt, match the frontend and backend versions before troubleshooting other behavior — a mismatch can explain symptoms that look like bugs.
After an update
Section titled “After an update”- Re-open Settings → About.
- Confirm the frontend and backend versions match and read the version you expect.
- If they don’t match, hard-refresh; if it persists, re-run the update.
If something goes wrong
Section titled “If something goes wrong”- Persistent version mismatch after a refresh and re-update — see the Troubleshooting runbook.