The Home app cannot update the state of the push button. #1124

phamvanan88 · 2025-10-16T09:18:40Z

phamvanan88
Oct 16, 2025

Hi, I created a push button in HomeSpan that stays ON for 400 ms, then automatically turns OFF. I updated the program, and it worked well for two days — when I pressed the push button in the Home app, the ESP32 output turned ON for 400 ms, then the relay turned OFF, and the push button in the Home app also correctly switched OFF.

However, after that, a problem occurred: when I press the push button in the Home app, the switch turns ON but does not return to the OFF state after 400 ms, even though the ESP32 output still works correctly (turns ON for 400 ms and then OFF).
I am using a HomePod mini as your HomeKit hub. Please tell me why this happens.

// ****************************** code ***********************************************
const int durt_sw=400;
class PushSwitch : public Service::Switch {
  public:
    SpanCharacteristic *power;
    int outputPin;
    unsigned long pulseStart = 0;
    bool isPulsing = false;
    //Ticker pulseTimer;
    //volatile bool resetFlag = false;

   PushSwitch(int pin,const char* name) : Service::Switch() {
      new Characteristic::Name(name);  // ✅ assign name here
      outputPin = pin;
      power = new Characteristic::On();
      pinMode(outputPin, OUTPUT);
      digitalWrite(outputPin, LOW);  //Relay OFF- High-level trigger (change to HIGH if using an active low-level trigger)
    }

