[4mREMOTIVE[24m(1)                 General Commands Manual                 [4mREMOTIVE[24m(1)

[1mNAME[0m
       remotive - work with the RemotiveLabs platform from your terminal

remotive
       Welcome  to  RemotiveLabs CLI - work with the RemotiveLabs platform from
       your terminal

       For documentation - ]8;;https://developer.remotivelabs.com\https://developer.remotivelabs.com]8;;\

       See 'remotive --manual' or 'man remotive' for the complete reference.

       [1mUsage[22m:

              $ remotive [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --version: Print current version

       • --manual: Show the complete reference, the same as 'man remotive'

       • --verbose: [experimental] Enable verbose logging to stderr  for  trou‐
         bleshooting [env var: REMOTIVE_VERBOSE]

       • --install-completion: Install completion for the current shell.

       • --show-completion:  Show  completion for the current shell, to copy it
         or customize the installation.

       • --help: Show this message and exit.

       [1mCommands[22m:

       • studio: Start a RemotiveStudio instance

       • setup: Set up the RemotiveLabs authentication and tool chain  on  this
         machine, interactively

       • doctor:  [EXPERIMENTAL] Verify that host system is ok, required compo‐
         nents are installed and that authentication is setup.

       • upgrade: Upgrade remotivelabs-cli, RemotiveBus (Linux) and  RemotiveS‐
         tudio Desktop to the latest released versions (macOS, Linux)

       • topology: Interact and manage RemotiveTopology resources

       • broker: Manage a single broker - local or cloud

       • cloud: Manage resources in RemotiveCloud

       • auth:  Sign in to RemotiveCloud and manage accounts, the default orga‐
         nization and service accounts

       • connect: Integrations with other systems

   remotive studio
       Start a RemotiveStudio instance

       [1mUsage[22m:

              $ remotive studio [OPTIONS] [WORKSPACE_PATH]

       [1mArguments[22m:

       • [WORKSPACE_PATH]: Workspace path

       [1mOptions[22m:

       • --topology-image TEXT: Optional docker image for RemotiveTopology  CLI
         [env var: REMOTIVE_TOPOLOGY_IMAGE]

       • --container-engine [docker|podman]: Specify container engine (default:
         the one set with 'remotive topology config set container-engine', oth‐
         erwise docker) [env var: REMOTIVE_CONTAINER_ENGINE]

       • --container-registry  TEXT:  Container  registry prefix, e.g.  my-mir‐
         ror.example.com [env var: REMOTIVE_CONTAINER_REGISTRY]

       • --force / --no-force: Override existing RemotiveTopology workspace  if
         it exists [default: no-force]

       • --broker-url  TEXT: Broker URL [env var: REMOTIVE_BROKER_URL; default:
         http://localhost:50051]

       • --advertised-broker-url TEXT: Broker URL advertised to Studio  clients
         (defaults to --broker-url).  Use when clients reach the broker through
         a tunnel or forwarded port

       • --host TEXT: Host to run RemotiveStudio [default: 127.0.0.1]

       • --port  TEXT: Port to run RemotiveStudio, or "auto" to use a free port
         assigned by the OS [default: 57123]

       • --browser / --no-browser: Open RemotiveStudio in a  web  browser  (ig‐
         nored when --desktop is set) [default: browser]

       • --desktop / --no-desktop: [Beta] Launch the RemotiveStudio desktop app
         instead of serving in a browser [default: no-desktop]

       • --desktop-version  TEXT:  [Beta]  Desktop version (e.g.  1.2.3) to in‐
         stall and launch (default: latest).  Requires --desktop

       • --log-level TEXT: Log level for RemotiveStudio server [default:  warn‐
         ing]

       • --help: Show this message and exit.

   remotive setup
       Set  up  the RemotiveLabs authentication and tool chain on this machine,
       interactively

       Goes through it one step at a time:

       1. RemotiveCloud sign-in

       2. Default organization

       3. RemotiveTopology subscription: starts a 30-day trial  when  there  is
          none

       4. CLI  version  (reports  a  newer  release; upgrade with 'remotive up‐
          grade')

       5. Container engine: docker when it works, otherwise podman -  saved  as
          the default for every command

       6. RemotiveBus (Linux): checks it is installed and running

       7. RemotiveTopology:  downloads it (or checks for a newer one) and shows
          its version

       8. RemotiveStudio Desktop [Beta]: checks it is installed (optional)

       Each step checks what is in place and asks before it  signs  you  in  or
       changes your settings, so it is safe to re-run.  It asks whether to keep
       the  signed-in  account,  its default organization and the container en‐
       gine; --only-missing keeps them.  Any step can be  skipped;  setup  says
       what  that  means,  e.g.   that no RemotiveTopology command runs without
       docker or podman.  Exits with 1 only when a step ran into an error.

       [1mUsage[22m:

              $ remotive setup [OPTIONS]

       [1mOptions[22m:

       • --container-engine [docker|podman]: Container engine to set  up  Remo‐
         tiveTopology  with (default: the saved one, else docker when it works,
         else podman) [env var: REMOTIVE_CONTAINER_ENGINE]

       • --container-registry TEXT: Container registry  prefix,  e.g.   my-mir‐
         ror.example.com [env var: REMOTIVE_CONTAINER_REGISTRY]

       • --no-browser:  Sign  in  without  opening  a browser: copy a link to a
         browser elsewhere and paste the code back

       • --only-missing: Only change settings that are not yet set

       • --help: Show this message and exit.

   remotive doctor
       [EXPERIMENTAL] Verify that host system is ok,  required  components  are
       installed and that authentication is setup.

       [1mUsage[22m:

              $ remotive doctor [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive upgrade
       Upgrade remotivelabs-cli, RemotiveBus (Linux) and RemotiveStudio Desktop
       to the latest released versions (macOS, Linux)

       Compares  the installed versions with the latest releases on files.remo‐
       tivelabs.com and, when anything is outdated, downloads,  signature-veri‐
       fies  and  runs  the install scripts.  The CLI's install script upgrades
       the CLI and, on Linux, an installed RemotiveBus (add --install-remotive‐
       bus to install it); the desktop app's install  script  upgrades  an  in‐
       stalled  RemotiveStudio Desktop (add --install-studio-desktop to install
       it).  --install-all installs whatever of the two is missing  and  avail‐
       able for this host:

       ]8;;https://files.remotivelabs.com/install.sh\https://files.remotivelabs.com/install.sh]8;;\ ]8;;https://files.remotivelabs.com/remotive-studio-desktop/install.sh\https://files.remotive‐
       labs.com/remotive-studio-desktop/install.sh]8;;\

       The  scripts  are  bash, so on Windows the command only reports (--check
       works everywhere).

       [1mUsage[22m:

              $ remotive upgrade [OPTIONS]

       [1mOptions[22m:

       • --check: Only report available updates; exit code 1 when any exist,  0
         when up to date, 2 when the check failed

       • --dry-run: Show what the installers would do without changing anything
         (no prompt)

       • --install-remotivebus:  Also  install  RemotiveBus  when it is not in‐
         stalled (Linux; an installed one is always upgraded)

       • --install-studio-desktop: Also install RemotiveStudio Desktop when  it
         is not installed (an installed one is always upgraded)

       • --install-all:  Also install every component that is not installed and
         has a build for this host

       • --help: Show this message and exit.

   remotive topology
       Interact and manage RemotiveTopology resources

       Read more at ]8;;https://developer.remotivelabs.com/docs/remotive-topology\https://developer.remotivelabs.com/docs/remotive-topology]8;;\

       [1mUsage[22m:

              $ remotive topology [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --topology-image TEXT: Optional docker image for RemotiveTopology  CLI
         [env var: REMOTIVE_TOPOLOGY_IMAGE]

       • --topology-workspace  TEXT:  Optional override for workspace path [env
         var: REMOTIVE_TOPOLOGY_WORKSPACE]

       • --container-engine [docker|podman]: Specify container engine (default:
         the one set with 'remotive topology config set container-engine', oth‐
         erwise docker) [env var: REMOTIVE_CONTAINER_ENGINE]

       • --container-registry TEXT: Container registry  prefix,  e.g.   my-mir‐
         ror.example.com [env var: REMOTIVE_CONTAINER_REGISTRY]

       • --help: Show this message and exit.

       [1mCommands[22m:

       • analyze:  [EXPERIMENTAL] Static analysis of RemotiveTopology platforms
         and instances

       • build: Build a topology environment from instance descriptions

       • clean: Remove the build and mappings output for the current workspace

       • config: Manage RemotiveTopology settings saved in the CLI config

       • convert: [EXPERIMENTAL] Convert signal database to different format.

       • gateway-mapping: [EXPERIMENTAL] List gateway mapping for ECU

       • generate: [DEPRECATED] Use 'build' instead.

       • prune: Remove cache and build output (workspace-scoped if inside  one;
         --all for every workspace)

       • recording-session: Work with recording sessions

       • show: Show information from database file

       • split: [DEPRECATED] Extract individual signal databases for each chan‐
         nel in a RemotiveTopology platform.

       • start-trial:  Allows you to start a 30 day trial subscription for run‐
         ning RemotiveTopology.

       • subscription: Manage RemotiveTopology subscriptions, you can  start  a
         trial subscription or check the status of your subscription.

       • validate: [EXPERIMENTAL] Validate file

       • version: Show RemotiveTopology CLI version.

       • workspace: Manage RemotiveTopology workspaces

   remotive topology analyze
       [EXPERIMENTAL]  Static  analysis  of  RemotiveTopology platforms and in‐
       stances

       [1mUsage[22m:

              $ remotive topology analyze [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • busload: [EXPERIMENTAL] Calculate the base (cyclic) CAN bus  load  per
         channel.

   remotive topology analyze busload
       [EXPERIMENTAL] Calculate the base (cyclic) CAN bus load per channel.

       Every  CAN frame with a cycle time is assumed to be sent continuously at
       that rate.  The on-wire size of each frame is computed from the CAN  2.0
       /  CAN FD frame format, with and without worst-case bit stuffing, so the
       true load lies between the two figures.

       Bit rates are taken from the platform file (baudrate /  baudrate_fd  per
       channel);  CAN  FD frames switch to the baudrate_fd for their data phase
       when one is given.  Channels without a bit rate still get bytes per sec‐
       ond, but no bus load percentage.

       [1mUsage[22m:

              $ remotive topology analyze busload [OPTIONS]

       [1mOptions[22m:

       • -f, --file TEXT: RemotiveTopology platform or instance file [required]

       • --json: Output results in JSON format

       • --help: Show this message and exit.

   remotive topology build
       Build a topology environment from instance descriptions

       [1mUsage[22m:

              $ remotive topology build [OPTIONS] [TOPOLOGY_OUTPUT_PATH]

       [1mArguments[22m:

       • [TOPOLOGY_OUTPUT_PATH]: Path to where generated files should be  writ‐
         ten.    Optional   in  a  workspace  (defaults  to  <workspace>/.remo‐
         tive/build, must be inside the workspace);  required  with  --no-work‐
         space.

       [1mOptions[22m:

       • --with-metrics:  Enable  Prometheus + Grafana metrics in the generated
         topology

       • --no-workspace: Skip the REMOTIVE_TOPOLOGY_WORKSPACE  check  (disables
         caching for this run)

       • -n, --name TEXT: Name of the generated topology

       • -f,  --file  TEXT: RemotiveTopology .instance.yaml file(s), applied in
         the order they are provided [required]

       • --help: Show this message and exit.

   remotive topology clean
       Remove the build and mappings output for the current workspace

       [1mUsage[22m:

              $ remotive topology clean [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology config
       Manage RemotiveTopology settings saved in the CLI config

       [1mUsage[22m:

              $ remotive topology config [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • get: Print the value in effect for a setting

       • set: Save a setting, e.g.

       • unset: Remove a saved setting, so its default is used

       • list: List the settings, their values and where each comes from

   remotive topology config get
       Print the value in effect for a setting

       [1mUsage[22m:

              $ remotive topology config get [OPTIONS] KEY

       [1mArguments[22m:

       • KEY: The setting, e.g.  container-engine [required]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology config set
       Save a setting, e.g.  'remotive  topology  config  set  container-engine
       podman'

       [1mUsage[22m:

              $ remotive topology config set [OPTIONS] KEY VALUE

       [1mArguments[22m:

       • KEY: The setting, e.g.  container-engine [required]

       • VALUE: The value, e.g.  podman [required]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology config unset
       Remove a saved setting, so its default is used

       [1mUsage[22m:

              $ remotive topology config unset [OPTIONS] KEY

       [1mArguments[22m:

       • KEY: The setting, e.g.  container-engine [required]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology config list
       List the settings, their values and where each comes from

       [1mUsage[22m:

              $ remotive topology config list [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology convert
       [EXPERIMENTAL]  Convert  signal database to different format.  Currently
       only CAN and LIN frames is supported.

       [1mUsage[22m:

              $ remotive topology convert [OPTIONS]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • -f, --file TEXT: RemotiveTopology platform file [required]

       • -o, --output TEXT: Optional path to  a  file  where  generated  signal
         database  should  be  written.   If  not  provided, the result will be
         printed to stdout.

       • --format TEXT: Signal database format to convert to.   Currently  only
         'remotive' is supported.

       • -c,  --channel TEXT: Optional channel(s) to convert.  If not provided,
         all supported channels will be converted.

       • --help: Show this message and exit.

   remotive topology gateway-mapping
       [EXPERIMENTAL] List gateway mapping for ECU

       [1mUsage[22m:

              $ remotive topology gateway-mapping [OPTIONS] [OUT_PATH]

       [1mArguments[22m:

       • [OUT_PATH]: Path to file where extracted  gateway  mapping  should  be
         written.   Optional  in  a  workspace  (defaults to <workspace>/.remo‐
         tive/mappings/<gateway-ecu>.mapping.yaml   for   legacy   and   <gate‐
         way-ecu>.gateway-mapping.yaml  for gateway-mapping, must be inside the
         workspace); required with --no-workspace.

       [1mOptions[22m:

       • -o, --only-fully-resolved: Only show fully resolved mapping

       • --no-workspace: Skip the REMOTIVE_TOPOLOGY_WORKSPACE check (paths  may
         point anywhere)

       • -g, --gateway-ecu TEXT: Gateway ECU name [required]

       • -p, --platform TEXT: Topology platform [required]

       • --format  TEXT:  Mapping  format to emit: 'legacy' (default) or 'gate‐
         way-mapping'

       • --help: Show this message and exit.

   remotive topology generate
       [DEPRECATED] Use 'build' instead.  Build a topology environment from in‐
       stance descriptions.

       [1mUsage[22m:

              $ remotive topology generate [OPTIONS] TOPOLOGY_OUTPUT_PATH

       [1mArguments[22m:

       • TOPOLOGY_OUTPUT_PATH: Path to where generated files should be  written
         [required]

       [1mOptions[22m:

       • --with-metrics:  Enable  Prometheus + Grafana metrics in the generated
         topology

       • -n, --name TEXT: Name of the generated topology

       • -f, --file TEXT: RemotiveTopology .instance.yaml file(s),  applied  in
         the order they are provided [required]

       • --help: Show this message and exit.

   remotive topology prune
       Remove cache and build output (workspace-scoped if inside one; --all for
       every workspace)

       [1mUsage[22m:

              $ remotive topology prune [OPTIONS]

       [1mOptions[22m:

       • --all: Remove caches for every workspace, not just the current one

       • --help: Show this message and exit.

   remotive topology recording-session
       Work with recording sessions

       [1mUsage[22m:

              $ remotive topology recording-session [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • create: Create a new recording session from recording files

       • instantiate: Create a topology instance ready to play a recording ses‐
         sion

       • recalculate:  Recalculate  the  recording  session  start and end time
         based on the files and their offsets

   remotive topology recording-session create
       Create a new recording session from recording files

       [1mUsage[22m:

              $ remotive topology recording-session create [OPTIONS] [OUT_PATH]

       [1mArguments[22m:

       • [OUT_PATH]: Write content to provided file path

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • -f, --file TEXT: Recording file(s), applied in the order they are pro‐
         vided, e.g.  candump.log, .csv [required]

       • --help: Show this message and exit.

   remotive topology recording-session instantiate
       Create a topology instance ready to play a recording session

       [1mUsage[22m:

              $ remotive topology recording-session instantiate [OPTIONS] RECORDING_SESSION [OUT_PATH]

       [1mArguments[22m:

       • RECORDING_SESSION: Path to the recording session file [required]

       • [OUT_PATH]: Write content to provided file path

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --help: Show this message and exit.

   remotive topology recording-session recalculate
       Recalculate the recording session start and end time based on the  files
       and their offsets

       [1mUsage[22m:

              $ remotive topology recording-session recalculate [OPTIONS] RECORDING_SESSION [OUT_PATH]

       [1mArguments[22m:

       • RECORDING_SESSION: Path to the recording session file [required]

       • [OUT_PATH]: Write content to provided file path

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --help: Show this message and exit.

   remotive topology show
       Show information from database file

       [1mUsage[22m:

              $ remotive topology show [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • signals: [EXPERIMENTAL] Show signals in the provided database file

       • constants: [EXPERIMENTAL] Extract constants from database file

       • instance: Shows the resolved instance

       • platform: Shows the platform from database, platform or instance file

       • ethernet:  [EXPERIMENTAL]  Shows  Ethernet configuration from database
         file

       • services: [EXPERIMENTAL] Show SOME/IP services from database file

   remotive topology show signals
       [EXPERIMENTAL] Show signals in the provided database file

       [1mUsage[22m:

              $ remotive topology show signals [OPTIONS] PATH [OUT_PATH]

       [1mArguments[22m:

       • PATH: Path to  the  Database  file,  supported  extensions:  '.arxml',
         '.dbc', '.xml', '.ldf', '.signaldb.yaml' [required]

       • [OUT_PATH]: Write content to provided file path

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --jsonl: Output results in JSONL format

       • --bf: Output results in broker format

       • --flexray-channel  TEXT:  FlexRay  physical  channel name relevant for
         Fibex databases

       • --can-channel TEXT: CAN physical channel name relevant for arxml data‐
         bases

       • --lin-channel TEXT: LIN physical channel name relevant for arxml data‐
         bases

       • --help: Show this message and exit.

   remotive topology show constants
       [EXPERIMENTAL] Extract constants from database file

       [1mUsage[22m:

              $ remotive topology show constants [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the Database file, supported extensions:  '.arxml'  [re‐
         quired]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --help: Show this message and exit.

   remotive topology show instance
       Shows the resolved instance

       [1mUsage[22m:

              $ remotive topology show instance [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:   Path   to  the  Database  file,  supported  extensions:  '.in‐
         stance.yaml' [required]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --check: Check topology

       • --full-platform: Show full platform, not  just  the  instance-specific
         parts

       • --verbose: (Deprecated) Has no effect

       • -o, --out-path TEXT: Write content to provided file path

       • --help: Show this message and exit.

   remotive topology show platform
       Shows the platform from database, platform or instance file

       [1mUsage[22m:

              $ remotive topology show platform [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:  Path  to  the  Database  file,  supported extensions: '.arxml',
         '.xml', '.instance.yaml',  '.platform.yaml',  '.dbc',  '.ldf',  '.sig‐
         naldb.yaml' [required]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --verbose: (Deprecated) Has no effect

       • -o, --out-path TEXT: Write content to provided file path

       • --help: Show this message and exit.

   remotive topology show ethernet
       [EXPERIMENTAL] Shows Ethernet configuration from database file

       [1mUsage[22m:

              $ remotive topology show ethernet [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:  Path  to the Database file, supported extensions: '.arxml' [re‐
         quired]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • --help: Show this message and exit.

   remotive topology show services
       [EXPERIMENTAL] Show SOME/IP services from database file

       [1mUsage[22m:

              $ remotive topology show services [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the Database file, supported extensions:  '.arxml'  [re‐
         quired]

       [1mOptions[22m:

       • --json: Output results in JSON format

       • --yaml: Output results in YAML format (default)

       • -s, --services TEXT: List of SOME/IP services to process

       • --help: Show this message and exit.

   remotive topology split
       [DEPRECATED]  Extract  individual signal databases for each channel in a
       RemotiveTopology platform.

       [1mUsage[22m:

              $ remotive topology split [OPTIONS] TOPOLOGY_OUTPUT_PATH

       [1mArguments[22m:

       • TOPOLOGY_OUTPUT_PATH: Path to a folder where  generated  signal  data‐
         bases should be written [required]

       [1mOptions[22m:

       • -f, --file TEXT: RemotiveTopology platform file(s), applied in the or‐
         der they are provided [required]

       • --help: Show this message and exit.

   remotive topology start-trial
       Allows  you  to  start a 30 day trial subscription for running Remotive‐
       Topology.

       You can read more  at  ]8;;https://developer.remotivelabs.com/docs/remotive-topology\https://developer.remotivelabs.com/docs/remotive-
       topology]8;;\.

       [1mUsage[22m:

              $ remotive topology start-trial [OPTIONS]

       [1mOptions[22m:

       • --organization  TEXT:  Organization to start trial for [env var: REMO‐
         TIVE_CLOUD_ORGANIZATION]

       • --help: Show this message and exit.

   remotive topology subscription
       Manage RemotiveTopology subscriptions, you can start a  trial  subscrip‐
       tion or check the status of your subscription.

       To  extend a trial subscription, or purchase a subscription, please con‐
       tact ]8;;mailto:support@remotivelabs.com\support@remotivelabs.com]8;;\.

       [1mUsage[22m:

              $ remotive topology subscription [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • start-trial: Allows you to start a 30 day trial subscription for  run‐
         ning RemotiveTopology.

       • status:  Show  the current RemotiveTopology subscription status for an
         organization.

   remotive topology subscription start-trial
       Allows you to start a 30 day trial subscription  for  running  Remotive‐
       Topology.

       You  can  read more at ]8;;https://developer.remotivelabs.com/docs/remotive-topology\https://developer.remotivelabs.com/docs/remotive-
       topology]8;;\.

       [1mUsage[22m:

              $ remotive topology subscription start-trial [OPTIONS]

       [1mOptions[22m:

       • --organization TEXT: Organization to start trial for [env  var:  REMO‐
         TIVE_CLOUD_ORGANIZATION]

       • --help: Show this message and exit.

   remotive topology subscription status
       Show  the  current RemotiveTopology subscription status for an organiza‐
       tion.

       [1mUsage[22m:

              $ remotive topology subscription status [OPTIONS]

       [1mOptions[22m:

       • --organization TEXT: Organization to  check  subscription  status  for
         [env var: REMOTIVE_CLOUD_ORGANIZATION]

       • --help: Show this message and exit.

   remotive topology validate
       [EXPERIMENTAL] Validate file

       [1mUsage[22m:

              $ remotive topology validate [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:  Path  to the Database file, supported extensions: '.arxml' [re‐
         quired]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology version
       Show RemotiveTopology CLI version.

       [1mUsage[22m:

              $ remotive topology version [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive topology workspace
       Manage RemotiveTopology workspaces

       [1mUsage[22m:

              $ remotive topology workspace [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • init: Initialize a RemotiveTopology workspace in the current directory

       • current: Show the current RemotiveTopology workspace

   remotive topology workspace init
       Initialize a RemotiveTopology workspace in the current directory

       [1mUsage[22m:

              $ remotive topology workspace init [OPTIONS]

       [1mOptions[22m:

       • --force / --no-force: Override existing RemotiveTopology workspace  if
         it exists [default: no-force]

       • --help: Show this message and exit.

   remotive topology workspace current
       Show the current RemotiveTopology workspace

       [1mUsage[22m:

              $ remotive topology workspace current [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive broker
       Manage a single broker - local or cloud

       [1mUsage[22m:

              $ remotive broker [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --ui: [Experimental] Launch the interactive TUI explorer

       • --help: Show this message and exit.

       [1mCommands[22m:

       • playback: Manage playback of recording sessions

       • record: Record data on buses

       • files: Upload/Download configurations and recordings

       • signals: Find and subscribe to signals

       • restbus: Control periodic frame transmission on a broker.

       • export: Export to external formats

       • scripting: LUA scripting utilities

       • license: View and request license to broker

   remotive broker playback
       Manage playback of recording sessions

       All offsets are in microseconds (μs)

       [1mUsage[22m:

              $ remotive broker playback [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list-files: List files on broker.

       • play: Starts playing the recording at current offset or from specified
         offset

       • repeat:  Repeat  RecordingSession  in  specific  interval  or complete
         recording To remove existing repeat config, use --clear flag.

       • pause: Pause the recording at current offset or specified offset

       • seek: Seek to specified offset

       • open: Open a recording session.

       • close: Close a recording session.

       • status: Get the status of all opened Recording sessions

   remotive broker playback list-files
       List files on broker.

       [1mUsage[22m:

              $ remotive broker playback list-files [OPTIONS] [PATH]

       [1mArguments[22m:

       • [PATH]: Optional subdirectory to list files in,  defaults  to  /  [de‐
         fault: /]

       [1mOptions[22m:

       • --recursive  /  --no-recursive:  List  subdirectories recursively [de‐
         fault: no-recursive]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback play
       Starts playing the recording at current offset or from specified offset

              Offsets can be specified in minutes (1:15min), seconds(10s), millis(10000ms) or micros(10000000us), default without suffix is micros.
              Sample offsets
              --offset 1.15min, 10s, 10000ms, 10000000us, 10000000,

       [1mUsage[22m:

              $ remotive broker playback play [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the recording session [env var:  REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --offset TEXT: Offset to play from

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback repeat
       Repeat  RecordingSession  in  specific interval or complete recording To
       remove existing repeat config, use --clear flag.

              Offsets can be specified in minutes (1:15min), seconds(10s), millis(10000ms) or micros(10000000us), default without suffix is micros.
              Sample offsets
              --start-offset/--end-offset 1.15min, 10s, 10000ms, 10000000us, 10000000,

       [1mUsage[22m:

              $ remotive broker playback repeat [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the recording session [env var:  REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --start-offset  TEXT: Repeat start offset, defaults to start [default:
         0]

       • --end-offset TEXT: Repeat end offset, defaults to end

       • --clear / --no-clear: Clear repeat [default: no-clear]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback pause
       Pause the recording at current offset or specified offset

       Offsets can  be  specified  in  minutes  (1:15min),  seconds(10s),  mil‐
       lis(10000ms)  or  micros(10000000us),  default without suffix is micros.
       Sample offsets --offset 1.15min, 10s, 10000ms, 10000000us, 10000000,

       [1mUsage[22m:

              $ remotive broker playback pause [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the recording session [env var:  REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --offset TEXT: Offset to pause at

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback seek
       Seek to specified offset

       Offsets  can  be  specified  in  minutes  (1:15min),  seconds(10s), mil‐
       lis(10000ms) or micros(10000000us), default without  suffix  is  micros.
       Sample offsets --offset 1.15min, 10s, 10000ms, 10000000us, 10000000,

       [1mUsage[22m:

              $ remotive broker playback seek [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:  Path to the recording session [env var: REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --offset TEXT: Offset to seek to [required]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback open
       Open a recording session.

       [1mUsage[22m:

              $ remotive broker playback open [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to the recording session [env var:  REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --force / --no-force: Force close and re-open recording session if ex‐
         ists [default: no-force]

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback close
       Close a recording session.

       [1mUsage[22m:

              $ remotive broker playback close [OPTIONS] PATH

       [1mArguments[22m:

       • PATH:  Path to the recording session [env var: REMOTIVE_RECORDING_SES‐
         SION_PATH; required]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker playback status
       Get the status of all opened Recording sessions

       [1mUsage[22m:

              $ remotive broker playback status [OPTIONS]

       [1mOptions[22m:

       • --stream / --no-stream: Blocks and continuously streams statuses  [de‐
         fault: no-stream]

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker record
       Record data on buses

       [1mUsage[22m:

              $ remotive broker record [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • start

       • stop

   remotive broker record start
       [1mUsage[22m:

              $ remotive broker record start [OPTIONS] FILENAME

       [1mArguments[22m:

       • FILENAME:  Recording  file  name  on  the  broker  (each  namespace is
         recorded to FILENAME_<namespace>) [required]

       [1mOptions[22m:

       • --namespace TEXT: Namespace to record [required]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker record stop
       [1mUsage[22m:

              $ remotive broker record stop [OPTIONS] FILENAME

       [1mArguments[22m:

       • FILENAME: Recording file name used when the recording was started [re‐
         quired]

       [1mOptions[22m:

       • --namespace TEXT: Namespace to record [required]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker files
       Upload/Download configurations and recordings

       [1mUsage[22m:

              $ remotive broker files [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • reload-configuration

       • delete: Deletes the specified files from the broker

       • download: Downloads a file from a broker

       • upload: Uploads a file to a broker - physical or in cloud.

   remotive broker files reload-configuration
       [1mUsage[22m:

              $ remotive broker files reload-configuration [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker files delete
       Deletes the specified files from the broker

       [1mUsage[22m:

              $ remotive broker files delete [OPTIONS] PATH...

       [1mArguments[22m:

       • PATH...: Paths to files on broker to delete [required]

       [1mOptions[22m:

       • --exit-on-failure / --no-exit-on-failure: Exits if there was a problem
         deleting a file [default: no-exit-on-failure]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker files download
       Downloads a file from a broker

       [1mUsage[22m:

              $ remotive broker files download [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to file on broker to download [required]

       [1mOptions[22m:

       • --output TEXT: Optional output file name

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker files upload
       Uploads a file to a broker - physical or in cloud.

       [1mUsage[22m:

              $ remotive broker files upload [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to local file to upload [required]

       [1mOptions[22m:

       • --output TEXT: Optional output path on broker

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker signals
       Find and subscribe to signals

       [1mUsage[22m:

              $ remotive broker signals [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: List signal metadata on a broker

       • subscribe: Subscribe to a selection of signals

       • namespaces: List namespaces on broker

       • frame-distribution: Use this command to get frames currently available
         on the specified namespace.

       • publish: Publish one or more signals to the broker.

   remotive broker signals list
       List signal metadata on a broker

       Filter are inclusive so --name-starts-with and --name-ends-with will in‐
       clude name that matches both

       [1mUsage[22m:

              $ remotive broker signals list [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --name-starts-with TEXT: Signal name prefix to include

       • --name-ends-with TEXT: Signal name suffix to include

       • --help: Show this message and exit.

   remotive broker signals subscribe
       Subscribe to a selection of signals

       Subscribe to two signals and have it printed to terminal

              remotive broker signals subscribe  --url http://localhost:50051 --signal can1:signal1 --signal can0:signal2

       Subscribe using a LUA script  with  signal  transformations,  read  more
       about  scripted signals at ]8;;https://developer.remotivelabs.com/docs/remotive-broker\https://developer.remotivelabs.com/docs/remo‐
       tive-broker]8;;\

              remotive broker signals subscribe  --url http://localhost:50051 --script myvss_script.lua

       [1mUsage[22m:

              $ remotive broker signals subscribe [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --signal NAMESPACE:SIGNAL_NAME: Signal(s) to subscribe to

       • --script FILE: Supply a path to a Lua script to use for signal  trans‐
         formation

       • --on-change-only  /  --no-on-change-only:  Only get signal if value is
         changed [default: no-on-change-only]

       • --x-plot / --no-x-plot: Experimental: Plot  the  signal  in  terminal.
         Note graphs are not aligned by time [default: no-x-plot]

       • --x-plot-size  INTEGER:  Experimental:  how  many points show for each
         plot [default: 100]

       • --help: Show this message and exit.

   remotive broker signals namespaces
       List namespaces on broker

       [1mUsage[22m:

              $ remotive broker signals namespaces [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --help: Show this message and exit.

   remotive broker signals frame-distribution
       Use this command to get frames  currently  available  on  the  specified
       namespace.

       [1mUsage[22m:

              $ remotive broker signals frame-distribution [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --namespace TEXT: Namespace [required]

       • --help: Show this message and exit.

   remotive broker signals publish
       Publish one or more signals to the broker.

       Values are scalars or comma-separated lists (e.g.  10,20,30).  When sig‐
       nals have different list lengths they are zipped to the longest; shorter
       signals are omitted from frames beyond their length.

       Publish a speed signal value of 50 on namespace can0:

              remotive broker signals publish --signal can0:Speed:50

       Publish multiple signals at once:

              remotive broker signals publish --signal can0:Speed:50 --signal can0:Rpm:3000.0

       Publish a sweep of speed values alongside RPM once:

              remotive broker signals publish --signal can0:Speed:10,20,30 --signal can0:Rpm:1000

       [1mUsage[22m:

              $ remotive broker signals publish [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --signal  NAMESPACE:SIGNAL_NAME:V1[,V2,...]: Signal(s) to publish [re‐
         quired]

       • --help: Show this message and exit.

   remotive broker restbus
       Control periodic frame transmission on a broker.  Restbus lets  you  in‐
       ject frames onto a bus at a fixed cycle time, optionally overriding sig‐
       nal values.  Typical workflow: add → start → update → stop/reset.

       [1mUsage[22m:

              $ remotive broker restbus [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • add: Register one or more frames (with optional cycle time override).

       • start:  Begin  transmitting  registered  frames on the specified name‐
         space(s).

       • stop: Pause transmission without removing configuration.

       • update: Change signal values to be emitted by the restbus.

       • remove: Remove specific frames from the restbus.

       • reset: Clear all configuration for a namespace.

   remotive broker restbus add
       Register one or more frames (with optional cycle time override).

       [1mUsage[22m:

              $ remotive broker restbus add [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --frame NAMESPACE:FRAME_NAME: Frame(s) to  add  (namespace:frame_name)
         [required]

       • --cycle-time FLOAT: Cycle time override in ms

       • --start / --no-start: Start frames after adding [default: no-start]

       • --help: Show this message and exit.

   remotive broker restbus start
       Begin transmitting registered frames on the specified namespace(s).

       [1mUsage[22m:

              $ remotive broker restbus start [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --namespace TEXT: Namespace(s) to start [required]

       • --help: Show this message and exit.

   remotive broker restbus stop
       Pause transmission without removing configuration.

       [1mUsage[22m:

              $ remotive broker restbus stop [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --namespace TEXT: Namespace(s) to stop [required]

       • --help: Show this message and exit.

   remotive broker restbus update
       Change signal values to be emitted by the restbus.

       [1mUsage[22m:

              $ remotive broker restbus update [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --signal  NAMESPACE:SIGNAL_NAME:V1[,V2,...]: Signal(s) to update (loop
         values) [required]

       • --initial NAMESPACE:SIGNAL_NAME:V1[,V2,...]: Signal(s) initial  values
         (emitted once before loop)

       • --help: Show this message and exit.

   remotive broker restbus remove
       Remove specific frames from the restbus.

       Unregisters  the named frames from the given namespace.  Unlike 'reset',
       this only removes the specified frames and leaves others intact.

       [1mUsage[22m:

              $ remotive broker restbus remove [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --frame    NAMESPACE:FRAME_NAME:    Frame(s)    to    remove    (name‐
         space:frame_name) [required]

       • --help: Show this message and exit.

   remotive broker restbus reset
       Clear all configuration for a namespace.

       [1mUsage[22m:

              $ remotive broker restbus reset [OPTIONS]

       [1mOptions[22m:

       • --url   TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;  default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --namespace TEXT: Namespace(s) to reset [required]

       • --help: Show this message and exit.

   remotive broker export
       Export to external formats

       [1mUsage[22m:

              $ remotive broker export [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • influxdb: Exports subscribed signals to InfluxDB line-protocol, really
         useful to dump some signals into influxdb for offline analysis and in‐
         sights.

   remotive broker export influxdb
       Exports  subscribed  signals to InfluxDB line-protocol, really useful to
       dump some signals into influxdb for offline analysis and insights.

       This is a sample for exporting and importing  to  InfluxDB  using  remo‐
       tive-cli and influx-cli

       Export: remotive broker export influxdb --url [URL] --output signals.in‐
       flux
       --signal  vehiclebus:Control.SteeringWheel_Position --signal Control.Ac‐
       celerator_PedalPosition
       --signal vehiclebus:GpsPosition.GPS_Longitude --signal vehiclebus:GpsPo‐
       sition.GPS_Latitude

       Output: Control, namespace:vehiclebus  SteeringWheel_Position=1.0,Accel‐
       erator_PedalPosition=0,Speed=0  1664787032944374000  GpsPosition,  name‐
       space:vehiclebus          GPS_Longitude=12.982076,GPS_Latitude=55.618748
       1664787032948256000

       Import:  influx write --org myorg -b my-bucket -p ns --format=lp -f sig‐
       nals.influx

       [1mUsage[22m:

              $ remotive broker export influxdb [OPTIONS]

       [1mOptions[22m:

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --api-key  TEXT:  Cloud Broker API-KEY or access token [env var: REMO‐
         TIVE_BROKER_API_KEY]

       • --signal NAMESPACE:SIGNAL_NAME: Signal(s) to subscribe to [required]

       • --on-change-only / --no-on-change-only: Only get signal  if  value  is
         changed [default: no-on-change-only]

       • --output TEXT: Write results to file, defaults to stdout

       • --help: Show this message and exit.

   remotive broker scripting
       LUA scripting utilities

       [1mUsage[22m:

              $ remotive broker scripting [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • new-script

   remotive broker scripting new-script
       [1mUsage[22m:

              $ remotive broker scripting new-script [OPTIONS]

       [1mOptions[22m:

       • --input-signal NAMESPACE:SIGNAL_NAME: Input signal(s) [required]

       • --output-signal TEXT: Name of output signal [required]

       • --save  / --no-save: Save file to disk - Default stored as [1moutput_sig‐[0m
         [1mnal[22m.lua [default: no-save]

       • --help: Show this message and exit.

   remotive broker license
       View and request license to broker

       [1mUsage[22m:

              $ remotive broker license [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • describe: Show licence information

       • request: Requests and applies a new or existing License to  a  broker,
         Note that internet access is required on your computer

   remotive broker license describe
       Show licence information

       More info on our docs page ]8;;https://developer.remotivelabs.com/docs/remotive-broker/getting-started\https://developer.remotivelabs.com/docs/remo‐
       tive-broker/getting-started]8;;\

       --connect  describes  how the connection is made to the broker and helps
       us properly connect to broker

       url = Connects to the broker with the specified url, this is  hotspot  =
       If you are using RemotiveBox (our reference hardware) you can connect to
       the  broker over its wifi hotspot.  Getting the license from a Remotive‐
       Box over its wifi hotspot requires you switch wi-fi network to the Remo‐
       tiveBox hotspot called 'remotivelabs-xxx' where 'xxx' is a random gener‐
       ated id.

       --url is the broker url, this is mandatory when connect type is "url"

       [1mUsage[22m:

              $ remotive broker license describe [OPTIONS]

       [1mOptions[22m:

       • --connect [hotspot|url]: How to connect to broker [default: url]

       • --url  TEXT:  Broker  URL  [env  var:  REMOTIVE_BROKER_URL;   default:
         http://localhost:50051]

       • --help: Show this message and exit.

   remotive broker license request
       Requests  and  applies  a new or existing License to a broker, Note that
       internet access is required on your computer

       More info on our docs page ]8;;https://developer.remotivelabs.com/docs/remotive-broker/getting-started\https://developer.remotivelabs.com/docs/remo‐
       tive-broker/getting-started]8;;\

       --connect describes how the connection is made to the broker  and  helps
       us properly connect to broker

       url  = Use url to connect to broker (use --url) hotspot = If you are us‐
       ing RemotiveBox (our reference hardware) you can connect to  the  broker
       over  its  wifi  hotspot.   Licensing a broker on a RemotiveBox over its
       wifi hotspot requires  you  switch  wi-fi  network  to  the  RemotiveBox
       hotspot  called 'remotivelabs-xxx' where 'xxx' is a random generated id.
       ]8;;https://developer.remotivelabs.com/docs/remotive-broker/getting-started/remotive-box\https://developer.remotivelabs.com/docs/remotive-broker/getting-
       started/remotive-box]8;;\

       --url is the broker url, this is mandatory when connect type is "url"

       [1mUsage[22m:

              $ remotive broker license request [OPTIONS]

       [1mOptions[22m:

       • --connect [hotspot|url]: How to connect to broker [default: url]

       • --url TEXT: Broker url, this is mandatory when connect type  is  'url'
         [env var: REMOTIVE_BROKER_URL; default: http://localhost:50051]

       • --help: Show this message and exit.

   remotive cloud
       Manage resources in RemotiveCloud

       [1mUsage[22m:

              $ remotive cloud [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • licenses: List licenses for an organization

       • organizations: Manage organizations

       • projects: Manage projects

       • auth: (deprecated) Moved to 'remotive auth'

       • brokers: Manage cloud broker lifecycle

       • recordings: Manage recordings

       • signal-databases: Manage signal databases

       • storage: Manage files (Beta feature not available for all customers)

       • service-accounts:  (deprecated)  Moved  to  'remotive auth service-ac‐
         counts'

       • samples: Manage sample recordings

   remotive cloud licenses
       List licenses for an organization

       [1mUsage[22m:

              $ remotive cloud licenses [OPTIONS]

       [1mOptions[22m:

       • --organization TEXT: Organization ID [env var:  REMOTIVE_CLOUD_ORGANI‐
         ZATION; required]

       • --filter-option TEXT: all, valid, expired [default: all]

       • --help: Show this message and exit.

   remotive cloud organizations
       Manage organizations

       [1mUsage[22m:

              $ remotive cloud organizations [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • default:  (deprecated)  Use 'remotive auth organization set/print' in‐
         stead

       • list: List your available organizations

   remotive cloud organizations default
       Use 'remotive auth organization set/print' instead

       [1mUsage[22m:

              $ remotive cloud organizations default [OPTIONS] [ORGANIZATION_UID]

       [1mArguments[22m:

       • [ORGANIZATION_UID]: Organization uid or empty to select one

       [1mOptions[22m:

       • --get / --no-get: Print current default organization [default: no-get]

       • --help: Show this message and exit.

   remotive cloud organizations list
       List your available organizations

       [1mUsage[22m:

              $ remotive cloud organizations list [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive cloud projects
       Manage projects

       [1mUsage[22m:

              $ remotive cloud projects [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: List your projects

       • create

       • delete

   remotive cloud projects list
       List your projects

       [1mUsage[22m:

              $ remotive cloud projects list [OPTIONS]

       [1mOptions[22m:

       • --organization TEXT: Organization ID [env var:  REMOTIVE_CLOUD_ORGANI‐
         ZATION; required]

       • --help: Show this message and exit.

   remotive cloud projects create
       [1mUsage[22m:

              $ remotive cloud projects create [OPTIONS] PROJECT_UID

       [1mArguments[22m:

       • PROJECT_UID: Project UID [required]

       [1mOptions[22m:

       • --organization  TEXT: Organization ID [env var: REMOTIVE_CLOUD_ORGANI‐
         ZATION; required]

       • --project-display-name TEXT: Project display name

       • --help: Show this message and exit.

   remotive cloud projects delete
       [1mUsage[22m:

              $ remotive cloud projects delete [OPTIONS] PROJECT

       [1mArguments[22m:

       • PROJECT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive cloud brokers
       Manage cloud broker lifecycle

       [1mUsage[22m:

              $ remotive cloud brokers [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: Lists brokers in project

       • describe: Shows details about a specific broker

       • delete: Stops and deletes a broker from project

       • delete-personal: Deletes your personal broker from project

       • create: Create a broker in project

       • logs: Exposes broker logs history or real-time tail of the broker.

   remotive cloud brokers list
       Lists brokers in project

       [1mUsage[22m:

              $ remotive cloud brokers list [OPTIONS]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud brokers describe
       Shows details about a specific broker

       [1mUsage[22m:

              $ remotive cloud brokers describe [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud brokers delete
       Stops and deletes a broker from project

       [1mUsage[22m:

              $ remotive cloud brokers delete [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud brokers delete-personal
       Deletes your personal broker from project

       [1mUsage[22m:

              $ remotive cloud brokers delete-personal [OPTIONS]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud brokers create
       Create a broker in project

       [1mUsage[22m:

              $ remotive cloud brokers create [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --tag TEXT: Optional specific tag/version

       • --silent / --no-silent: Do not print the response [default: no-silent]

       • --api-key TEXT: Start with your own api-key

       • --help: Show this message and exit.

   remotive cloud brokers logs
       Exposes broker logs history or real-time tail of the broker.

       When using the --tail option, --history-minutes is skipped even if  sup‐
       plied

       [1mUsage[22m:

              $ remotive cloud brokers logs [OPTIONS] BROKER_NAME

       [1mArguments[22m:

       • BROKER_NAME: Broker name to see logs for [required]

       [1mOptions[22m:

       • --tail / --no-tail: Tail the broker log [default: no-tail]

       • --history-minutes TEXT: History in minutes to fetch [default: 10]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings
       Manage recordings

       [1mUsage[22m:

              $ remotive cloud recordings [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: List all recording sessions in a project.

       • describe: Shows details about a specific recording in project

       • import: Imports a file from Storage as a recording.

       • mount:  Prepares  all recording files and transformations to be avail‐
         able for playback

       • download-recording-file: Downloads the  specified  recording  file  to
         disk

       • delete:  Deletes  the  specified recording session including all media
         files and configurations.

       • delete-recording-file: Deletes the specified recording file

       • upload: Uploads a recording to RemotiveCloud.

       • upload-broker-configuration: Uploads a broker configuration directory

       • download-broker-configuration: Downloads the specified broker configu‐
         ration directory as zip file

       • delete-broker-configuration: Delete the specified broker configuration

       • copy: Copy recording to another project

       • play: (deprecated) Plays a  recording  (Deprecated  -  Use  recordings
         playback play)

       • pause: (deprecated) Pause recording (Deprecated - Use recordings play‐
         back pause)

       • seek:  (deprecated)  Seek  into recording (Deprecated - Use recordings
         playback seek)

       • stop: (deprecated) Stop recording (Deprecated - Use  recordings  play‐
         back stop)

       • playback:  Support for playback of a recording on a cloud broker, make
         sure to always mount a recording first

   remotive cloud recordings list
       List all recording sessions in a project.  You can  choose  to  see  all
       valid recordings (default) or use --is-processing and you will get those
       that are currently being processed or that failed to be validated.

       [1mUsage[22m:

              $ remotive cloud recordings list [OPTIONS]

       [1mOptions[22m:

       • --is-processing  /  --no-is-processing:  Use  this  option to see only
         those that are being processed or are invalid [default: no-is-process‐
         ing]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings describe
       Shows details about a specific recording in project

       [1mUsage[22m:

              $ remotive cloud recordings describe [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings import
       Imports a file from Storage as a recording.

       NOTE that Storage is not yet available to all customers

       [1mUsage[22m:

              $ remotive cloud recordings import [OPTIONS] URI

       [1mArguments[22m:

       • URI: Remote storage path [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings mount
       Prepares  all  recording  files  and transformations to be available for
       playback

       [1mUsage[22m:

              $ remotive cloud recordings mount [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --ensure-broker-started  /  --no-ensure-broker-started:  Ensure broker
         exists, start otherwise [default: no-ensure-broker-started]

       • --transformation-name TEXT: Specify a custom signal transformation  to
         use [default: default]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings download-recording-file
       Downloads the specified recording file to disk

       [1mUsage[22m:

              $ remotive cloud recordings download-recording-file [OPTIONS] RECORDING_FILE_NAME

       [1mArguments[22m:

       • RECORDING_FILE_NAME: Recording file to download [required]

       [1mOptions[22m:

       • --recording-session  TEXT: Recording session id that this file belongs
         to [env var: REMOTIVE_CLOUD_RECORDING_SESSION; required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings delete
       Deletes the specified recording session including all  media  files  and
       configurations.

       [1mUsage[22m:

              $ remotive cloud recordings delete [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings delete-recording-file
       Deletes the specified recording file

       [1mUsage[22m:

              $ remotive cloud recordings delete-recording-file [OPTIONS] RECORDING_FILE_NAME

       [1mArguments[22m:

       • RECORDING_FILE_NAME: Recording file to download [required]

       [1mOptions[22m:

       • --recording-session TEXT: Recording session id that this file  belongs
         to [env var: REMOTIVE_CLOUD_RECORDING_SESSION; required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings upload
       Uploads  a recording to RemotiveCloud.  Except for recordings from Remo‐
       tiveBroker you can also upload Can ASC (.asc), Can BLF(.blf) and Can LOG
       (.log, .txt)

       [1mUsage[22m:

              $ remotive cloud recordings upload [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to recording file to upload [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --recording-session TEXT: Optional existing recording to  upload  file
         to

       • --help: Show this message and exit.

   remotive cloud recordings upload-broker-configuration
       Uploads a broker configuration directory

       [1mUsage[22m:

              $ remotive cloud recordings upload-broker-configuration [OPTIONS] DIRECTORY

       [1mArguments[22m:

       • DIRECTORY: Directory to upload [required]

       [1mOptions[22m:

       • --recording-session   TEXT:  Recording  session  id  [env  var:  REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --overwrite / --no-overwrite: Overwrite existing configuration  if  it
         exists [default: no-overwrite]

       • --help: Show this message and exit.

   remotive cloud recordings download-broker-configuration
       Downloads the specified broker configuration directory as zip file

       [1mUsage[22m:

              $ remotive cloud recordings download-broker-configuration [OPTIONS] BROKER_CONFIG_NAME

       [1mArguments[22m:

       • BROKER_CONFIG_NAME: Broker config name [required]

       [1mOptions[22m:

       • --recording-session   TEXT:  Recording  session  id  [env  var:  REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings delete-broker-configuration
       Delete the specified broker configuration

       [1mUsage[22m:

              $ remotive cloud recordings delete-broker-configuration [OPTIONS] BROKER_CONFIG_NAME

       [1mArguments[22m:

       • BROKER_CONFIG_NAME: Broker config name [required]

       [1mOptions[22m:

       • --recording-session  TEXT:  Recording  session  id  [env  var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings copy
       Copy recording to another project

       [1mUsage[22m:

              $ remotive cloud recordings copy [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION: Recording session id [required]

       [1mOptions[22m:

       • --from-project TEXT: Source project [required]

       • --to-project TEXT: Destination project [required]

       • --help: Show this message and exit.

   remotive cloud recordings play
       Plays a recording (Deprecated - Use recordings playback play)

       [1mUsage[22m:

              $ remotive cloud recordings play [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings pause
       Pause recording (Deprecated - Use recordings playback pause)

       [1mUsage[22m:

              $ remotive cloud recordings pause [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings seek
       Seek into recording (Deprecated - Use recordings playback seek)

       [1mUsage[22m:

              $ remotive cloud recordings seek [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --seconds INTEGER RANGE: Target offset in seconds [x>=0; required]

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings stop
       Stop recording (Deprecated - Use recordings playback stop)

       [1mUsage[22m:

              $ remotive cloud recordings stop [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings playback
       Support  for playback of a recording on a cloud broker, make sure to al‐
       ways mount a recording first

       [1mUsage[22m:

              $ remotive cloud recordings playback [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • play: Start playing a recording.

       • pause: Pause a recording

       • progress: Shows progress of the recording playing.

       • seek: Seek seconds into a recording

       • stop: Stop playing

       • subscribe: Allows you to subscribe  to  signals  based  on  a  mounted
         recording without knowing the broker URL.

   remotive cloud recordings playback play
       Start  playing  a recording.  There is no problem invoking play multiple
       times since if it is already playing the command will be  ignored.   Use
       --repeat to have the recording replayed when it reaches the end.

       [1mUsage[22m:

              $ remotive cloud recordings playback play [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --show-progress /  --no-show-progress:  Show  progress  after  started
         playing [default: no-show-progress]

       • --repeat  /  --no-repeat: Repeat recording - must keep command running
         in terminal [default: no-repeat]

       • --help: Show this message and exit.

   remotive cloud recordings playback pause
       Pause a recording

       [1mUsage[22m:

              $ remotive cloud recordings playback pause [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings playback progress
       Shows  progress  of  the  recording  playing.   Use --repeat to have the
       recording replayed when it reaches the end.

       [1mUsage[22m:

              $ remotive cloud recordings playback progress [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings playback seek
       Seek seconds into a recording

       [1mUsage[22m:

              $ remotive cloud recordings playback seek [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --seconds INTEGER RANGE: Target offset in seconds [x>=0; required]

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings playback stop
       Stop playing

       [1mUsage[22m:

              $ remotive cloud recordings playback stop [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:   Recording   session   id    [env    var:    REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud recordings playback subscribe
       Allows  you to subscribe to signals based on a mounted recording without
       knowing the broker URL.  This simplifies when  playing  recordings  from
       the cloud.

       Terminal plotting is not yet supported here so we refer to remotive bro‐
       ker signals subscribe --x-plot for this.

       [1mUsage[22m:

              $ remotive cloud recordings playback subscribe [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION:    Recording    session    id   [env   var:   REMO‐
         TIVE_CLOUD_RECORDING_SESSION; required]

       [1mOptions[22m:

       • --broker TEXT: Broker to use

       • --signal NAMESPACE:SIGNAL_NAME: Signal(s) to subscribe to

       • --script FILE: Supply a path to a Lua script to use for signal  trans‐
         formation

       • --on-change-only  /  --no-on-change-only:  Only get signal if value is
         changed [default: no-on-change-only]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud signal-databases
       Manage signal databases

       [1mUsage[22m:

              $ remotive cloud signal-databases [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: List available signal databases in project

       • delete: Deletes the specified signal database

       • upload: Uploads signal database to project

       • describe: Shows all metadata related to this signal database

       • download: Downloads the specified signal database to disk

   remotive cloud signal-databases list
       List available signal databases in project

       [1mUsage[22m:

              $ remotive cloud signal-databases list [OPTIONS]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud signal-databases delete
       Deletes the specified signal database

       [1mUsage[22m:

              $ remotive cloud signal-databases delete [OPTIONS] [SIGNAL_DB_FILE]

       [1mArguments[22m:

       • [SIGNAL_DB_FILE]: Signal database file

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud signal-databases upload
       Uploads signal database to project

       [1mUsage[22m:

              $ remotive cloud signal-databases upload [OPTIONS] PATH

       [1mArguments[22m:

       • PATH: Path to signal database file to upload [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud signal-databases describe
       Shows all metadata related to this signal database

       [1mUsage[22m:

              $ remotive cloud signal-databases describe [OPTIONS] [SIGNAL_DB_FILE]

       [1mArguments[22m:

       • [SIGNAL_DB_FILE]: Signal database file

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud signal-databases download
       Downloads the specified signal database to disk

       [1mUsage[22m:

              $ remotive cloud signal-databases download [OPTIONS] [SIGNAL_DB_FILE]

       [1mArguments[22m:

       • [SIGNAL_DB_FILE]: Signal database file

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud storage
       Manage files (Beta feature not available for all customers)

       Copy file from local to remote storage and vice versa, list  and  delete
       files.

       [1mUsage[22m:

              $ remotive cloud storage [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • ls: Listing remote files

       • rm: Deletes a file from remote storage, this cannot be undone

       • cp: Copies a file to or from remote storage

   remotive cloud storage ls
       Listing remote files

       This  will list files and directories in project top level directory re‐
       motive cloud storage ls rcs://

       This will list all files and  directories  matching  the  path  remotive
       cloud storage ls rcs://fileOrDirectoryPrefix

       This  will list all files and directories in the specified directory re‐
       motive cloud storage ls rcs://fileOrDirectory/

       [1mUsage[22m:

              $ remotive cloud storage ls [OPTIONS] [URI]

       [1mArguments[22m:

       • [URI]: Remote storage path [default: rcs://]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud storage rm
       Deletes a file from remote storage, this cannot be undone

       remotive cloud storage rm rcs://directory/filename

       [1mUsage[22m:

              $ remotive cloud storage rm [OPTIONS] URI

       [1mArguments[22m:

       • URI: Remote storage path [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud storage cp
       Copies a file to or from remote storage

       remotive cloud storage cp rcs://dir/filename .  remotive  cloud  storage
       cp rcs://dir/filename filename

       remotive  cloud storage cp filename rcs://dir/ remotive cloud storage cp
       filename rcs://dir/filename

       [1mUsage[22m:

              $ remotive cloud storage cp [OPTIONS] SOURCE DEST

       [1mArguments[22m:

       • SOURCE: Remote or local path to source file [required]

       • DEST: Remote or local path to destination file [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --overwrite / --no-overwrite: Overwrite existing file on RCS [default:
         no-overwrite]

       • --help: Show this message and exit.

   remotive cloud samples
       Manage sample recordings

       [1mUsage[22m:

              $ remotive cloud samples [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • import: Import sample recording into project

       • list: List available sample recordings

   remotive cloud samples import
       Import sample recording into project

       [1mUsage[22m:

              $ remotive cloud samples import [OPTIONS] RECORDING_SESSION

       [1mArguments[22m:

       • RECORDING_SESSION: Recording session id [required]

       [1mOptions[22m:

       • --project TEXT: Project to import sample recording into [env var:  RE‐
         MOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive cloud samples list
       List available sample recordings

       [1mUsage[22m:

              $ remotive cloud samples list [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive auth
       Sign  in  to RemotiveCloud and manage accounts, the default organization
       and service accounts

       Every command that talks to RemotiveCloud (cloud, topology, broker, stu‐
       dio, connect) uses the signed-in account, so this is where to start.

       Get started:

       remotive auth login sign in with your browser remotive auth whoami  show
       who  you are signed in as remotive auth organization set --it choose the
       default organization

       How it works:

       • Credentials are saved under ~/.config/remotive.  Several accounts  can
         be saved and one is active; 'list', 'activate' and 'deactivate' switch
         between them.

       • Service  accounts  belong  to a project and are meant for CI and other
         automation: create one  and  a  token  with  'service-accounts  create
         --it'.

       • In  CI,  where  no one can sign in, set REMOTIVE_CLOUD_AUTH_TOKEN to a
         service-account token instead, and REMOTIVE_CLOUD_ORGANIZATION and RE‐
         MOTIVE_CLOUD_PROJECT to the organization and project.   Locally  there
         is no need for them: sign in instead.

       • In  a  virtual  machine or over ssh, where no browser can open, 'login
         --no-browser' prints a link to open in any browser instead.

       'remotive setup' goes through sign-in, the default organization and  the
       rest of the tool chain step by step.

       [1mUsage[22m:

              $ remotive auth [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • login: Sign in to RemotiveCloud in your browser and save the account

       • whoami:  Show  the signed-in account, after checking the token against
         RemotiveCloud

       • print-access-token: Print the access token of the active  account,  or
         of --account, for scripts and tools

       • deactivate: Sign out of the active account; its saved credentials stay
         for 'activate'

       • activate:  Make  a saved account the active one, by name or by picking
         from a list

       • list: List the saved accounts and which one is active

       • organization: Show or set the default organization of an account

       • service-accounts: Manage project service accounts and their access to‐
         kens

   remotive auth login
       Sign in to RemotiveCloud in your browser and save the account

       Opens the sign-in page in your browser and saves  the  credentials  once
       you are signed in.  Where no browser can open, such as in docker, a vir‐
       tual  machine or an ssh session, it falls back to a link you open in any
       browser; --no-browser goes straight to the link.

       [1mUsage[22m:

              $ remotive auth login [OPTIONS]

       [1mOptions[22m:

       • --browser / --no-browser: Does not automatically open browser, instead
         shows a link [default: browser]

       • --help: Show this message and exit.

   remotive auth whoami
       Show the signed-in account, after checking the token  against  Remotive‐
       Cloud

       [1mUsage[22m:

              $ remotive auth whoami [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive auth print-access-token
       Print  the  access  token  of  the  active account, or of --account, for
       scripts and tools

       [1mUsage[22m:

              $ remotive auth print-access-token [OPTIONS]

       [1mOptions[22m:

       • --account TEXT: Email of the account you want to  print  access  token
         for, defaults to active

       • --help: Show this message and exit.

   remotive auth deactivate
       Sign  out  of  the active account; its saved credentials stay for 'acti‐
       vate'

       [1mUsage[22m:

              $ remotive auth deactivate [OPTIONS]

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive auth activate
       Make a saved account the active one, by name or by picking from a list

       [1mUsage[22m:

              $ remotive auth activate [OPTIONS] [TOKEN_NAME]

       [1mArguments[22m:

       • [TOKEN_NAME]: Name, filename or path to a credentials file

       [1mOptions[22m:

       • --help: Show this message and exit.

   remotive auth list
       List the saved accounts and which one is active

       Shows #, Active, Type, Token, Account,  Organization,  Created  and  Ex‐
       pires.   Use  --short for a compact view with only Active, Type, Account
       and Organization.

       [1mUsage[22m:

              $ remotive auth list [OPTIONS]

       [1mOptions[22m:

       • --short: Compact view: Active, Type, Account, Organization

       • --help: Show this message and exit.

   remotive auth organization
       Show or set the default organization of an account

       [1mUsage[22m:

              $ remotive auth organization [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • print: Print the default organization

       • set: Set the default organization, by uid or interactively with --it

   remotive auth organization print
       Print the default organization

       [1mUsage[22m:

              $ remotive auth organization print [OPTIONS]

       [1mOptions[22m:

       • --account TEXT: Account to print for; defaults to the active account

       • --help: Show this message and exit.

   remotive auth organization set
       Set the default organization, by uid or interactively with --it

       [1mUsage[22m:

              $ remotive auth organization set [OPTIONS] [ORGANIZATION_UID]

       [1mArguments[22m:

       • [ORGANIZATION_UID]: Organization uid

       [1mOptions[22m:

       • --it: Select interactively from available organizations

       • --account TEXT: Account to set for; defaults to  the  active  account.
         Interactive selection always uses the active account.

       • --help: Show this message and exit.

   remotive auth service-accounts
       Manage project service accounts and their access tokens

       [1mUsage[22m:

              $ remotive auth service-accounts [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • list: List service-accounts

       • create: Create a new service account with one or more roles.

       • update: Update an existing service account with one or more roles.

       • delete: Delete service account

       • tokens: Manage project service account access tokens

   remotive auth service-accounts list
       List service-accounts

       [1mUsage[22m:

              $ remotive auth service-accounts list [OPTIONS]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts create
       Create a new service account with one or more roles.

       Must only use lowercase letters, digits, or dashes, and must not contain
       -- or end with a dash.

       remotive  auth  service-accounts  create NAME --role project/user --role
       project/storageCreator

       Add --it to be guided step by step - project, name, roles - access token
       included:

       remotive auth service-accounts create --it

       Supported roles project/admin - Full project support, view, edit, delete
       and manage users project/user - View, edit, upload, delete but no  admin
       project/viewer  - View only project/storageCreator - Can upload to stor‐
       age but not view, overwrite or delete org/topologyRunner - Can start Re‐
       motiveTopology org/studioRunner - Can start RemotiveStudio

       [1mUsage[22m:

              $ remotive auth service-accounts create [OPTIONS] [NAME]

       [1mArguments[22m:

       • [NAME]: Service account name (required without --it)

       [1mOptions[22m:

       • --role TEXT: Roles to apply (required without --it)

       • --project TEXT: Project ID (required without  --it)  [env  var:  REMO‐
         TIVE_CLOUD_PROJECT]

       • --it:  Create it step by step, access token included; asks for what is
         left out

       • --help: Show this message and exit.

   remotive auth service-accounts update
       Update an existing service account with one or more roles.

       remotive  auth  service-accounts  update  --role   project/user   --role
       project/storageCreator

       Supported roles project/admin - Full project support, view, edit, delete
       and  manage users project/user - View, edit, upload, delete but no admin
       project/viewer - View only project/storageCreator - Can upload to  stor‐
       age but not view, overwrite or delete org/topologyRunner - Can start Re‐
       motiveTopology org/studioRunner - Can start RemotiveStudio

       [1mUsage[22m:

              $ remotive auth service-accounts update [OPTIONS] SERVICE_ACCOUNT

       [1mArguments[22m:

       • SERVICE_ACCOUNT: Service account name [required]

       [1mOptions[22m:

       • --role TEXT: Roles to apply [required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts delete
       Delete service account

       [1mUsage[22m:

              $ remotive auth service-accounts delete [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: [required]

       [1mOptions[22m:

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts tokens
       Manage project service account access tokens

       [1mUsage[22m:

              $ remotive auth service-accounts tokens [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • create: Create and download a new service account access token

       • list: List service account access tokens

       • describe: Describe service account access token

       • revoke: Revoke service account access token

   remotive auth service-accounts tokens create
       Create and download a new service account access token

       [1mUsage[22m:

              $ remotive auth service-accounts tokens create [OPTIONS]

       [1mOptions[22m:

       • --expire-in-days INTEGER: Number of days this token is valid [default:
         365]

       • --service-account TEXT: Service account name [required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts tokens list
       List service account access tokens

       [1mUsage[22m:

              $ remotive auth service-accounts tokens list [OPTIONS]

       [1mOptions[22m:

       • --service-account TEXT: Service account name [required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts tokens describe
       Describe service account access token

       [1mUsage[22m:

              $ remotive auth service-accounts tokens describe [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: Access token name [required]

       [1mOptions[22m:

       • --service-account TEXT: Service account name [required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive auth service-accounts tokens revoke
       Revoke service account access token

       [1mUsage[22m:

              $ remotive auth service-accounts tokens revoke [OPTIONS] NAME

       [1mArguments[22m:

       • NAME: Access token name [required]

       [1mOptions[22m:

       • --delete  /  --no-delete: Also deletes the token after revocation [de‐
         fault: delete]

       • --service-account TEXT: Service account name [required]

       • --project TEXT: Project ID [env var: REMOTIVE_CLOUD_PROJECT; required]

       • --help: Show this message and exit.

   remotive connect
       Integrations with other systems

       [1mUsage[22m:

              $ remotive connect [OPTIONS] [COMMAND] [ARGS]...

       [1mOptions[22m:

       • --help: Show this message and exit.

       [1mCommands[22m:

       • protopie: ProtoPie Connect bridge-app to connect  signals  with  Remo‐
         tiveBroker

   remotive connect protopie
       ProtoPie Connect bridge-app to connect signals with RemotiveBroker

       Subscribe to signals and send signal values to your Pie in a simple way.
       You  can  subscribe  to  signals from command line using --signal or use
       --config to use a json configuration file.

              $ remotive connect protopie --signal vss:Vehicle.Chassis.SteeringWheel.Angle --signal vss:Vehicle.Speed

       You can use a configuration file for this if you have many signals, want
       to share the configuration or you want  custom  mapping  of  the  signal
       name.

              $ remotive connect protopie --config my-protopie-config.json

       Sample my-protopie-config.json

              {
                &quot;subscription&quot;: {
                  &quot;Vehicle.CurrentLocation.Heading&quot;: {
                    &quot;namespace&quot;: &quot;vss&quot;
                  },
                  &quot;Vehicle.Speed&quot;: {
                    &quot;namespace&quot;: &quot;vss&quot;,
                     &quot;mapTo&quot;: [&quot;Speed&quot;, &quot;VehicleSpeed&quot;]
                  }
                }
              }

       For  simple  changes to signal names its possible to use a simple string
       expression that will be applied to all signal names before its published
       to ProtoPie connect, i.e replacing chars or substring to match variables
       in Pie.  This is intended for simple use cases when you do  not  have  a
       configuration  file, otherwise we recommend using the mapTo field in the
       configuration.

       Supported transformations: lower(), upper(), replace("old", "new")

       This will replace all occurrences of .  (dot) with  _  (underscore)  and
       lowercase the signal name

              $ remotive connect protopie --signal vss:Vehicle.Chassis.SteeringWheel.Angle --signal-name-expression &#x27;replace(&quot;.&quot;, &quot;_&quot;).lower()&#x27;

       [1mUsage[22m:

              $ remotive connect protopie [OPTIONS]

       [1mOptions[22m:

       • --config  FILE:  Configuration file with signal subscriptions and map‐
         ping if needed

       • --signal TEXT: Signal names to subscribe to, mandatory when not  using
         script

       • --signal-name-expression TEXT: [Experimental] String expression to re‐
         name signal names, i.e 'lower().replace(".","_")'

       • --changed-values-only  / --no-changed-values-only: Only receive signal
         when its value is changed to minimize amount  of  data  received  [de‐
         fault: changed-values-only]

       • --broker-url  TEXT: Broker URL [env var: REMOTIVE_BROKER_URL; default:
         http://localhost:50051]

       • --api-key TEXT: Cloud Broker API-KEY or access token [env  var:  REMO‐
         TIVE_BROKER_API_KEY]

       • --pp-connect-host  TEXT:  ProtoPie Connect URL [default: http://local‐
         host:9981]

       • --help: Show this message and exit.

RemotiveCLI 0.45.1                 2026-11-04                       [4mREMOTIVE[24m(1)
