Repository navigation
- Min LQI and the end-device switch are filters, not layouts: links hidden by the slider stay in the physics at a fifth of their pull, hidden end devices stay in it entirely, nothing is parked by the slider, and a slider move wakes the simulation gently with only the changed links ramping their pull over a second. The arrangement you untangled survives slider drags; it still adjusts, it no longer rearranges.
- Fixed: every wake of the physics turned the whole map a little (about 3° per re-layout). d3's link and collision forces split their push unevenly between the two nodes of a pair, which adds up to a net torque; the panel now uses its own link, collision and repulsion forces with equal and opposite pushes.
- Node repulsion falls off as 1/distance^1.5 instead of 1/distance (normalised at 100 px): clusters keep their spread, a lone node is no longer pushed across the map by a dense cluster elsewhere.
- "fit view" (was "reset view"): turns the map so its long axis follows the window's and zooms to everything drawn, turn and zoom as one eased motion. A first visit and "reset to defaults" fit by themselves, once at once and once more when the layout has mostly settled.
- Keys: f fit (F without turning), r re-layout, / find, E end devices, D devices list, O options, h help, ← → Min LQI by a step, ↑ ↓ Min LQI to the next stop (0, redundant, connected, 255), Esc closes the card, a menu, the find box or the selection, one per press. Home Assistant's own keys (e, d, c, ?) keep working. Every control has a hover explainer, with its key where it has one.
- Find takes comma-separated terms, a name matches any of them; the devices list filters the same way.
- Min LQI follows "connected" by default (was "redundant"); the routes slider is shown only while "pull routes" is on, and ticking it sets the overlay to 1.0 if it was off.
- Defaults: node size 24, spacing 0.7. The end-device dot is 70 % larger; the join electron scales with the node size.
- Fixed: route arrows and thick path lines lagged one selection behind.
- Fixed: after a release the "panel updated" banner asked for a Home Assistant restart when a page reload was all it took.
Full Changelog: v2.2.0...v2.3.0