Switch does not go back to the correct state if the turn on / off is not possible on tile cards and more info screen

[jlpouffier]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

This is a pretty old issue, I am just taking the time to post it now.

On the Voice Preview Edition, we have a mute switch that cannot be deactivated if the physical rocker switch is enabled.

This is the behavior in the device page, on the entities page:

CleanShot.2025-05-26.at.09.52.05.mp4

On the mode info screen, and on the tile card feature, the switch never goes back to the correct state.
We end up in a weird state where some elements show the correct on state, but some show the incorrect off state.

Have a look:

More info

CleanShot.2025-05-26.at.09.52.55.mp4

Feature tile card"

CleanShot.2025-05-26.at.09.53.48.mp4

Describe the behavior you expected

I would expect the same behavior I see on the entities card on the device page.
The switch going back to the on state after a few second

Steps to reproduce the issue

1. The simplest is the use a Voice Preview Edition
2. Mute it physically with the rocker switch
3. Try to unmute it on the device page, the more info screen of the switch, a tile with a toggle feature

What version of Home Assistant Core has the issue?

2025.5.3

What was the last working version of Home Assistant Core?

I think it never worked

In which browser are you experiencing the issue?

Brave Version 1.78.102 Chromium: 136.0.7103.113 (Official Build) (arm64)

Which operating system are you using to run this browser?

macOS 15.5 (24F74)

State of relevant entities

Problem-relevant frontend configuration

Javascript errors shown in your browser console/inspector

Additional information

No response

[pghattas]

I am seeing the same thing as well. Several random entities are reporting the wrong state.

[cociweb]

The same applies to ESPHome devices, where the on_turn_on is intentionally blocked in optimistic mode. It stays in the ON state until I force it to the ON state via the ESPHome web GUI/programatically.

switch:
  - platform: template
    name: Valve 01
    id: V01
    internal: True
    optimistic: True
    on_turn_on:
      - lambda: |-
          if (!id(bool_true))  {
            #do ON stuff
          }
          else {
            id(V01).publish_state(false);
          }
    on_turn_off:
      - lambda: |-
          if (id(bool_true)) {
            #do  OFF stuff
          }
          else {
            id(V01).publish_state(false);
          }

Unfortunately, id(V01).publish_state(false); workaround does not work either.