Current behaviour
A BlueOS setup currently cannot be changed to another vehicle type without needing its stored Cockpit configuration wiped.
This is mostly relevant to developers, but could also be relevant to some users in cases where they're upgrading one vehicle with a new thing and passing the old electronics to another vehicle as a hand-me-down (e.g. BlueBoat -> RPi5, and its RPi4 -> BlueROV2 with an RPi3).
It's frustrating to swap to a different firmware, and then have Cockpit pretend it's largely still the same vehicle type as before, despite knowing Cockpit has support (including default View and joystick profiles) for several different vehicle types.
Expected or desired behaviour
If a vehicle changes type (e.g. by flashing a new firmware), switch Cockpit to a relevant profile for that firmware.
Prerequisites
Current behaviour
A BlueOS setup currently cannot be changed to another vehicle type without needing its stored Cockpit configuration wiped.
This is mostly relevant to developers, but could also be relevant to some users in cases where they're upgrading one vehicle with a new thing and passing the old electronics to another vehicle as a hand-me-down (e.g. BlueBoat -> RPi5, and its RPi4 -> BlueROV2 with an RPi3).
It's frustrating to swap to a different firmware, and then have Cockpit pretend it's largely still the same vehicle type as before, despite knowing Cockpit has support (including default View and joystick profiles) for several different vehicle types.
Expected or desired behaviour
If a vehicle changes type (e.g. by flashing a new firmware), switch Cockpit to a relevant profile for that firmware.
Prerequisites