Closed ohadbenita closed 3 years ago
At the bottom of the app settings, there's a button to reset the frontend cache. Tap it.
Thanks that did the trick, sorry for wasting your time
On Mon, 5 Apr 2021 at 20:43 Thomas Lovén @.***> wrote:
Closed #132 https://github.com/thomasloven/lovelace-layout-card/issues/132.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thomasloven/lovelace-layout-card/issues/132#event-4552642375, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHJP7PTJK55V44B4GBJT5SLTHHZEJANCNFSM42HPWSNA .
-- https://lightricks.com/ https://www.facebook.com/Lightricks/ https://twitter.com/Lightricks https://www.instagram.com/lightricks/ https://www.youtube.com/channel/UCKWhLS9QMr1oNthZL1fZB4A https://www.linkedin.com/company/lightricks/ Ohad Benita Senior Backend Developer ▪︎ Lightricks +972-50-8246047 @.*** https://lightricks.com
Thanks for reporting back!
My Home Assistant version: 2021.3.4
Layout-card version (FROM BROWSER CONSOLE): 2.2.3
What I am doing: Using the
custom:layout-break
card to break columns in acustom:vertical-layout
card and opening this configuration in the latest version of the iOS companion app.What I expected to happen: Due to the fact that the iOS app is single column, the view is expected to load in one column without any errors.
What happened instead: An error saying "Custom element doesn't exist: layout break."
Minimal steps to reproduce:
Error messages from the browser console:
By putting an X in the boxes ([X]) below, I indicate that I: