I am confused as to why both the frontend and backend would require internet access for a single functionality, although if there are valid reasons for that then we should likely have a warning about no control station internet access like we do for when the BlueOS device has no internet access.
Perhaps we could also:
add warnings to individual pages that require a particular connection type to function correctly
expand those warnings to mention which features are not available (or at least some broad types of features)
link to the tether passthrough docs if the connection to BlueOS is wired, and the control station is detected to have internet while BlueOS is detected not to
On the parameters front specifically, we might want to allow/enable:
storing one or more sets of parameters on the vehicle as a backup (which users could select between in a dropdown when "restoring")
automatically fetching the latest parameters when internet is first detected within a boot session, and storing it with a date if it differs from an existing backup file
I am confused as to why both the frontend and backend would require internet access for a single functionality, although if there are valid reasons for that then we should likely have a warning about no control station internet access like we do for when the BlueOS device has no internet access.
Perhaps we could also:
On the parameters front specifically, we might want to allow/enable: