Watch running but buttons not responsive

[SailingGreg]

Hi, the watch is working but have been unable to gain access to the configuration menu as the buttons are not responsive. Is there a trick to getting access to the menu?

[SailingGreg]

I think is because of the alignment in the case - I can assess the menu sometimes if I press button 4 which pushes the watch assembly to the left and then button 1. The other option is to take the case apart and to press button 1 directly

[pandalanax]

Before assembling i tested everything and the buttons worked. However after putting the watchy together, i get the same as @SailingGreg . Things i tried:

• USB plugged in/out
• remove the case
• charged about 30 minutes

EDIT: All while out of case:

1. unplugged and reconnected battery, no change..
2. unplugged the battery and then plugged in usb, buttons work on USB.
3. unplugged USB and reconnected the battery, buttons do not work.
4. USB+Battery connected, buttons doesn't work

[SailingGreg]

@pandalanax I have found that you need to hold the button down for the order of a second for it to be recognised

[pandalanax]

Can not confirm this.. However playing with it a bit longer revealed that out of case the button works 8/10 times with battery plugged in. When i put it inside the case, the button won't work though. Furthermore, when i get it out of the case it needs some time before the buttons work again.. definitely far away from calling anything deterministic here

[pandalanax]

wow, if you push the buttons from above and not from the side they work just fine.. seems like they don't have the right angle when pushed from the side

[lhanneus]

Same for me, the buttons do not respond.

[Brettevel]

I have found SW1, SW2 and SW3 to be somewhat responsive but SW4 to be entirely unresponsive and it feels physically harder to press. Has anyone else noticed this or is mine broken?

[exu-g]

For me it's SW1 that's having issues. Harder to press and pretty much unresponsive. Though the others also sometimes took multiple presses to register.

[ZikZakFR]

I just received it. I plugged in the battery and the screen then charged the battery. The screen refreshed properly. The wiki indicates to test calling the menu by pressing switch 1 but without any info which button SW1 is... I tried al of them and no reaction from the watch. After 30 minutes plugged-in I unplugged it and tried the 4 buttons again but still no response from the watch. Note that nothing else than the battery and the screen have been connected (no case, screen not glued to the pcb, etc.)

What can I be missing?

[ZikZakFR]

Replying to self. SW1 must be the bottom-left one, I pushed it several times (like a double-push) and eventually got access to the menu. I'm not sure what the top-left button is supposed to do but the right hand-side buttons are navigational ones and the menu seems a bit laggy. Overall I might be more an unresponsive system than a hardware glitch.

I'll now assemble everything. The wiki might need an update about the SW location and their effect.

[exu-g]

@ZikZakFR It's not that obvious, but SW1-4 are links that lead to the Hardware layout.
https://watchy.sqfmi.com/docs/hardware#bill-of-materials
There the switches are labeled.

[ZikZakFR]

Thanks, of course with this picture it helps a lot. So SW2 is what seems to be a back-to-home-screen.

Watch is now almost fully assembled (minus the glass) and actually with the plastic buttons the switches seems to register way better, compared to other reports above.

[PyroDevil]

I initially had problems with the buttons as well. See #43

[SailingGreg]

I've tried a bit of duck tape on the back of the buttons for the plastic case to take some of the slack out and that seems to improve the responsiveness for buttons 1 & 2 but has not helped with buttons 3 & 4

[bserinese]

Button 4 is very unresponsive for me, even when out of the case. SW1 and SW2 work fine for moving up and down the menu, but it is difficult to enter with SW4. Took 20 minutes to change the time. I'm hoping this is a software issue and not hardware.

[rainer38]

I also have problems with the buttons. While the PCB is outside the case they do work but not very good. But as soon as i put the PCB in the case the buttons (mainly SW1) doesn't work anymore. No matter how i try to press it nothing happens.

I have to investigate what i can do and will try to directly bridge the button on the PCB and see if this works.

[rainer38]

I tried to assemble the PCB and case again and now i have paid attention about the routing of the battery cable. Because there are a few positions where the cable overlaps some quite high components and i have the feeling it gets some pressure on the PCB when i screw it together. So this time i bend the cable a few times to get sure it lays quite free inside the case and now it seems much better with the responsiveness of the buttons. I can press all buttons and they do react as expected.

Interestingly SW1 is still the one i have to press the hardest to get it to work and it doesn't get recognized all the times. SW2-4 seems to works quite good. So for the moment i can live with the current state of the buttons.

[SailingGreg]

@sqfmi is there an issue with the switches that used are on the board?

[botmayank]

Hey I've also faced an issue with the switches, is there any indication if its a firmware or a hardware issue? I've re-assembled the buttons and the battery wire etc 2-3 times now, and am pretty confident nothing is damaged and assy is more or less spot-on. Even directly pressing the button (especially SW1) without the plastic part is flaky at best.

