Repository navigation
Havne 0.8.0 lets a log or a warning start from the car's own state: conditions judged in a session, alerts in the app (a banner, colored values and, on Android, a tone), armed recording that writes a window when a condition fires, one plugin store for every import, and computed signals with functions, comparisons and chains. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.8.0-windows-x64.zip |
| Linux (x86_64), the app | havne-0.8.0-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.8.0-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.8.0-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.8.0_amd64.deb (Debian, Ubuntu) or havne-core-0.8.0-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.8.0_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.8.0-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.8.0-py3-none-<platform>.whl; Python 3.11 or later |
The other files under Assets check a download or debug one: SHA256SUMS.txt, the build provenance (.intoto.jsonl) and the SBOM (.spdx.json), described below under Verifying the downloads; the Windows PDBs (-symbols.zip) and havne-cli's Linux debug info (-dbgsym deb, -debug tarball). The AppImage runtime's sources, fuse-3.15.0.tar.xz and type2-runtime-20251108.tar.gz, are there as LGPL-2.1 asks: the runtime links libfuse statically (the AppImage's notice says more). GitHub adds the source code archives.
Try it
Windows
- Download
havne-0.8.0-windows-x64.zipand unzip the whole folder. - Run
havne.exe. The program isn't code-signed, so SmartScreen may stop it the first time: choose More info, then Run anyway. - Press Demo data on Home, then Connect.
The zip's README.txt covers adapters and what each file is. havne-cli.exe is beside havne.exe: havne-cli stream mock://demo --values --count 20 prints a simulated car's frames and values.
Linux (x86_64 or 64-bit ARM, glibc 2.39 or later: Ubuntu 24.04 and newer, Debian 13 and Raspberry Pi OS 13, Fedora 40 and newer, Arch)
- Download
havne-0.8.0-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.8.0-linux-aarch64.AppImage. chmod +xit, then run it.- Press Demo data on Home, then Connect.
It takes OpenGL, fonts and FUSE from the system; a minimal install may lack them. docs/linux.md says what to install, how to reach an adapter (serial permissions, Bluetooth, SocketCAN) and where Havne keeps its files.
For havne-cli and the core alone: sudo apt install ./havne-core_0.8.0_amd64.deb (./havne-core_0.8.0_arm64.deb on ARM), or unpack havne-core-0.8.0-linux-x86_64.tar.gz (havne-core-0.8.0-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.8.0-android-arm64-v8a.apkand open it. Android asks to let your browser or file manager install apps the first time; Play Protect may offer to scan an app from outside Google Play. - Open Havne. On Dash, press the Demo data row, then Connect.
A later release installs over this one and keeps its settings and recordings. A Havne built by CI or from source carries another key, so uninstall it first.
What's new since 0.7.4
Conditions and alerts
- A condition file is a set of named tests of a session: a signal above or below a level (with hysteresis and a hold), the link's state, or one of the frames check's findings, joined by
allorany, each marked for an alert, a recording or a marker. Conditions are judged on the frames' own time, so the same recording replayed gives the same events at any speed, and one whose input has gone stale says so (docs/condition-files.md, ADR-0063). - Settings, Alerts adds, edits, switches off and removes alerts on the session's signals and its link, with levels typed in your units, and imports and exports a condition file. A gauge's panel makes an alert from its own danger or warning levels.
- A banner under the header on every page, and over the gauges in the drive view, shows the highest alert with the value it fired at; a gauge or Live value an alert reads takes the alert's color. On Android an alert can play a short tone (one beep for a warning, two for a danger) at the alarm volume, so it sounds with the phone on silent.
- Armed recording: the Armed button beside Start log (and in the drive view) records nothing until a condition set to record fires, then writes a folder for each window, from the condition's
beforeto itsafter.havne-cli log --conditions <file> --armedand Python'sRecorder(armed=True)do the same. - A recording keeps its session's conditions, and the viewer draws each time one was ON as a bar along the chart's foot, with a Conditions... list beside Stretches... that moves the view to one.
havne-cli conditions checksays what a condition file holds and why it is refused,havne-cli stream --conditionswrites a line at each change, and Python hasConditionSet,Session.set_conditions()andRecordedConditions.schema/condition-file.schema.jsonis the format's JSON Schema.
One plugin store
- Settings, Signals is one list of plugins: every signal set on the device is a plugin there, each variant a row a press picks for the vehicle, and the vehicle's own plugins come first under "For this car:". One Import... takes a plugin package, a signal file (as a new plugin or into one of your own) or an OBDb set (ADR-0064).
- At the first start after the update, the vehicles' signal files move into the store, each as a plugin of your own picked for the vehicles that had it; one that could not move is listed with why. Add a signal saves into the vehicle's own plugin, and renaming a signal keeps the Dashboard gauges and layouts that show it.
- More on a row saves a variant as a signal file, exports a plugin, copies it to your own, or marks an imported one as yours so a newer export updates it in place.
havne-cli plugins wrap,putanddropand Python'sPlugin.wrapmake and change packed plugins.
Signals and requests
- Signal files in format 2 compute with functions, comparisons and a conditional, give a stale input as no value, and read other computed signals up to 8 deep, as
examples/boost-ratio.jsondoes (ADR-0062). - A set may derive up to 1024 requests, so an OBDb import of a whole car's set keeps its signals. The app asks a session's ranked signals, the Dashboard's gauges and the rows ticked on Live, not every signal of a large set; the rest read "Not asked" until a tick asks them (ADR-0051, ADR-0056).
- A connected car is recognized as soon as it answers its VIN. The minimum time between sweeps paces Live and the Dashboard too, and J2534 sessions pace their requests by the replies.
- The Log page is now Activity, so "log" names only a recording.
Fixes
- On Android, a save that fails or is refused leaves nothing behind and never removes a document you chose to replace; a CSV save can replace a CSV file.
- Opening a recording with a long events log can be canceled at once, and a rare crash in Qt 6.12's step-by-step script memory cleanup is avoided.
havne-cliexits 1 when it can't write a refusal. The full list is in the CHANGELOG.
What's verified, and where
Havne's claims are tiered (docs/testing.md):
- Every build runs the full test suite on Windows, macOS and Linux in CI, plus sanitizers, fuzzing, clang-tidy, CodeQL and the load test; a GCC or Clang warning fails it. Dev's CI run 43783701411 passed on this release's tree, and the release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2711 of 2711 tests; the skipped cases are the ones gated on what a Windows machine lacks (Linux, Wireshark's
tshark, the car's raw recordings) or that the cross-arch step runs, and the cross-arch (x86) step passed 111 of 111. - Conditions have run against the simulated car (
mock://) and recordings only; the tests check that a recording's replay gives the events it recorded. - On a phone: a development build on the test phone (Android 16) under
mock://demo: the store's migration of the phone's settings and plugin, the one list on Settings, Signals and an OBDb import, the Activity page, the four looks, Export layout; three alerts firing in Activity, their band in the drive view and on Live with colored values, the Alerts page, the tone on a danger alert, and Armed writing two windows that the viewer opened with their conditions. The release APK of v0.8.0-rc1 then ran on the test phone: it installed over the development build, connected tomock://demoand showed its values. - On a car: nothing new in 0.8.0 has run on a car.
- Not yet run: the published downloads haven't connected to an adapter or a car, and the iPhone app has not run on a device.
Verifying the downloads
SHA256SUMS.txt holds every download's SHA-256, the debug files' and the SBOM's. One signed build provenance from this repository's release workflow covers every download, attached as havne-0.8.0.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.8.0-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.8.0-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.8.0-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.8.0_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.8.0-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.8.0.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.8.0.spdx.json, is attested to the zip, the APK, the AppImages, the debs, the tarballs and the wheels: add --predicate-type https://spdx.dev/Document/v2.3 to check it.
The APK is signed with Havne's release key, whose certificate SHA-256 is fb4f415a1f6c0dc56ee54dcd454c29d2226bc293c7b4c978a9b9bc8e74c4210f (packaging/android/release-cert.sha256). With the Android SDK's build tools, apksigner verify --print-certs havne-0.8.0-android-arm64-v8a.apk prints it.
Third-party data
Havne's core carries data from others, each under its own terms, listed in core/THIRD_PARTY_NOTICES.txt, which core's packages ship and every download's notice repeats, and compiled into every binary:
- Trouble-code titles: SAE J2012's generic powertrain and network codes, from Wal33D/dtc-database (MIT).
- Vehicle makes: the manufacturer codes of NHTSA's vPIC, a work of the US government.