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

Aesthetic adjustment to correctly display a samsung remote custom card #18

Closed
Ninuss opened this issue Sep 17, 2021 · 4 comments · Fixed by #27
Closed

Aesthetic adjustment to correctly display a samsung remote custom card #18

Ninuss opened this issue Sep 17, 2021 · 4 comments · Fixed by #27

Comments

@Ninuss
Copy link

Ninuss commented Sep 17, 2021

Hi, I tried looking in the code to find the spot where a layer of the Samsung remote controls is displayed shifted by a large amount of pixels to the right in the Home Assistant dashboard. I have not succeeded. I attach some screenshots to immediately understand the imperfection, circled in red I highlight the card and the horizontal navigation bar. Everything is perfectly functional anyway, but, if I can also be a little more precise, the lower part of the photo of the remote control would be missing, but that's not a problem, just a simple detail. Thanks in advance for your reply.

Desktop Screenshot 2021 09 17 - 10 55 51 78_LI

Desktop Screenshot 2021 09 17 - 10 56 07 61_LI (2)

@dimagoltsman
Copy link
Owner

closing as inactive

@FrancYescO
Copy link
Contributor

i still have this bug

@si458
Copy link
Contributor

si458 commented Jul 17, 2022

I have the same problem here but with the apple tv 4k remote?
It renders the image on the left but then you scroll all the way to the right and you find random text string for each button?

@mitchan95
Copy link

I have this same problem with the LG_new remote - tried implementing the fix used here for the samsung remote but it did not work

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

Successfully merging a pull request may close this issue.

5 participants