From 218e8db32bf911bf1200eea2b1ef1d8695b42bc3 Mon Sep 17 00:00:00 2001
From: digiblur <3240875+digiblur@users.noreply.github.com>
Date: Thu, 14 Nov 2019 15:52:10 -0600
Subject: [PATCH] Correct SetOption to include the zero

---
 Configuration-Procedure-for-New-Devices.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Configuration-Procedure-for-New-Devices.md b/Configuration-Procedure-for-New-Devices.md
index 8f65c4d4..552bd9a2 100644
--- a/Configuration-Procedure-for-New-Devices.md
+++ b/Configuration-Procedure-for-New-Devices.md
@@ -6,7 +6,7 @@ If your device is similar to the existing built-in module (e.g., a particular MC
 
 1. Begin this procedure by disabling power state saves. Some improper GPIO assignments can cause device reboots. Disabling this setting avoids repeated flash writes. Also, it is best to allow Tasmota to return to a fail safe state in case of a bad configuration. Ensure that boot loop control is not disabled.  
 
-   `Backlog SetOption 0; SetOption36 1`  
+   `Backlog SetOption0 0; SetOption36 1`  
 
 2. Assign every available GPIO to successive `Relay<x>` components. For the initial GPIO probe, exclude "dedicated" GPIO such as GPIO0/GPIO2 and Tx/Rx, etc. You can use a [Template](Templates) to easily perform these assignments:  
    `{"NAME":"ID Components","GPIO":[0,0,0,0,21,22,0,0,23,24,25,26,27],"FLAG":0,"BASE":18}`