Updating a Unit

Automatic update

Will be triggered automatically depending on the Unit update settings and the mass update flags for the Repo.

Manual with version change

It is enough to open the Unit settings and change the commit and/or branch. After clicking the Update button, an MQTT command will automatically be sent to update the Unit.

Manual without version change

To update a Unit without changing the version, use the Send update MQTT message tab in the main menu. The commands listed there are responsible for forcing an update of information on the Unit side:

1. Firmware — sends an MQTT command for a full program update, as if you had done it manually when creating a Unit. When using the Pepeunit libraries, a forced update can be skipped if the commit hash is the same; this behavior can be configured via client parameters.
2. Schema — sends an MQTT command to update the Output->Input interaction schema. This is useful when a new link has been added and a full program update is not required.
3. Env — sends an MQTT command to update the env.json file. This command is especially useful when all required variables are moved into env_example.json by the Unit Developer, and a full Unit program update is not needed.
4. Log — sends an MQTT command requesting local logs from the Unit. This command deletes all logs stored in Pepeunit and expects the Unit to send logs via MQTT. It is especially useful when the Unit has critical errors or was temporarily disconnected from the network.