#frontend-archived
1 messages · Page 89 of 1
Is anyone here familiar with the custom AV card from sharethelove.io? It uses what it calls a "dormant sensor" for a tap action to call a Harmony command and I'm having trouble getting it to fire
seems like sometime after the latest beta revision lovelace broke for me
started complaining about the IDs, that were until then autogenerated
I removed all of the Id’s working fine now
Anyone having problems with Lovelace after the 0.84.2 update? All of a sudden my configuration is broken
@boreal pawn I am also having lovelace issues after the 0.84.2 update. It no longer seems to use my ui-lovelace.yaml
rebooting hassio does not resolve the issue.
@pure gate @boreal pawn Did you do it according to the breaking change?
Yeah I've got the same. @subtle rune what do you mean? I read the changelog and couldn't find any specifics that I had to do. Did I miss something?
@boreal pawn "For existing Lovelace testers" here: https://www.home-assistant.io/blog/2018/12/12/release-84/
I did miss that, thanks alot. I only read through the github page
I'm gonna try that
Is it possible to specify width of a horizontal-stack ?
It's either one column wide or the entire window.
Unless you nest them. Then they become thinner.
Thanks
@subtle rune thank you!
Np
I'm trying to get monster card to filter on friendly_name, but fail all the time.
Shouldn't this work to show automation.alarm_away_mode_armed (friendly_name: [Alarm] Away Mode Armed)?
filter:
include:
- entity_id: "automation.*"
attributes:
friendly_name: '*[alarm]*'
I finally get that my ui-lovelace.yaml file is not used anymore, and the config is in storage. But where are my images stored now? I have image-cards, but they don't seem to use the images in config\www\images anymore.
Are the images imported to storage in some way?
is there any reason the home page would stop working when upgrading to the latest beta?
Good morning, I am updating from version 82.1 to the new 84.2, when I do I loose my front end. I tried to do as instructed (You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode.) but I do not see that option anywhere. Has anyone had this issue?
@scenic aspen file and images paths are still to www folder
@daring pier you need to be at /lovelace
@mild veldt but if I rename a picture that is in use, it still shows. And I can't get imeges to show, even if I put them in the folder. So frustrating.
Yes
And are you yaml or storage mode for editing?
Storage
And how are you editing your config?
I see now that image is showing when I bropsw on my mobile.
Caching. Cool
Thank you, must ble chrome on my laptop messing with me.
Sweet. Thank you @mild veldt
hi all
lovelace on chrome browser, when i refresh the page, all states updates to on or off. for example a binary_sensor motion goes from clear to off
lovelace in yaml mode
@shadow smelt known issue. Fix will be in next beta
Hi to all, now the tap_action on the glance card are not working for me
the default config is working but cant change it with tap_action
thanks @mild veldt sorry for the replication
@mild veldt sorry my fault, thanks for that
Just upgraded HA to 0.84.2 and now the lovelace url just gives a 404 not found error. Any ideas on that?
What release were you on before the update? @stoic solstice
0.81.4
No did not. Can't figure out how. and the /lovelace url gives 404
PLEASE check the release post, it has the instructions https://www.home-assistant.io/lovelace/yaml-mode/
Why isn't this info in the releawse notes?
well, if you had read the release notes carefully, you would not ask that question
I searched for lovelace and can't find anything that informs about this. Perhaps if i open and read through every fix that's mentioned in the notes?
that is not the release post.
every release has a blog post that you should read carefully for breaking changes
Well, then maybe this site: https://www.home-assistant.io/docs/installation/raspberry-pi/ should link there isntead?
It refers to this link as release notes
again, you are looking at the wrong place.
the install instructions don't change every release
Thre are upgrade instructions on that page
yes, the upgrade instructions also don't change with every release
True, but still it should link to a place where all the changes are correctly noted instead of the releases that apparently are wrong
oh well, thanks for the help. I guess i can get it working again now
ok, so enable yaml mode and still get a 404 not found when accessing /lovelace
@raven nacelle Any other ideas?
Does /states work?
yes
Go to
and choose Lovelace from there?
That interestingly works...
And then make it the default again I guess
oh... you need to add the tab. Wasn't needed earlier
By choosing yaml mode you miss the UI editing part, which is pretty nice but not finished
I don't know what tab you mean
Might try that later. If i understand it correct i should be able to import my config
oh, in the url /lovelace used to work. Now it needs to be /lovelace/0
You can through the raw config editor, yes
@stoic solstice oh, yes, that /0 for the default view
yeah wasn't needed earlier on 0.81.4
I guess there was a redirect or something to /0
Well, I don't even remember from that far back🙃
I've refused to upgrade as i heard many had issues but now i needed/wanted a new feature that wasn't in myu old version sp
For those who are struggling like me to bring old groups as-is into the lovelace config by hand, here is the script you can use ```
- id: all_groups
title: My Groups
icon: mdi:home
cards:
{%- for y in states.group %}{%- set g = y.entity_id %}- type: entities
title: {{g.split('.')[1].replace('_', ' ')|title}}
show_header_toggle: false
entities:
{%- for x in states | selectattr('entity_id', 'in', state_attr(g,'entity_id')) |list %}- {{ x.entity_id }}
{%- endfor -%}{% endfor %}
- {{ x.entity_id }}
- type: entities
I have around 900+ entities, and impractical to use UI editor, and I've organized all my entities in my old UI into groups, and ☝ script basically converts those groups into lovelace, that I can move around within the views. BAM!
The auto generated mode should do about the same
@glossy birch Yes, just use the default mode (I think it is called storage) that gives a decent starting point.
Hi, I'm Remco, new on the chat here.
Looking for some help with my new Lovelace config, I've searched the forum and docs, but can't find the right code
- entity: light.ambilight
name: GREEN
icon: 'mdi:spotlight'
tap_action:
action: call-service
service: light.turn_on
service_data:
entity_id: light.ambilight
rgb_color: '0,255,0'
type: entity-button
This doesn't seem to work 😦
@raven nacelle @winter hollow the problem is that I couldn't get the entity_ids that I want to organize - I am using my own yaml and UI editing was out of question
I am not using storage... yet 😉
if you are starting off, use storage. The UI editing is amazing and evolving rapidly.
either ways, it is easy to convert to storage at later date
Hey,
i'm lost since I updated hass to 0.84, can I use my previous lovelace file ?
yes, just use the yaml-mode (read the release post for instructions)
lovelace:
mode: yaml
?
@raven nacelle UI editing is definitely not for me... I was tired of selecting entities in a dropbox that has 850 entities... I keep picking the same entities all over - again and again and then I gave up
@blazing hamlet add ```yaml
lovelace:
mode: yaml
we will probably get drag and drop cards soon
and other options to change the layout of our cards
those are the big ones that I am looking forward do
@glossy birch I included it to lovelace.yaml 😅
@blazing hamlet LOL
@blazing hamlet when I read the docs, it does not explicitly mention where to put the lovelace mode to yaml. I see that it can be confusing for newcomers.
not your fault
my super guessing powers are limited
Is it possible to add a thermostat card to an entity_filter card?
Could it be posssible, that you can only pass 1 state to tap_action > service _data with an entity button? I'm trying to pass the entity_id and a rgb_color. But it only works when I remove the rgb_color.
@glossy birch you can start typing in the dropdowns to quickly filter out all the other stuff
@mortal cape the entityids are not typeable 😭
I start typing "garage" and get only my entities with that word...?
the entity_ids are pretty long with GUID in them - they are auto generated, and hard to use dropdown
oh I see
let me show you what they look like
Hey. New to home assistant, so forgive me if this is not the right place to ask. Upgraded to 0.84.2, and tried the lovelace ui editing. Seemed to work nicely, but now the "Configure ui" button doesn't work.
they are like this media_player.snapcast_group_bde597975a001d05519d2ae52103dba1 - except I have 20 of them
lol
😃
so... i've been fighting an entity-button for about 3 hours... hoping someone can take a look and tell me what i'm doing wrong... I just want to press a button and execute a script without any other interactions...
using the card configurator -
type: entity-button
name: Prepare for Guests
tap_action:
action: call-service
service: script.toggle
service_data:
entity_id: script.prepare_4_guests
entity: script.prepare_4_guests
when i click it i get a dialog box to execute the script... I just want it to execute without the additional dialog
~format
To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks. Here's an example:
```
code here
```
Click on the link to learn how to format: https://raw.githubusercontent.com/skalavala/HassBot/master/format.gif
@raven nacelle in my non-lovelace setup, when I click on my camera, it opens up a window with full screen view... does it still work with lovelace now?
yes../
use the picture-entity card
type: picture-entity
entity: camera.patio
show_name: false
show_state: false```
I am using picture-glaance card, when I click on it, nothing happens
- id: camera_playarea_camera
type: picture-glance
title: Playarea Camera
entity: camera.playarea_camera
camera_image: camera.playarea_camera
show_info: true
tap_action: dialog
entities:
- switch.wemobackyardlightswitch
- binary_sensor.playarea_camera_motion
this is what I use
I had picture-entity earlier, and I switched to glance as I wanted to add binary sensors and lights at the bottom
@raw brook - thanks, I hadn't seen that before, how to insert formatted text...
then you are probably looking at a combination of vertical and horizontal stack card
hmm...
let me try the glance card for camera
I like to be able to click on the zamera image and open up in full screen mode, where I can see more details
it's not standard formatting in the card configuration tool, is it?
@glossy birch that’s not how you define tap actions
Docs should be up to date on how it should be
@mild veldt enlighten me please! I have no idea what I am doing there... time to hit the docs
I was trying to limit the amount of time I spend on LL, and get basic stuff going
On mobile right with one hand trying to get my little one to nap 😃
@mild veldt I appreciate it... I just need a pointer 😃
type: glance
title: camera
show_header_toggle: false
entities:
- camera.porch
- camera.patio``` works fine for me
awesome! @raven nacelle
although glance is not the right card for cameras
let me try that
lol since the update I can't toggle entities by a click (lights or switchs)
@blazing hamlet in which cards? Default tap_action is more-info
If you want toggle you'll need to define the tap_action
1sec
tap_action:
action: toggle
fixed, thanks 😉
Dose anyone remember seeing a picture glance card created by a user that was kinda animated looking? I can't remember where I saw it
Is there any way to make entity buttons equal height? https://imgur.com/a/saY71qC
@mild veldt thanks for pointing me about the tap action. I never updated my initial lovelace code that I generated from the initial version. It works fine now...
@raven nacelle this works as expected - ```yaml
- type: picture-glance
id: camera_playarea_camera
title: Playarea Camera
entity: camera.playarea_camera
camera_image: camera.playarea_camera
show_info: true
tap_action:
action: more-info
entities:
- switch.wemobackyardlightswitch
- binary_sensor.playarea_camera_motion
@scenic aspen Is that not where I am? the top of my screen says #frontend-archived.
Is there any way you can reduce the card size of the lights? It looks pretty ugly being that size
I have a lot lights, and I liked the old view! 😦
Horizontal stack them?
I tried, but the size is fixed
How do you add the sliders?
Thomas a custom_card https://github.com/thomasloven/lovelace-slider-entity-row
Cool, hopefully it’s officially added to HA soon.
I hope so too...we definitely need the slider - can be used for so many things
We need to get things polished up before we start bringing in more new stuff and is the whole idea behind supporting custom cards. If the base doesn't have it, anyone can make it 😃 But in due time, I think something like slider will eventually make its way into the core
I am sure once LL becomes default and the kinks are ironed out we can add some of these things.
@mild veldt just on your previous comment on scaling https://github.com/home-assistant/home-assistant-polymer/issues/2334
😉
yeah, just saw that as well
could have sworn there was already an issue for it, but can't find it now
may be it was in ui-schema repo
I have one scaling issue there related to alarm control panels
but did not see anything else
maybe it was gauge, which is pretty much the same thing as the light not scaling...
you can probably add a feature request label to that issue and leave it there
yeah, gauge may be https://github.com/home-assistant/home-assistant-polymer/issues/1765
but gauges still better than some of our other elements
I cannot move issues...if you can, you can move it
yeah, i will...later...man, I'm tired today 💤
👍
Is there a way to add customer components when I use Lovelace as mode: storage ?
I upgraded from version 82.1 to the new 84.2, when I do and I click Overview it is saying No config found (Reload UI-Lovelace.yaml. I tried to do as instructed (You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode.) but I do not see that option anywhere.
@vapid field use the raw editor that is in the menu when in edit mode
@daring pier do you have ids in your file?
also might want to clear your cache
@mild veldt Ok, so I add the custom component to www folder then add something to the raw editor?
yeah, the instructions haven't changed on how you add custom components other than you need to use the raw editor to edit them currently
same file path, www
@mild veldt Thanks will give it a try!
Is there any way to migrate ui-lovelace.yaml to the new format? it looks like it's making me start from scratch
@mild veldt maybe you have a snapshot how you entered it into the raw editor? I just added at the end:
resources:
- url: /config/www/slider-entity-row.js
type: js
But it will not work:/ Get an error in the log
https://xxx.com/config/www/slider-entity-row.js:1:1 Uncaught SyntaxError: Unexpected token <
@mild veldt I am unsure what you mean by id's
@visual ibex read the release notes for 0.84 on how to do that
@vapid field looks like you downloaded the html and not raw file
@mild veldt I was looking in the wrong place - I was looking in the change log and couldn't find how to do it. Thanks for the tip.
@daring pier in your ui-lovelace.yaml file are there id tags?
you might just need to try clearing your cache a few times as well
@mild veldt I use the the raw editor in the Lovalace, but I don´t think this is correct. It looks first to my https://hassio/whatever
@vapid field the unexpected token < means you have an HTML file in your www folder
open that file and I guarantee it will be HTML and not javascript
@mild veldt I do not have any Id's and I will try to clear cache. TY
@daring pier also, how did you get to your lovelace page? Through a bookmark or through the dev-info?
You'll want to go through dev-info initially
@mild veldt I downloaded the https://github.com/thomasloven/lovelace-slider-entity-row put the slider-entity-row.js into the www
you don't want html, though
what I typically do, if I don't use wget or curl is to open the raw, and paste it into the file
i have the .js file
I don't mean the extension, I mean the actual contents of the file
I think I miss something here, or I´m to stupid to understand what you mean haha
@vapid field go here: https://github.com/thomasloven/lovelace-slider-entity-row/blob/master/slider-entity-row.js
Right click on Raw and then Save link as to get the raw contents, i.e. javascript
Here's a good list to read through when getting started with custom cards: https://github.com/ciotlosm/custom-lovelace#faq
then i put that to the www folder, right?
great
should be this
resources:
- url: /local/slider-entity-row.js
type: js
local matches to what you have in config/www
Oki, do i need to reboot the HA?
no
did not get an error in the log now
not if you had the www folder before all of this
yes I had it
@mild veldt Thank You. That did bring everything back however I lost all of my view tabs and now it looks like it did before I started with lovelace.
that's the auto-generated dashboard
@mild veldt I get error when I try to add the "Unknown card type encountered: slider-entity-row."
read through the release notes on how to start using yours
@mild veldt OK Thank you very much.
@vapid field double check your path of the downloaded file. Double check your spelling. Double check the file contents
@mild veldt One more thing before I start reading all night 😃 It never did ask me to change storage will that be an issue?
It won't ask you that until after you try to take control and configure it
Right now, you're using generated mode. i.e. Your dashboard is autogenerated based on the available entities
Nothing is stored
Once you take control, you'll be converted to storage mode UNLESS you configure yaml mode in your configuration file
@mild veldt don´t get it to work:/ Give up now but thanks for the help. Will give it a try tomorrow when I´m filled up with a night of sleeping:) Thanks again!
Might want to check out arsaboo's config who pointed you to the card in the first place as well: https://github.com/arsaboo/homeassistant-config
@vapid field tagging you so you don't miss my message above
currently there is no feedback once I click "save" after a finished "raw config edit" session, right? or is it just me?
Hi, does monster card support tap_action? ``` - type: custom:monster-card
card:
type: glance
title: lights
columns: 4
show_state: false
tap_action:
action: toggle
filter:
include:
- domain: light
hey guys, I updated today to HA 0.84.2 but facing some problems with lovelace and tap action in element, anyone else here having issues?
I set lovelace in mode: yaml again to keep editing my yaml files and not configuring via ui. But toggles and tap_actions like this dont work anymore 😦
Xiaomi Vacuum page
- icon: mdi:robot-vacuum
id: vacuum
title: Staubsauger
cards:- type: picture
image: /local/xiaomi_vacuum.png
tap_action: call-service
entity: vacuum.jurgen_cleansmann
service: vacuum.locate
- type: picture
# Xiaomi Vacuum page
- icon: mdi:robot-vacuum
id: vacuum
title: Staubsauger
cards:
- type: picture
image: /local/xiaomi_vacuum.png
tap_action: call-service
entity: vacuum.jurgen_cleansmann
service: vacuum.locate
@brave badge you need to define the tap action per entity, so no, you couldn't do that with a monster card as you don't have entities to add more options to.
Do custom cards work with the new storage method of Lovelace?
@simple jolt they do but from what I've seen you needed to configure them in the raw editor
@flat timber I did but non of the custom cards are displaying on the tracker card. Although they do work.
Tracker card does not work with storage
You could keep a copy of your resources in your old ui-lovelace to allow it to work
@mild veldt can I have the storage option enabled but also have a ui-lovelace.yaml file in config?
@mild veldt that worked. Thanks.
Note that after updating a card resource your frontend won't reflect the change until you clear the cache or you manually copy the ui-lovelace resources and put them in via the raw editor
@raw brook from what i see from sensor card was removed config like line_color has example
is there any particular reason why removed?
doesn't seem to make sense to remove a important option like that but at same time I'm sure that there's got to have a reason for it
There is no reason to have and it too much control. Line color can be changed with them which is really all that's needed
what you mean by Line color can be changed with them
by removing those options you forced to have all sensors with same color, witch will remove the freedom of personalise your own tastes
why have has example temperature and humidity sensor all with same color line graph, when you can have different color to distinguish one from other
Just realized entity-filter is not working in 0.84 or is this just me 😃
@cunning violet what does your filter look like?
@mild veldt https://pastebin.com/uk9svA0e
@cunning violet did you read through the release notes
?
there were some breaking changes
specifically related to wrapping on and off with quotes in your case
How did I miss that one.... Thanks mate
not trying to sound dumb but im having issues getting lovelace to update... in the ui-lovelace.yaml i have title: main
views:
!include lovelace/views/main.yaml
lovelace/views/main.yaml i have https://paste.ubuntu.com/p/rhrMFqwJ42/
@mild veldt Ok thanks!
Hi! I'm using a glance card in a vertical-stack for showing my lights in the livingroom. For the entities in the glance card i've set tap_action: toggle. But i can't get it to work. also tried to clear my browser cache. Someone an idea why?
action: toggle```@paper oxide
@mild veldt Thanks! His config help me:) I need to use a type: entities and not type: slider-entity-row as I was thinking.
type: entities
title: Lights
entities:
- entity: light.hallway_spotlight
type: custom:slider-entity-row
@brave badge thanks! But why?
Good day, I´m trying out Lovelace and I have issues with adding scene actiations. I´ve copy pasted the example from the docs but modified to use scene instead. But hass complains about the middle row
Seems different than the docs
@paper oxide docs changed: https://www.home-assistant.io/lovelace/glance/#configuration-variables
Like that
This does not work:
- type: entity-button
icon: mdi:sleep
name: God natt
tap_action:
action: call-service
service: scene.turn_on
service_data:
entity_id: scene.god_natt
entity: scene.god_natt
Hass says syntax error
Seems to be intendation error (mapping values are not allowed here in...)
Ok so example in docs is incorrect. Should be like this
- type: entity-button
icon: mdi:sleep
name: God natt
tap_action:
action: call-service
service: scene.turn_on
service_data:
entity_id: scene.god_natt
entity: scene.god_natt
Hello guys, my Lovelace dissapear, and now I see that are some ways to configure the new interface.
Whats the best way to do it? via .yalm?
add
lovelace:
mode: yaml
to your config
Is there a picture-glance card showing the actual temperature value of that room instead of requiring an extra click?
i'd look into something like https://www.home-assistant.io/lovelace/sensor/ + https://github.com/thomasloven/lovelace-card-modder instead of picture-glance
i haven't tried that myself though
@hushed palm use picture-elements for something like that
Does anyone have any recommendations for wall mounted tablets running Lovelace in fully kiosk or something similar?
I noticed in 0.84.2, that I have an entity card with three sensors on it, but it still displays the group_toggle at the top:
- title: Current Conditions
type: entities
entities:
- entity: sensor.dark_sky_summary
- entity: sensor.dark_sky_temperature
- entity: sensor.dark_sky_humidity
Is that expected behavior or a bug I should open an issue on?
I should add that I know I can turn it off with show_header_toggle: false, but prior to this I thought it only displayed that if there were switch-type entities on the card
So, updated hass.io to 0.84.2. Copied my lovelace yaml into the raw config editor and my ui was back to normal. The problem is that when opening the raw config editor it is completely blank. Anyone else seen this? Anyone know what to do?
I have the same thing as @hallow spruce
I had to put show_header_toggle: false on all my cards
Trying to find documentation on how to edit the entities/information that shows on the pop-up window when you click on an entity, anyone who knows what I mean and knows where I can find the code? My googleskillz are not enough 😛
Does anyone know if the picture element card support moving gifs?
@cloud escarp I use wallpanel, works great turns screen on when you walk up to it.
@scenic lantern Just tried and it does 😃
glad you asked that...now I can have moving icons for fan, etc.
when I add 2 history graphs on the same sensor, with different hours_to_show, they both have the same number of hours. Is this a known bug or something?
@raven nacelle awesome! Thanks. That's my exact use case, want to use it for my fans.
Hi everyone, sorry to drop in with a question have been looking for this the last couple of days, I migrated to HA 0.84 and am redoing my lovelace setup (in yaml mode). I am using includes for my various views but each time I make a change in one of the files I need to restart HA. Is there a way to force lovelace to reload including all included files?
ah deam.. as I feel the tap_action: in entetys is removed...
Just spent to much time with configuring that i dont get it how I now call a service directly
tap_action:
action: call-service
Does'nt work so..
ah
hä?.. Argh brain
so its done! ```entities:
- entity: light.vorraum_white
tap_action:
action: toggle```
thank you - Now I have to change the 223 other entetys...
Can I set height and width for a picture entity? Think not, is there any better way to view camera picture so it get a little bigger? I use two images in a horizontal-stack.
@copper mural I have solved this via an iframe card & a local lighthttp server to serve the html and what else might be needed...
Fixed my own issue, aparrently refreshing the page with F5 (or force refresh) doesn't refresh lovelace includes in yaml mode. Clicking the refresh from the top right menu does.
@ornate monolith can confirm that, looks like the lovelace.yaml does not allow include for auto-reloading
: have a relay to turn on the fireplace and I temperature gauge sit in the living room could I make them talk and use the thermostat card
~climate.generic_thermostat
thanks @split granite
has someone made a custom element for picture-element that pops up a custom "more-info" card?
I want to do a hold action on my tv that pops up a remote for it. tapping just toggles it on/off via broadlink
@drowsy summit https://github.com/thomasloven/lovelace-popup-card
@mild veldt I saw that, but will it work as an element in a picture-element card. It looks like it is a card of it's own
I can think of one way to find out
lol.. I suppose so
I guess I maybe asked for the wrong thing.. what I need is a custom ACTION. I have this element in a picture-element card - type: state-icon tap_action: action: toggle entity: switch.tv_sanyo_power style: top: 41% left: 25% transform: scale(1.5) I would like to have a hold_action that pops up a custom card
If lovelace-popup-card can do that, I can't figure out how lol
did you try adding a hold_action of more-info?
I am using a custom card called flex-table-card. It works well on a pc. I can see the values change. On an Apple device, all I see is NaN. Just wondering if someone might have seen this in other instances or it is a common Lovelace error?
not common
did it again. Installing node red borks the system.
@little dew #node-red-archived
@mild veldt yes.. standard more-info card pops up, not the custom one
Really? Looking at the code I thought it would work. I might play with it later
the picture element is a floorplan of my house and setup as a panel. I had to add the custom card after the picture element card or nothing showed on the page. I don't imagine this would be the cause, but perhaps it is.
this might help https://hastebin.com/hodifohodu.bash
hey all, I was attempting to troubleshoot my ecobee and while in the "raw config editor", I accidentally commented out the top view comment and saved.
I'm not unable to load any lovelace UI to undo this adjustment.
anyone have any idea where I can modify this since the ui-lovelace.yaml doesn't actually get used now (0.84.2)?
@short void you'll need to edit the file .storage/lovelace which is your config, but stored in json format and then reboot HA
Thank you, I'll look into this tomorrow morning
Hmm, just glancing at it on my phone and I don't see the view portion listed. I assume this is because when I commented it out, it completely removed it. Ugh.
Comments are not saved
So, since 0.84.2 I’m having issues with my picture elements card. I have state-icons that don’t work anymore on tap_action
I saw there was a braking change on that but can’t see where i went wrong
Ok nevermind found it
Is anyone else having problems with lovelace? I just cant activate and I get the regular UI instead
I was using lovelace no problem until now
Hi all
I am trying toi add a historycal graph_card in HA
title: 'My Graph'
entities:
- sensor.outside_temperature
- entity: media_player.lounge_room
name: Main player```
Can i simply put this card in confifguraion.yaml?
No, are you using lovelace in storage mode?
I activated lovelace in the gui
developent page?
''i'' and then enable lovelace
Right top, click Configure UI
oke
Holy crap
this is awsome
thanks
I can simpy add an card
and choose historical_card?
so custom_updater only works in yaml mode - is it standard for custom cards ? (new to lovelace - decided to check it out with 0.84)
I think its standard
- type: history-graph
title: 'My Graph'
entities:- sensor.outside_temperature
- entity: media_player.lounge_room
name: Main player
I can choose history-graph
Like this - type: history-graph title: 'Warmtepomp grafiek' entities: - sensor.warmte_pomp_sensor_aangepast name: Test
With error: YAML Error: TypeError: Cannot read property 'startsWith' of undefined
Or do i have to use json format?
No yaml remove the first - and adjust your indents
Thanks
@drowsy summit popup-card does what you want. The problem is that you're using panel mode, and then only the first card is loaded. You can solve this by using a stack containing your floor plan and the popup card.
Hi! After i copyed my lovelace code into the "Raw config editor" all my resources got changed like this https://pastebin.com/3QpR9FNR. Is this correct?
Yes. The hass parser orders the keys alphabetically.
hopefully a quick one - are there any deficiencies moving to storage mode vs yaml? also not sure if I understand the instructions correctly - do I start with my ui.yaml and then convert or do I need to remove it prior to starting hass?
I have this view and want to style as in the code, but it seems the picture-element card doesn't like the card-modder. Or am i wrong in something?
https://pastebin.com/RCsNFxBr
@hot gyro There are three modes, auto, manual and yaml. ui-lovelace.yaml is only used in yaml mode. It can still be present in the other two, but will be ignored.
If you wish to use the UI editor with your old config. You start up without doing anything special - because the default is auto mode. Then you open up the raw config editor and paste the contents of your ui-lovelace.yaml. This will activate manual mode.
What causes this? https://blahblahblah:8123/lovelace/11:0:0 Uncaught
ok thanks - so it did start in auto and now I need to chase down why it has entities not available that shouldnt be there ... will have a look
you cant use third party cards in auto ? only in yaml mode ?
In auto no, in manual yes you can. So not only in YAML
You can add them in the raw config editor
I'm really sorry to ask this, but lots of googling appears to be giving me out of date info. Whats the fix for having 2 cards side by side, not taking up full width of the browser?
I have put a horizontal stack in a vertical stack, but the vertical stack is only about 10% the width of the browser window.
panel: true https://www.home-assistant.io/lovelace/views/
If you edit a view with the ui editor now, there is no panel option?
@jade gust the ui editors are still evolving. You can always toggle the yaml view editor to add options
Hi guys, I need some help. Im trying to get into the lovelace game, but I cant figure out which file to edit. Im on 0.84.1 and using lovelace as default. But the ui-lovelace.yaml seem obsolete now and I dont have any lovelace in .storage.
@polar kelp Looks like your Layout card is not editable with the config UI
@brisk osprey click on configure UI in the top right menu
Considering so many people have the question about the new lovelace ui, and how it uses it setup, maybe there's time to do a better explanation on the release note? : )
^^^ this
Just add a huge stopsign.jpg with the title WHEN YOU UPDATE TO 0.84.1+ YOUR LOVELACE UI WILL USE THE NEW CONFIG FILES READ INFO HERE
as an example there is menu unused entities - its full of entities being used and shown on my views ... doesnt make any sense to me - I would expect to only see entities in there that are currently not shown
sure it's entities that are unused then? cause mine works as it should
thanks @winter hollow
@polar kelp BEAUTIFUL!! Thank you!
100% @minor viper
@minor viper a PR to the docs is always welcome
@next sigil That's probably true. I haven't tried it yet.
Editing the docs doesn't require any skills 😉
But nah, something that's obvious for you guys working with it behind the scenes without us knowing it, isnt that obvious when something new releases
did i say i hate typing? if not.. i hate typing 😄
@polar kelp The card works just as intended, but shows no edit-buton.
can still edit it just fine thru the raw config editor thou
and i hate people on daily basis
Makes sense. There's nowhere to put an edit button...
I plan to take a look at GUI editing after the holidays.
And I suppose cards that are inside the layout-card aren't editable either, just like core stacks.
which card you referring to?
@minor viper that are nice standard excuses for lazy ppl not wanting to do the PR 😉
who said i wasnt lazy?
Is the picture-elements card moddable by card-modder custom card?
i didnt, i juz stated the fact 😉
Or it could be just that i suck at doing PR? Hence why i have a co-worker who adjusts the most writing i do before handing it over to a customer
thats exactly how PRs work - you do it, someone reviews it and everybody is happy 😃
Hi again 😉
The best person to write docs are the person having issues, the people behind the feature will most likely be in another mindset
Is there a way to change the text size in lovelace with a gauge card?
It's just that one thing i've learned when working with IT, you have to treat your customer as a baby.. even if something is simple for you to comprehend, think that the customer has 0 knowledge about anything. And write after that aswell, or throw in some pictures so they can comprehend what you're trying to explain
@wheat current understandable : )
Because the my next is now bigger then the gauge itself
@foggy tendon Yes. But not the elements in the card.
I actually almost added modding elements as a feature, but then I realized that's a built in feature of elements anyways, so I took that out.
With the new templating, though, I should probably add it back...
@polar kelp thanks, so i can use card-modder only for the first card?
I'd like to dim an image inside a card-modder card like this:
style:
background: url(/local/lovelace/images/info.jpeg)
Is it possible and how?
im getting this error but i dont understand what it means https://********.gq/frontend_latest/bf7146608f595468a214.chunk.js:3157:1377 Uncaught TypeError: Cannot read property 'name' of undefined
@icy shard is related to weather and/or plant cards. Should be fixed in next beta
okay
just wanna make sure I got this right. Either you edit lovelace via the gui, or the lovelace file in .storage right? No way in doing it in yaml like before?
also, is there any need to have the lovelace.yaml located in the Hassio folder? if you're running through the .storage instead? 😃
@brisk osprey you should not touch the files in .storage that is only for HA to touch
If you use storage mode you can only edit your UI through the UI. The UI also has a raw editor to edit you config as YAML
@minor viper no, it doesn't use the yaml file when using storage
alright thank you, then i'll remove it when i get home 😃
got it.....(silently closing the file and moving away from the computer...)
Thanks again @winter hollow
Does "Covers" not work together with picture-glance? I've added one and can't control the cover, but if I add a light I can control it (toggle).
Do I need to add something else? (right now I've only added '- cover.garage' under entities
hello, updating .83-> .84 caused quite a few issues in my setup, most I|ve figured out now (mqtt/owntracks, and appleTV no longer working) however....the lovelace UI for me now seems to be partially missing....
Some views are missing and it seems to be a mix of the old "groups" and my new lovelace-ui ....is that possible?
Yes
Read the release notes
Or actually, no it is not a mix, it is just your groups with the Lovelace elements 😉
yeah, i know... 😃
i have already checked the "breaking changes" and can't figure out what remains the problem
You are in generated/auto mode
Either click the configure UI button, and copy your old yaml in the raw config
Or go to yaml mode
For the last see the docs and link in the release notes
@wind tusk read the docs on how to define your tap_actions
tap_actions are fixed
?
tap_action: action: tap
wat? no
@mild veldt tried the different versions, with different actions (cover.close_cover etc) but couldn't get it to work...
Or maybe it's me who's missunderstanding tapping?
~share
Please use https://www.hastebin.com/ or https://paste.ubuntu.com/ to share code.
tapping the actual cover icon brings up the history graph for my cover, taping the image brings up the camera
so you don't have a tap_action defined and it is using the default more-info
ops, wrong example, that was from my first try using popup-card, but the normal entity looks the same 😃
read the docs again. there are only 5 options for action
Ahaaa! Thanks, missed that part
So adding this https://www.hastebin.com/raw/madagaralu to configuration.yaml will run Lovelace off the lovelace-ui.yaml like before?
yes
allright, easy as that 😉
you will not be able to use any GUI editor features
ah, ok, thought so, I just discovered those too, haha
so....is there any way of "importing" my config and be able to continue editing in UI?
Yes, copy your config into the raw config editor
From just briefly looking at the UI editor it looks like I will need some time to learn that (too), hopefully these kind of changes will not be that frequent
Well, it's a big switch from one UI (states) to a new one (Lovelace) - the devs don't plan on doing this regularly 😉
Good thing 😃 from a beginners perspective, starting this summer with HomeAssistant and "coding" in yamls it for sure is not a platform I'd recommend for someone who wants to j"ust have a automation system that works"
Don't misunderstand me, I enjoy the playing around, but I would not trust this system with my life
You should not trust any system with your life, systems have bugs.
Especially not a free one.
true that
I have HA controlling my doorlock....I have to say I consider pulling the batteries off the lock before going to a vacation
I won't let any system control my home's physical security 😉
It always bothered me that all ”smart” locks are open-on-fail. I know it’s for safety and evacuation and stuff, but I don’t want my door to open because I forgot to change batteries. And my main breaker is outdoors.
@mild veldt tried these 2 ways, but still going to "more-info" https://hastebin.com/dabacizazu.css
Do you see whats wrong?
@wind tusk your service data is not formatted properly
They shouldn’t work, but neither should they open more-info. Weird...
@wind tusk you don't want it to just toggle the cover? only open?
Or is there some kind of fallover if service_data isn’t an object nowadays?
If it could toggle it, that would be fine, but dont see any toggle options for covers in HA?
@polar kelp we just pass the service_data as is
With the 0.84.3 the !include works with lovelace? Docs?
@foggy tendon if you're in yaml_mode, yes
Thought so. Then it should just fail with a log error and not open the more-info dialog.
I don't know if it is now, he said it was previously, but that was when he didn't have any tap actions defined
@mild veldt where to read documentation?
It is still opening the more-info box
hmmm
@foggy tendon https://www.home-assistant.io/lovelace
- type: picture-glance
title: Garage
entities:
- entity: cover.garageport
icon: mdi:arrow-up-bold
tap_action:
action: call-service
service: open_cover
service_data:
entity_id: cover.garageport
camera_image: camera.garage
should work, I believe
I'm not sure why more-info is showing still though...so
Martikainen: do you have any !includes in your config?
Yepp, using your lovelace generator to split my config
Any tips how to get a floorplan-image for picture-elements card?
but in this specific file there are no includes
Ok. Just checking. There have been some update weirdness with the core includes before...
Are you sure the generator runs without error?
yepp
Can you find this section in the generated ui-lovelace?
Bleh! Phone keyboard...
@copper mural some use sweethome3d
Hm I found it, but it hadn't updated, looks like my old test
Thank @polar kelp
I used sketchup for mine.
Sounds like its more advanced as you used it 😉
It’s about as simple as a CAD program can get...
does this look incorrect? https://hastebin.com/cikinexepi.css
Looks fine to me
odd that lovelace-ui turns everything in reverse order 😛
No, wait. That’s not a service
copied my yaml-config into the raw editor - > https://www.hastebin.com/ekujuhotik.coffeescript
It should probably be service: cover.open_cover
I removed the lovelace-ui and generated it again, still the same, with the code that Iantrich pasted
and no errors in ha.log
and editing lovelaceui manually with the correct service didn't change anything, still more-info box
What version of Home Assistant are you running?
84.2
I’m out of ideas.
tried changing the entity from cover to light, now the light turns on, but no service is called
😄
I'll give it another go tomorrow with fresh eyes..
@solid wigeon cards don’t need ids anymore. Try just removing that line.
...if it’s a card id. If it’s a view id there’s some other problem...
@mild veldt hmmm.... there is nothing related to !include in the lovelace docs page...
well....something new.... "Expected a value of type undefined for name but received "Media Streaming"." ....no need for name either?
title 😃
got it
thanks for the help @tardy shore and @polar kelp ! I'll let you know if I figure it out 😃
@foggy tendon docs on include are out of the scope of lovelace specific docs. You just follow the standard HA configuration docs on include if that's what you're looking for
@mild veldt ok, i'll try to do my best as i already use !include in configuration.yaml. Is it almost the same way?
It’s exactly the same way.
it should be same. what issues are you running into? I believe you have to currently restart HA to have changes reflected on the frontend if they are inside an !include
@polar kelp @mild veldt thanks....
(Disclaimer because it’s you 😉: exactly the same on 0.84 or later)
need to have everyone assign flair to themselves somehow specifying which version and mode they are running LL in, lol
@mild veldt no need to restart HA with includes
Kind of A/S/L thing.
🤷
<-- latest, None
just use the reload button top right 😃
ah, that's right
.84/venv/yaml
dev/venv/depends
.82/hassio/auto
V/E/M
Perfect! Let’s make it a social standard!
dev/venv/windows/linuxsubsystem/storage
dev/venv-WSL/manual
I actually really like this idea. I could write up a pinable message about it when I’m at a keyboard.
just don't ask any devs as it will just confuse others 🤣
@polar kelp we'll make it into a bot alias
~vem
Help us help you. To quickly explain your environment please specify V/E/F
- Version - Which version of Home Assistant are you running?
Example: 0.84.3, 0.82.0, 0.85.beta.1 - Enviroment - How are you running Home Assistant?
Example: venv, venv-WSL, docker, hassio, native - Frontend: - Which kind of frontend configuration are you using?
Example: auto, manual, yaml, legacy (not lovelace)
Examples: 0.84.3/venv/yaml
That was quick
Well, I'd seen the discussion, and just flipped back to this channel when you posted and edited it
@split granite can you make it into a bot alias?
actually, I can do that, but don't remember how...
Probably, there's a character limit, but I'll have a go
The bot commands are now a Git repo
ladeda
What do you want the alias called?
~vem
~vem
Help us help you. To quickly explain your environment please specify V/E/M
- Version - Which version of Home Assistant are you running?
Example: 0.84.3, 0.82.0, 0.85.beta.1 - Enviroment - How are you running Home Assistant?
Example: venv, venv-WSL, docker, hassio, native - Frontend: - Which kind of frontend configuration are you using?
Example: auto, manual, yaml, legacy (not lovelace)
Examples: 0.84.3/venv/yaml
🤣
If you edit your post that'll fix the pin, I'll fix the bot
So, to confirm, V/E/F
~vef
Help us help you. To quickly explain your environment please specify V/E/F
- Version - Which version of Home Assistant are you running?
Example: 0.84.3, 0.82.0, 0.85.beta.1 - Enviroment - How are you running Home Assistant?
Example: venv, venv-WSL, docker, hassio, native - Frontend: - Which kind of frontend configuration are you using?
Example: auto, manual, yaml, legacy (not lovelace)
Examples: 0.84.3/venv/yaml
There you go @polar kelp 😉
I had already edited the post for VEM, but I'll change it to VEF.
If we could find something to call the environment that starts with a T would be neat, though...
o/ all
I can't find in the doc: what is the new configuration that replaces " localstorage.defaultpage" ? It does not work since 0.84
It's still set when you click the thing... but with a capital P localstorage.defaultPage...
what are all the readings to get known to lovelace?
@vapid lance If you're looking for a configuration.yaml setting to make lovelace default, there's no such thing.
~lovelace
If you want to talk to the bot, please use #botspam @viral root 😉
@polar kelp not at all, I'm setting different default page per device, for instance: my phone has /lovelace/mobile per default 😃
ok
@polar kelp indeed: defaultPage (with capital P), but does not seem to work
Just setting localstorage.defaultPage in my browser works.
hmm
defaultPage :"lovelace/mobile" is the setting
in fact, the url is ok, but the page does not load... strange 😃
pff... forget it, it seems the settings changed to set up page name... it"s not "id" any more ?
ok it's "path"...
maybe could be cool to add it to the changelog ?
Was probably lost in the barrage of other breaking changes. Glad it at least made it to the docs, honestly...
clear. just by curiosity, IMHO 0.84 broke a lot of things, even more than during the last hackathon. Any reason ? The rush to replace the default view ?
Yes and no.
The plan was to release lovelace as default with 0.84, which Balloob had declared could not happen without a working GUI editor. This brought a lot of problems with backwards compatibility and workarounds to still allow manual editing and such...
Then Frenck had an idea that changed everything - put the automatically or UI generated stuff in .storage. In one stroke, that solved lots and lots of problems. But the work to make that possible took some time, so the release couldn't be finished before the beta was published. That's why thinks may seem kind of half-finished in 0.84.
That's half of the reason. The other one is basically that there were a lot of things that were inconsistent or not just right that we have wanted to change for a while, and they were all bunched together into one break-everything release rather than several breaking ones.
TL/DR: Somebody solved a bunch of problems, and created some new ones as a result 😛
And: Would you rather have to fix your config once, or several times over the next few months?
what I dont get is things like now I got a toggle on any card except the alarm panels for the auto view .. links dont work but just being displayed - camera are entity icons automatically with a status - just looks a bit rushed
Good evening folks, do I really have to name the entity twice for the entity-button when used with a service?
https://www.home-assistant.io/lovelace/entity-button/
yes
just found out that I can switch to action: toggle instead of action: call-service with service: switch.toggle ...
won't help with scene.turn_on though ...
Is it know though, that I have to click the entity-buttons twice?
First time they shrink, next they do ...
Looks like this for me
Seems to be because of a horizontal-stack they are packed in
mmmh, no, they even change size when I resize the window
@vapid lance I added it to the changelog. Thanks.
PSA for all: We very much welcome PRs for documentation errors that you come across and doing so super easy and gets your feet wet on contributing to open source if you haven't before.
Users are the ones that are most likely to spot errors and doing a quick PR helps us all out.
@polar kelp was wondering, lately it seems i see some problems with some cards and also custom updater and tracker card, now the weird parts is that the error always refer to
Can't find card-tools. See https://github.com/thomasloven/lovelace-card-tools```
i don't even have that card card-tools
i only see this behaviour sense versions 0.84 +
Have you tried following the instruction?
ohhh dumm me didnt pay attention to it, sounds like now you need card-tools.js
my bad
No worries
Card-tools is a collection of neat functions that I use in many cards. Previously I’ve just copied them every time, but by puting them in their own plugin I can give them more focus and keep the quality higher in regards to descriptive errors and such.
hey, can someone tell me why I have this (marked in red) and only after some time I have the one marked in green (while in popup it's always ok)? i have deleted cache in browser and it didn't help https://i.imgur.com/MfUEaH1.png
@polar kelp I need to carve out some time and play around with those card tools. That's so cool that you made those.
I have a few custom cards that could use some TLC and that would be a great addition
It'd be awsome if they could be of use to someone else than me!
I would love to see something like that be a base that HA provides to custom card creators to build off of
All of it lowers the bar of entry for others, which is a huge plus
I actually suggested that at some point. I think having access to things like createCardElement would minimize the step from custom card to core card.
Yeah, that would be great. There are more and more amazing custom cards out there. Many of them will never make it into core, but making them easier to create is amazing and hopefully we can come with a way to more easily install/maintain them as well
@tired ice the translations are acting kind of weird for some things in lovelace. I haven’t really kept up, but I’d guess someone is looking at it.
Not sure if i missed a breaking change, but is tap_action: more-info not working for climate entities any longer?
within Picture-elements card
@keen mantle you have. https://www.home-assistant.io/lovelace/changelog/
ah, got it. didn't notice the action is now under tap_action, rather than defined next to
thanks @mild veldt
Any idea why this is giving an error?
- type: entity-button
entity: input_select.home_mode
name: Security Mode
tap_action:
action: call-service
service: input_select.select_option
service_data:
entity_id: input_select.home_mode
option: Away
mapping values are not allowed in this context in "/home/homeassistant/.homeassistant/ui-lovelace.yaml", line 38, column 20
- type: entity-button
entity: input_select.home_mode
name: Security Mode
tap_action:
action: call-service
service: input_select.select_option
service_data:
entity_id: input_select.home_mode
option: Away
guessing you followed the example? Looks like it was wrong
Merged 😉
Is it possible to hide the header toggle on the entity-filter cards? They don't seem to have an show_header_toggle option
The entity-filter card isn't really a card, it's just a filter around the card that you define. You likely just didn't define that card as the default is an entities card. Go ahead and do so and then you can set show_header_toggle
- type: entity-filter
entities:
- device_tracker.demo_paulus
- device_tracker.demo_anne_therese
- device_tracker.demo_home_boy
state_filter:
- home
card:
type: entities
title: People at home
show_header_toggle: false
@mild veldt awesome, that was the piece I was missing! Thank you!
i get "Unable to parse...blablabla, line 421..." in the raw editor. Would be helpful to see the line numbers then... 😃
@brisk osprey raise a feedback issue in ui-schema as recommended in lovelace docs
Ahh - Just struglle hard to turn on scenes with a toutch
somebody care to share a config example?
ah finaly
- type: entity-button
icon: mdi:sleep
name: God natt
tap_action:
action: call-service
service: scene.turn_on
service_data:
entity_id: scene.god_natt
entity: scene.god_natt
helped
Hi
I am trying to install a new theme. I have created a yaml file called theme_midnight.yaml
In config: frontend: themes: !include theme_midnight.yaml
themes: !include theme_midnight.yaml
error: ``` - Invalid config for [frontend]: expected a dictionary for dictionary value @ data['frontend']['themes']['accent-color']. Got '#E45E65'
~yaml
YAML is the mark up language used by Home Assistant. Consistent indenting (two spaces per level) is key - read more at https://home-assistant.io/docs/configuration/yaml/
Is it possible to use a include file in a card?
I would like to make a list of entities for example all my magnetic switches and then include that file wherever needed so i only have to make changes in one place.
When in yaml mode, yes
Ohh cool
how do i update the tasmota switch value automatically on the lovelace ? the light is on but the dashboard shows as off
so the state is 'off' and you want it to say 'on'?
yup just wanna update the current state of the switch entity
other switches are working fine
you can't update the state
?except for few, is it the tasmota version
but, regardless, this is not #frontend-archived related
Thank you, between the new update broke my lovelace. Any fix ??
the dashboard has the badges which is seen like in the states page
did you read the release notes?
will read it again, i believe🤔 i skipped the main part
you're likely in auto mode
let me give it a other shot
lovelace:
mode: yaml
does this needs to be in cofig yaml ?
yes, configuration.yaml
It kind of does. It was a change we made for lovelace.
@mild veldt successfully running lovelace on yaml :), but my systemmonitor entity is not available
read breaking changes. pretty sure there was something changed there
#330944238910963714 can help you out further
@mild veldt Thank you mate 😃
i get the error when i go to the normal frontend, not lovelace
Just trust me 😉
First I want to say thank you, for the cool new lovelace integrated into the default frontend, including an editor to configure it. Thats the right way! Today I nearly always use the feature panel: true with my surrounding card to get the cards to the optimal size. In that area the editor cant handle it, the edit link is even now shown here. Probably the reason is also the nesting of cards. I would suggest to let us directly scale each card by using either % values, fixed values in the raw mode or by using mouse actions or whatever. As soon you have this editor ready. You are a big step towards an end user usable product! Next step would be to get rid of this configuration.yaml thing. It is horrable. We need a single file per topic not that one big thing with includes, where everbody can do things in a different way. Also all configurable by the UI.
how I can stack horizonal and vertical stack?
@forest pebble being thick-skinned, posted a message that is more than 15 lines. It is now available at: https://paste.ubuntu.com/p/MhWQHWsNnY/
thank you @forest pebble
@naive tulip No problem - bookmark the following page. It should help out in the future.
https://home-assistant-lovelace-gallery.netlify.com/#
Just started using the UI editor for Lovelace today and short of stating good job, I wanted to point out a few things I noticed from a UX perspective.
Obvious Omissions:
-
Tab Order - There needs to be a simple way to reorder tabs. At present the only way I can see to do this is to delete all of the tabs and start building them again from scratch.
-
Tab View Variabls - There seem to be some omissions in the Tab Creation window, like Panel and Background
-
Moving Cards Between Tabs - There should be a way to move and or copy Cards from one tab to another. I am aware that I can open a card, copy the code, create a new card in another tab and paste the code. This feels sloppy from a UX perspective though. Reminds me of that old trope of designers vs developers.
@forest pebble t's great this link.. thank you
@forest pebble any suggestions will be lost in here. If you or anyone else have feature requests, they should be logged in https://github.com/home-assistant/ui-schema/issues
also note that this is obviously not our full UI editor. Things are evolving quickly
@mild veldt Thanks I was wondering about that.
The suggestion to add suggestions to chat should be removed from the bottom of the lovelace introduction page. Or at least made clear that suggestions go to ui-schema and discussions alone go to chat.
https://www.home-assistant.io/lovelace/
Ill post up in the ui-schema page.
Thanks again.
PRs to docs are welcome as well 😉
Hi, why a binary sensor with device_class door is now on or off instead of open/closed? This happens only in lovelace
fix will be in next beta @brave badge
*hot fix
Thanks, is there a PR for that? I can't find it
Ah ok, it's in polymer... Thank you!
How Do you run scripts now?
same as scenes?
@civic sedge depends on what card you adding them to, somewhat. Alignment of variables/options is not 100% complete. Easiest is to just add to an entities card
I guess toogle wont work
I had
name: Kill
tap_action: call-service
entity: media_player.bad
now
tap_action:
action: call-service
service: scene.turn_on?
Pewwww this braking change is a nightmare
Its literally the same though
except as an object
tap_action:
action: call-service
service: media_player.turn_off
service_data:
entity_id: media_player.bad
Hi all, i was wondering if there was a way to make a view in lovelace that i would be able to load without the h.a. header. The point to this is to have my old tablet as a control panel. It would be mounted on a wall, always on with the custom view showing in a browser.
Ok. I have used the lovelace add-on before just to test lovelace but if I don't want to use that one does the new method create a new lovelace setup from the default gui? Or how does this work. I have tried to find a an explanation but can't find any that I can see explains this. Also if I have a lovelace file, do I need to delete it before setting the system up now for the new method? And is it only from the (i) that i do the switsh to lovelace? When/were should I get the question aboute what type I want to use?
Also, do I need to reboot after clicking "use lovelace as default"?
@mild veldt that's the thing. I don't want to use my existing yaml file made with the add-on. I want to start from scratch. What then?
Just upgrade. You have to explicitly state yaml mode to use you ui-lovelace
I'm already on the latest version. When clicking the "test lovelace" in the info part of Hass I only get a blank screen saying "
Error while loading this panel. Go back" the logs don't give me anything stating what goes wrong.
Clear your cache
~lovelace
Hi, is there a way to hide the top line (blue menu) for a view that should only be shown in fullscreen?
I just have a suggestion for when the time comes that you shutdown the old HA UI and just go to lovelace. Because a lot of us are making custom UI's that are for tablets and use images etc could you put two directory's in for a tablet and a mobile version, so when you initially logon to HA you get asked which one you want to use then you use that lovelace configuration. It would mean that you could make a custom UI for tablets with a bigger screen size and use the normal lovelace UI for smaller devices such as phones. Just an idea?
Quick question, not sure what I'm missing, on the picture-elements, for an element of state-icon, can I not control the icon image and size?
@slender pond You could raise a feature request in the Feature Request of the forum
I believe though that there's already some plans for that, but it won't be until after states (the current UI) stops being the default (and possibly not before it's gone)
what to do now after i clicked to have lovelace as default? nothing changed yet...
i need proof 😄
oh it worked
ssl error
hah
😮
there is change yeah 😄
👍
relogin did it i think 😛
@split granite was the comment about the plans to my comment?
No
The answer to your question is in the docs
If there's no option listed, it's not possible (at least currently)
Icon images can usually be changed with customize though
The doc is a bit confusing to be honest, it mentions Icon Element, but its not clear how its a applied.
Actually I see now there are two different types, state-icon and just icon. state-icon doesn't let you change the icon directly where icon does.
configuration.yaml
anyone know if there's like a to do list card that can tie into ha like google keep? https://imgur.com/a/Jbv0Dvq - I want to fill the space next to the temperature with like something say 'shopping list' or something like that
Since this last upgrade the glance card tap_action stopped working. Can anyone help me understand if something changed?
- type: glance
entities:
- entity: group.luzes_sala
tap_action: toggle
I think its like
tap_actionn: toggle
https://www.home-assistant.io/lovelace/glance/ it's now a list type thing
hum... thanks but it still doesn't work @slender pond
- type: glance entities: - entity: group.luzes_sala tap_action: toggle
the documentation doesn't have any example. I actually had read it again already since the upgrade but it seems unchanged.
- type: glance
title: Sala
show_state: false
entities:
- entity: group.luzes_sala
tap_action:
toggle
this, right?
not working. I am 100% sure it reloaded because I slightly changed a name
Ohh sorry hold up
ok I got it
- type: glance
title: Better names
entities:
- entity: binary_sensor.garage
name: Movement?
tap_action:
action: more-info
exactly 😄
I found it by browsing the Discord history 😃 Yesterday someone posted it
thank you so much @slender pond !
I would gladly stop editing yaml files manually but I tried to use the on-screen editor and I can't seem to understand how to build a card. I tried to build this exact card there and it keeps saying it is invalid 😦 I wonder where I can learn how to do it.
have you tried letting the automatic thing do it's work then editing the yaml?
well... my yaml files were already very much to my liking and the automatic thing doesn't add much value to it. I guess I'll keep editing yaml files until the ui editor is more evolved.
http://hassio.local:8123/states/ not found?
using lovelace and did an iframe to this url... smthg missing?
i want the old states view in lovelace too
remove the / after states
I think there might be something wrong with your lovelace?
Can I ask about the ID in lovelace? A few versions back, Lovelace generated ID's everywhere but it seems in 0.84.x this has been replaced by Path and Path is optional. So can I go through in the raw editor and delete all the ID lines?
they don't seem to be causing any problem although in one tread on the forum someone reports they are crashing his lovelace
thanks Zac
Is it possible to apply a theme to the Alarm Panel card?
0.85 you can 😉
wiped out all ID's and don't use path and all is well
Great! thanks
@mild veldt Thank you for the link.
Anyone know how I would adjust a css element that has the name #map? do I go --map?
Anyone here use the folder-row card?
Can lovelace transition lights?
How do i make my css in lovelace work across different sizes of screens and like not get messed up?
I just tried switching to the ui configurable lovelace and.. does it not support custom cards at all?
the only way to preserve the functionality is to do "Raw config editor" as far as I can tell..
Hi lovelacers
What's the best way to have a picture element navigate away from my HA instance?
I can't use the "Configure UI" option. The card configurator just loads and the code never comes up. Is this known?
@wary dust You've tried putting a URL in navigation_path?
@split granite yep
- type: image
image: /local/assets/cctv.png
tap_action:
action: navigate
navigation_path: 'http://security.<my-domain>.ca'
style:
top: 50%
left: 91.8%
width: 100px
Does anyone have any idea how I can move eastside beside driveway?
Image: https://imgur.com/a/eWV19Ir
Yaml: https://paste.ofcode.org/38nXQXuwuqEYvXewa9XWU5m
@slender pond This is what I use for a camera grid view
cards:
- type: horizontal-stack
cards:
- type: picture-entity
entity: camera.driveway
- type: picture-entity
entity: camera.backyard
- type: horizontal-stack
cards:
- type: picture-entity
entity: camera.garage
- type: picture-entity
entity: camera.front_door```
That formatting is terrible btw
Mine?
Could someone explain me why this
- name: Aus
entity: scene.klo_aus
type: entity-button
icon: 'mdi:sleep'
tap_action:
action: call-service
service_data:
entity_id: scene.klo_aus
service: scene.turn_on
```turns on every scene on I got ? _ But only at this card
while this
entity: scene.sz_aus
type: entity-button
icon: 'mdi:sleep'
tap_action:
action: call-service
service_data:
entity_id: scene.sz_aus
service: scene.turn_on ```works as expected
https://hastebin.com/awequsiloy.sql <-- Config going crasy
https://hastebin.com/caxukivaku.sql <-- Config working
(am I crasy? That is absulutley the same)
@slender pond no mine in that post 😆
Oh haha I was gonna say jeez is there like a formatting secret that saves me from doing all this copy and pasting. Knowing my luck in about 2 months there will be
@civic sedge scenes work as expected using services?
Wich services? @slender pond
It works now btw - I copyed the working config from an other room over
But Its bugging me that this behaviur occurs
@wheat current Yes, it's installed and ready. 😃
@mild veldt have cleared my cach 100 of times. Not helping. Today I also fixed a base url issue. But i Still get the same "error wile loading this panel". I have tested with both :8123/lovelace and .com/lovelace with the same issue...
does picture-entity support navigate now?
and if yes, does it already work from 0.83 onwards?
So, action: navigate is in the docs. So it should support it "now". But with a quick glance the change seems to be recent, so I assume it is not in 0.83
@atomic citrus what's your configuration look like?
@hybrid bobcat navigate to Lovelace from dev-info 
And what mode are you in?
@mild veldt same when accessing it from dev-info. Mode? I still on old gui (have not set lovelace as default because of my issue)
Just to confirm. You did not set YAML mode?
Hi! I am using YAML mode on 84.3 and i keep getting this error. ```Wed Dec 19 2018 13:16:30 GMT+0100 (sentraleuropeisk normaltid)
https://XXXXXXXXXX.duckdns.org:8123/lovelace/0:0:0 Uncaught
@mild veldt nope, when/were do I do that?
@hybrid bobcat so you're on 0.84.x, have never used lovelace before and when you click on "Try lovelace" from
is does not load? Any errors in you browser console or HA logs?
I used the add-on to create lovelace file and tested it by using :8123/lovelace to test it out before 0.84.x but never set it as default.
@mild veldt
what version are you on now?
@hybrid bobcat easiest way to try Lovelace is to just upgrade 0.84. No need for add ons. Likely that the add-on didn't have everything you needed to run LL in a previous version where IDs were required
@mild veldt I'm on latest. 0.84.3. so what to do from here? Delete the add-on and the ui-lovelace.yaml and reboot? Would that be enough to get the mode option question? Because I don't know when or where to expect that question.
@hybrid bobcat you shouldn't need to delete that file if not in YAML mode but it wouldn't hurt either. So, yes, delete Lovelace YAML file, make sure you don't have anything about Lovelace in your configuration YAML file and reboot. Should get an auto generated dashboard when you try Lovelace then
@mild veldt 👍 will test when I come home from work. Thanks in advance!
Nope. Leave work early 😉
@mild veldt whish I could 😂 but the psychiatric institution really want to have their assault system up and running before Christmas 😂
I won't get in the way of that 😃
there is a way to increase the aspect ratio of a picture-elements card?
Change the picture
it's a plan of the house
I think thomasloven means you should alter the file. So change the aspect ratio of the image file you use in the picture-element card.
I have changed the aspect ratio of the pics as you suggested but I'm not satisfied with the result 😃
is there smth like a tv remote 'template' for lovelace?
@naive tulip , what is the point you are not satisfied with? Does HA not display with your chosen aspect ratio?
@viral root no. I would recommend using picture-elements with buttons
is there a good guide for lovelace with examples so I can read up on it
Yeah, start with the docs. If you need inspiration for views and ways to arrange things, just google it. There are many people sharing their configurations.
@livid ruin nothing related to HA it display the png file in the correct way.. I'm not satisfied with the result with my png file.. it has a rectangular view maybe it's too large for the aspect ratio of the card.. and I'm seeing the image too small
@mild veldt 👍
so you had the image the size you wanted before but not the ratio? did you stretch the image or add "white" space to it
try the other method see if that looks better
In a subfolder of your config directory called "www".
thanks
if I change the rotation of the image vertically, it is much better
https://www.home-assistant.io/components/http/#hosting-files @viral root - did you read the note?
After all, the project has grown organically. One side effect is that information is sometimes scattered and not always properly linked to.
some tuts would be fine 😃
Feel free to write some 😉
There are plenty in the internet! Just google. Or write your own and link it!
The docs are largely user input, so if you think you can improve them, please do
For the floorplan thing I also followed some tutorials.
That has the benefit that you're not reading outdated tutorials from an old version of HA 😉
but should be managed 😃
Yeah, but anybody can fix the ones on the site
ye
If you find an outdated one, you can fix it
any help on how to get into that? editing the docs?
If there is no one managing, then they are not. This is a project done in the free time of most participants.
@viral root Top right of every page - Edit this page on Github
And it often seems more important to get a new feature in than to update the docs. But these problems are present in all projects of all sizes.
👍
I think Home Assistant is rather exemplary in the state of their docs. I know much, much worse projects...
A question about the tap_action: setting. Is it possible to set it to the whole card? Its quite tideous work to add two lines to every entity! Lots of lines...
I think you need to add it to every entity. The configuration is not expecting it anywhere else.
yeah ha & co have very nice docs!
That would be a real shame. Can I add that as a suggestion for future updates? 😃
Sure, post it on the forum, in the feature request section
alright, will do @split granite
Hi, I installed a new raspberry with hassio. I'm trying to setup lovelace with the UI and when I click on configureUI/ take control I get this error: "Saving failed: Not supported"
Any ideas?
Never mind... solved.
Hello!
i hope you can give me some advice i am using Lovelace and have Hass.io .82.1
i hesitate to upgrade to .84.3 because i donnot know which format of lovelace i should use in the future.
should i stick to yaml mode or is it going to be removed in the near future?
should i change to storage mode? is this the way for the future? do i loose any features or customizations?
is there a comparison or a simple advice in this case?
thx
@gloomy raven yaml mode is not going to be removed
going to storage mode you lose the ability to use !include and !secret and cannot edit the file in an IDE as it is system managed but does provide you a UI interface that will be more intuitive
storage is the future and where development/features will be more noticeable
ok so i can edit the file in the ui inteface to change the code? i donnot loose any functionaliity?
i do not need a IDE if i can change all code especially for custom cards in the "new" ui like in the "configurator"
no need for !secret also because i use Hass.io it locally.
there is a raw editor that allows you to work on custom cards for now, but doesn't provide any syntax highlighting or validation until you try to save. we hope to make it more robust in time. we also hope to better support custom cards so that they can have UI editors as well
thx, i think i give it a try ;)
too long after i messed up my installation the last time,
its time again 😉
Is it possible within Lovelace to have a script represented by an icon where when you tap the icon the script executes?
Yes, depending on what card you are working on.
hey guys, im updated to 84.3, changed to storage mode and saved my lovelace yaml file in the editor, it was giving me an issue when I tried to custom-ui stuff, so I cleared out the code from the editor but left a line in there I think and now nothing is displaying on the lovelace page, not even the menus. I swapped the configuration to using the yaml file and it works, but I want to use storage mode. I reinstalled a previous snapshot then upgraded again, but its still that way.
@honest cliff you likely had an error in your yaml that you saved in the raw editor. we're hoping to make the more robust so that at the very least you can get back to the editor.
you can edit the storage file, not recommend, but in your case that would be the resolution. it is stored in json, instead of yaml, which can in some ways make it a little harder to work with/debug.
also, what do you mean by custom-ui?
actual custom-ui or custom cards?
@mild veldt I meant "Configure UI" and where do I find the json file to edit? I dont mind poking at it to try to edit. Worst case I burn it all down and start over. No big.
hey guys, since version 84 there have been quite some changes in lovelace, in particular the - type: entity-button icon: mdi:sleep name: God natt tap_action: action: call-service service: scene.turn_on service_data: entity_id: scene.god_natt
- type: entity-button
icon: mdi:sleep
name: God natt
tap_action:
action: call-service
service: scene.turn_on
service_data:
entity_id: scene.god_natt
thing is anoying. ther are two entity entity definitions in here
we could have a default, where entity_id can be omitted and it would take the vale of entity from the icon itself
- entity: scene.kickern
icon: mdi:soccer
tap_action:
action: call-service
service: scene.turn_on
service_data:
entity_id: scene.kickern
is a better example. the scene.kickern is totaly redundant
goode evening people
i have read this:
So if you were using Lovelace before 0.84, you now have two options. Option one is to use the new storage mode and import your existing file. You can do this by opening the Lovelace UI and click on Configure UI,
i cant find the configure UI button
top right corner I think
there is nothing there
i ugprade from older version to 0.84.5 and ium getting the no config found erro
x-special/nautilus-clipboard
copy
file:///home/malte/Pictures/Screenshot%20from%202018-12-19%2020-29-01.png
thats a local url :p
year
I was giving it a try
the thre dots on the top right
there I have a submenu ´configure ui´
there is non three dots
is there a bell?
nope
you look on your phone?