You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Custom remote-ui builds on UCR3: does the firmware accept unsigned images? #824
We are a German smart-home integrator evaluating the Remote 3 as the control surface for our own system (CeNVIS). We already run our own integration driver against the Integration API, which works well.
The remote-ui README states: "This application is part of the official Remote Two firmware. Custom versions can be built and installed on the device."
Our question concerns the Remote 3 specifically:
Can a self-compiled remote-ui be installed on a UCR3, or does the firmware only accept signed images?
If it is possible — is there a documented procedure, and does it void the warranty?
Is the main branch of remote-ui the same code base as the UCR3 firmware? Our device reports ui 0.70.1, the repository shows commits up to v0.74.5.
Device: UCR3, serial 3613S, os 2.8.4, core 0.69.4-bt, ui 0.70.1.
Background: we need our own visual identity — typography, background, page layout — rather than the tile grid. If a custom UI is not possible on the UCR3, that is a legitimate answer and we would plan accordingly.
I'm currently traveling and try to reply a detailed answer until the end of the week.
In short: a self-compiled UI app (custom remote-ui or any other static binary compatible with eglfs) can be installed and uninstalled with a REST call. Signing is not required. Only firmware images are signed.
From https://{remote-ip}/doc/core-rest/#/system/installCustomComponent:
☢️ VOIDS WARRANTY ☢️
The void_warranty query parameter is required to install a custom component:
The user has to agree and confirm, that the warranty will be voided by installing a custom component.
The confirmation will be recorded in a write-once location on the device and cannot be reverted!
The value of the parameter must be yes, otherwise the installation is aborted and 401 returned.
Custom archive requirements:
TAR GZip archive (either .tgz or .tar.gz file suffix).
In the root of the archive, there must be a release.json file describing the custom version.
See CustomRelease schema for the release.json format.
No symlinks. They are automatically removed during the installation.
UI:
The UI binary must be named remote-ui in the ./bin subdirectory.
All application files must be in one of the following subdirectories, other locations are not accessible at runtime:
./bin: application binary, usually only remote-ui.
./config: configuration data. Path is accessible with UC_CONFIG_HOME environment variable.
./data: application data. Path is accessible with UC_DATA_HOME environment variable.
web-configurator:
An index.html file must be in the root of the archive.
We can't support a Remote running a modified UI app, and faults caused by a modified build aren't covered by warranty (e.g. abusing the haptic motor by running it 24x7). Your statutory rights on the hardware are unaffected. Please note that we currently only sell to private individuals. For business enquiries please contact us: support@unfoldedcircle.com
Is the main branch of remote-ui the same code base as the UCR3 firmware? Our device reports ui 0.70.1, the repository shows commits up to v0.74.5.
We are reworking our automatic source publishing, unfortunately it hasn’t been working for the last few firmware releases.
We’ll update the repository with the latest 0.82.1 version included in the just released beta firmware 2.11.0 within the next days. This will also include updated Qt installation instructions to build and run the development desktop version on Debian 13.
A lot of development has happened since UI version 0.70.1. If you enable beta releases on your device, you’ll get the newer remote-ui versions. There have been many enhancements lately on the beta OTA channel. We can’t give an estimate yet for the next public firmware release.
Public and beta firmware release notes are on our website and Discord channel:
We are now moving the remote-ui development from our internal repository to the public repository!
From now on it will always be up-to-date and even contain the code of the next release.
In the last few days there were a few big updates:
updated documentation, including OpenSpec for agentic development
updated Qt runtime to 5.15.19
new Docker build images, including cross compilation to Windows
Activity
zehnm commentedon Sep 17, 2026
I'm currently traveling and try to reply a detailed answer until the end of the week.
In short: a self-compiled UI app (custom remote-ui or any other static binary compatible with eglfs) can be installed and uninstalled with a REST call. Signing is not required. Only firmware images are signed.
kennymc-c commentedon Sep 17, 2026
From https://{remote-ip}/doc/core-rest/#/system/installCustomComponent:
olivercensys commentedon Sep 19, 2026
zehnm commentedon Sep 20, 2026
Yes: a self-compiled UI app (custom remote-ui or any other static binary compatible with eglfs) can be installed on Remote 3 (and Remote Two).
At the moment this is only documented in the Core-API specification:
https://github.com/unfoldedcircle/core-api/blob/84e7a5b8d3be41340041c34199cf7b66f47625c1/core-api/rest/UCR-core-openapi.yaml#L10511-L10729
We can't support a Remote running a modified UI app, and faults caused by a modified build aren't covered by warranty (e.g. abusing the haptic motor by running it 24x7). Your statutory rights on the hardware are unaffected. Please note that we currently only sell to private individuals. For business enquiries please contact us: support@unfoldedcircle.com
We are reworking our automatic source publishing, unfortunately it hasn’t been working for the last few firmware releases.
We’ll update the repository with the latest 0.82.1 version included in the just released beta firmware 2.11.0 within the next days. This will also include updated Qt installation instructions to build and run the development desktop version on Debian 13.
A lot of development has happened since UI version 0.70.1. If you enable beta releases on your device, you’ll get the newer remote-ui versions. There have been many enhancements lately on the beta OTA channel. We can’t give an estimate yet for the next public firmware release.
Public and beta firmware release notes are on our website and Discord channel:
If you have any development questions you can ping me directly on our Discord channel (same username "zehnm").
zehnm commentedon Oct 7, 2026
We are now moving the remote-ui development from our internal repository to the public repository!
From now on it will always be up-to-date and even contain the code of the next release.
In the last few days there were a few big updates: