Skip to main content

Health Check & Setup Verification

The :LovelaceHealth command is the fastest way to confirm the Neovim extension can talk to the Lattice daemon and that this client is paired/trusted.

Running the Health Check

vim
:LovelaceHealth

Expected Output

When everything is working, you'll see:

## Connection Status

✓ Connected to Lattice daemon
  Socket: ~/.lovelace/lattice/daemon.sock

## Ping

✓ pong

## Pairing / Trust

✓ Device is set up

If the device is not paired yet:

## Pairing / Trust

✗ Device not set up
To pair this Neovim client:
  :LovelaceAuth

Common Scenarios

Daemon Not Running

Start the daemon:

bash
lattice-ctl daemon start
lattice-ctl daemon status

Then re-run:

vim
:LovelaceHealth

Socket Path Issues

The plugin discovers the socket path in this order:

  1. daemon.socket_path (plugin config)
  2. LATTICE_SOCKET
  3. LATTICE_SOCKET_PATH
  4. LOVELACE_SOCKET_PATH (compat with other tooling)
  5. ~/.lovelace/lattice/daemon.sock
  6. /tmp/lovelace-daemon.sock

To override:

lua
require("lovelace").setup({
  daemon = {
    socket_path = "/custom/path/to/daemon.sock"
  }
})

Socket Permissions

If you see permission errors:

bash
ls -la ~/.lovelace/lattice/daemon.sock

Enable Debug Logging

lua
require("lovelace").setup({
  log_level = "debug"
})

Then check:

vim
:messages

Auto-Start Configuration

By default, the extension will attempt to start the daemon if it cannot find a socket:

  • Command: lattice-ctl daemon start
  • Follow-up: it retries connection and verifies readiness via ping

To disable auto-start:

lua
require("lovelace").setup({
  daemon = {
    auto_start = false
  }
})

Troubleshooting Workflow

  1. Run:

    vim
    :LovelaceHealth

  2. If disconnected:

    bash
    lattice-ctl daemon start
lattice-ctl daemon status

  3. Re-run:

    vim
    :LovelaceHealth

  4. If not set up:

    vim
    :LovelaceAuth

Next Steps