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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v11.17.0

Compare Source

✨ Features

• hass: add suggested_area from node location (#​4627) (b9544ec)

🐛 Bug Fixes

• socket reconnection loop and trust proxy validation error (#​4604) (aed2082), closes #​4564 #​4535 home-assistant/addons#4597 #​4535

🔧 Chores

• deps: move frontend-only deps out of runtime deps (#​4630) (0ca1850)

---

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.16.2 -> 11.17.0

Risk: 🟢 Safe

The Deep Dive

Update Scope

This PR updates the deployed Z-Wave JS UI Docker image pin in ansible/roles/zwavejs/defaults/main.yaml from zwavejs/zwave-js-ui:11.16.2@sha256:c43f88e2e395bb4b37c9e87e64998b751b1e1908318177623cebe08867e1eb42 to zwavejs/zwave-js-ui:11.17.0@sha256:79827886d44929105b625b07ce9870e739502d8b421bff5b11a4c17f811fb577. The role still deploys the same Docker Compose service, serial device, persistent store, UI port, and websocket port through Traefik in docker-compose.yaml.j2. The bundled zwave-js driver remains 15.23.5 and @zwave-js/server remains 3.8.0 between v11.16.2 and v11.17.0.

Performance & Stability

• Upstream PR 4630 moves frontend-only packages out of runtime dependencies and reports a smaller production image; this is deployment-relevant because the Ansible role pulls the image onto pantrypi, the host in the zwavejs inventory group.
• Upstream PR 4604 fixes a Socket.IO reconnect loop after rejected auth handshakes. That path is used by this deployment because the compose template publishes both the UI and websocket through Traefik in docker-compose.yaml.j2.

Features & UX

• v11.17.0 adds an optional Home Assistant MQTT Discovery setting, useLocationAsSuggestedArea, which publishes a Z-Wave node Location as Home Assistant device.suggested_area. It is disabled by default, and this repo has no Ansible-side setting for it in the Z-Wave JS compose environment (template). To use it, enable Use node location as suggested area in the Z-Wave JS UI Home Assistant / MQTT Discovery settings and rediscover node values as described in the upstream docs.

Newer Versions

• v11.18.0 is newer and currently latest, but I found no evidence that it fixes a regression or CVE introduced by v11.17.0.
• The newer release adds zwave-js 15.24.0, Home Assistant MQTT discovery updates for reactive power/energy, and a debug log capture fix. Those are additive follow-up changes, not blockers for this image pin.

Hazards & Risks

None identified. v11.17.0 lists feature, fix, and dependency-classification changes rather than migrations; the deployed role keeps the same volume, device, UI, and websocket wiring, and the core Z-Wave JS driver/server versions are unchanged from v11.16.2 to v11.17.0.

Sources

• PR #2272 changed Ansible image pin
• Z-Wave JS UI v11.17.0 release
• Z-Wave JS UI v11.18.0 release
• Socket reconnect and trust proxy fix
• Home Assistant suggested_area feature
• Runtime dependency reduction
• Z-Wave JS UI security advisories
• OSV package search

---

🟢 Verdict: Safe

Safe to merge: this PR only advances the deployed image pin, v11.17.0 has no migration for this compose deployment, and v11.18.0 does not appear to fix a regression introduced here. After merge, a normal smoke check of the Z-Wave JS UI and Home Assistant Z-Wave entities is sufficient.