EDIT: I see the Alpha has been released … should look before i leap
Let me lead into another question the @jimz011, if you are saying that all that is needed is to create groups can i ask if you are able to give a preview of the two files that will be getting edited.
I am keen to roll out your new version when it arrives but if i could see what these two files will look like i can start the work of reorganising my HA instance to make it easier when it does become available.
The Screenshot look amazing!!!
Can’t wait to try it, great work man!
Well, for the basic installation all you would need to edit are these 2 files:
By installing it and filling in these 2 files you will have at least the following views working and filled with your own entities:
If all is right, these views should all work with just filling in those 2 files I mentioned above.
Also, the following popup cards should work when you filled in that file:
All the unmentioned views can be edited to your own likings (and if you really want to you can just edit the mentioned views as well just like you would do with my previous versions). The 2 mentioned files are only used for auto filling lovelace.
If you use decluttering-card note that you will have to put them into another folder than /templates/ as all lovelace_gen templates live there now and they might cause errors. If you have placed the decluttering templates in a new folder don’t forget to change its path within ui-lovelace.yaml.
You can put your own created cards into any view you want. It will NOT affect the autofilling of those views unless you remove lines. You can use the empty views (the ones not mentioned) to create your own views with them. Only the header is precoded so you can start right away. Obviously you can simply change anything you want as it is just as modular as you were used to.
The alpha title is there because I haven’t had the chance to install this on a clean setup and test it other than that it should work just as well.
I hope I have informed you well enough,
You could also read the documentation
That is great to hear, let me know if you face any troubles.
@jimz011 i have one small suggestion for your documentation, it is very thorough and i look forward to the late nights doing this all again but it would be helpful (for me anyway) if you add a section entitled hardware.
In that section it would be awesome to see a list of all the hardware you use for this so that if i want to replicate any features i don’t already have i know what i should be looking for.
Ok, that sounds cool. I will add that to the documentation, will edit it tonight as I think that is a great idea.
However, most of the code is made for any hardware. The auto filling templates don’t care if you use a sonoff, koogeek, tradfri or hue. It only cares about the type (switch, light or climate for example).
The only views you might face trouble with other hardware is the remote control view (and maybe vacuum, but I will have an answer to that soon).
I’m browsing your GitHub 
and just wondered what {% raw %} does?
As in…
# lovelace_gen
# card
type: custom:simple-weather-card
{% raw %}
style: |
ha-card {
border-radius: {{ states('input_select.border_radius') }};
box-shadow: {{ states('input_select.box_shadow') }};
opacity: 0.8;
font-size: 12px;
font-family: Helvetica;
}
{% endraw %}
Lovelace_gen adds jinja2 templating to lovelace. However some cards like markdown card and card-mod also support jinja templating. The RAW line makes sure that lovelace_gen doesn’t parse the parts within those RAW lines as the card should handle it instead of lovelace_gen. Without it lovelace_gen will try to parse it, and because lovelace_gen doesn’t know about states it will throw errors.
This is only necessary on views with # lovelace_gen And is only needed if there are other jinja templates within that card/style.
Edit: https://github.com/thomasloven/hass-lovelace_gen#what-if-i-want-jinja-in-my-lovelace-interface
Just set this up, took me around 30 minutes to get the minimum running, now the tweaking starts. So far it looks amazing, fantastic work, great documentation. 
I’m very glad to hear that. I didn’t have the chance to test it other than on my own machine (which will obviously work). So I hope the docs are thorough enough.
I will look into making the setup multilanguage as it is English right now. Though that might take some time as I don’t know how I want to do this yet.
I also wonder if the autofilled views work fine for you. (Namely frontpage, lights, switches, security, battery and climate views)
Docs were fine for me, but I’m pretty used to home assistant in general and have experience in lovelace as well, so I don’t know if I’m a good measure.
The views autofilled as expected. Will do some more testing on the weekend.
Another question, do the popups work too? Namely lights (rgb, color temp and switches?) thermostat (you should see a arch style slider) and last question. Do the badges on the frontpage work (the ones showing how much lights are on? They have a popup too btw)
Didn’t test those yet and I don’t have a thermostat (could setup a generic one for testing if you like). The badges work fine for me. Changed back to my old config until I find some more time for tweaking and testing.
By the way, I found a small error in the frontpage view. The navigation path for the light button is /lovelace/light however the path in the light view is lights not light
That is great news, I actually feared that it would be too hard (as my older versions are imho a lot harder to configure) but it seems it isn’t too hard after all? Thanks.
Well thanks for testing it, I will upload the fix later!
I think it was relatively easy to setup, installing the cards is a piece of cake with HACS. Copying the files was also easy, then filling out the entities was fast with the VS Code plugin.
I didn’t do more, just wanted to do a quick test. I think the fine tuning will take some more time, but that’s anyway different for everyone.
How is this looking on a tablet? Can anyone share some screenshots?
Thanks!
Well, uhm I am actually trying to create some video’s now. However, I can tell you that it is not optimized for tablets as I have fixed everything into a vertical-stack. It will look exactly the same on a tablet when used in portret mode, just slightly bigger.
I am working on a tablet version (yes I know I have said that for months) but I had to get this mobile version out first. Because that is done, I can start on the tablet version. Though I have to warn that it works a lot better on newer tablets than on older ones.
Hi @jimz011
Thanks for all your continued work and for sharing your amazing lovelace setup, I don’t use it exactly but have learnt so much looking through your configs and how it all goes together.
Just when I got my head around building my setup using decluttering-cards you’ve completely rewritten all the code using lovelace_gen, so back onto the learing treadmill I go lol.
One quick question, I’ve looked through the new config briefly and note that you use many of the same mdi icons on buttons that I do, however in the screenshots you’ve uploaded your icons looks very different to mine, do you use a different subset or something?
Thanks again
Brad
Somewhere in the documentation it is written that he uses other icons for his personal setup from the pro version of FontAwesome.