4 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	c3675688c8	Wait for a deadline instead of polling for one ... The timer thread promoted due work on a fixed one-second tick, so every delayed item was 0-1000ms late whatever the load — measured on the house at 705ms mean on a rollershutter stop, which is 2-4% of a 26-second travel and accumulates in the position the motor node believes it is at. It now sleeps to the soonest deadline and is woken when a nearer one is scheduled, which measures 0.9ms end to end through Redis. A promoted timer also went to the back of the queue. It goes into a due lane of its own that `claim` reads first, so work that has waited out a deadline is not held up by work that is merely queued. Beside it, in the same code: seeding a message now bumps its version, so a re-put flow's synchronous nodes no longer wait forever on a value that is sitting in state; the consumer group drops the consumers of engines that are gone (138 had accumulated on this installation); and the cast that closes the long-standing `xclaim` mypy error. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-27 11:51:58 +02:00
stroblmeandClaude Opus 5	bd2c4b66e9	Publish the connector contract and authoring guide ... Adds reference/connector-contract.md and code/connectors.md to the site, with the node-type reference finally linking the contract it describes. Strict build passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-24 12:13:40 +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	11e032386b	Publish the documentation site: docs.fluksio.com ... A zensical site under docs/, served by a new `docs` compose service behind Traefik, built with --strict in CI. Same pattern the sibling n3xd workspace uses. Getting started splits the way the landing page does — one path is `pip install fluksio` and a training script, the other is a Docker stack and an afternoon in the browser — because the two audiences will not spend the same amount of time. Everything after that is shared: the concepts, the web interface (app and portal), the CLI and the API, and a reference for node types, payload types and configuration. The three flow guides move here from the docs submodule rather than being copied, so there is one version of them. Styling mirrors DESIGN-GUIDELINES.md: the app's token palette remapped onto Material's variables in both schemes, Inter, the 16px panel radius, and the one terracotta accent spent on the facility lane of the audience split. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M7Xv3cJEW5c8AXxn2hoojV	2026-08-22 05:55:34 +02:00