Skip to content

Releases: omcular/zigbee2mqtt-map-panel

v2.3.0

Choose a tag to compare

@omcular omcular released this 31 Oct 10:18
  • 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

v2.2.0

Choose a tag to compare

@omcular omcular released this 31 Oct 06:29
  • Permit join from the map: a toolbar button opens the network for 254 s with a countdown (click again to close), a router's card offers "permit join here" and, while a join runs, "also here" (each router keeps its own 254 s; the button lists the running countdowns), and a dot circles every node the network is open through. A pairing feed, a bubble over the map, follows the newcomer: joined → interviewing → paired or failed. Administrators only.
  • The map follows Zigbee2MQTT's device list without a scan: a renamed device gets its new name (an open card follows), a joined device appears at once (parked at the edge until a scan shows its links, selected after a successful interview), a removed device stays in grey with its links until the next scan.
  • Mesh-health sensors: "Mesh connected at LQI", "Mesh redundant at LQI" and "Mesh routers ignored" (routers with no two-sided link in the scan, i.e. a router that went dark; 0 when all is well, so it is the one to alert on). The integration computes them after every scan and the panel shows the same values. Attributes name the bottleneck link, the single point of failure, the cut-off routers and the routers that did not answer the scan. A history graph of the three is the mesh over time.
  • Background scan interval in steps of 0.25 h (15 min) instead of 0.5 h.
  • Option "Zigbee2MQTT frontend" and the help say which form to use on HAOS and on Core/Container (the frontend's URL with scheme), and that https HA cannot embed a plain-http frontend.
  • Fixed: a node that had been parked at the edge (no links yet) came back pinned, on the parking row, once a later map gave it links. Parked and pinned are kept apart now; such a stray pin is cleared by double-clicking the node.

Full Changelog: v2.1.0...v2.2.0

v2.1.0

Choose a tag to compare

@omcular omcular released this 29 Oct 07:10
  • Releases carry the integration as a zip asset, which is what HACS downloads from now on (install counts per release).
  • Ghost devices (addresses in neighbour tables that Zigbee2MQTT does not know) are hidden unless the option
    "show ghost devices" is on; their card names the routers still holding them.
  • Min LQI filters router links only; end-device links stay whatever the threshold (they are one-sided by nature and
    often 40–60, so a "connected" view used to cut dozens of healthy sensors loose).
  • Devices without a visible link are docked in rows along the bottom of the screen, whatever the zoom, pan or rotation,
    instead of being parked somewhere in the graph.
  • New defaults: device images on, spacing 0.5, names for routers only.
  • LQI labels run along their link, just above it; the left value is what the left-hand node hears.
  • "save PNG" works again (the exported SVG carried the xmlns attribute twice and never loaded).
  • "node size" (was "image size") also scales the squares and dots when images are off.
  • Option "hover popups": off leaves only the cards a click opens. A drag hides an open popup.
  • Min LQI marker stays visible at "off". Cursor is the normal arrow, a hand on nodes only.
  • Renamed: "dragging pins nodes", "pull routes (may take very long)".
  • Map: clicking or tapping a node also opens its card, which stays until clicked (or Esc, background, another node)
    and carries the device's "Z2M" and "HA" links; it stays while the Z2M drawer is open. Clicking the selected node
    again brings a closed card back.
  • Toolbar: Min LQI is now the LQI colour bar itself (value on hover): a marker shows the setting, press or drag on the bar to change it
    (mouse and touch). The bottom legend box is gone; its notes are in the help.
  • Options: "smooth link colours" removed; link colour always runs continuously from red through orange to green.
  • Fresh install: the integration scans by itself about 20 s after setup, and the panel asks for a scan the moment it
    learns there has never been one, so a new user sees a map without pressing anything.
  • Options are grouped under Show, Layout, Scans and Panel.
  • Layout: the scan button and status line moved to a footer bar; option controls at the bottom swaps the two bars
    (status on top, controls within thumb reach on a phone; menus then open upwards).
  • Devices not in Zigbee2MQTT's device list get no Z2M link (Zigbee2MQTT has no page for them).
  • Toolbar: "pull fresh map" is now a download icon button right before the status text.
  • Status line: "scanned 33m ago" / "scanned 2d ago" instead of the date and time; the exact time on hover.
  • Min LQI follows the mesh's "redundant" threshold until you move the slider, so a first look
    shows the mesh instead of every marginal link. Clicking "connected" or "redundant" in the status line makes it follow
    that threshold on every new map; dragging the bar fixes a value. "reset to defaults" brings the automatic mode back.
  • Devices list: sortable by name, type, LQI (weaker direction first, then the stronger) and last seen.
  • Help: each entry as a small heading with its explanation indented below (was a two-column table).
  • Dropdowns stay inside the panel: shifted left when they would stick out, narrower and wrapping on a phone.
  • Routes overlay (slider "routes" in options › Show, 0 = off): after a scan with "routes on pull", links carrying
    active routes are drawn thicker, the more routes the thicker (the slider sets how strongly), with an arrow in the link's colour at the end the traffic flows to; other links are
    unchanged. A selected router's path to the coordinator is drawn extra thick and its card names the hops.
  • Node card: a router whose routing table could not be read says so (Tuya modules do not answer the request).
  • Link tooltip: routes laid out one line per direction, "A → B → destinations", destinations named, status only when
    not active.
  • Node and link tooltips stay inside the map area: flipped to the other side of the pointer near an edge, never cut off
    on a phone. On touch, a tap on an open tooltip closes it instead of reaching the map below.
  • Two-finger twist rotates the map on touch screens (with a small dead zone, so a pinch does not wobble).
  • Cursors: a hand on nodes (they are clicked more than dragged), no question mark on links.
  • A click on the map while a dropdown is open only closes the dropdown (no deselect, drag or pan).
  • Keys: Esc closes the Zigbee2MQTT drawer, else an open dropdown, else clears the selection; Ctrl-A selects every node
    on the map (again: none), Ctrl-Shift-A clears the selection (not while typing in a field).
  • Layout: nodes are pushed off links they do not belong to, and those links bend away (options: keep nodes off
    links
    , 0 turns it off).
  • README: networkmap_fast is merged into zigbee2mqtt-user-extensions, link to it there.
  • Panel: devices ▾ dropdown in the toolbar. With a node selected it lists that device and its neighbours with
    both LQI directions, otherwise every device (the "find" text filters it). Click a name to select it on the map;
    "HA" opens the device page in Home Assistant, "Z2M" the device in the Zigbee2MQTT frontend, in a drawer over the
    map (Ctrl-click for a new tab).
  • Options: Zigbee2MQTT frontend URL (optional) for those Z2M links: the add-on's sidebar path (opened through the
    add-on's ingress, administrators only, nothing to expose) or the frontend's own URL.
  • Panel: multi-select with Ctrl/Shift-click, on the map and in the devices list; the list shows one block per selected
    device. A few pixels of jitter during a click no longer count as a drag (a Shift-click used to pin the node).
  • Panel: ⚙ top right opens the integration's page in Home Assistant (options, entities, reload).
  • Panel: the selected node survives leaving and re-entering the panel (device page and back).
  • Panel banner says whether a page reload or a Home Assistant restart is needed (files updated without a restart
    showed a permanent "reload" banner before).
  • tools/release_map.sh waits for one workflow run per workflow file (it hung waiting for a third run).

Full Changelog: v2.0.1...v2.1.0

v2.0.1

Choose a tag to compare

@omcular omcular released this 27 Oct 06:29

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Choose a tag to compare

@omcular omcular released this 27 Oct 05:47

Full Changelog: v1.1.0...v2.0.0

v1.1.0

Choose a tag to compare

@omcular omcular released this 27 Oct 04:33

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Choose a tag to compare

@omcular omcular released this 27 Oct 04:15