yes! that would be awesome! I already had a go at that, didn’t exactly know how tbh, but if failed obviously. What would that template be? Since user-agent isn’t an attributes available in the states?
Also, if you’d add that template capability there, checking it for not Chrome would be possible too
mayker
(maykar (pronounced "maker" with a southern accent))
354
Once it’s added as a template variable (will try to get it in next release) you’d start with something like:
yes, very very nice. So short and simple. beautiful. Hope you can make it, to would really step up CH even further!
thank you so very much.
that would solve all, because:
{{ 'Chrome' and 'Mac' in useragent }}
would then be possible also, as would
{{ 'Chrome' not in useragent }}
just tested it locally with the full useragent in the {% set useragent = 'copieduseragent' %} and that works perfectly.
Is there anyway to specify a different customer header behavior for one specific tab, i.e on one of the tab I would like to enable footer mode but on the others header should stay at top? I thought previously that query_string can help about that but after several try I believe I am on wrong track.
By the way I really like this custom components great functionalities.
Hi All, stumbled across this beauty of an addon whilst trying to figure how to use a POS Chinese Tablet as a locked down interface for HA for my Airbnb guests. Kudos to all involved!
I have however noticed a very obvious work around. Despite making the exception run kiosk mode for a specific user/device, and also only allowing access to one specific tab, if the user swipes down and refreshes the page, then the sidebar appears for about 2 or 3 seconds before Custom Header kicks in with its magic. In this time the User is able to tap items in the sidebar such as Map or Logbook. Once he does that, those sections will load and the Airbnb guest can see way more information that I am comfortable with.
Now I know I can just disable Map and Logbook by disabling default_config from my configuration.yaml but I actually like those sections being in the sidebar for me and my partner. Was wondering if there is any other workaround?
mayker
(maykar (pronounced "maker" with a southern accent))
370
Build failed for some reason, its there now.
mayker
(maykar (pronounced "maker" with a southern accent))
371
I don’t think this is something that I can prevent due to the nature of how custom elements are loaded in Lovelace, the amount of custom elements you use, and the speed of the device. I will look into it, but cannot promise anything.
mayker
(maykar (pronounced "maker" with a southern accent))
372
Can you just disable the pull to refresh feature in the browser you are using or use a browser that allows you to disable it?