3 Commits

Include renames

Author	SHA1	Message	Date
stroblme	93e45274d0	Let a teardown's cancellation through, and reap the workers it leaves ... Node stop paths cancelled their background task and then caught CancelledError around the await, which swallows a cancellation aimed at the caller — the trap Supervisor._cancel already documents. One shared Node._cancel_task now waits the way the supervisor does; mqtt's publisher and subscription and delay's cron call it. The api container also collected zombie python workers: orphaned when --reload replaces the process holding their handle, they reparent onto a PID 1 that reaps nothing but its own. `init: true` on the backend service.	2026-08-28 11:27:01 +02:00
stroblmeandClaude Opus 5	ba707c8051	nodes: what porting the house needed from the vocabulary ... Four small things, each with a device behind it. An MQTT filter now routes what it subscribed to. `+` and `#` reached the broker and were then looked up in an exact-match dict, so every message a wildcard subscription received was dropped in silence. `json_key` lifts a value out of the object a device wraps it in — Victron publishes `{"value": 47}` on every path, which was otherwise a Python node per port. The trigger node learned `passthrough` and `wait_port`, because how long to wait can be a value rather than a constant: a rollershutter takes 26 seconds up and 28 down. A wait of zero sends nothing afterwards and still cancels what the last message scheduled, which is how a stop is commanded once instead of forever. The HTTP sender takes fixed `query` parameters, so an API key is a secret reference rather than a message on the canvas, and `send_inputs` off for a request whose inputs are only a trigger. Also: `delay` accepts fractional seconds, and `TZ` reaches the container, so a cron expression means local time. Left unset it is UTC, as before. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-22 14:16:08 +02:00
stroblmeandClaude Opus 5	60d7ec81c0	Rename the import package app to fluksio ... A wheel whose top-level module is `app` collides with anything else in a user's venv, so the package that is about to be published takes the name it is published under. Only the Python package moves; the repo, the Docker WORKDIR and the compose project keep theirs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 21:48:05 +02:00