Repository navigation
Releases
lanowl 0.4.0
The owl reads less and says each thing once. A device's routine log lines stop reaching it, a
scheduled audit with nothing new is skipped, and a log line that keeps coming back is told with
its count. Unsaved Settings survive a reload. One default changed: see Upgrade.
What's new
- Routine log lines are learned. Once the owl has said "nothing worth telling" about the same
kind of line three times, lines like it are no longer sent to it, and with nothing else new no
model call is made. A line lanowl tags (a login, a link, storage…) is never learned, a burst is
read again, and a line unseen for 30 days is forgotten. A device's sheet lists them, each with
Forget.devwatch.routinesets it.
Device kinds. - A log line that recurs is told with its count. lanowl keeps 30 days of each tagged line per
device. The owl still judges every new line on its own, so nothing goes untold because it
recurs; when it tells one, it says "again", on how many days and at which usual hours: in full
the first time, then in one sentence. In the digest a device's log note sits under its open
issue instead of being told twice. - A scheduled audit with nothing new is skipped. When the owl would be told exactly what the
last audit was told, that audit's words stand and the Now card says when it was checked again.
At least one audit a day runs; Audit now and an incident always run one.
cadence.llm_when_unchanged: trueruns every one, as before.
config.yaml. - The Now tab reads "All answering · 2 to decide" when every device answers but something
waits under Needs you. The week's drops are one line under the headline instead of on every
group tile. Ask opens on a new chat after a day, with questions made from what the dashboard
shows. - Unsaved settings stay. A device's settings with unsaved changes no longer close on a click
beside the sheet, Escape or a swipe down, and every Settings form keeps its unsaved changes in
the browser tab across a reload (never a password or a token).
Settings. - A Linux device's backup paths in its form. Once
backupis ticked, the device form has a
backup: pathsfield. A path that starts with-, or an ESXi VM name with anything but letters,
digits,.,_and-, is refused when it is saved and again before a backup runs.
Devices. - Fixed:
- the internet watcher could not read a backup router whose login is named in the inventory
(credentials:): every outage said it had no login; - a service that answers again says so, instead of reading as the device coming back;
- a new critical found during a scheduled audit gets that audit's diagnosis, and the digest no
longer repeats it at once; - an
httpcheck'spathwith a scheme, spaces or control characters is refused; - the Devices tab's Services follow the chosen site, a duration of 3 h 59.5 min reads "4h00",
and the internet drawer gives the paging floor exactly.
- the internet watcher could not read a backup router whose login is named in the inventory
Upgrade
Nothing changed in docker/compose.yaml. With the updater running, Update now in Settings
does it. Without it:
docker compose -f docker/compose.yaml pull
docker compose -f docker/compose.yaml run --rm lanowl lanowl --check
docker compose -f docker/compose.yaml up -dfixesandscorecardare now off when config.yaml leaves them out, like every other optional
feature. The example sets both tofalse, so a config copied from it is unchanged; if yours has
no such lines and you used them, addfixes: {enabled: true}andscorecard: {enabled: true}.wan.criticalis gone from the example: nothing read it.
Upgrading has the rest, the shell included.
- Images, amd64 and arm64:
ghcr.io/alessandromatera/lanowl:0.4.0and
ghcr.io/alessandromatera/lanowl-sandbox:0.4.0. - On PyPI:
pip install -U lanowl.
Found a problem? Open an issue and say
what lanowl --version prints.
Documentation · AGPL-3.0
lanowl 0.3.0
lanowl now tells you when a new release is out and, if you let it, updates itself. A device's long
week and the Timeline fold to what matters, and an update that needs a reboot proposes it. Nothing
to change in your config.
What's new
- lanowl's own updates. Settings → lanowl's version and updates shows the release you run,
the latest one on GitHub and what is new in it, with Check now. lanowl asks GitHub once a
day, with nothing but its version in the request; a newer release is one line in the next
digest, once.self_update.check: falseswitches the check off.
Settings. - The updater, optional.
docker compose -f docker/compose.yaml --profile updater up -dstarts
one more container, the only one that holds Docker's socket (root on that machine). It takes
one word from lanowl, "update", and decides the rest itself: it pulls lanowl's own images,
replaces only lanowl's own containers, and keeps the new ones only if lanowl runs 3 minutes
without a restart and its dashboard answers. Otherwise the old ones come back, and Telegram
quotes the new one's last log lines. Then Update now in Settings, or Update by itself at
an hour of your choice (self_update.auto).
The updater. - Long lists fold. A device's What happened shows the newest five rows that matter;
Show all opens the whole week in place. The Timeline opens on Today, every other day is one
line with its count, and inside a day the routine log reads, where nothing needed you, are one
line of their own. Nothing is left out: a jump to a row opens what holds it. A device's
vulnerability matches sit behind a fold under the scan's verdict. - An update that needs a reboot proposes it. When an update leaves a machine asking for a
reboot, its row says "a reboot finishes them" and lanowl proposes that reboot at once, with
Approve and Reject on the dashboard and on Telegram: checked first, its alerts held while
it restarts, as any reboot. A machine lanowl cannot reboot says "reboot it yourself". - Fixed: the morning drift review stopped with an error when the week's last internet event
was an outage of the main link, and could count the main link's drops in the wrong row. - The image takes Debian's security fixes newer than its base image at build time.
Upgrade
docker/compose.yaml has the new optional updater service, so pull the repository too:
cd lanowl
git pull
docker compose -f docker/compose.yaml pull
docker compose -f docker/compose.yaml run --rm lanowl lanowl --check
docker compose -f docker/compose.yaml up -dFrom this release on, with the updater running, Settings can do it for you.
Upgrading has the rest, the shell included.
- Images, amd64 and arm64:
ghcr.io/alessandromatera/lanowl:0.3.0and
ghcr.io/alessandromatera/lanowl-sandbox:0.3.0. - On PyPI:
pip install -U lanowl.
Found a problem? Open an issue and say
what lanowl --version prints.
Documentation · AGPL-3.0
lanowl 0.2.0
The owl can now run a command of its own on a device, a Telegram reply tells it which message you
mean, and a device's log reaches your phone at once only when the device matters. Nothing to
change in your config.
What's new
- The owl runs its own command on a device. In your questions it writes a command for any
device lanowl logs in to, and any Shelly, in the device's own language: a RouterOSprint, an
ip route, a Home AssistantGET. One on the kind's read-only list runs at once. Anything
else comes to you first as a Run a command card with the exact command, Approve and
Reject on Telegram and the dashboard; the answer waits up to 5 minutes and gets the output.
Rejected, unanswered or stopped: nothing ran, and nothing can run it later. What comes back is
masked (passwords, keys, tokens, password hashes). Withactions.enabled: falseonly the
read-only list runs. What the owl can run. - Reply to any message on Telegram and the owl gets that message with your question, and the
part you selected: "why?" under an alert is about that alert, and lanowl adds whether its
incident is still open and what became of the proposals on it. - A short reply answers the owl's question. An "Ok" to the question its last answer ended
with now does what it offered, instead of ending the topic. - Device logs follow the device's priority. A note from a device's own log comes at once
only from acriticality: criticaldevice, or when the owl reads someone getting in or a
device about to fail. Every other device's note waits for the next digest: one line a device
under Device logs, its newest note and how many since the last digest. A note never sends
a digest by itself. Alerts. - Docs: the shell's compose line gives
LANOWL_HOST_IP, a compose file of your own names
the published images, and the FAQ installs from PyPI.
Upgrade
cd lanowl
git pull
docker compose -f docker/compose.yaml pull
docker compose -f docker/compose.yaml run --rm lanowl lanowl --check
docker compose -f docker/compose.yaml up -dUpgrading has the rest, the shell included.
- Images, amd64 and arm64:
ghcr.io/alessandromatera/lanowl:0.2.0and
ghcr.io/alessandromatera/lanowl-sandbox:0.2.0. - On PyPI:
pip install -U lanowl. It now needs aiohttp 3.14.4 or later, and pip upgrades it.
Found a problem? Open an issue and say
what lanowl --version prints.
Documentation · AGPL-3.0
lanowl 0.1.0
The first release of lanowl, the self-hosted AI network monitor. It checks every device on your
network once a minute and tells you once per incident. When something breaks, a local model on
your own Ollama, the owl, investigates with read-only tools and writes the cause into the alert.
It changes nothing by itself: a fix runs only when you press a button.
lanowl is pre-alpha. It comes out of a monitor that has run a real home network since August
2026; expect rough edges, and keep backups.self on.
Install
git clone https://github.com/alessandromatera/lanowl && cd lanowl
docker compose -f docker/compose.yaml up -d
docker exec lanowl lanowl --setup-codeThen open http://<this host>:8088/: the first-run setup finds your router and your devices
and fills in the config for you. The
quick start has the details.
- Images, amd64 and arm64:
ghcr.io/alessandromatera/lanowl:0.1.0and
ghcr.io/alessandromatera/lanowl-sandbox:0.1.0(the model's sandboxed shells). - On PyPI:
pip install lanowl. Docker is the supported way: the image carries the tools the
owl's diagnostics run.
What it does
- Watches every device every minute (ping, TCP, HTTP, SNMP): one message per incident, one
when it is over. The internet every 15 seconds: a failover to your backup line is not "no
internet". - The owl (any Ollama model with tool calling) investigates every incident, answers your
questions on Telegram and the dashboard, and grades its own diagnoses. - Finds devices: the router's DHCP and ARP, a ping to every address, a few ports on each.
- Security: a daily review of what each machine exposes, with a written fix; auth logs;
what changed since yesterday; a monthly vulnerability scan. - Upkeep: updates, reboots, service restarts and backups, each behind your button.
- Around it: the dashboard with its first-run setup and Settings, Telegram with buttons and
commands, MQTT, remote sites over WireGuard. - Kinds: MikroTik, OpenWrt, Linux, ESXi, UniFi, Home Assistant, Reolink, Shelly built in;
any other kind is a YAML profile.
What you need
Docker with Compose 2.24 or later, on a machine that stays on (Linux recommended). Ollama for
the owl and a Telegram bot for your phone are optional: everything else works without them.
What you need.
Found a problem? Open an issue and say
what lanowl --version prints.
Documentation · AGPL-3.0