If you find any information on this page useful, feel free to buy me a coffee:
Homekit Infused 5 (Lovelace) by Jimz011
This is Homekit Infused 5, a complete lovelace dashboard solution for Home Assistant.
In a nutshell Homekit Infused will turn your Home Assistant dashboard into a Homekit styled variant with a beautiful header which gives a more tablet/phone app style to your dashboard.
Note: Homekit Infused is a YAML style dashboard, this means that a basic understanding of YAML is advised. However if you follow the documentation/video tutorials you should be able to create a dashboard nonetheless. You should be able to create a beautiful dashboard without too much effort!
Homekit Infused does NOT replace any of your existing dashboards so you can rest assured that installing HKI will not destroy any of your existing dashboards. You can use Homekit Infused in conjunction with other dashboards.
In short Homekit Infused 5 is all of the below and much much more!
Having trouble convincing your partner to use HA? HKI has a really amazing WAF!
A beautiful header with notifications that is customizable per view and is added to each view for you automatically.
A customizable navigation bar which can also be set at the bottom of the screen.
An automatically created menu.
Create new views super fast by only defining a view name, title and icon. Just these lines will create a new view, a menu entry, a navigation bar button and icon and a header title, cool huh?
2 Fully customizable themes where you can change the entire look and feel of Homekit Infused in REAL-TIME!
Share your own created themes with the HKI community by creating scripts, the best themes will be added to future HKI releases!
A LOT of preconfigured addons which you can add to any of your views, by default all addons are preconfigured for fast dashboard creation.
Custom addon which allows you to use ANY home assistant card available either core or community created cards.
A fully customizable per user profile menu.
A fully customizable Alarm panel.
Known to be one of the best documented dashboards around, HKI 5 is no different and even better!
Experienced users can go fully custom YAML on a per view basis (this is particularly useful for HKI 3 and 4 users that want to migrate)
Easy updates, copy/replace 2 folders on each update!
Blazing fast frontend, even with large setups (watch my videoâs to see it in action).
Over 200+ new settings compared to HKI 4!
And MUCH MUCH I mean MUCH more!
*Note: None of the custom-cards used in this project are made by me and every custom-card used has a reference to their original creators as well as the original link to their repoâs. All contributors/donators and people that gave me the inspiration are mentioned in the docs on the last page!
You can use this thread on the Home Assistant community to ask any questions you have.
Or join me on Discord together with @dwains. You should check out his theme as well: Click Here for Dwains Dashboard.
Thank you for taking the time to read all this and I hope you enjoy this release just as much as my wife and I do. Enjoy!
Good stuff! Time to dig through this for some inspiration.
I started trying to figure out how you did that âcool popup menuâ at the very start of your video, and then I realized it was just the iOS accessibility tools.
Hello and congratulations for the excellent work !! I really like what youâve done! could you also share your configuration.yaml files and others? I would like to do something similar but Iâm not very experienced and Iâm trying to understand from your lovelace.yam file. thanks anyway and again congratulations !!
I will try to keep the repo up to date with new changes. But at the moment I am a bit tired of HA have been working 8 months straight on Home Assistant so I need a short break. Currently I am cleaning code and preparing the code to have light and dark themes and to have it change depending on the state of the sun. I will update the title of the thread whenever I push a new update.
Hi,
Great setup!
Could you please tell me about the use of the Input Booleans (and provide configuration if possible). I am trying to recreate the remote UI for my Fire Stick, but at the moment, nothing happens when I try and open the remote popup.
Thanks!
Popup cards only work if all the popup cards on that view are setup correctly. If 1 single card is configured wrong or of 1 of the entities do not exist the card will not work.
The best way to use popup cards is to first make sure that all the cards actually popup (so keep them empty at first) I would even consider adding the popup cards one by one. Read up on the docs of that specific card. Also I have to mention that you should not use popup cards if the card has lights/devices that are regularly unavailable. If one entity in the card is not found it will just show the standard more-info window.
The config of my popup cards can be found above the home view. Just try to remove all popup cards and just add a single one to try. The other cards will then just be a standard more-info window (like you have now, but that is most likely of some missing entity somewhere).
First of all, great stuff! I am learning a lot from your config.
I have a question regard your scene activation. Just wondering how you are able to have the scene button show on and off state with input_boolean.
So for example your dagverlichting scene, when pressed activates your scene.dagverlichting, then pressing it again will it turn off the lights in the scene? Or do you have to press another scene to deactivate an activated sceneâŚ
I am seeing your automation:
- alias: scene dagverlichting on
initial_state: 'true'
trigger:
- platform: state
entity_id: group.scene_dagverlichting_on
to: 'on'
- platform: state
entity_id: group.scene_dagverlichting_off
to: 'off'
condition:
condition: and
conditions:
- condition: state
entity_id: group.scene_dagverlichting_off
state: 'off'
- condition: state
entity_id: group.scene_dagverlichting_on
state: 'on'
action:
- service: input_boolean.turn_on
data:
entity_id: input_boolean.scene_dagverlichting
- alias: scene dagverlichting off
initial_state: 'true'
trigger:
- platform: state
entity_id: group.scene_dagverlichting_on
to: 'off'
- platform: state
entity_id: group.scene_dagverlichting_off
to: 'on'
action:
- service: input_boolean.turn_off
data:
entity_id: input_boolean.scene_dagverlichting
Not sure I understand how this works⌠what is contained in the groups ie. group.scene_dagverlichting_on / off? Could you please elaborate?
Thanks a bunch!
The scenes are just the same as the standard home assistant scenes. So they are âone-wayâ only. I wanted them to be more like Apple Homekit does, where the scenes are lit when activated but only if all devices in the scene matches its state. E.g. I have a scene with 3 switches, I have set it up so that when I activate the scene all 3 switches turn on. The scene will light up showing it is activated. Now imagine you turn a device off. The scene would no longer be active as the states do not match to what you have set up in the scene. So I want the scene to be unlit (turn off). But I also wanted it to light up if I would manually turn all these devices on, as normally it would only turn on if you would actuate the scene.
It is a bit hard to explain, but basically I use multiple scenes, an âonâ and âoffâ scene. The input_booleans are made as dummy switches, as scenes can not be switched on or off, but they call a service, so a button wouldnât change itâs state. The automations are made for the scenes to show the state on or off. It will always turn on if I activate a scene, and it will always turn off (or show as off, as the states no longer match the scene) when one of the devices changes its state. But I wanted the scene to be lit as well when I manually change the switches to âonâ. The automation doesnât do this, that is where the groups come in. The first group is the âonâ group which are all the devices that have to be âonâ for the scene to be turned to âonâ, in my example those 3 switches have to be âonâ. I have set it up so that the group will only be shown as âonâ when all 3 switches are âonâ.
The automations are based on those groups being on or off and they correspond with the scenes I have set up in scenes.yaml, I have only done state and not the exact brightness of entities etc. because that would take a lot more work.
Anyways this is roughly how I try to make the scenes turn on/off. Have you seen the video I posted (the top post)? It shows what it does roughly. Also I am working on making this a whole lot simpler, easier to setup with less failure (as this will never work good after a restart and you will have to press all the scenes once to get it to work again). I will keep you informed if I have an update for this. For the time being I suggest youâd experiment a bit, if you have any more questions donât hesitate to ask.
@chenchen119 I made a video to show you exactly what I mean:
Click on the image to start the video:
Please donât mind the crappy English, it is not my native language and it was late, was tired and couldnât talk too loud because of a sleeping wife (she already hates it that I spend so much nights working on HA, so canât get her mad about noise too eh ) At least she loves the results xD.
have been working 8 months straight on Home Assistant so I need a short break. Currently I am cleaning code and preparing the code to have light and dark themes and to have it change depending on the state of the sun. I will update the title of the thread whenever I push a new update.
) At least she loves the results xD.