Repository navigation
Linux
Readout.Linux runs the same app on Linux, on Microsoft's GTK4 backend for .NET MAUI
(dotnet/maui-labs, a
preview). It compiles the app's own pages and code; only the Bluetooth connection and a few
fixes for gaps in the preview backend are Linux's own. Bluetooth goes through BlueZ over
D-Bus. The MCP server for AI assistants works there too.
On Debian 13 (trixie) or Fedora, install it from packages.alejandro.md:
curl -fsSL https://packages.alejandro.md/setup.sh | sudo shsudo apt install readout(sudo dnf install readout on Fedora.) The package puts the app in /usr/lib/readout,
readout on the path and an entry in the app menu, and pulls in GTK 4 and BlueZ. Debian 12
(bookworm) has GTK 4.8, older than the 4.12 the backend needs, so the repository has no
Readout for it.
Elsewhere, get a tarball from the GitHub releases
(or build one with ./publish-linux.sh), unpack it and start readout/Readout. It's
self-contained (no .NET install); the machine needs GTK 4.12 or later (libgtk-4-1), ICU and
OpenSSL 3. The packages come from the same build through ./package-linux.sh.
For the meter, BlueZ has to be running with a powered Bluetooth LE adapter
(sudo systemctl enable --now bluetooth). BlueZ's default policy lets any local user scan
and connect, so nothing needs root or the bluetooth group.
READOUT_FAKE_BLE=1 uses the simulated meter, and Try the demo meter works as everywhere
else.
- Tabs sit at the top, and pages pushed on top of a tab get a back button in the title bar.
- Graphs zoom with the mouse wheel (or a touchpad), pan by dragging, and reset on a double-click.
- Export CSV opens a save dialog instead of a share sheet.
- BlueZ reports a meter's signal strength only while scanning, so once connected the signal bars show the strength from the scan and hide after 30 seconds without a new one.
- No continuity beep or vibration yet (as on Windows). Alert boxes show no title.
A real 121GW on Fedora 43 (KDE on Wayland, GTK 4.20, BlueZ 5.87): it found the meter, connected in about 2 seconds, showed live readings and the graph, sent short and long key presses, followed dial changes, and reconnected by itself when the meter's Bluetooth came back.
tools/linux-test/ runs the app in Docker (Ubuntu 24.04, GTK 4.14, Xvfb) with the simulated
meter, or against mock-bluez.py, a stand-in for BlueZ that plays a 121GW. Docker's VM has no
Bluetooth, so this is how the BlueZ code gets tried without a meter.
docker build -t readout-linux-test tools/linux-testdotnet publish Readout.Linux -c Release -r linux-arm64 --self-contained -o <dir> -p:DebugType=nonedocker run -d --name ro -v <dir>:/app -v <out>:/out readout-linux-test <mode>Use linux-x64 on an x86 machine. The modes are fake (the simulated meter), mock (the
BlueZ code against mock-bluez.py) and none (no system bus). The app's log is
<out>/app.log. Pass -e SCREEN=1280x800x24 to try a small screen.
Developing
Platforms
Reference (in the repo)