Update zwavejs/zwave-js-ui Docker tag to v11.16.2

[renovate]

This PR contains the following updates:

Package	Update	Change	Pending
zwavejs/zwave-js-ui	minor	11.15.1 → 11.16.2	11.17.0

---

Release Notes

zwave-js/zwave-js-ui (zwavejs/zwave-js-ui)

v11.16.2

Compare Source

✨ Features

• bump @​zwave-js/server@​3.8.0 (#​4621) (d6902dc)
• bump zwave-js@​15.23.5 (#​4620) (dd4bf1e)

v11.16.1

Compare Source

✨ Features

• bump zwave-js@​15.23.2 (#​4615) (a21b2d8)
• bump zwave-js@​15.23.4 (#​4618) (d496275)

🔧 Chores

• deps: pin zwave-js dependency (#​4617) (da840fe)

v11.16.0

Compare Source

✨ Features

• bump zwave-js@​15.22.2 (#​4600) (1e66ea6)
• bump zwave-js@​15.23.0 (#​4613) (802f564)
• ui: move pagination to top of nodes table (#​4605) (08b46dc), closes #​3603 #​4488

🐛 Bug Fixes

• docs: clarify default value of BACKUPS_DIR (#​4597) (0224aca)
• specify exact Node.js version in release workflow (c80566f)

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "after 2am and before 8am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

zwavejs/zwave-js-ui (docker) 11.15.1 -> 11.16.2

Risk: 🟢 Safe

The Deep Dive

Update Scope

Ansible role zwavejs Docker image tag at ansible/roles/zwavejs/defaults/main.yaml:3 bumped from 11.15.1 → 11.16.2 (and digest updated). This deploys to the pantrypi host (ansible/inventory/default) via docker-compose. The container runs behind Traefik with only TZ=America/New_York set in the environment — no other env vars or runtime config change in this PR. Nothing else in the role (template, tasks, handlers) changes.

Performance & Stability

Bundled zwave-js library bumps make up almost the entire delta: 15.22.x → 15.23.5 over v11.16.0, v11.16.1, and v11.16.2. v11.16.2 also bumps @zwave-js/server from ^3.2.1 (in v11.15.1's package.json) to ^3.8.0. This is relevant because Home Assistant talks to this container over the zwave-js WebSocket protocol on port 3000 (ansible/roles/zwavejs/templates/docker-compose.yaml.j2:23-28). I verified the schema range directly: zwave-js-server 3.8.0's src/lib/const.ts declares minSchemaVersion = 0, maxSchemaVersion = 48, and the 3.8.0 release notes confirm schema 48 was added on top of prior versions. HA's pinned zwave-js-server-python==0.70.0 speaks schema 47, which is inside [0, 48] — so HA will continue to negotiate successfully.

Features & UX

v11.16.0 moves pagination to the top of the nodes table (UI-only, no config). No new env vars or settings are introduced in any of v11.16.0/.1/.2, so the existing docker-compose.yaml.j2 template needs no changes.

Key Fixes

v11.16.1 pins the zwave-js dependency, so the runtime library version is deterministic per image tag — minor build-system hygiene, no behavioral change. The only doc-related fix (clarifies default of BACKUPS_DIR) does not apply: this deployment uses default paths and no BACKUPS_DIR env var is set.

Newer Versions

v11.17.0 was released 2026-05-05, still inside the 14-day minimumReleaseAge window — Renovate has it queued as Pending. It ships #4604 (socket reconnection loop + TRUST_PROXY validation error) and a Home Assistant suggested_area enhancement. Neither is a regression introduced by v11.16.x — they are pre-existing bugs that pre-date v11.15.1, so they do not raise the risk of this PR. Notes on applicability: the TRUST_PROXY fix only matters if the env var is set, and this deployment does not set it (docker-compose.yaml.j2 only sets TZ); the socket-reconnect loop only fires when zwave-js-ui auth is enabled and a JWT expires.

Hazards & Risks

None identified. Patch-level upstream changes are zwave-js library bumps (15.22 → 15.23.5) and one UI pagination tweak. No env vars, ports, mounts, or settings have been added/removed/renamed across v11.16.0–v11.16.2 that touch this deployment's docker-compose template. The image is pinned by digest, so the deploy is reproducible. After Semaphore runs the playbook on pantrypi, verify the container comes up healthy and that Home Assistant's zwave-js integration reconnects on port 3000.

Sources

• zwave-js-ui v11.16.0 release notes
• zwave-js-ui v11.16.1 release notes
• zwave-js-ui v11.16.2 release notes
• zwave-js-ui v11.17.0 release notes (pending Renovate stabilization)
• PR #4604 — socket reconnection loop and trust proxy fix (lands in v11.17.0)
• Issue #4605 — pagination at top of nodes table
• zwave-js-server 3.8.0 release (schema 48)
• zwave-js-server 3.8.0 const.ts (minSchemaVersion=0, maxSchemaVersion=48)
• zwave-js-server-python 0.70.0 schema constants (HA pinned client)
• GitHub Security Advisories — zwave-js/zwave-js-ui (empty)

---

🟢 Verdict: Safe

Routine minor patch bundling zwave-js library bumps (15.22 → 15.23.5) and a small UI tweak. No env-var or schema changes affect the deployment's docker-compose template. After merge, Semaphore will deploy to pantrypi; spot-check container health and that Home Assistant reconnects to the zwave-js WebSocket.