Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonoff touch - physical switch delay #891

Closed
KaSroka opened this issue Sep 20, 2017 · 13 comments
Closed

Sonoff touch - physical switch delay #891

KaSroka opened this issue Sep 20, 2017 · 13 comments
Labels
stale Action - Issue left behind - Used by the BOT to call for attention

Comments

@KaSroka
Copy link

KaSroka commented Sep 20, 2017

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.

@davidelang
Copy link
Collaborator

davidelang commented Sep 20, 2017 via email

@PeggyFree
Copy link

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

@jeylites
Copy link

jeylites commented Oct 3, 2017

@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"?

@davidelang
Copy link
Collaborator

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.

@jeylites
Copy link

jeylites commented Oct 3, 2017 via email

@jeylites
Copy link

jeylites commented Oct 4, 2017

@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?

@jeylites
Copy link

jeylites commented Oct 4, 2017

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.

@jeylites
Copy link

jeylites commented Oct 4, 2017

@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?

@davidelang
Copy link
Collaborator

davidelang commented Oct 5, 2017 via email

@alton76
Copy link

alton76 commented Oct 5, 2017 via email

@jeylites
Copy link

jeylites commented Oct 5, 2017 via email

@stale
Copy link

stale bot commented Apr 23, 2018

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.

@stale stale bot added the stale Action - Issue left behind - Used by the BOT to call for attention label Apr 23, 2018
@stale
Copy link

stale bot commented May 7, 2018

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.

@stale stale bot closed this as completed May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Action - Issue left behind - Used by the BOT to call for attention
Projects
None yet
Development

No branches or pull requests

5 participants