Update tab
The Remote Update tab lets you update the gateway software in the field without requiring physical access. The update command is delivered to the gateway over MQTT; the gateway then uses the Companion Updater service to pull the new Docker image and restart itself.
A brief connectivity drop may occur during the process — this is expected. Once the update completes, the gateway reconnects and the operation is added to the Update History table with a processed status.
Update Screen
The screenshots below show the update form and the Command selector dropdown. Hover to reveal the zoom icon, or click to view full screen.
Figure 1 — Update form: Command selector, Target Image Tag field, and Update History table.
Figure 2 — Command dropdown: Self Update, Compose Pull & Up, and Pull & Up options.
Update Commands
The platform provides three update commands. Choose the one that best matches your installation architecture:
Recommended — Default
Self Update
The gateway updates itself. It references the current image version registered on the platform and pulls the Docker image via the Companion Updater, then restarts the service. The safest and most practical method.
Advanced
Compose Pull & Up
Pulls the image via Docker Compose and restarts all services. For gateway setups running multiple containers, this updates the entire service group in a single command.
Manual
Pull & Up
Only pulls the image and starts the gateway service. Suitable for single-container setups without Compose. Use the Target Image Tag field to pin to a specific version.
Form Fields
The update form consists of two input fields and one action button:
Update Process
When a remote update is triggered, the platform follows these steps:
Command Selection
The user selects the command and an optional target image tag.
MQTT Delivery
The platform sends the update command to the gateway's MQTT queue.
Image Pull
The gateway pulls the new image from the Docker registry via Companion Updater.
Service Restart
The gateway service restarts, reconnects to the platform, and status is updated.
Update History
Every update operation is automatically logged in the Update History table at the bottom of the screen. Each row shows the date, command used, operation status, and a detailed message:
Using Target Image Tag
To test a specific version or roll back, enter a version tag such as v1.0 or v1.5 in the Target Image Tag field. If left empty, the gateway will use its own registered image tag (the Registered Image value shown on the platform).
Post-Update Verification
After the update completes, confirm that the top record in the Update History table shows a processed status. Then switch to the Logs tab to verify the service restart messages. If the status remains pending, check the gateway's MQTT connectivity.