Well, if you want the setup to be like mine you don’t have to edit any of the preprogrammed views (only the 2 files mentioned in the docs) however ofc if you want to customize it you can and you have all the freedom there.
I will push out some fixes in an hour or so. Updating should be relatively simple with my provided instructions.
Regarding the imap sensor, do you use mine or the official one? If you downloaded my modified version from my repo it might not work with gmail as I have modified it to work with outlook/hotmail (which the core version does not do). However if the core one doesn’t work for you it wouldn’t hurt trying the modified one on my repo (I don’t use gmail, so I haven’t tested that)
I will keep my entity names as I have too many, so I have to update your views and templates. For example legacy_popup_cards contains your person entities, so have to update it.
I’m using the core version (I tried yours with the same result). It could possibly comes from my 2 steps validation on my gmail account but I’m not sure and I haven’t find any ressources on google.
Thanks for your job by the way ! There’s a lot of good stuff in your setup
Ah yes, legacy popup_cards is one thing that wasn’t easy to do. I wish I could automate it like the views. Btw, you don’t need to put in entities like lights, switches, thermostat, sensors and binary_sensors. This is all handled by the template itself. The popup card for lights and devices and such is preprogrammed and the right entity will always be chosen. Though it also means that you’ll be stuck with the popup card I created.
Though obviously you can change whatever you want. I just wanted to mention that if installed and you fill in the 2 files provided (groups first, global_config last) then the following views will work out of the box without any editing of views and/or popup cards. The things that will work automatically are the following
views:
climate
lights
devices
security
alarm panel
frontpage
weather
battery
location
menu
about
test
vacuum (depending if you did install the extra automations/code from the optional folder)
waze traffic
laundry room
themes
cleaning
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:
light and switch popups (rgb/color_temp/switch)
thermostat popups
all popups within the weather and vacuum views
all sensors and binary sensors popups
all frontpage popups
Essentially what this means is by filling just those 2 files (nothing else and no editing of other files) you will get all of these elements working. The legacy popup cards are meant for cards that can’t do a service_call and only have a more-info window when pressed upon. In all other cases I have replaced popup cards with browser-mod which simply does a service-call (and thus use the same template for each button, sensor, thermostat etc etc.)
Ofc this is not a requirement and you can edit the setup just as much as you want as I wanted it to be a thing of 2 worlds (easy to setup/use for people that don’t want to edit a ton of views, but modular enough to have it customized).
Okay that’s good to read I will probably have less work than I thought
For Imap with Gmail I made it work. It was because I have two step validation on my account. In that case you have to generate an “application password”. It’s a different password that gives access to your account. It’s possible to do that in the Security panel on your google account page. Than in your secrets.yaml you can just paste this password instead of your google account password
@jimz011 i have finally after almost 24 hours and numerous shouting matches at the screen got things up and running, as stated though there is a couple of weird things coming up that i will probably seek your assistance on, biggest bug bear is the lights button doesn’t open (May be because my lights are actually switches?!?) and the customizer integration keeps crashing my HA.
I do however have a bit of feedback from my experience that may be useful to others;
The customize.yaml file has Font Awesome icons in it, maybe for your github would be best sticking to the MDI icons as its a whole other number of steps to add in the Font Awesome
I kept losing my front end view when i first made the changes, turns out in the configuration.yaml you cant have default_config: and default: has to be one or the other… who would know lol
If anyone is using a NEST thermostat warn them against doing a fresh install as currently they cannot be added as an integration into HA. If you already have it all good, but if its removed for whatever reason you wont be able to add it back in until Google resolves the problem.
When people are ‘Not Home’ it no longer greys out the picture on the landing page, it was a nice feature though i suppose personal taste. (sure i could copy the old code)
You used to have a notifications.yaml file in the lovelace folder, has this been replaced with /templates/frontpage_header.yaml ? Wasn’t clear on that
There seems to be an issue with the Themes, during a Check config i get the errors shown below, remove the theme files and the configuration comes back valid
Invalid config for [frontend]: expected a dictionary for dictionary value @ data['frontend']['themes']['accent-color']. Got 'var(--md-teal-A400)'
expected a dictionary for dictionary value @ data['frontend']['themes']['area-color-off']. Got 'white'
expected a dictionary for dictionary value @ data['frontend']['themes']['area-color-on']. Got 'Gray'
expected a dictionary for dictionary value @ data['frontend']['themes']['background-image']. Got 'center / cover no-repeat url("/local/images/wallpapers/valentine-test1.jpg") fixed'
expected a dictionary for dictionary value @ data['frontend']['themes']['border-radius']. Got '12px'
expected a dictionary for dictionary value @ data['frontend']['themes']['box-shadow']. Got '2px 2px 2px 0px rgba(0,0,0,0.75)'
expected a dictionary for dictionary value @ data['frontend']['themes']['button-card-light-color']. Got 'var(--primary-color)'
expected a dictionary for dictionary value @ data['frontend']['themes']['button-card-light-color-no-temperature']. Got 'var(--primary-color)'
expected a dictionary for dictionary value @ data['frontend']['themes']['card-background-color']. Got 'rgba(100, 100, 100, 1.0)'
expected a dictionary for dictionary value @ data['frontend']['themes']['card-color-off']. Got 'linear-gradient(to bottom right, #e0e0e0, #910039)'
expected a dictionary for dictionary value @ data['frontend']['themes']['card-color-on']. Got 'rgba(255, 255, 255, 1.0)'
All in all though, awesome work, awesome product … for an Alpha its pretty good.
If you don’t mind i am happy to feedback any issues i face as i progress ?
Hi @andrew.vint, thank you for your feedback (it is always appreciated). I will try to answer all the questions to satisfaction.
the customize.yaml file is actually an example file and should not be copied. It is meant as an example so that people know how they can create their own version. The examples will be removed from the master branch so that people will no longer face that problem. I can put in an mdi variant in there if desired. But seeing people don’t have my specific entities, they would need to do it themselves anyways.
default_config: and default: are not allowed together no. This is actually not something caused by my setup, but just the way HA handles it since a bunch of versions ago. I ask people to use default_config because a lot of times people don’t keep up with the HA updates (which I totally understand) and fall behind in stuff that has become the default for months and thus might miss some basic domains like person or mobile_app just because they have an old config. Default config basically replaces all of the following config within configuration.yaml (https://www.home-assistant.io/integrations/default_config/). These domains are now all loaded by just having this single line (it is no longer needed to define them separately in configuration.yaml).
For that reason my documentation also recommends you to do this on a clean install (because that will eliminate these kind of human error as they will have all the latest and greatest stuff). E.g. If you set your location in the UI instead of in configuration.yaml you can change the home location without ever restarting HA. (might not sound useful, but it is if you have an RV) it also protects you from privacy issues with sharing your configuration.yaml with others (yes you could do it with secrets, but this way is simply better imho)
NEST indeed has the problem that you can’t re-add them if you delete them (though they can be restored from a snapshot). I can mention this in the docs and will add that. I do wonder how many people do not know this actually?
When people are not home triggering a gray picture was actually never the way it should work XD. For me it never was grayed out when not home (yes it was intentional, like you said it’s about taste). If you did happen to get it to become gray you might have had it configured wrongly (which happened to pan out nicely for you )
The notifications are moved to the /lovelace/notifications/notifications.yaml location.
@Scoobydoofus I have searched 2 nights for the overheating problem.
I think I have found it, it is related to css in my themes. Disabling the themes stops overheating it. I will address this issue (but it might require me to redo and overthink how to theme it again)
Anyone else getting this error when trying to add customizer repo? Fri Jan 24 2020 02:00:59 GMT+0200 (Eastern European Standard Time) Validation for andrey-git/home-assistant-customizer failed.
because to my knowledge they all should have one. It might be that I forgot one though.
Edit: note that the popup templates are the cards that are shown in the popup, and that they do not have the actual service-call to call the browser popup. Those are situated within button-card templates and they should (if I’m not wrong though) all contain these lines.
Ok, then let me recheck, I fixed that first one I found (im not that far into my setup to check all the different popups) so I guess I shouldn’t have generalized it that much because it may not be having the same reaction.
But, in quickly checking now, whatever popup is being called when you click the top two buttons on the vacuum page is currently still doing it, but it’s global settings I can’t figure out what template it’s calling at the moment… if I have my phone and laptop both open to HA and click the info button it opens on both.
Ah, yes, I see it now funny thing is: it doesn’t do it when single tapped, it does do it when used with a hold_action. Seems I forgot to add it to the tap_action (try hold_action for fun and see what that does plz).
hold action does NOT do it for me but tap action does?? weird, I thought I was going nuts when I couldn’t find it missing from any when I knew I had added it to one or two already.
So if it does it for you while tapping but not while holding there is something really crazy going on
In any case, I have found the lines where it is missing so I will add that. I have a bunch of other fixes coming up very soon. Once again thanks for the feedback.
In regards to the heavy load on showing the gui. I have a dashboard running on a rpi3, it’s only purpose is to show the gui on a screen. I found that the pi overheated if I had moving icons (like spinning fan icons in buttons or the weather card with the moving icons). Just something to look at, if that might have something to do with it.
)
