Allow users to change the system ID in the Vehicle Setup component by nukelet · Pull Request #4365 · bluerobotics/BlueOS

nukelet · 2026-09-02T18:59:19Z

We would like to provide a unified way for users to configure the system ID for a vehicle. As it currently stands, there are two sources of truth for the vehicle ID that need to be kept in sync:

The MAV_SYSID parameter in the Ardupilot firmware
The MAV_SYSTEM_ID environment variable, which is used to determine the vehicle ID in mavlink-server/mavlink2rest

This PR aims to provide an interface in the UI for users to change the vehicle ID:

Introduce a new autopilot_manager endpoint, /system_id, to set the value for MAV_SYSTEM_ID through a POST request, making the change persistent across reboots by storing the variable in the environment field of bootstrap/startup.json
Add a simple component to the Vehicle Setup tab that allows users to modify the Vehicle ID to their desired value

Note that (currently) it is necessary to restart the BlueOS container in order to have the MAV_SYSTEM_ID environment variable propagated to all services (there is a button in the Vehicle ID setup UI for restarting the container).

Depends on #4364
Fixes #3604

Copilot

🟡 Changes recommended

Error handling, input validation, and coordination between the two system-ID updates must be corrected.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds unified vehicle system-ID configuration across ArduPilot and BlueOS services.

Changes:

Adds persistent MAV_SYSTEM_ID configuration.
Adds Vehicle Setup editing and restart controls.
Displays the active system ID.

File summaries

File	Description
`core/services/ardupilot_manager/settings.py`	Defines the startup configuration path.
`core/services/ardupilot_manager/api/v1/routers/index.py`	Adds the system-ID persistence endpoint.
`core/frontend/src/components/vehiclesetup/overview/VehicleInfo.vue`	Displays the active system ID.
`core/frontend/src/components/vehiclesetup/overview/SystemId.vue`	Adds system-ID editing and restart controls.
`core/frontend/src/components/vehiclesetup/Configure.vue`	Registers the Vehicle ID setup page.

Review details

Files reviewed: 5/5 changed files
Comments generated: 4
Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

+    except Exception as error:
+        logger.warning(f"Unable to write MAV_SYSTEM_ID to bootstrap/startup.json: {error}")


joaoantoniocardoso · 2026-09-03T01:23:43Z

Cool!

I didn't test it yet, but I have one point: if we move the parameter set part to the backend, we allow non-UI clients to complete the full change-mavlink-id journey. If so, I'd adjust the endpoint name to be more generic.

Thanks

nukelet · 2026-09-03T02:38:11Z

Yeah, that's a good idea, I'll move the PARAM_SET bits to the backend and rename the endpoint to something like /system_id. I'll also address some of the comments from the bot review. Thanks for the suggestion!

Copilot

🟡 Changes recommended

The update can leave IDs inconsistent, and the verification loop unnecessarily delays every save.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Files reviewed: 7/7 changed files
Comments generated: 4
Review effort level: Balanced

nukelet · 2026-09-04T10:14:25Z

+        with open(autopilot.settings.startup_settings_file, "r+", encoding="utf-8") as startup_settings:
+            settings = json.load(startup_settings)
+            environment = settings["core"].get("environment", [])
+
+            # make sure to remove MAV_SYSTEM_ID if it is already defined in
+            # bootstrap/startup.json
+            environment = [v for v in environment if not v.startswith("MAV_SYSTEM_ID=")]
+            environment.append(f"MAV_SYSTEM_ID={value}")
+            settings["core"]["environment"] = environment
+
+            startup_settings.seek(0)
+            startup_settings.write(json.dumps(settings, indent=2))
+            startup_settings.truncate()


i disagree with the bot here, if we fail to write to startup.json then we have bigger problems to worry about. it's definitely not the weakest link here

Implement support for changing the vehicle's system id on the firmware side through a PARAM_SET message that configures the MAV_SYSID parameter. Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

…ration This endpoint sets the MAV_SYSID firmware parameter and also sets the MAV_SYSTEM_ID environment variable (used by mavlink2rest) to its new value by updating bootstrap/startup.json. Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

Introduce the SystemId component with an input field for setting the vehicle's system ID. It also comes with two buttons: - A "Save" button that calls ardupilot_manager's /system_id endpoint to change the system id - A "Reboot Core" button which restarts the blueos-core container since the MAV_SYSTEM_ID environment variable change requires a container reboot to propagate Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

Follow the same naming convention as the command_long_message and param_set_message helpers. Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

nukelet · 2026-09-04T10:50:06Z

I moved the system ID change operation entirely into the backend and renamed the endpoint to /system_id. You can poke at it with curl:

curl -X POST http://<blueos-addr>/autopilot-manager/v1.0/system_id\?value\=42 -v

