Choose an available full release
Open My One-Home and go to Downloads. It lists official Stable releases for which your account has download rights. Read the version, publication date and release notes and compare them with your installation’s Core version. A new number in a demo or on the website does not mean the package is already available.
For the backend and home management, you need the full Core package. For v0.37 this is One-Home-Core-v0.37.0-Lichtgroepen.zip. One-Home-v0.37.0-Lichtgroepen.zip contains the interface for a theme tester or development website and does not install a backend by itself.
Prepare the existing installation
The command below applies to an existing standard installation using /home/onehome/.env and /home/onehome/data. For another setup, follow your administrator’s installation arrangements. Always read the installation instructions included with the release you will actually use.
Choose a suitable time: the home interface may briefly become unavailable during the switch. Keep the current installation identity, database, configuration and encryption keys together. Creating a new key does not resolve a problem with existing encrypted connections.
- Record the current Core version and normal access address.
- Check that a usable backup and its recovery information are available.
- Check free storage. The v0.37.0 updater requires at least 2 GiB of free space.
- Extract the full Core ZIP into a new release directory on Core, retaining the existing central configuration and data directory.
Run the documented update process
From the extracted release directory, run: bash scripts/update-onehome.sh. This command is intended for the administrator with access to the standard Core installation. Do not run it in a directory containing only a website or interface package.
The script creates a recovery copy, preserves the existing database and relevant configuration, and builds the new Core. The existing container stays active during the build; the switch and checks follow. Do not interrupt the running update. Keep the final output and reported backup path.
Check more than the version number
After completion, open your normal Core address with /app/ and sign in with your existing account. A practical update check includes your own home data and real device operation. A running process or visible start screen is insufficient.
- Check the reported Core version and open existing rooms.
- Check One-Links, recognisable device names and room assignments.
- Test a real device and wait for its confirmed state. For light groups, also test a group with several lights.
- Check a second screen and an account with view-only permissions. Home data should match, while screen preferences can remain separate.
- Later, check My One-Home for updated last contact and a confirmed version transition.
Assess an unsuccessful update
Record the exact error and the point at which the update stopped. The standard updater includes an automatic rollback route for an unsuccessful switch. This can restore the previous container, database and central configuration from the recovery copy. Check what is actually running again before starting a second attempt.
A failed build, insufficient storage and a failure after switching require different follow-up steps. Keep the output for that reason. Do not delete an existing database, keys or connections to hide a startup error. Have manual recovery performed with components known to belong to the same installation.
Document recovery and follow-up
Keep the recovery copy until the home works normally again. A browser layout backup does not replace it: that backup has no Core database or resident permissions. A Cloud backup may additionally require the separately stored recovery key.
For help, use My One-Home > Support and include the previous and intended versions, error message, time and checks already performed. Do not share an .env file or secret key. After recovery, record the version actually running and recheck local operation and access permissions.