flex-horseshoe-card
flex-horseshoe-card copied to clipboard
AmoebeLabs
Card layout issue in App Home Assistant on Android tablet
I am using the flex horseshoe card on an Android tablet. When I open Home Assistant in Chrome, Firefox or Edge, the layout is correct. When I open Home assistant on my tablest with the App, the laytout is wrong. The problem is that the icons are placed incorrectly. The size of the icon is also larger. How can this be solved?
Same here - the floating white thing in the bottom right of this screenshot is the "light" icon from the "one bulb" default example - ignore the "geyser", I intentionally removed the icons there.
I anticipate this might be a problem with the Home Assistant app rather than horseshoe card since the card renders fine in chrome on the android device.
Same here, on Android app not correctly aligned.. xpos: is with the same value of the circle. `icons:
- id: 0 animation_id: 0 xpos: 50 ypos: 75
circles:
- id: 0
animation_id: 0
xpos: 50
ypos: 70
radius: 35 `
Similar behaviour for me, but mdi-icon is completely invisible for me in Home Assistant Companion:
Companion:
Chrome (Mobile / PC):
Card-configuration: card_02.txt
Very good news: Working for me on Android since latest beta-1534-9f3f552 of Home Assistant Companion.
Still not working for me. E.g. xpos & ypos of icon lpaces icon correctly in browsers, but it places the icon totally wrong in the Home Assistant Android app. I'm a bit surprised this is still the case after multiple years.
Still not working for me. E.g. xpos & ypos of icon lpaces icon correctly in browsers, but it places the icon totally wrong in the Home Assistant Android app. I'm a bit surprised this is still the case after multiple years.
Did you clear the frontend cache in the Companion App ?
And could you specify the Android & WebView version?
Apologies, I'm so sorry. Apparently v1.1 broke something and v1.2 fixed it again. My bad.
Apologies, I'm so sorry. Apparently v1.1 broke something and v1.2 fixed it again. My bad.
No worries. v1.1 did not contain the fix for Android. That was v1.2.
Now if that one works for you, I'm happy that I was able to fix that long standing bug!