This was a bit more painful to figure out than I anticipated since there isn't a clean way for the onboard computer to know that the MAV_SYSID parameter was updated successfully in the firmware. The frontend (system id 255) gets to hear about it immediately because Ardupilot will (following the MAVLink spec) acknowledge a PARAM_SET operation by broadcasting a PARAM_VALUE message containing the new value of the updated parameter; however, since the onboard computer (which emits the PARAM_SET) has the same system id as Ardupilot (who broadcasts the PARAM_VALUE) and mavlink-server doesn't allow loopback messages, BlueOS never gets the PARAM_VALUE confirmation (this took me an embarassing amount of time to figure out).

patrickelectric

It's in a good direction, let's continue

patrickelectric · 2026-09-04T12:01:30Z

+        while time.time() - start_time < timeout:
+            if await self.is_heart_beating():
+                continue


not sure if I follow, isn't this the same than waiting 30s ? also.. would be nice to put the reference where in the system reflects in this 30s value.

yes, this should have been a break instead of continue. definitely needed more coffee when wrapping up these changes

patrickelectric · 2026-09-04T12:05:14Z

+        logger.warning(message)
+        return PlainTextResponse(message, status_code=503)
+
+    try:


IIRC try here is unnecessary since you are using the index_to_http_exception decorator

patrickelectric · 2026-09-04T12:14:08Z

+        url: '/version-chooser/v1.0/version/restart',
+      }).finally(() => {
+        // Give the backend a bit to go down, then reload so the user reconnects to the fresh core
+        setTimeout(() => window.location.reload(), 15000)


we should not guess, take a look in PowerMenu: waitForBackendToBeOnline

patrickelectric · 2026-09-04T12:19:58Z

+    try:
+        await autopilot.vehicle_manager.set_system_id(value)
+
+        if autopilot.vehicle_manager.target_system != value:


wait, isn't this supposed to be done already in set_system_id ?

patrickelectric · 2026-09-04T12:22:43Z

+        if autopilot.vehicle_manager.target_system != value:
+            return PlainTextResponse("Failed to set system ID", status_code=500)
+
+        with open(autopilot.settings.startup_settings_file, "r+", encoding="utf-8") as startup_settings:


it would be better to have it encapsulated by a class or something, maybe the settings itself, over opening and manipulating a settings file inside an api endpoint.

also.. maybe not even in autopilot.settings, but maybe autopilot.bootstrap.settings, with that you can create the abstraction in autopilot.bootstrap; also, if we are going to have shared logic of bootstrap here and with other services, does it worth to have a commonwealth place for it ?

nukelet force-pushed the configurable-vehicle-id branch 3 times, most recently from 8705e73 to d5fce82 Compare September 2, 2026 19:23

nukelet requested a balanced review from Copilot September 2, 2026 19:25

Copilot started reviewing on behalf of nukelet September 2, 2026 19:25 View session

Copilot AI reviewed Sep 2, 2026

View reviewed changes

nukelet force-pushed the configurable-vehicle-id branch 2 times, most recently from c489361 to cac5a82 Compare September 4, 2026 10:00

nukelet requested a balanced review from Copilot September 4, 2026 10:00

Copilot started reviewing on behalf of nukelet September 4, 2026 10:01 View session

Copilot AI reviewed Sep 4, 2026

View reviewed changes

nukelet added 4 commits September 4, 2026 07:24

core: libs: VehicleManager: add helpers for configuring the vehicle id

e649649

Implement support for changing the vehicle's system id on the firmware side through a PARAM_SET message that configures the MAV_SYSID parameter. Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

core: libs: VehicleManager: adjust naming for heartbeat message builder

ddefebf

Follow the same naming convention as the command_long_message and param_set_message helpers. Signed-off-by: Vinicius Peixoto <vinicius@nukelet.dev>

nukelet force-pushed the configurable-vehicle-id branch from cac5a82 to ddefebf Compare September 4, 2026 10:33

nukelet requested a review from a team September 4, 2026 10:35

patrickelectric requested changes Sep 4, 2026

View reviewed changes

		except Exception as error:
		logger.warning(f"Unable to write MAV_SYSTEM_ID to bootstrap/startup.json: {error}")

Uh oh!

Conversation

nukelet commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

joaoantoniocardoso commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nukelet commented Sep 3, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

nukelet Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

nukelet commented Sep 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

patrickelectric left a comment

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

nukelet Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026

Choose a reason for hiding this comment

Uh oh!

patrickelectric Sep 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

nukelet commented Sep 2, 2026 •

edited

Loading

joaoantoniocardoso commented Sep 3, 2026 •

edited

Loading

nukelet commented Sep 4, 2026 •

edited

Loading

patrickelectric Sep 4, 2026 •

edited

Loading