JVC Projector - not responsive for automation

[msavazzi]

The problem

The current time (ON 6 sec - OFF 60 sec) is too long and it means that when powered on the automations will be invoked 1 minute after the project is on. This is bad as the warming is shorter and it can create issues with several items like powering on media players, amplifier settings, roller opening, etc.

What version of Home Assistant Core has the issue?

core-2024.1.5

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

JVC Projector

Link to integration documentation on our website

No response

Diagnostics information

No response

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 @steveeasley, mind taking a look at this issue as it has been labeled with an integration (jvc_projector) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `jvc_projector` 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 jvc_projector` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[msavazzi]

@SteveEasley I needed this for the pull request. As I wrote in the comment there "When in off or standby with the 60 sec the projector is checked every 1 minute. This is bad for all "power on" automations. In my case when the projector is powered on and enters in the warming status I have to power on the media player, the amplifier, open the curtain, close the shadows. All of this must be finished before the projector gets out of warming and is on... and this takes less than 1 minute. So If we check in SLOW every 1 minute in 80% of the cases the projector is on but the automation has not started, and is not good. I tested it for some time before changing it :)"

For your question on power on, no I do not use the integration to power on the projector, in fact I want HA to be in “read only” towards the projector, this is why I added the sensors and, in my case, I disable the remote. For me is too risky for me to manage the projector remotely. So the source of all automation is the projector itself. This is why is important for me to have it responsive in the Standby – Warming – On status 😊

M

From: Steve Easley @.> Sent: Saturday, 10 February, 2024 14:24 To: home-assistant/core @.> Cc: Massimo Savazzi @.>; Author @.> Subject: Re: [home-assistant/core] JVC Projector - not responsive for automation (Issue #109732)

Hey, I am not sure I understand the issue. The intervals are there just to detect changes in state (power, input, etc) made from outside the integration (like using the physical remote to power on/off).

Are you saying you are not using the integration to power on the projector? Could you maybe describe a specific situation that causes an issue?

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/109732#issuecomment-1937006911, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUJNQBGZQYZYAR4UD3F45LYS5YG3AVCNFSM6AAAAABC2OUVPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGAYDMOJRGE. You are receiving this because you authored the thread.Message ID: @.***>

[SteveEasley]

When I commented here I didnt realize you had created PRs. So deleted the comment since I was addressing my questions in the PR. But thanks for the extra explanation. Will be nice to get your improvements into the integration!

[joostlek]

One thing I still am wondering, why is it "bad" to use the projector in automations? Because if this is a personal reason that only affects you, you could just disable polling and create your own polling interval on your own instance.

[msavazzi]

@joostlek from a technical perspective projectors are very delicate machines, their lamp is delicate and should be managed correctly (i.e. minimize the number of on/off, respect cool down time, etc...). They are extremely costly (a lamp could easily be 400+€). They are quite sensitive to power fluctuation as well and often you need to have a precise power on sequence to avoid issues on the video signal. For all this reasons is not the kind of device everyone wants to manage via automations, it's ok to have the remote :) if someone needs it, but is not for everyone. Instead "reading" the status of the projector is interesting for a lot of people as they can become the source of several automations. So I think is not just for myself :)

[joostlek]

To me it just sounds like users need to think thoroughly about your automations and not just do something.

[msavazzi]

Fixed in latest merge - 5s - 10s are the new times