    boolean update() override {
      if (power->getNewVal()) {
        //Serial.printf("🔘 PushSwitch: GPIO %d ON\n", outputPin);
        digitalWrite(outputPin, HIGH);  
        pulseStart = millis();
        isPulsing = true;
      }
      return true;
    }
`
    void loop() override {
      if (isPulsing) {
        if (millis() - pulseStart >= durt_sw) {
        digitalWrite(outputPin, LOW);     
        power->setVal(false);              
        isPulsing = false;
        // where to change code: replace above cd
        }
      }
    }
}; ```
<img width="450" height="973" alt="IMG_0594" src="https://github.com/user-attachments/assets/a1907bcc-10b3-4cf3-8681-0dffbf0d6641" />

phamvanan88 · 2025-10-16T09:19:42Z

phamvanan88
Oct 16, 2025
Author

0 replies

HomeSpan · 2025-10-17T02:20:00Z

HomeSpan
Oct 17, 2025
Maintainer

If it was working and suddenly stopped, this suggests that HomeKit is disconnecting from the device for some reason. When the issue occurs, can you still control the device from the Home App, or do you get "No Response?" If you get it into a state where it fully works again, and then it stops working, if you type 's' into the Serial Monitor, does HomeSpan say it is connected? Note that setting the Log Level to 2 will allow you to see all transmissions to and from the device so you will be able to tell if the the device is sending an off event to HomeKit after the 400ms timer runs out.

One possible reason for the device to work and then stop working is a mismatch of iOS between your phone and your HomePod mini. Make sure they are both updated to the latest version of iOS26.

1 reply

phamvanan88 Oct 19, 2025
Author

Please ignore the other devices that show “No Response” in the photo. I have other devices that I don't use, but I still don't remove them.
Let me describe the issue again:

Fan service: When I tap the fan card in the Home app, the on/off switch works correctly. It’s controlled by a toggle switch, and the state updates properly.
Switch service: This one is configured as a push button. When I tap the card in the Home app, it turns on for 400 ms and then automatically changes back to off (physical output only) (as coded), the physical output on the ESP32 responds correctly — it turns on and then off after 400 ms.
However, in the Home app, the push button card stays in the “On” state even after 400 ms. The Home app doesn’t update to “Off” immediately. It only switches back to “Off” after several minutes (or sometimes longer). I don’t know why this happens. But I remember that sometimes it is released to the off-state properly, in a 400 ms duration, as coded

Remark:

My HomePod mini is running version 26.
My iPhone is on iOS 18.7.1.
I paired the ESP32 HomeSpan device with Home Assistant first, then exposed it to the Home app through Homebridge (HASS).
So my question is: if I don’t control the device directly from my iPhone, but only through Home Assistant, could this issue be affected by iOS behavior?
this is the notice on the serial monitor:

**1. start on command:** 
16:39:25.302 -> <<<< #### 192.168.1.13 #### <<<<
16:39:25.302 -> PUT /characteristics HTTP/1.1
16:39:25.335 -> Host: 192.168.1.12
16:39:25.335 -> Content-Length: 49
16:39:25.335 -> Content-Type: application/hap+json
16:39:25.335 -> ------------ END BODY! ------------
16:39:25.335 -> {"characteristics":[{"aid":2,"iid":9,"value":1}]}
16:39:25.335 -> ------------ END JSON! ------------
16:39:25.335 -> In Put Characteristics #1 (192.168.1.13)...
16:39:25.335 -> Updating aid=2 iid=9 (okay)
16:39:25.335 -> 
16:39:25.335 -> >>>>>>>>>> 192.168.1.13 >>>>>>>>>>
16:39:25.335 -> HTTP/1.1 204 No Content
16:39:25.335 -> 
16:39:25.335 -> 
16:39:25.335 -> -------- SENT ENCRYPTED! --------

===>

2. This is a notice about the automatic update of the off-state on this push button card; I follow the state of that push button card on HASS. Whenever it changes to the off-state, I record that notice in the serial monitor.

16:40:01.367 -> <<<< #### 192.168.1.13 #### <<<<
16:40:01.367 -> GET /characteristics?id=1.5,2.9,1.7,1.13,2.6,2.12,1.10,1.16,1.19 HTTP/1.1
16:40:01.367 -> Host: 192.168.1.12
16:40:01.367 -> ------------ END BODY! ------------
16:40:01.367 -> In Get Characteristics #1 (192.168.1.13)...
16:40:01.367 -> 
16:40:01.367 -> >>>>>>>>>> 192.168.1.13 >>>>>>>>>>
16:40:01.367 -> HTTP/1.1 200 OK
16:40:01.367 -> Content-Type: application/hap+json
16:40:01.367 -> Content-Length: 282
16:40:01.367 -> 
16:40:01.367 -> {"characteristics":[{"iid":5,"value":29.3,"aid":1},{"iid":9,"value":0,"aid":2},{"iid":7,"value":75,"aid":1},{"iid":13,"value":0,"aid":1},{"iid":6,"value":0,"aid":2},{"iid":12,"value":0,"aid":2},{"iid":10,"value":0,"aid":1},{"iid":16,"value":1,"aid":1},{"iid":19,"value":1,"aid":1}]}
16:40:01.409 -> -------- SENT ENCRYPTED! --------

HomeSpan · 2025-10-19T12:29:48Z

HomeSpan
Oct 19, 2025
Maintainer

I don't use Home Assistant / HomeBridge so don't know if that may be causing an issue, but I do know that if you pair and operate just using the iPhone, they must be on the same iOS. The mix of iOS 26 on the HomePod and iOS 18 on the iPhone often creates issues with events not properly being handled on the iPhone.

Also, the above log message do not show HomeKit EVENTS, which is the standard way a HomeKit device sends updates back to HomeKit and the Home App. What is shown above seems to be HASS asking for an update to the state of all the devices' characteristics. There is nothing wrong with that, but this should only be required when an iPhone first opens the Home App after some time. The line power->setVal(false); in your code should cause HomeSpan to generate an EVENT message (it will say "EVENT" on the log output) after 400ms.

Is there a way you can pair directly without using HASS to test?

1 reply

phamvanan88 Oct 19, 2025
Author

This is the notice on the serial monitor when the ESP32 dev wroom32 runs well (switches on, then off, in 400ms), which applies to both the physical output and the state of the push button card.

20:57:44.043 -> PUT /characteristics HTTP/1.1
20:57:44.043 -> Host: Entrance\032Room\032Bridge._hap._tcp.local
20:57:44.043 -> Content-Length: 49
20:57:44.043 -> Content-Type: application/hap+json
20:57:44.043 -> ------------ END BODY! ------------
20:57:44.043 -> {"characteristics":[{"aid":2,"iid":9,"value":1}]}
20:57:44.043 -> ------------ END JSON! ------------
20:57:44.043 -> In Put Characteristics #14 (192.168.1.3)...
20:57:44.043 -> Updating aid=2 iid=9 (okay)
20:57:44.043 -> 
20:57:44.043 -> >>>>>>>>>> 192.168.1.3 >>>>>>>>>>
20:57:44.043 -> HTTP/1.1 204 No Content
20:57:44.075 -> 
20:57:44.075 -> 
20:57:44.075 -> -------- SENT ENCRYPTED! --------
20:57:44.465 -> 
20:57:44.465 -> >>>>>>>>>> 192.168.1.3 >>>>>>>>>>
20:57:44.465 -> EVENT/1.0 200 OK
20:57:44.465 -> Content-Type: application/hap+json
20:57:44.465 -> Content-Length: 49

I still can not see the homekit event, it might be the same as the notice in my last comment;
Thanks. I have 3 ESP32s. Two of them (ESP32-C3 Super Mini & ESP32-S3 Super Mini) are paired directly with HomeKit on the iPhone. The remaining one (ESP32 Dev WROOM32) was paired with Home Assistant (HASS) and exposed to the Home app via Homebridge on HASS.
My Wi-Fi: I have separate 2.4 GHz and 5 GHz SSIDs. I keep my HomePod mini and my iPhone on the 5 GHz network because I cannot play music on the HomePod if the HomePod and my iPhone are on different networks (bands). Since I realized this, I will move both my iPhone and HomePod to the 2.4 GHz network to match the ESP32s.
I already unpaired the ESP32 from HASS and paired it directly with the Home app on my iPhone. It runs well (as coded), switching on and off after 400ms (both the physical output and the state of the push button in the Home app). I thought I had found the cause of the trouble.
However, the two other ESP32s (C3 & S3) still run well even when my iPhone and HomePod are on the 5 GHz network. I don't know why the ESP32 Dev WROOM32 is having this trouble; I spent a lot of time checking my code and testing on many ESP32s.
And when I keep the HomePod on the 2.4 GHz network and my iPhone is on the 5 GHz network, the ESP32 Dev WROOM32 shows "No Response" in the Home app, but the two others still run well. Is there any difference between these chips?
We can control devices from another network when I have a Home Hub (HomePod mini). Why does the Home app suggest I move my iPhone and HomePod to the same Wi-Fi?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The Home app cannot update the state of the push button. #1124

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

The Home app cannot update the state of the push button. #1124

Uh oh!

phamvanan88 Oct 16, 2025

Replies: 3 comments · 2 replies

Uh oh!

phamvanan88 Oct 16, 2025 Author

Uh oh!

HomeSpan Oct 17, 2025 Maintainer

Uh oh!

phamvanan88 Oct 19, 2025 Author

Uh oh!

HomeSpan Oct 19, 2025 Maintainer

Uh oh!

phamvanan88 Oct 19, 2025 Author

phamvanan88
Oct 16, 2025

Replies: 3 comments 2 replies

phamvanan88
Oct 16, 2025
Author

HomeSpan
Oct 17, 2025
Maintainer

phamvanan88 Oct 19, 2025
Author

HomeSpan
Oct 19, 2025
Maintainer

phamvanan88 Oct 19, 2025
Author