[bensonk]

I got my Watchy a few days ago and have been having this problem too. When I read the thread here, I realized that it's at least partly a hardware problem. I took it apart, and found that the injection molded buttons had a bit of an overhanging edge on them, which seems to be where they were broken off of a sheet. Filing down the back of the button so it's smooth seemed to help a lot.

I also noticed that the PCB had a similar finish -- that the flat part of the PCB the buttons press against had a bit of a jagged overhang. I very carefully filed that smooth also.

My buttons now work much better, but I still wouldn't call them reliable. The way they operate now feels like firmware rather than hardware. I suspect there's something holding control of the CPU for longer than we'd like, which then makes it impossible for it to detect the button press.

[botmayank]

My buttons look smooth and I was able to do a sanity check for continuity on the legs of the switches, seems OK. I wonder if I need to touch up the solder. At this point I think the handleButtonPress() method in https://github.com/sqfmi/Watchy/blob/master/src/Watchy.cpp is a bit bulky and leading to missed presses.

In case anybody else wants to try, with the switch released, 1 and 2 are shorted and 3 and 4 are shorted. So when you press the microswitch, 1/2 should short to 3/4.

       Button
         TT  
1---| ````````|---2
3---| ,,,,,,,,|---4

[thoop]

Loving my watchy so far! I am only having trouble with the bottom left button.

I found a simple example of usage of the ext1 wakeup from deep sleep on the internet and changed it to use the watchy GPIO's. I am still seeing missed button presses on the menu button (buttom left) when the other buttons are always working 100% as expected. That at least points to the Watchy.cpp code not being the issue.

I saved this in a separate .ino file and uploaded this (and only this, no Watchy.cpp) to my watchy for testing:

/*
Deep Sleep with External Wake Up
=====================================
This code displays how to use deep sleep with
an external trigger as a wake up source and how
to store data in RTC memory to use it over reboots

This code is under Public Domain License.

Hardware Connections
======================
Push Button to GPIO 33 pulled down with a 10K Ohm
resistor

NOTE:
======
Only RTC IO can be used as a source for external wake
source. They are pins: 0,2,4,12-15,25-27,32-39.

Author:
Pranav Cherukupalli <[email protected]>
*/

//original example
//#define BUTTON_PIN_BITMASK 0x8004 // GPIOs 2 and 15

#define MENU_BTN_MASK GPIO_SEL_26
#define BACK_BTN_MASK GPIO_SEL_25
#define UP_BTN_MASK GPIO_SEL_32
#define DOWN_BTN_MASK GPIO_SEL_4

#define BUTTON_PIN_BITMASK MENU_BTN_MASK|BACK_BTN_MASK|UP_BTN_MASK|DOWN_BTN_MASK

RTC_DATA_ATTR int bootCount = 0;

/*
Method to print the reason by which ESP32
has been awaken from sleep
*/
void print_wakeup_reason(){
  esp_sleep_wakeup_cause_t wakeup_reason;

  wakeup_reason = esp_sleep_get_wakeup_cause();

  switch(wakeup_reason)
  {
    case ESP_SLEEP_WAKEUP_EXT0 : Serial.println("Wakeup caused by external signal using RTC_IO"); break;
    case ESP_SLEEP_WAKEUP_EXT1 : Serial.println("Wakeup caused by external signal using RTC_CNTL"); break;
    case ESP_SLEEP_WAKEUP_TIMER : Serial.println("Wakeup caused by timer"); break;
    case ESP_SLEEP_WAKEUP_TOUCHPAD : Serial.println("Wakeup caused by touchpad"); break;
    case ESP_SLEEP_WAKEUP_ULP : Serial.println("Wakeup caused by ULP program"); break;
    default : Serial.printf("Wakeup was not caused by deep sleep: %d\n",wakeup_reason); break;
  }
}

/*
Method to print the GPIO that triggered the wakeup
*/
void print_GPIO_wake_up(){
  uint64_t GPIO_reason = esp_sleep_get_ext1_wakeup_status();
  Serial.print("GPIO that triggered the wake up: GPIO ");
  Serial.println((log(GPIO_reason))/log(2), 0);
}
  
