Tasmota: Sonoff touch - physical switch delay

Created on 20 Sep 2017  Â·  13Comments  Â·  Source: arendst/Tasmota

I've flashed tasmota to my sonoff touch and I can see slight delay when using touch button. It's much faster to turn on the light by mqtt message than with touch button. Is there any option I can tweak? Stock sonoff firmware was much faster.

stale

Most helpful comment

Let me help :
SetOption13 --> 1 = Enable button single press only for immediate response. Disable by holding 4 x SetOption32

By the way, the "Disable by holding 4 x SetOption32" feature is curious.

https://github.com/arendst/Sonoff-Tasmota/wiki/Commands

All 13 comments

The problem is that tasmota lets you do different things if you press the button
multiple times, so it needs to wait and see if you are only pressing it once or
if you are pressing it multiple times.

There s an option that lets you disable this. I don't remember it at the moment

Let me help :
SetOption13 --> 1 = Enable button single press only for immediate response. Disable by holding 4 x SetOption32

By the way, the "Disable by holding 4 x SetOption32" feature is curious.

https://github.com/arendst/Sonoff-Tasmota/wiki/Commands

@PeggyFree

are you referring the line below to set it to "0.1"?

define KEY_HOLD_TIME 40 // [SetOption32] Number of 0.1 seconds to hold Button or external Pushbutton before sending HOLD message

I don't understand what it means by "Disable by holding 4 x SetOption32"?

no, @PeggyFree is saying to issue the command "setoption13 1" to disable all the multipress options. This isn't a code change, it's a setting change.

Noted, will give it a shot...

On Wed, Oct 4, 2017 at 1:31 AM David Lang notifications@github.com wrote:

no, @PeggyFree https://github.com/peggyfree is saying to issue the
command "setoption13 1" to disable all the multipress options. This isn't a
code change, it's a setting change.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/891#issuecomment-333919451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIw6wGpnsuy_C1aPqbsZ15XFnSOs0_-Eks5som9VgaJpZM4Pd5r5
.

>

Sent from Iphone Mobile

@davidelang

Tasmoata excepted the command I ran "setoption13 1" but there is still a lag on the touch buttons. There are times when it will lock up the button for a few seconds. And other times especially when it comes out from being ideal, the button becomes less responsive and than it catches up a few seconds later.

What can I do to resolve this?

I realize something while reading #947 , I did not set the MQTT IP address while running my button test. After setting the correct address it became responsive. My only concern is, what if MQTT looses connection?

@ionciubotaru suggested there was an update on MQTT library, I'm using the latest 5.8.0 downloaded from Download Tasmota regardless, it still locks up when MQTT fails.

@arendst
I noticed when all the switches are [ON] state and the Touch loose wifi connection eg: wifi turned off. The relays turn OFF and ON every few seconds. It is like the Touch is rebooting, looking for a valid wifi connection. I'm not sure if its a bug or it suppose to react this way?

There is a longstanding bug with the arduino libraries that if it has trouble
making a connection, nothing else can take place.

That explains a lot, can a time out be setup, stop trying to communicate
after 5 attempts? And re-attempt to connect after a reboot cycle.

On Thu, Oct 5, 2017 at 8:51 AM David Lang notifications@github.com wrote:

There is a longstanding bug with the arduino libraries that if it has
trouble
making a connection, nothing else can take place.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/891#issuecomment-334329577,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae1zH4TsoXVC7-VFOVRyT5U_9masNBvkks5spCgcgaJpZM4Pd5r5
.

@alton76 I was going to ask the same as well....

On Thu, Oct 5, 2017 at 8:51 PM, alton76 notifications@github.com wrote:

That explains a lot, can a time out be setup, stop trying to communicate
after 5 attempts? And re-attempt to connect after a reboot cycle.

On Thu, Oct 5, 2017 at 8:51 AM David Lang notifications@github.com
wrote:

There is a longstanding bug with the arduino libraries that if it has
trouble
making a connection, nothing else can take place.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
issuecomment-334329577>,
or mute the thread
auth/Ae1zH4TsoXVC7-VFOVRyT5U_9masNBvkks5spCgcgaJpZM4Pd5r5>

.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/891#issuecomment-334455104,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIw6wAKnzeTPdo2GI-2f5QO0jwEEDk3Sks5spNDhgaJpZM4Pd5r5
.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ximonline picture ximonline  Â·  3Comments

TylerDurden23 picture TylerDurden23  Â·  3Comments

smadds picture smadds  Â·  3Comments

abzman picture abzman  Â·  3Comments

esp32x picture esp32x  Â·  3Comments