Remote „picture“ looks distorted after installing HA core 2024.8

[amstermk]

Describe the bug

On iPads the picture of the apple-remote looks distorted after installing HA core 2024.8. See enclosed jpg.

On iPhone or Firetablet HD10 it looks fine/as it should

To Reproduce

Just add the fireremote card to dashboard on an iPad

Expected Behavior

I expect the remote to look like it should on iPad

Which Type of Device Do You Own?

AppleTV 4k gen 2 2021
IPad Pro 11inch 2nd generation

Troubleshooting Steps Completed

No response

Additional context

No response

[PRProd]

Greetings @amstermk!

Thank you for your report. I have also noticed this issue, and already opened a bug report at home-assistant/iOS#2908 - I will reference this report over there too.

-Doug

[bpectel]

I’m having the same problem

[tanderson1973]

Having similar issues using Firemote with dashboards/cards for JVC and Apple remotes only in HA desktop application MacOS, (first two images, along with HA Version) , when using via chrome browser appears as should(Last image)

![Uploading Screenshot 2024-08-11 at 7.51.45 AM.png…]()

[vasqued2]

Here is a workaround that works for me and I am curious if it works for others. If it consistently works, I expect it will help find the root cause.

1. Create a new Firemote card on the same dashboard tab that your other card/cards are on. It can be any type of remote.
2. Go into Show Code Editor mode and change the entity to any invalid entity name and save the new card. This should create a text visual for the card that simply says "Unknown entity: Invalid Entity Name from the YAML." I used the same English name I use for my remote.
3. Move this new card so it is the first one in the dashboard.
4. Refresh the dashboard on the device having problems to the Unknown entity card displays.
5. All the other cards should magically render correctly once refreshed.

The downside is you have the Unknown Entity text as the first item on your dashboard tab. I am curious if it works for everyone.

Example after adding a new card for with an invalid entity name and putting it first.

[amstermk]

Tried your workaround… and yes that works for me. So one positve feedback!

[nsleigh]

Works for me too.

[PRProd]

@vasqued2 ~ Works on my iPad too! You're a hero!

type: custom:firemote-card
device_family: amazon-fire
device_type: fire_tv_4_series
entity: Ignore me
compatibility_mode: default

This card MUST be first for the temp hack to work

[vasqued2]

@PRProd I was chasing ghosts until you pointed out the iPad/HA 2024.8.0 connection.

Once I confirmed the workaround for my card, I wanted to try it with others to see how consistent it was. Plus I was able to replace my old hacked-together Roku remote control tab with the much simpler and prettier Firemote in the process.

Thanks for your help and the card.

[PRProd]

Thanks for your kind words @vasqued2! It's so awesome to be a part of a group of people who volunteer and help each other out!

[nsleigh]

This card MUST be first for the temp hack to work

YYMV but I found it just had to be before the working remote.

[PRProd]

Update

home-assistant/iOS#2908 has been closed after a lot of very fruitful conversation by a lot of very smart people.

PR home-assistant/iOS#2918 has been merged. Another PR home-assistant/frontend#21695 has been made with the frontend team that should complete the fix for iPad rendering.

After these fixes are officially deployed for iPad OS, this issue still might persist with some older/legacy browsers and devices. I'm unsure about the impact to current Firemote users at this time. Details here: home-assistant/iOS#2908 (comment)

[piitaya]

I open a PR to fix in the weather chart card repository. Similar fix can be added to this repository to supports legacy browsers.

[PRProd]

@piitaya ~ I noticed that, and took a quick look at it. Thank you for all of your work!

I'm focusing hard on #477 right now, so I'll likely hold off on making any legacy browser fixes until I've completed that project first.

[PRProd]

The rendering issue within iPadOS has been fixed in the latest companion app update, 2024.8 released Aug 22, 2024.

Please download the latest version from the app store.

Closing issue.