pickfit

BrowseDeveloper CLIs

lox

Scriptable CLI for Loxone Miniserver to monitor and control smart-home devices.

Use it

Before you install: known vulnerabilities

pickfit found 9 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:zip 2.4.2 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • crates:quick-xml 0.37.5 Quadratic run time when checking a start tag for duplicate attribute names (RUSTSEC-2026-0194, high, fixed in 0.41.0)
See 7 more

Linux x86_64

You need first

  • Needs the network
  1. Download lox Linux binary to PATH

    mkdir -p ~/.local/bin && curl -fsSL -o ~/.local/bin/lox https://github.com/discostu105/lox/releases/download/v0.29.0/lox-linux-x86_64 && chmod +x ~/.local/bin/lox && curl -fsSL https://github.com/discostu105/lox/releases/download/v0.29.0/lox-linux-x86_64.sha256 | cat && sha256sum ~/.local/bin/lox
Where the README and reality differ
  • README: lox config init ~/loxone-config as one-time setup
    What worked: lox setup set --host/--user/--pass (or LOX_PASS) is required before lox config init

Check that it works

lox --version

The output should contain “lox 0.29.0”.

First thing to try

lox completions bash

Run lox completions bash to set up shell completion, then use lox to list commands.

What it does

  • Control lights, blinds and thermostats
    Not tested
  • Monitor your house in a live terminal view
    Not tested
  • Keep Miniserver config versions in a git repository
    Not tested
  • Let AI agents use your smart home through MCP
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • turn off all lights when leaving
  • show energy meters overview
  • close blinds conditionally on temperature
  • list light controllers as JSON
  • stream real-time state changes as JSON

An alternative to eisber/lox-cli.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.29.0

Differences the test machine hit

  • README: cargo build --release or brew install discostu105/lox/lox
    In the test: downloaded prebuilt lox-linux-x86_64 v0.29.0 from GitHub releases to ~/.local/bin/lox and verified sha256 matched
  • README: lox tui --demo try it without a Miniserver
    In the test: lox tui --demo aborts when stdin/stdout are not a TTY

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.