void setup(){
  Serial.begin(115200);
  delay(1000); //Take some time to open up the Serial Monitor

  //Increment boot number and print it every reboot
  ++bootCount;
  Serial.println("Boot number: " + String(bootCount));

  //Print the wakeup reason for ESP32
  print_wakeup_reason();

  //Print the GPIO used to wake up
  print_GPIO_wake_up();

  /*
  First we configure the wake up source
  We set our ESP32 to wake up for an external trigger.
  There are two types for ESP32, ext0 and ext1 .
  ext0 uses RTC_IO to wakeup thus requires RTC peripherals
  to be on while ext1 uses RTC Controller so doesnt need
  peripherals to be powered on.
  Note that using internal pullups/pulldowns also requires
  RTC peripherals to be turned on.
  */
  //esp_deep_sleep_enable_ext0_wakeup(GPIO_NUM_15,1); //1 = High, 0 = Low

  //If you were to use ext1, you would use it like
  esp_sleep_enable_ext1_wakeup(BUTTON_PIN_BITMASK,ESP_EXT1_WAKEUP_ANY_HIGH);

  //Go to sleep now
  Serial.println("Going to sleep now");
  delay(1000);
  esp_deep_sleep_start();
  Serial.println("This will never be printed");
}

void loop(){
  //This is not going to be called
}

In the Serial output when running this example, the pins are: GPIO 25 = top left GPIO 32 = top right GPIO 4 = bottom right GPIO 26 = bottom left (the one with the issue)

[aborzanovic]

Having a similar issue, my Watchy's bottom left button only works without the enclosure and when pressing as hard as I can. And even then it only works every 5th time. :(

[ma-mueh]

Same issue here, watch arrived today. All buttons except SW1 seem to work relatively well. Without the case sometimes opening the menu works, however with the enclosure in place I can't open any menus at all.

[GuruSR]

The buttons do work, though I think it is basically CPU lag happening. The device goes into deep sleep between screen changes, I notice when it does, the buttons respond rather quickly, then not, not sure if they're causing the CPU to exit deep sleep.

[Brettevel]

That would make sense, I do think the general unresponsiveness is a software issue as I noticed that they seem to be more responsive when using the 'basic' example. Although there is one button for me that is definitely physically harder to press and even when other buttons are working somewhat as expected it is barely working at all.

[PrimalNaCl]

What I have been able to reproduce is that I get ONE shot at the menu working after a reset. So I have to upload a sketch (because it's in the enclosure and I'm not going through that bullshit process of cosmological planetary alignment of resassembly again) so that I can get it to reset and THEN I can get into the config menu ONE time.

It's truly hateful. Why does the compilation take so abysmally long? I'm on a surface laptop 3 running win10. Process load throughout is less than 20% and it takes a good 5 minutes to compile even the basic face.

[Nurgak]

I have the same issue: new Watchy, perfectly assembled and working, but bottom left button somewhat unresponsive.

When pressed hard (harder than I would like to press an SMD button from the side), I can eventually get into the menu. I don't have to press any of the other buttons as hard to register a press.

I really hope this is related to firmware. No time to investigate right now and it's not hugely problematic, but it would be nice to get to the bottom if it.

[brianmay]

@Nurgak If you haven't already done so, have a look at #84. This could be your issue.

[rroels]

I have the same issue, my "menu" button only works about 10% of the time. This particular button is not as clicky as the others. It even sounds different. A very hard press is needed to trigger it.

This is a very minimal firmware that does nothing except read/print the button state in a continuous loop:

#include <Arduino.h>

int btn_menu = 26;
int btn_back = 25;
int btn_up = 32;
int btn_down = 4;

void setup(){
    pinMode(btn_menu, INPUT);
    pinMode(btn_back, INPUT);
    pinMode(btn_up, INPUT);
    pinMode(btn_down, INPUT);
    Serial.begin(115200);
}

void loop(){
    int state_menu = digitalRead(btn_menu);
    int state_back = digitalRead(btn_back);
    int state_up = digitalRead(btn_up);
    int state_down = digitalRead(btn_down);

    if ( state_menu == HIGH ){
        Serial.print("menu\n");
        delay(500);
    }
    if ( state_back == HIGH ){
        Serial.print("back\n");
        delay(500);
    }
    if ( state_up == HIGH ){
        Serial.print("up\n");
        delay(500);
    }
    if ( state_down == HIGH ){
        Serial.print("down\n");
        delay(500);
    }
}

This confirmed it's a hardware issue and not a software issue. Clearly it has nothing to do with lag, or deep sleep, or interrupts or whatever. The button has a mechanical issue that makes it harder to press.

However, the weird thing is that more people have this issue and it's always the same button... On discord I've heard of others with a "mushy" button, and it's always SW1, never any of the others. Makes me wonder if there is anything in the production process that causes this...

Because of how the button feels (less "clicky") I don't think it's soldering issue either. I believe it's really a mechanical issue with the button itself. I ordered replacement buttons and they should arrive later this week. I couldn't find a source for the original buttons, but these have exactly the same dimensions and specs: https://www.mouser.com/ProductDetail/710-436333045822 https://www.mouser.com/ProductDetail/710-434351045816 https://www.mouser.com/ProductDetail/710-436351045816

I wasn't sure which ones would be the best match, so I purchased some of each. I will give an update if that fixed it for me.