Remote_receiver binary sensors stopped updating

ESPHome
1

I’ve been using an home made ESPHome IR Pickup for a good 18 months and it’s been 100% spot on at picking up various button presses on my Denon (Panasonic) remote.

The yaml for remote_receiver: and a typical binary_sensor is;

remote_receiver:
  pin:
    number: D4
    inverted: true
    mode:
      input: true
      pullup: true
  tolerance: 50%
  filter: 250us
  idle: 20ms
  buffer_size: 2kb
  dump: panasonic

binary_sensor:  
  - platform: remote_receiver
    name: "Bathroom MP Power"
    panasonic:
      address: 0x2A4C
      command: 0x042C0028

This ESPHome sensor (Loft-Sensor) is picked up in HA and if I press the corresponding buttons on the amp remote, the ESPHome log shows (for example);

[17:14:15][D][binary_sensor:036]: 'Bathroom MP Power': Sending state ON
[17:14:15][D][binary_sensor:036]: 'Bathroom MP Power': Sending state OFF
[17:14:15][I][remote.panasonic:070]: Received Panasonic: address=0x2A4C, command=0x042C0028

The corresponding entities have been automatically created in HA so for example - binary_sensor.loft_sensor_bathroom_mp_power

Up until this morning, pressing the ‘power’ button would cause the state of the binary sensor to go from off to on and back to off. I could then use this as a trigger for an automation.

Now the binary sensor (all of them) seem to have stopped working. I can see the sensor ‘sends’ the state change to HA but HA never reacts to it and the binary sensors state doesn’t change.

I’ve been away from home for 2 days and this was working when I left on the morning of the 18th.

I noticed that ESPHome Builder 2026.6.0 was released on the 18th and this must have been auto updated so is it likely to be this and if so, how to fix it ?

It’s not mentioned in the Breaking Changes!

HA Supervised 2025.6.1 (but same under 2025.5.3)

2

First verify it.

3

It’s working exactly how it’s supposed to and nothing seems wrong here. I suspect the problem lies with your automation and how you’ve set it up to deal with state changes.

Ya, it sends a very sequence of state changes from starting in the state Off then ON and lastly it settles back on OFF. Thats how its always worked for years and nothing unusual here that im seeing.

Hey, we all travel out of state when we go to the gentleman’s clubs in fear of being spotted by someone we know so, thats not a very good excuse bud! ; )

Seeing your automation part would likely shed some more light on this and if you post that part, ill hop in the Mystery Machine and go get my helper Scooby-Doo because he loves solving a good mystery!

4

I’ve rolled back to the previous ESPHome Builder and reinstall the firmware on my sensor and it’s all back and working as expected so it definitely breaks when I go to 2025.6

5

It definitely is not my automations as even without those, you can see that state of the binary sensor doesn’t change by looking at the logbook and history.

If I roll back to ESPHome Builder 2025.5 it all works as expected.

The only thing that changed was the auto update as my automations have run as is for over 18 months.

6

Here’s a very simple automation that never gets triggered - The states of the sensor never changes when the button is pressed on the IR Remote.


alias: Testing - Loft IR Pickup
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.loft_sensor_bathroom_mp_power
conditions: []
actions:
  - action: notify.persistent_notification
    metadata: {}
    data:
      title: Testing...
      message: MP Power On
mode: single

I have tried ‘from off’, and ‘to on’ as well as any state or attribute - all the same result.

This is what is shown in the ESPHome Builder Logs;

ESPHome-connection_4

and here’s the binary sensor as auto created by the ESPHome Integration;

binary_sensor-IR2
binary_sensor-IR2613×818 33.1 KB

I’ll stress again that all this works a expected under ESPHome Builder 2025.5.x and has worked for more than 18 months.

7

Sometimes HA rediscover a device as a new one, even though it already existed.
When that happens all entities are decorated with a _2 and these will then be used until the user intervene.
The original entities still exist, but are not receiving updates anymore.
This seems to be possible to happen to any entity in HA.

If this is the case for you, then the next time you update will probably go well and no entities will be closed, since the bug seems to occur at random.

8

Regards,

I havevthe same problem. I m detecting binary input. Detection failed after update. Sensors is not updating.

So i introduced small delayed_off 100ms and it works again.

Hope this helps.

9

I’ve checked all the entities that are auto created by the integration and there are no _x ones.

10

That will sure help, it is indicative of a bug, likely some kind of race condition. But it might not get noticed here, so I think you should post a bug report on github for this. Be sure to add the fact that a delay makes a difference.

11

I’d like to try this workaround, but I can’t figure out where to introduce this delayed_off.

12 
binary_sensor:
  - platform: ...
    # ...
    filters:
      - delayed_off: 100ms
1 Like
13

Thank you ! I can confirm that the workaround works for me also.

14

I filed a bug for this at ESP8266 Infrared binary sensors stopped triggering in ESPHome 2025.6.0 · Issue #7154 · esphome/issues · GitHub .

2 Likes