Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warning when requesting user for code from TVs about the screen staying on. #117526

Closed
thewan056 opened this issue May 15, 2024 · 2 comments · Fixed by #117548
Closed

Add warning when requesting user for code from TVs about the screen staying on. #117526

thewan056 opened this issue May 15, 2024 · 2 comments · Fixed by #117548

Comments

@thewan056
Copy link

The problem

My OLED TV needed to be sent back for warranty so I decided to factory reset my TV. After that was done, HA decided to notify me that I needed to reconfigure my Android TV integration. I unintentionally clicked reconfigure and the integration requested me to input a new code. Since I needed to return the TV and only readd the replacement TV on my HA I decided to close and ignore the request. I didn't realize that the TV was on and still showing the code requested by HA until a few days later. The TV still works fine, were sending it in for dead pixels, but we decided to not watch TV until we get a new one so no one entered the TV room since I factory reset the TV. Now theres the code and the UI surrounding the code burned into my TV.

I would like to see a warning in both the docs and the UI for anything that requests code from a TV that tells users the TV screen does not change or turn off without user intervention and therefore risks image retention or burn in especially if your TV is an OLED.

What version of Home Assistant Core has the issue?

core-2024.5.3

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

Android TV Remote

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

home-assistant/frontend#20796

(I don't believe adding a warning to the user interface informing the user of possible damage to their devices is a "feature request" from my understanding of English. However if I am mistaken please tell me, as you do not really make clear what goes where, which is why I originally thought this was a UI issue. This should be made more clear and simple especially since HA is going to target the average Walmart shopper going forward and there will be an influx of less technical people in the future.)

@home-assistant
Copy link

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

Code owner commands

Code owners of androidtv_remote 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 androidtv_remote 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)


androidtv_remote documentation
androidtv_remote source
(message by IssueLinks)

@tronikos
Copy link
Contributor

Fixing in #117548. The setup flows already mention that the TV will turn on but not the reauth flow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants