If you check your text logs, they are all there. Also, have you tried card-loader? It’s a custom card that forces cards to load in a specific order. It recently got rid of a few of my errors.
EDIT: You have, I didn’t read your full post. Please ignore me.
mayker
(maykar (pronounced "maker" with a southern accent))
733
Searching your issue and this popped up:
Do you experience the same thing as the people in the comments here?
I don’t think that this is coming from CCH (could be wrong). I will look into it though.
mayker
(maykar (pronounced "maker" with a southern accent))
734
Keep CCH commented out in your resources section for a while and be sure to interact with HA a good bit, click around to history, hassio tab, etc. and see if the error pops up again. If it does, then we can rule CCH out.
Is it possible to use Compact Custom Header for setting a different Lovelace UI view for Mobile and Tablet respectively?
Because the width of tablet is wider, causing all my card components to spread across wide width.
Thanks.
mayker
(maykar (pronounced "maker" with a southern accent))
736
Yes, make an exception config for the tablet and mobile. If they are always the same tablet and mobile device use user_agent, if not use media_query. Then hide views/tabs to show certain views to one and not the other.
I did just delete all my views and just added a standard entity card, set it to the default theme, restarted and it keeps appearing. So it doesn’t seem to be any custom cards’ fault!
1 Like
mayker
(maykar (pronounced "maker" with a southern accent))
738
Just pushed a small update to conditional templates to avoid confusion between this and other template implementations as well as help those that are used to Jinja templates.
Can now use return in templates if you prefer.
Can use either entity or states in templates.
I adjusted wiki examples to use states, but there’s no difference between the two examples below. Use whichever you prefer (not a breaking change).
So now that we have swipe capabilities via CCH, I noticed an interesting behavior which is both unsurprising and somewhat problematic. In my implementation, the swipe feature engages when interacting with cards that have a horizontal slider. I’m not sure what, if anything, can be done to curtail this behavior. Thoughts?
mayker
(maykar (pronounced "maker" with a southern accent))
747
I can probably do something about that. What cards are you using that scroll horizontally and are you using prevent_default?
just so I get it right, should the swipe feature cause movement in the views, when only moving from left to right (and vv) in the menu? Without selecting a new tab that is. Its not that it selects another view, but it seems to reload it from the side the swipe went…
I find it very difficult to swipe through the menu, but it might be an app issue?