diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md
new file mode 100644
index 0000000..f9a039d
--- /dev/null
+++ b/KNOWN_ISSUES.md
@@ -0,0 +1,119 @@
+# Known Issues - TasmotaManager
+
+This document tracks known issues discovered during testing that are deferred for future fixes.
+
+---
+
+## Issue #4: Template Verification Timeout/Failure
+
+**Status:** Deferred  
+**Discovered:** 2025-10-28 (Testing after v1.02)  
+**Severity:** Medium  
+**Affects:** Template update and verification process
+
+### Description
+Template verification consistently fails even after 3 retry attempts. The device restarts successfully and the template appears to be applied, but the verification step times out or reports mismatches.
+
+### Example Log Output
+2025-10-28 09:18:18 - WARNING - MasterFan-0110: Template mismatch on verification (attempt 3)
+2025-10-28 09:18:18 - WARNING - MasterFan-0110: Template verification failed (attempt 3/3)
+2025-10-28 09:18:50 - WARNING - BathFan-4919: Template mismatch on verification (attempt 2)
+
+### Observed Pattern
+- Occurs on multiple devices
+- All 3 verification attempts fail
+- Happens after successful restart command
+- May be timing-related
+
+### Possible Causes
+1. Insufficient delay after restart (Current: 2-3 seconds, May need: 5-10 seconds)
+2. Network congestion - May improve with parallel processing
+3. Template comparison issue
+4. Module verification too early
+
+### Recommended Fix
+1. Increase initial verification delay to 5-10 seconds after restart
+2. Increase retry delays to 5 seconds between attempts
+3. Add more detailed logging
+4. Consider checking if device is responsive before verification
+
+### Related Code
+- File: TasmotaManager.py
+- Method: check_and_update_template()
+- Lines: ~950-1100
+
+---
+
+## Issue #5: Blank Console Parameter Name
+
+**Status:** ✅ FIXED (v1.04-console-empty-param-fixed)    
+**Discovered:** 2025-10-28 (Testing after v1.03)  
+**Severity:** Medium  
+**Affects:** Console settings application
+
+### Description
+The console settings code is attempting to set a parameter with a blank/empty name, causing verification failures and errors.
+
+### Example Log Output
+2025-10-28 09:18:29 - WARNING - BathFan-4919: Verification failed for blank parameter
+2025-10-28 09:18:31 - ERROR - BathFan-4919: Failed to set console parameter after 3 attempts
+
+### Observed Pattern
+- Affects multiple devices
+- Empty parameter name
+- Occurs before rule1 and Rule1 commands
+
+### Possible Causes
+1. Empty entries in console_set configuration
+2. Parsing issue in add_from_console_set() function
+3. Legacy console dict has empty key
+
+### Recommended Fix
+1. Add validation in parsing loop to skip empty entries
+2. Add validation before sending command
+3. Check configuration files for empty entries
+
+### Related Code
+- File: TasmotaManager.py
+- Method: apply_console_settings()
+- Lines: ~1600-1800
+
+---
+
+## Testing Notes
+
+**Test Environment:**
+- Date: 2025-10-28
+- Version: v1.03-mqtt-delay-fixed
+- Devices Tested: ~20+ devices
+
+**Devices Affected:**
+- MasterFan-0110
+- BathFan-4919
+- BedLamp-1516
+- Multiple other devices
+
+---
+
+## Priority for Future Work
+
+1. Issue #2 - Parallel Processing
+2. Issue #5 - Blank Console Parameter (easier fix)
+3. Issue #4 - Template Verification (more complex)
+
+---
+
+## Completed Issues
+
+**Issue #1** - Template Activation Fix (v1.02-template-activation-fixed)
+**Issue #3** - MQTT Delay Fix (v1.03-mqtt-delay-fixed)
+**Issue #5** - Blank Console Parameter Fix (v1.04-console-empty-param-fixed)
+- Root cause: Empty string in Traditional console_set array in configuration
+- Fixed by removing the blank entry from network_configuration.json
+
+---
+
+## Notes
+- Issues #4 and #5 discovered during production testing on 2025-10-28
+- Both issues are non-critical - devices appear to function despite errors
+- Recommend addressing after Issue #2 is complete