Ahh OK, thanks @Burningstone I’ll look into it further.
1 Like
@jimz011 i am going through the global config and as per your screenshots you have two pictures and a middle one.
Being a family of four i was wondering if i need to do anything special to get four pictures on the frontpage in a grid format. e.g two on one row and another two on the bottom row ?
1 Like
Check out the frontend.yaml file in the lovelace/views folder. With the information in there you should be able to remove “tala” and add two new persons with the same methodology as the first two.
1 Like
Very good question. Well yes, you would have to make slight changes. You will have to change the frontpage.yaml (in views) and put the middle photo in a horizontal-stack (and copy it so that you’d have two pictures).
You could simply hardcode the entities instead of using the global config. However if you do want to use global config, I’d recommend you to read up on how lovelace_gen works.
Basically the global config consists of categories and within those categories there are dictionary values. E.g.
rooms:
- living
- bedroom
- office
To call one of these values you’d simply put in _global.rooms[VALUE_HERE]
Replace value here with a number where the first item in the list is 0.
You don’t need to use the global config though. Hardcoding like you were used to will work just as fine.
I will add some different templates if desired for example a frontpage template which has 4 pictures or even 5. Or a template that only has 2. If you want me to create that let me know and I will put them in the addon branch of my repo (it isn’t created yet).
Hey Jim,
trying to make coffee (…) of you setup, Ive copied a few files and try to get them to work. What I was wondering is if in the frontpage_header template you’ve not made a typo, and miss this here:
- type: conditional
conditions:
- entity: alarm_control_panel.ha_rpi4_alarm
state: 'armed'
card:
if not, why is this not in the same indent?
1 Like
Hey, just set this up on my own installation, been watching this thread waiting for you to release it eagerly!
Couple of notes from the documentation. First, on the Installation page, the three manual plugins are now available via HACS (unless there’s a reason we should be installing them manually…?)
And secondly, on the Configuration page you talk about editing notifications.yaml but don’t say where it is, I was able to do a search but it would be handy to tell people where they can find it.
Great job, looking forward to customising this for our home!
1 Like
I was looking at my own code and couldn’t find it immediately. I did find it though, it is because it is already inside a conditional card (namely the swipe-card) this card has to be shown always when the alarm is armed. However the smoke sensor should only be shown when the alarm is triggered.
So that is the reason that it doesn’t have the same indent.
ok thanks, good to know! continuing the exploration 
1 Like
Ah very good, I will change that in the docs.
Yes the manual plugins are on HACS now (they weren’t when I wrote the docs). Though 2 of them still need my changes that I did to the js files (namely light and thermostat popup card).
Let me know if you face other problems.
So thanks for the work you did here, i have it working (i think).
I dont have alof of sensors that you have so my frontpage doesnt look even close on what it is, and i am almost thinking that i am doing something wrong here.
for example the menubar it only shows when i refresh the frontpage for a few seconds, after that it disappears again.
i will keep adding my stuff to see if i can get close to what it should be.
i have a fresh installation so i can play around all i want.
Could you please send me a screenshot? The frontpage should work regardless.
If you are looking for the original header/menu bar, well it doesn’t exist in my setup. You can find the original header at the bottom if you install it correctly.
A screenshot would help.
Thanks @jimz011 … one quick thing while your online … why am i getting the following error message in Check Config ?
Error loading /config/configuration.yaml:
in "/config/configuration.yaml", line 58, column 15: Unable to read file
/config/configuration/lovelace_gen/lovelace_gen.yaml.
I can seem to find it in your Github either
Hm seems like you used my configuration.example.yaml example.
In your configuration.yaml, change the following line:
lovelace_gen: !include configuration/lovelace_gen/lovelace_gen.yaml
To
lovelace_gen: !include global_config.yaml
It shouldn’t be that path, so I guess you have taken it from the example and not from the actual provided configuration.yaml file (so not configuration.example.yaml).
Let me know if this fixes it for you.
thats all i have, it almost looks like alot of plugins are not loaded.
log files are full with errors:
2020-01-22 16:51:55 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
2020-01-22 16:51:55 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
2020-01-22 16:51:55 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
2020-01-22 16:51:55 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
2020-01-22 16:52:00 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
2020-01-22 16:52:00 WARNING (MainThread) [homeassistant.helpers.condition] Error during or-condition: argument of type 'NoneType' is not iterable
Hm, ok it seems the header is working fine (just not well enough configured yet). Though it says the alarm is armed (not sure if this is the case though). But if it is, that is the reason why you don’t see the buttons.
Also did you copy the ui-lovelace.yaml file from my repo? (I guess you did but you never know).
I think that you do not have an alarm (am I correct?) if so please use the optional-configuration provided on my repo. It creates a manual alarm which you can configure later on. It will help you showing the display though.
I don’t see the footer, but that might be the screenshot?
@Mkipz I see you are Dutch?
You can join my Dutch slack group so I can give you proper support if you’d like.
For english slack please refer to my first post in this thread.
Yes header is working fine, indeed the alarm is armed but i dont have one.
i did copy your ui-lovelace.yaml file.
i will add the optional configuration, everything or just the alarm?
Yes footer is because of the screenshot.
have another question for you, sorry…
configuring some notifications, I try to use this in the notifications.yaml:
- type: conditional
conditions:
- entity: binary_sensor.critical_devices_offline
state: 'on'
card:
!include
- '../templates/template_notification.yaml'
- icon: mdi:alert
# [[[ return 'mdi:numeric-' + states['sensor.count_critical_devices_offline'] + '-box'; ]]]
name: >
[[[ return `${states['sensor.critical_devices_offline'].attributes.message}` ]]]
spin: true
this works fine, so I know the condition is correct, and the message is displayed (its truncated I think, but that’s a detail…)
Im trying to template the icon though, and in regular JS it would be like commented:
[[[ return 'mdi:numeric-' + states['sensor.count_critical_devices_offline'] + '-box'; ]]]
this doesn’t show. tested the html variant (I think) like:
- icon: >
[[[ return `mdi:numeric-${states['sensor.count_critical_devices_offline']}-box` ]]]
doesnt work either though, so, being new to the Lovelace-gen specifics, would like to ask you if and how we can template in this field?
thanks!
edit/update
NM… found it, missed the .state:
[[[ return `mdi:numeric-${states['sensor.count_critical_devices_offline'].state}-box`; ]]]
does it!
let me compare (can’t see your setup yet) is this what’s supposed to happen:
I just joined. thanks!