If the cache is clear, custom_header removed, kiosk mode installed and my 3.6 theme folder it should work automatically.
@msmykalov did you update browser mod and cleared your cache after updating? Also make sure you only have one instance of HA running on the same device. E.g. if you open 2 browser windows, it will trigger the popup on the windows that was seen as latest active. I am working on a fix for device ids.
Yep, I updated browser mod. I use the app for AndroidâŚ
And did you clear the cache?
No( I will try now. Itâs strange cause when I do âhold tapâ it vibrates ⌠I cleaned the cache
this is probably because you have multiple windows open (or havenât cleared cache).
Close everything to be sure, then open an incognito window, then try the popup. If it still doesnât work please check the following:
If it still doesnât work, Iâd suggest reinstalling the update (just get the update from my repo and do a copy/replace on all files, get the update file not the actual release 
)
If that still doesnât work I will suggest waiting till I find a fix. But it really should work 
I have the latest versions. Nothing helps⌠I will try to reinstall. I remember that when I updated HKI and tried to open popup - it opened
to be absolutely sure, close every single lovelace session you have (also on e.g. your phone, tablet, tv or whatever). Device_id this isnât working properly atm so this is a temporary fix. If that still doesnât work, I will suggest downgrading browser_mod to 2.3.0 I believe and then download the button templates from HKI 3.5.3 (can be found in the releases on my repo). If I remember correctly nothing really changed except for those device_idâs.
Hm, that should work fine⌠Though I havenât tried the auto-fill code in a while so I might need to revisit it for changes.
please check the following /homekit-infused/base/includes/empty-button.yaml and check if the code matches the code below
type: custom:button-card
entity: input_boolean.dummy3
color_type: blank-card
aspect_ratio: 1/1
If it doesnât then not all files were updated in your update
I have the sameâ:sweat_smile:
You did great work,HKI wonderful, in previous version here were OK)) Maybe something wrong in my configsâŚ
For the people wondering when I will ever start working on the footer again I have some great news, some people asked me why there was no footer (though there is one in the screenshots).
We know that Maykar has stopped development of CH, but thanks to a few great devs like Thomas Loven and KTibow a footer is possible again albeit in a slight different style.
Expect an update for this in the upcoming week.
Cleared cache on both Android app and browser (even tried another browser).
Issue seems to persist. Incognito mode on Chrome also shows the double header.
Everything is up to date.
This doesnât work eitherâŚ
I will release an update this weekend which will partly revert the changes to the header from last update.
This will most likely fix your issue!
Alright! Thanks for your great support. Iâll wait for the update.
Homekit Infused 3.6.1
*Welcome back precious footer
Changes:
BREAKING CHANGES (this ONLY applies to people coming from 3.6.0!):
Notes:
Tips:
!secrets on any other file than configuration.yaml and your main lovelace file. Needless to say, this doesnât work in split files. If you happen to have a split configuration I will suggest preparing for this change by removing all the secrets you might find in your config. If you really rely on !secrets then move the necessary config into configuration.yaml since that file is not affected by this change.How to update:
I will first stress out that you will have to make a backup of your current setup (as you should always do).
Drag and drop all the files into the root of your Home Assistant setup (the paths must match so if you have done it right it will ask you to overwrite files, click yes and the update is complete) Now restart your Home Assistant.
You can find update paths for each version here https://github.com/jimz011/homekit-infused/tree/updates/
Great update! Thanks for the quick work 
Hi Jim, thatâs not 100% correct. You can use secrets in all files that are included in configuration.yaml as well, meaning you can continue splitting the config with packages etc.
The issue lies with integrations that load other yaml files, just as lovelace_gen does.
Well the current beta doesnât allow secrets in split files. When I remove those secrets errors are gone 
That sounds like an issue then. For me it worked fine when I commented out lovelace_gen (for which there is a PR from petro, which I didnât test yet).