Epson Projector is considered "off" when in warmup state

[gorstj]

The problem

When Epson Projector TW7100 is turned on it appears 'off' whilst still in the warmup state after around ~40 seconds

This appears to be an unresolved previously reported bug 55004 https://github.com/home-assistant/core/issues/55004

When in the warmup state it should appear as 'on'. (accepting it can't recieve commands in warmup state)

The on-->off-->on status when turning my projector on interferes with automations bases on the projector power status.

What version of Home Assistant Core has the issue?

core-2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Epson

Link to integration documentation on our website

https://www.home-assistant.io/integrations/epson

Diagnostics information

2023-06-02 22:25:33.987 DEBUG (MainThread) [epson_projector.projector] Sending command to projector PWR ON 2023-06-02 22:25:34.067 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:25:34.068 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:25:34.068 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 2 2023-06-02 22:25:38.453 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:25:38.453 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:25:38.453 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 2 2023-06-02 22:25:48.454 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:25:48.454 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:25:48.454 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 2 2023-06-02 22:25:58.455 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:25:58.456 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:25:58.456 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 2 2023-06-02 22:26:08.459 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:26:08.459 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:26:08.459 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 2 2023-06-02 22:26:18.459 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:26:18.459 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:26:18.644 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 02 2023-06-02 22:26:28.461 DEBUG (MainThread) [epson_projector.projector] Getting POWER info 2023-06-02 22:26:28.461 DEBUG (MainThread) [epson_projector.projector] Getting property PWR 2023-06-02 22:26:28.500 DEBUG (MainThread) [homeassistant.components.epson.media_player] Projector status: 01 2023-06-02 22:26:28.501 DEBUG (MainThread) [homeassistant.components.epson.media_player] Setting unique_id for projector 2023-06-02 22:26:28.501 DEBUG (MainThread) [epson_projector.projector] Getting property CMODE 2023-06-02 22:26:28.703 DEBUG (MainThread) [epson_projector.projector] Getting property SOURCE 2023-06-02 22:26:28.726 DEBUG (MainThread) [epson_projector.projector] Getting property VOLUME

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @pszafer, mind taking a look at this issue as it has been labeled with an integration (epson) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of epson can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign epson Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

epson documentation epson source _{^{(message by IssueLinks)}}

[Anto79-ops]

I have an Epson projector and see the same. I'm OK with this because the picture is not at it fullest/best/brightest until the lamp is warmed up. But I guess that is preference.

One way around this for instant on/off is to turn it on/off using the integration rather than the power button on the remote or unit itself.

[gorstj]

Thanks for your thoughts @Anto79-ops However it is an issue if it goes from Off-->On-->Off-->On when I use Home Assistant to turn the projector (I have an automation that alters the lights depending on the on/off status of the projector).

I have had a look at the code but I can't see where any of the timeouts or interpretation of states is based and hoping @pszafer can give me a pointer!

[Anto79-ops]

Oh, that's interesting. I have the same automation connecting my projector state to lights but I don't see this type of behavior yeah, maybe further investigation is required in this case.

[pszafer]

Once in the past I had implemented optimistic mode for Epson, but it was rejected as I recall, because in the UI it would show as ON, there will be services available like in ON state, but it wouldn't accept those command. For automation I could add attribute with current lamp state and then after turn on you could wait until attribute is Ready.

[gorstj]

Once in the past I had implemented optimistic mode for Epson, but it was rejected as I recall, because in the UI it would show as ON, there will be services available like in ON state, but it wouldn't accept those command. For automation I could add attribute with current lamp state and then after turn on you could wait until attribute is Ready.

That sounds like an awesome compromise

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.