Merge branch 'main' of git.stroblme.de:Fluksio/app
Docs / docs (push) Canceled after 0s
pre-commit / pre-commit (push) Canceled after 0s
Test Backend / test-backend (push) Canceled after 0s

This commit is contained in:
2026-08-22 10:23:19 +02:00
2 changed files with 9 additions and 0 deletions
+1
View File
@@ -12,6 +12,7 @@ Deferring because out of scope is fine, but don't mention deferring than.
### To be sorted
- BUG/UI when adjusting e.g. a slider value (drag), upon release the slider briefly jumps back to the previous position. We should fix that such that the slider stays at the dragged position. If sth. goes wrong with the transmit; we should show a notification. Check for all other widgets where this would apply as well
- FEAT/UI when an installation is added to the hub, the dialog which shows the access code should disappear automatically
- BUG/UI the "Connect" button in "Remote Access" when adding an installtion to the hub is invisible and only shows upon hovering (could also be a local browser issue)
- CHORE/PKG the SPA is not in the wheel: `fluksio serve` serves no UI, on the
+8
View File
@@ -93,6 +93,14 @@ external interfaces. See `docs/architecture/structure.canvas` → *Backend M
does as well. Exercised against the real unit — fan speed, mode, setpoint
to the half degree, power off and back on — each checked against the
unit's own answer, and it was left as it was found
- [x] The aircon reaches both firmware generations: adapters shipped from 2025
report `firmType` `WF-RAC-HTTPS` and wrap port 51443 in TLS with a
self-signed certificate naming their MAC, where older ones answer plain
HTTP there and drop the handshake. Nothing announces which before the
first exchange, so the node tries TLS, falls back, and remembers — a unit
that gets updated costs one retry rather than a reconfiguration. The
payload is identical across both, so only the transport moved. Verified
against one unit of each generation, read and command
- [x] Node lifecycle as a protocol (`start`/`stop`/`report_health` on `Node`),
replacing the controller's per-type isinstance chains — the same hooks a
connector implements, validated on the built-in nodes first