From 797fd4a69faea8bcb81895cbe75486e367c8aa79 Mon Sep 17 00:00:00 2001
From: Vasiley <25254807+Vasiley@users.noreply.github.com>
Date: Sun, 19 Nov 2017 14:19:36 -0600
Subject: [PATCH] Update sensor.lacrosse.markdown (#4011)

---
 source/_components/sensor.lacrosse.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_components/sensor.lacrosse.markdown b/source/_components/sensor.lacrosse.markdown
index d024d174403..3dc7a9f842e 100644
--- a/source/_components/sensor.lacrosse.markdown
+++ b/source/_components/sensor.lacrosse.markdown
@@ -25,7 +25,7 @@ The `lacrosse` sensor platform is using the data provided by a [Jeelink](https:/
 Since the sensor change their ID after each powercycle/battery change you can check what sensor IDs are availble by using the command-line tool `pylacrosse` from the pylacrosse package.
 
 ```bash
-$ sudo pylacrosse -D /dev/ttyUSB0 scan
+$ sudo pylacrosse -d /dev/ttyUSB0 scan
 ```
 To use your `lacrosse` compatible sensor in your installation, add the following to your `configuration.yaml` file: