v3.2.0 - Endless Possibilities + discovery for Netgear, Fast.com and Mobile App (all experimental)

[3.2.0]

Adds unlimited-depth tiers (a fed Switch, and now an Access Point too,
can feed further Switches/Access Points/Servers to any depth), renames
Homelab to Server everywhere it's shown, per-server Security targeting,
Netgear and Fast.com Auto-Discovery, a real expandable tree for the
Nodes editor page with reordering and continuous numbering at every
tier, a "Core Switch" rename for the top-level Switch menu, and a
confirmed fix for bandwidth connectors drawing a phantom second strand
whenever only one of Download/Upload was configured.

Added

• Unlimited tiers. A fed Switch can carry its own access_points,
  fed_switches, and homelabs, and those can carry theirs, to any
  depth - not just the one level of Fed Switches supported previously.
  Every extra level adds one row to the diagram between the Access
  Point row and Connected Devices. A Switch/AP feeding several children
  is centred over every column beneath it, with its own stem and mini
  bus-line; offline state cascades down the whole chain; PoE totals sum
  Access Points, Servers, and Switches at every depth.
• An Access Point can be a parent too. Straight off the bus or
  nested under a Switch, an Access Point can now feed its own
  fed_switches, homelabs, and further access_points (a wireless
  mesh) - everywhere a Switch could feed something, an Access Point now
  can as well. An Access Point that feeds anything also gets its own
  dotted line down to the Clients box, the same as a Primary AP in
  Tiered layout, with its Connected Devices circle hanging off that
  line if it has one.
• A Server can hang off anything, not only sit at the top level -
  under any Switch or Access Point, at any depth, with its own
  Containers/VMs, PoE, and Connected Devices intact. (See the Homelab →
  Server rename below.)
• Per-server Security targeting. VPN, Firewall, DNS Filtering, and
  Reverse Proxy are still configured once and pointed at a device type
  (Server among them), but each Server can now choose which of those
  items it actually shows:

  homelabs:
    - entity: sensor.server_a
      security: { dns: true, reverse_proxy: true }
    - entity: sensor.server_b
      security: { vpn: true }

  A Server with no security key shows every item pointed at it,
  exactly as before - additive, not a breaking change.
• Netgear Auto-Discovery - experimental. Covers the official
  netgear integration (Orbi, Nighthawk, and other pynetgear-supported
  routers), confirmed against home-assistant/core's own source. Offers
  a Router candidate via one of its connected devices' trackers as a
  reachability proxy - the same technique OpenWrt (LuCI) already uses,
  since Netgear has no dedicated router-status entity, and its
  one enabled-by-default entity (the firmware Update entity) reports
  "off" when simply up to date - which this card's offline check
  would otherwise misread as offline. Every attached device is offered
  as a Client; Netgear's own integration never distinguishes a
  satellite, switch, or AP from an ordinary phone or laptop, so nothing
  from it is ever offered as a Switch/AP node. Marked experimental
  because of the client-proxy reachability check and less real-world
  mileage than the router integrations already supported.
• Fast.com added to Speedtest Auto-Discovery (fastdotcom platform,
  confirmed against home-assistant/core's own source) - a single
  Download-only sensor, no Ping/Jitter/Upload/ISP, since that's the
  only figure fast.com measures. Its single_config_entry manifest
  flag means at most one Fast.com service will ever be found.
• Home Assistant Mobile App Auto-Discovery (mobile_app platform,
  confirmed against home-assistant/core's own source) - every device
  running the official Companion app gets one device_tracker entity,
  offered on the Clients page. Clients-only: unlike every router-brand
  integration above, there's no Router/Node concept here at all - a
  phone or tablet is always a personal device, never network hardware.
• Editor: the Nodes page is a real expandable tree.
  • Every Switch or Access Point row has a chevron that expands it in
    place, with a live online/offline dot and a count of everything
    below it.
  • "+ Access Point / + Switch / + Server" sit directly inside the same
    card as the row they add to, ahead of its children, instead of at
    the bottom of a long flat list.
  • "Add AP / Add Switch / Add Server" are three separate buttons at
    the bottom of the page, each creating the right node type directly,
    instead of one "Add Node" button that always defaulted to an
    Access Point.
  • Move up/down now works at every tier, not just the top level - an
    Access Point, fed Switch, or Server reorders among its own siblings
    of the same kind under the same parent (Access Points, Switches,
    and Servers are always drawn as three separate blocks, so that's
    the only reordering that's meaningful).
  • Fallback labels ("Switch 3", "AP 4", ...) now share one running
    count per kind across the whole tree, instead of restarting at 1
    under every new parent.
  • A discovered candidate's "Add as" dropdown now lists every eligible
    Switch/Access Point in the tree, with a breadcrumb ("D-Link ›
    Workshop PoE"), not only top-level Nodes - this also lets a
    discovered Proxmox Server attach under an existing node instead of
    only ever becoming a new one.
  • Deleting a Switch/AP with devices below it asks for confirmation
    first. Only one Access Point can be Primary, wherever it sits in
    the tree.

Changed

• "Homelab" is now "Server" everywhere it's shown - buttons,
  headers, tooltips, dropdown options, and the diagram's own fallback
  label text. Display-only: the YAML keys (homelab, homelabs, the
  homelab Security target value, ...) are unchanged, so no existing
  config needs to change.
• The top-level "Switch" menu is now "Core Switch" - its entry in
  the menu list and its own page header only. Every Node-level "Switch"
  (Fed Switches, the node-type dropdown, "Main Switch" as a Security
  target, tree labels, ...) is unchanged, since that's a distinct,
  still-called-Switch concept from the one Core element between
  Router/Gateway and Nodes.
• A Switch's mini bus-line is now drawn as one exact centre-to-centre
  stretch per child, instead of a single line inset by a fixed amount
  from the group's edges - this replaces the previous inset-based
  adjustment, which could still overshoot the last drop by a few pixels
  in a mixed AP/Fed-Switch row.
• Four long inline descriptions became hover tooltips (the same small
  (i) icon already used elsewhere), instead of a paragraph sitting
  underneath the control: Clients page - Grouping, Show Client Names;
  Advanced page - Show IP Addressing, Enable Animations.

Known limitations

• A Switch that feeds other devices doesn't show its own Connected
  Devices circle - there's no free row for it. An Access Point in the
  same position does (see "Added" above).
• A Primary AP anywhere but straight off the bus (inside a Switch's
  group, or hanging off another Access Point) still renders Flat, not
  Tiered.
• Each Security item (VPN, Firewall, DNS, Reverse Proxy) still has one
  entity; Servers can each choose whether to show it, not point it at a
  different entity per server.
• Auto-Discovery still never knows which switch physically feeds which
  switch/AP - no supported integration exposes that uplink topology to
  Home Assistant - so a deep, discovered tree still has to be assembled
  by hand via the attach-to-existing dropdown or the Node editor.
  Netgear's own integration goes a step further and can't tell a
  satellite, switch, or AP apart from an ordinary client at all, so its
  devices only ever show up as Clients.
• The Nodes tree's expanded/collapsed state lives only in the open
  editor session; reordering or deleting inside a Switch collapses
  whatever was expanded beneath it.