Fix button press timing issue by increasing SetOption32 to 40
Issue: Some Tasmota switches (e.g., KitchenBar) required multiple button presses before responding, while others (e.g., KitchenMain) worked immediately. Root Cause: SetOption32 was set to 8 (0.8 seconds) which creates too short a time window for multi-press detection. This causes the device to sometimes misinterpret single presses or require multiple attempts. Solution: Changed SetOption32 from 8 to 40 (4.0 seconds) in both Traditional and SONOFF_ULTIMATE console_set profiles. This matches the working devices and provides a longer, more reliable detection window for single button presses when using rule: "on button1#state=10 do power0 toggle endon" SetOption32 controls the button hold time in 0.1s increments. A higher value means the device waits longer to confirm it's a single press vs multi-press, resulting in more reliable single-press detection. Tested on KitchenBar (192.168.8.244) - button now responds reliably on first press. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
2f3fd5d711
commit
8f758599cf
@ -84,7 +84,7 @@
|
||||
"SetOption4 1",
|
||||
"SetOption13 0",
|
||||
"SetOption19 0",
|
||||
"SetOption32 8",
|
||||
"SetOption32 40",
|
||||
"SetOption40 40",
|
||||
"SetOption53 1",
|
||||
"SetOption73 1",
|
||||
@ -101,12 +101,10 @@
|
||||
"SetOption4 1",
|
||||
"SetOption13 0",
|
||||
"SetOption19 0",
|
||||
"SetOption32 8",
|
||||
"SetOption32 40",
|
||||
"SetOption40 40",
|
||||
|
||||
"SetOption53 1",
|
||||
"SetOption73 1"
|
||||
|
||||
]
|
||||
}
|
||||
}
|
||||
Loading…
Reference in New Issue
Block a user