From 8404a3844c9357d6f5066f86e7154d20c868bf8d Mon Sep 17 00:00:00 2001
From: gitwazza <49083727+gitwazza@users.noreply.github.com>
Date: Thu, 6 Jan 2022 22:16:21 +1100
Subject: [PATCH] Explain how to access Z-Wave JS logs (#21050)

Add details on how to access the Z-Wave JS logs. Note: I'm not sure about the prevailing (best) way to indicate the path to an option in the GUI. I've followed close to the other example on this page, but adjusted slightly to provide current UI and additional detail.
---
 source/_integrations/zwave_js.markdown | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index b8aaf7058f3..5a231111f63 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -756,3 +756,11 @@ If the interview is complete, then the device does not yet have a device file fo
 When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu:
 
 **Configuration** -> **Integrations** -> **Z-Wave JS** -> **Configure** -> **Download a dump of your network to help diagnose issues**
+
+#### How to access the Z-Wave JS logs
+
+Z-Wave JS writes details to its logs. To access these logs go to the following.
+
+   **Configuraton** -> **Devices & Services** -> **Integrations(tab)** -> **Z-Wave JS (CONFIGURE)** -> **Logs(tab)**
+
+You need to keep this browser tab open for logging to be active.