diff --git a/docs/_images/qr-code-inclusion.png b/docs/_images/qr-code-inclusion.png
index 698a54dffb58..8000d6b79b6d 100644
Binary files a/docs/_images/qr-code-inclusion.png and b/docs/_images/qr-code-inclusion.png differ
diff --git a/docs/_images/smart-start.png b/docs/_images/smart-start.png
index dadc3742bd83..355c711d6fc7 100644
Binary files a/docs/_images/smart-start.png and b/docs/_images/smart-start.png differ
diff --git a/docs/getting-started/security-s2.md b/docs/getting-started/security-s2.md
index 48e601f62556..86573b8b4cd6 100644
--- a/docs/getting-started/security-s2.md
+++ b/docs/getting-started/security-s2.md
@@ -136,6 +136,12 @@ For modern devices, **SmartStart** makes the inclusion even easier for the user
 
 > [!NOTE] Confirming the inclusion process like with normal S2 inclusion is recommended, so users can react to a failed bootstrapping attempt.
 
+## Z-Wave Long Range
+
+Devices using Z-Wave Long Range can only be included via SmartStart. Since not all devices support Long Range, the protocol choice in the above screenshot should only be available after scanning a QR code that indicates support for Long Range (see below), or when the provisioning entry was added manually. Note that the **S2 Unauthenticated** and **S0 Legacy** security classes are not available for Z-Wave Long Range.
+
+> [!NOTE] We recommend to **not** preselect Z-Wave Long Range, even on supporting devices. Z-Wave Long Range is a separate protocol and the devices are not part of the Z-Wave mesh, so this choice should be an opt-in rather than an opt-out.
+
 ## Using QR codes to include devices
 
 Scanning a QR code can further simplify the inclusion process, because it limits the user interaction to scanning the code (and pushing a button for conventional inclusion):