#frontend-archived
1 messages Β· Page 97 of 1
yeah ok, should read more carefully
Lovelace isn't designed for fixed layouts, but that card, or a mix of vertical and horizontal stack will get you as close as you can
that card had configuration option for background image, that fixed the issue
Hi, I have strange issue in my lovelace dashboard. When I open entity with a chart, it shows the chart for a while and after few second, the chart is replaced by random chart from other entity. It is super weird π
Eg. I opened Vacuum detail, it correctly shown vacuum state chart, after a while the chart was replaced with processor usage chart. https://i.imgur.com/5nNVpM2.png
I can reproduce this with any entity with chart detail, all are now replaced with processor use after a minute or two, but few hours ago, it was being replaced by different chart
@winter knoll known issue https://github.com/home-assistant/home-assistant-polymer/issues/2438
hey folks, im seeing an error in lovelace...custom element doesnt exist: button-card
config?
sorry ill grab it
- url: /local/button-card.js
type: module
- type: horizontal-stack
cards:
- type: custom:button-card
color_type: icon
entity: light.bedroom_light
action: toggle
name: Main Light
icon: mdi:floor-lamp
#color: rgb(255, 131, 0)
- type: custom:button-card
entity: switch.bedside_lamp
name: Bedside Lamp
anyone know the deal with custom components and Kindle Fire tablets?
it seems that once the card becomes "official" it works fine. like the alarm card, or the thermostat card
im getting this error
ERROR (MainThread) [frontend.js.latest.201901091] http://192.168.0.133:8123/local/button-card.js:1:8 Uncaught SyntaxError: Unexpected token {
it was recently updated - make sure you have latest version of the card
yeah i just downloaded the latest version and still get that error
clear all data and cookies?
@vapid field There's not supposed to be a { at position 8 of line 1. Are you sure you got the right file?
In the old version there was, though.
Yeah I just got the latest version last night
@polar kelp could you link the correct version so I can triple check please
Assuming we're talking about kuujis button-card: https://github.com/kuuji/button-card/blob/master/button-card.js
Thanks @polar kelp that's the one I have
I'm not at home right now, but I'll try removing existing .js file and redownload it again
You should also add a version tracker variable to the URL. This is likely to be a caching problem. See the article I linked before.
is anyone aware of any change with the conditional card in 0.86.0b3?
I am trying to add one and it just won't save
- type: conditional
conditions:
- entity: sensor.recycling_bin_today
state: "True"
card:
type: picture-entity
entity: sensor.recycling_bin_today
show_name: false
show_state: false
image: /local/images/recycling_bin_tomorrow.png
I have created the sensor
I was following an example from someone else doing the exact same thing. Iβll try without.... he may have had single quotes...
Yeah that was more of a question. I didnt think you needed them but I could be wrong.
how can I use last-changed with an entities card?
I've tried this and it doesn't work.. as well as many other iterations
- type: entities
title: Family Room Lamp
show_header_toggle: false
entities:
- entity: switch.family_room_lamp
- entity: sensor.family_room_lamp_power
options:
secondary_info: last-changed
@viral sorrel
- entity: sensor.family_room_lamp_power
secondary_info: last-changed
is enough.
thanks.. and it seems it's needed after each entity
Hey guys, some shameless self promotion incoming. Check out my new lovelace card! https://community.home-assistant.io/t/lovelace-check-button-card/92980 You can use it to track all sorts of things.
@lofty summit cool idea! Going to add it on sharethelove
@polar kelp - can we discuss secondary_info?
Sure
So I've been playing with a combination of versions...currently running the latest HA .86rc and card-tools 0.2. As I mentioned, the code works fine before yesterday's card-tools commit. Now, the behavior I am seeing is that my custom elements are being rendered when the page is being built (stepping through w/ Chrome debugger)...but something comes through after that which wipes out my custom elements and replaces them with the 'standard' entity rows.
Would your change explain that behavior?
That's odd...
I thought so too π
It should work in the rc... Is it not working with the next-branch of card-tools either?
@mild veldt cool thanks! π
I tried earlier, but was on the dev branch at the time, not rc
It sounds like a ll-rebuild or rebuild-view event that's going wrong somehow.
Should work on dev too
I'll drop in the .3 and retry (it is also at the beginning of my resources FWIW)
Can you briefly describe that the ll-rebuild is doing?
In short it causes a card to be rebuilt after a custom element has loaded in.
.3 actually causes a different problem...the custom entityRow that I create no longer returns an updateComplete
It's fired by the placeholder lovelace puts in when it can't find a custom card whenever the correct customElement is defined. It's handled by the view or stack cards to avoid having to reload everything at once (which caused the flashing before)
Did you notice that cardTools.litHtml() is now a function?
(If you're using that)
I did not...let me take a look
So I guess I'm not clear on how to use that now (just learning off your previous examples in fold-entity-row). My current render function looks like this:
render() {
return window.cardTools.litHtml`
${this._wrappedElement}
`;
}
What should that look like in the enw world?
render() {
return cardTools.litHtml()`
${this._wrappedElement}
`;
}
The readme in the next-branch is also updated with new examples.
There are a few breaking changes. Sorry.
well, well, well...looks like we might be back up & running!
I'm going to run a few more tests, but it looks like everything is fine with .3 after the litHTML change. Thank you!
If you get a chance, I also wanted to call your attention to the issue I logged yesterday. Your default row type for climate is incorrectly set to toggle. Would it be possible to change to climate in the .3 release? Customizing climate happens to be my primary use case for secondary_info!
Of course. Thank you!
just updated to the latest version of HA and my lovelace frontend has completely disappeared
Great timing. Release of 0.86 is just hours away. Will it not load at all, or is it filled with different stuff?
im trying to get theme loaded from themes/ folder, but it just keeps saying theme not defined. Can theme be loaded from yaml file, or do i need to add it to configuration.yaml ?
https://pastebin.com/pXPu3PDN this my config
That should work so far
made selector for it by youtube guide
automations : https://pastebin.com/Mis6s4nq
hass script check doesnt give any errors
then in theme folder i have material_dark_theme.yaml
@raven nacelle does your demo dashboard work on a mobile device? or do you use a custom url?
@potent fjord What's the first line of themes/material_dark_theme.yaml?
You're welcome
@hot gyro demo.home-assistant.io works on mobile too for me
Can we change the line color on the sensor card by using a template within customize_glob to change hs_color to diff variables depending on temperature? Or is the only way to set up themes for each sensor card?
didnt check mine is downstairs so I thought I'll ask π
@simple jolt Themeing is the official way. Card-modder can probably do it too, though.
@polar kelp yea donβt really want to create an entire theme just so I can have diff line colours.
I can fully sympathize with that. This might help: https://github.com/thomasloven/lovelace-card-modder
Hello, I am totally new to HA, and I am testing it out. I have got it up and running with KNX-support. (I have a lot of knx-equipment). According to what i have researched the "lovelace" UI is the way to go, and the Arelia-app is the best app(?). But I was wondering if it was possible to show a "dimming bar" for lights, directly in the UI, instead of just turning the light on and off? (If i click in the name i get a bar, but i want to do it directly).
https://github.com/thomasloven/lovelace-slider-entity-row is possibly what you're after
Thanks I will check that out
@polar kelp would you know which element represents the line colour to use with card modder?
@simple jolt there's plenty of existing themes where you could simply modify what you want
And you can also define a theme with only a single variable. The rest will be filled in from the current user theme. But the point was to not have to do that.
Home Assistant 0.86 has been released. Lovelace is now officially the default UI!
so with lovelace becoming the new default UI what is going to happen with all the components that turn into yellow bars in lovelace?
Yellow bars mean that the entity is not available
if you are in storage or yaml mode you should correct those yourself
Do you have an example? There are some components that add and remove entities dynamically.
when in generated mode, check your group config for non existing entity's
thanks i was able to get them corrected.. i thought they were unsupported components..my setup non lovelace is pretty different from the lovelace version
almost want to migrate it again and updat eit
For plugin creators: card-tools has been updated to version 0.3. Breaking changes! Changelog at end of readme.
Updating should help get rid of the flashing interface bug.
@weak flume it WAS the double quotes. I changed to single and it's working. Go figure....
@polar kelp custom-updater doesn't show the update yet
@polar kelp Thank you for the update! Just released the updated secondary_info plugin to go along with it.
@icy robin What secondary_info plugin?
@polar kelp when i try to load lovelace it just loads something that looks almost exactly like my frontend...i think it has autogenerated it and written over my old lovelace config
just seen that 0.86 has been released so will try that and see if it fixes things
Yes. That is the default behavior. Your config is still safe. Check yaml mode in the docs. On mobile, canβt link.
How will the new editor and custom cards work?
hassio still saying 0.85.1 is the latest version. Guessing 0.86 will become available tomorrow?
Bram has put one out for the weather-card
But it is only for editing right now. Does not show as an option for a new card yet. That functionality will be added later.
@mild veldt so i need to make a custom_cards.yaml for all my custom cards?
after upgrading to 0.86, the iOS app has started sometimes showing blank views until i force a refresh
If they donβt you can edit the yaml from the UI
@icy robin Thanks for that plugin, waiting for a solution like this for a long time π Finally I can put last_seen attribute of gmap device tracker under the name! Thanks!!!
@icy robin you should add that to the list https://sharethelove.io/custom-resources/rows
so let me get this straight, lovelace no longer uses what's in your ui-lovelace.yaml file?
@mossy otter https://www.home-assistant.io/lovelace/yaml-mode/
oh awesome, thanks!
am guessing that custom components can't be used on the yaml mode?
non yaml mode rather
if you switch back to yaml mode, everything works as before
Can you use yaml mode AND use the editor in the frontend?
no
you would mess up your yaml, if it is allowed to use the ui editor
the structure and the comments, etc
so the ui editor is using a different file
you are welcome
UI/storage mode has a raw yaml editor that allows to add custom resources
Well, this is annoying. Conditional cards don't accept empty string for state and state_not.
@winter hollow that sounds interesting. CAn you tell me a little more about that or point me towards some docs?
Check the demo: https://demo.home-assistant.io
@polar kelp fold-entity-row is broken with latest card tools
or maybe it's that I'm still on b3 - don't have release yet
@timid burrow it's rare for qemux86-64 to be last. I think we got put on some list.
anyone here use the darksky custom weather card?
when I enable tooltips: true on it the card dissapears in my frontend. dont know why. no error messages show in HA log
i am.. working for me
do you have the tooltips setting enabled?
yes
damn, mind sharing your config for the card so I can have a look at it and see if I messed something up?
sure..
I've really only changed some of the text positions and sizes. I can't edit anything at the moment because the card-tools is broken with 0.86.0b3 and I'm waiting for 0.86
all the tooltip stuff you highlighted is default
is card-tools required for this card?
nope
hmm dont know why but as soon as I enable tooltips: true card dissapears again, even tried adding javascript: latest to config.yaml
you got the new version from today?
yeah, just upgraded was actually a 0.8.2 version released as well. updated through tracker card and custom component buit the code is the same as on the github from what I can tell with a quick glance
same action in firefox and chrome with tooltips enabled
ok. weird
I am using that one as well
m.p.frankland is on the forum right now.... he might reply
ah last forum post helped me find an error thanks, will post in thread
sweet!
did you have to setup the slots for the tooltip popups to work?
hi friends
# This file was automatically generated by lovelace_migrate.py
# https://github.com/dale3h/python-lovelace
resources:
- url: /local/monster-card.js?v=1
type: js
title: Home
views:
- id: 0 # Automatically created id
title: Home
cards:
- type: glance
is this the right place to put the recourses into ui-lovelace ?
yes
hmm...
im getting
Custom element doesn't exist: monster-card.
{
"type": "custom:monster-card",
after restarting...
@dire salmon the migrate script is outdated and should not be used
Delete that file, remove yaml mode and restart
You'll then get an autogenerated view
and now it works must have missed some entity in the card
Select "Configure UI" from the top right and then raw config editor and you can copy the yaml into your ui-lovelace if you want to use yaml mode then
@mild veldt I did it ages ago.... and have all my layouts and cards setup how i like them...
do i copy paste it after deleting the file ?
am confused..
I see. It does look pretty old. Are you on 0.85 by chance?
0.85.1
you have yaml mode activated?
I dont know
then no
so from the ui editor you added a monster card?
to add the resource you need to use the ui editor as well:
menu > configure ui > raw config editor
ui-lovelace.yaml is not used when you are not in yaml mode
aah I see I see
if not in yaml mode, your configuration will be managed by the system
all edits will be done from the ui
π
@tepid locust I haven't - just defaults. as I said I can't edit lovelace until I get 0.86
I got it fixed, I must have been missin and entity in my config for the card. once I copy pasted the entities from the github into my config it worked
sweet
I was using a really old version up until yesterday evening
ah....
are packages going to work with lovelace?
yes
just upgraded to 0.86 - haven't played with lovelace before... my UI is now a big mess... i previously had a tab on home page for each room - basically configured with groups. i seem to have no problems with the slugify issue or the time/time pattern thing. HA started fine - it's just that now HA picked what to show on an overview - which is a bunch of card like things, some cameras, and now tons of icons that i previously had organized in via groups. SO, i selected the Configure UI option and it throws an error - "Saving failed: Unknown error" - in the log, there's a really long error message starting with ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140176861739832] Error handling message: {'type': 'lovelace/config/save', followed by a long list of entities and then a trace back ending with: TypeError: 'NoneType' object does not support item assignment. Anyone seen this and know how to workaround it?
sounds like it's displaying a default states page... can you click on side panel and then i in dev tools and click try lovelace?
i don't seem to have anything in a side panel that says "try lovelace"
click i in dev tools down the bottom of the panel
in the dev tools area , i have 6 little icons - like i have always had - services, states, events, templates, mqtt, and Info. nothing says "try lovelace" - clicking into info, nothing there either... i think my error issue is a browser cache issue.. i opened HA w/ a different browser & i can get into the UI editor and the view i''m getting is not as messy as what i had originally
Info = i then look in the right at the bottom of dicplayed info
@hoary ginkgo it will be fixed in 86.1
It's a bug when going from auto configured to storage mode
I'll roll 86.1 in an hour or so
ah.... I might get 86.1 before 86.0 at this rate lol
@hoary ginkgo you can get into the buggy state if you open the browser, then restart HA and then click on configure UI
If you refresh browser before clicking configure, it will go all good
on 86.0
86.1 won't have this issue
OMG how did you even work that out! lol
@timid burrow - ok, i see what you mean now - still don't see that "try lovelace" option - but also verified what @half osprey said... so i can get to the configure UI in original browser now
does it say states instead? It's because of what balloob said.. a bug..
yes, ok - wasn't realizing that was related to the bug too - thanks
anyone having problem with thermostat card?? mines just a small dot insteead of a thermostat
nvmnd its only config mod
e
how come lovelace doesnt auto update new automations or scripts? or entities?
because it's a clean break between frontend and backend
and you can display whatever you want to be displayed
i like how you can remove old entities very easily but i feel it will be tricky to find new stufff. but i do see the unused entities page so that will help
i was wondering if it was my config choice
86.1 has been released with the lovelace fix @hoary ginkgo
qemux86?
π€· I don't manage that one
thanks
hahahaha... I bet @mortal cape we'd see 86.1 before 0.86... usually see that almost immediately actually when you post
should i change from storage to auto generated?
well i just added a view.. but how i can change the order? i tried to add it manually in the raw config but couldnt get it to refresh
cut and paste.... when you save it will auto refresh
Just a note, Lovelace does not support having two tabs open and making changes in one and seeing it live update in the other
@polar kelp seems that the folding row card is not working since new card tools and it's not working with 0.86.1 either.. I was waiting for 0.86.0 to test (I'm on b3 at the moment) but report on forum that still not working in 0.86.1
Is there anyway to "import" a yaml lovelace ui to then use the online editing tool to make changes/future updates?
yes - just cut and paste it in raw mode editor
Thanks @timid burrow
sure
Iβll take a look at that @timid burrow. Thank you.
no thank you for the great cards!
Hi. Just updated to the newest version with Lovelace as default UI. All my light, presence detection entities are gone. Is that because I canβt use !include lights.yaml anymore? Hope it makes sense
@vapid field include in lovelace? If you want that you need to use yaml mode
lovelace:
mode: yaml
in config yaml
Is it possible to make a button, script or something that could refresh lovelace like in the dot menu?
Yes. But it's not easy.
hey guys, if I edit lovelace via the UI editor where does it save the config?
nevermind found it config/.storage/lovelace
just wanted to make sure it was a file I could backup before I went crazy editing π
Sure. That works. Or you could copy out of the raw editor, I guess.
thats true, I run duplicati to automatically backup
I was confused by where it was saving it
so long as its a file Im good
@timid burrow I think fold-entity-row should be fixed now.
@polar kelp , can you give me a hint how the refresh can be done?
I'm having an old tablet with chrome in kiosk mode and there the refresh menue doesn't work with touch.
Don't know why, always have to vnc to it and refresh.
input booleans are not supported on lovelace?
what do you mean by not supported? mine work fine
ahh possibly they've changed name from input_boolean to something else?
this is what happens when I don't update for a long time...
hmmm doesn't look like input_booleans have changed name yet I can't see mine at all...
input_booleans broke in my install too.
0.86?
Yes
Upgraded from 0.84.x to 0.86
Some includes had to be moved back to configuration.yaml too
And I removed some automations, but they still come as error messages during hassio ha restart, even though I removed them from lovelace and config-files.
This was really a breaking release for me.
@old karma It requires a plugin, possibly using card-tools and this function: https://github.com/thomasloven/lovelace-card-tools#fireevent
what file am I supposed to edit to edit the lovelace UI in the new version? Only thing I see is a file called lovelace in storage
Is it possible to move a view (left or right) in the UI or only in YAML?
Thanks @polar kelp , just want to write that VNC is easier for me. π
You are GREAT!
@placid geyser no, not yet possible in the UI
Thanks @winter hollow
@mossy otter Solved it - Removed /config/.storage/core.restore_state and /config/.storage/lovelace - Still has some issues, but the input_booleans are back atleast.
@timber peak interesting!! What further issues are you having?
Hey guys, so I'm playing around with lovelace, and trying to have a default_view that's family proof, and hoping that I can have another tab that continues to auto-generate an entry for everything, A tab I'll call "Advanced" which would essentially be an auto mode copy of the original default_view. Anyone done something similar?
@cerulean scarab As of right now you can't keep on autogenerating when you've taken control yourself
before I had customize_domain assumed_state: false to get the slider switch for *.switches, how do I do that in lovelace?
That should still work
I figured, I removed all customize from the config.yaml file and deleted the domain stuff as well, sorry. works again
but another question, there are some entities that dont have the cogweel option to edit name. I could do it by toggle editor, but is it expected behavior that it only works for some?
Yes, only for entities that have an unique id I believe
or that are in the entity registry
Anyone know how to get the configurator dialogs to show up in Lovelace?
There are three dots in the top right corner. Click them and select "Configure UI"
https://github.com/custom-cards/upcoming-media-card <-So I was trying to add this to HA now that lovelace is out, but... Where's the config file for lovelace? The ui-lovelace.yaml doesn't exist
There are three dots in the top right corner. Click them and select "Configure UI"
raw config editor?
Then in the same menu click raw editor
No, resources go there
Hi, a quick question: with the new lovelace UI configuration, should it be possible to have the same power as with the ui-lovelace.yaml file ? For instance in the sense of custom lovelace components and styles ? Thanks!
yes
and the customs components I add through the UI configuration will be mantained automatically ?
What do you mean with "maintained"?
the updater for custom lovelace components
Then no.
but I see that in the end I do have the raw editor
there I believe I can reference resources as in the old ui-lovelace.yaml
in the name: Kingia Castle
how is - type: 'custom:ha-demo-card' referenced?
The only way to add a custom card to the configuration (at this point) is through the raw editor.
yes, but in the sample there are no resources defined
name: Kingia Castle
resources: []
views:
- cards:
- type: 'custom:ha-demo-card'
- cards:
- cards:
- style:
border-radius: 20px
box-shadow: '3px 3px rgba(0,0,0,0.4)'
border: 'solid 1px rgba(100,100,100,0.3)'
overflow: hidden
type: 'custom:card-modder'
card:
- style:
- cards:
I don't see any resource there
in my local configuration (yaml) I have:
resources:
- url: /local/custom-lovelace/card-tools.js?v=0
type: js - url: /local/custom-lovelace/card-modder.js?v=1c480b
type: module
how should I reference them ?
The same way. The demo had to use some weird tricks to get everything to work. One of them is to import card-modder natively. Unfortunately
thanks bramkragten, I think I'm getting the hang of this!
Famous last words
The ones before or after the comma?
Hi everyone! Anyone with Javascript errors after upgrading to 86.1?
/frontend_latest/app-3b4bb4ed.js:365:157 Uncaught TypeError: Illegal constructor
Same error also shown on the official demo page https://demo.home-assistant.io/
I'm on Chrome 71.0.35.7898 on mac 10.14.2
on the lovelace UI editor...toggle editor is always blanked out
is there a way to activate that?
Toggle editor?
I mean every time I create something new on my lovelace UI it requires me to type it in yaml
one sec i'll grab a screenshot
That happens for cards that don't have an editor yet. Try e.g. the Entities card.
ahh gotcha
Ideally, I'd like to do half raw yaml, half editor but am guessing that feature doesn't exist yet right?
Getting there
It's a big project. The work done so far is incredible.
type: conditional
conditions:
entity: device_tracker.google_maps_1023187584267879
state_not: home
any idea what's wrong with this? Worked fine on my yaml config before so can't really see what's wrong with it now?
Error in card configuration.
{
"type": "conditional",
"conditions": {
"entity": "device_tracker.google_maps_102318758418723742879",
"state_not": "home"
}
}
@wise storm What is white? The button? The menu? The interface?
@mossy otter Conditions should be a list
@polar kelp The menu on the top right side. The three dots. When the dropdown menu shows displaying unused entities and help, the middle selection is white. Tried looking in the code for any html there, and it's just empty.
@polar kelp When I click the white button, something from what I understand is a lightbox shows up that is just white.
thanks @polar kelp got it working now!
Just noticed that also the notification boxes in the bottom left corner that shows a call has been done doesn't contain any text. It's just a black box.
This shows up in the log: "https://siteurl-redacted/frontend_es5/58305e17c69452ef67b3.chunk.js:233:70632 Uncaught TypeError: Cannot read property 'isRTL' of undefined"
That's... interesting...
Is your interface by any chance in a language that's written right to left?
And do you see the same behavior here? https://demo.home-assistant.io
@polar kelp Nope, language is in English. The demo site works fine.
How is it with groups btw. Would they cause issues with lovelace? I have a lot of entities sorted in group configs.
Hey, I must be dumb or simple, but, how on earth do I set up Columns in Lovelace?
@wise storm No, they shouldn't.
@proper crater Columns in glance card? https://www.home-assistant.io/lovelace/glance/
No, three individual columns with whichever cards I specify in each. Can't get my head around it.
Trying to get the layout to work perfectly on Fire tablet I'm going to be mounting.
That's something that is not possible yet... for now the cards are placed in columns based on the height of the card to spread them evenly
or you could create a view consisting of stacks
Ah, OK.
with the view set to panel
How would one go about doing that? That sounds ideal.
Hey guys -- If I add a view in LoveLace from the UI, do I have to restart HA before I can move cards to it?
I tried to get slider-entity-row to work. Where should I put the .js file? I get this error that the custom element doesn't exist
put it in your www folder in your config folder
Was just curious because I created a view named Garden, and it was not showing up in the Move Card list -- did a shift refresh and it's there now, thanks guys
if you just created www restart home assistant
@proper crater have you tried use the vertical stack? https://www.home-assistant.io/lovelace/vertical-stack/
that's how I define columns
I got another plugin to work but not this for some reason. I'll read up on that link and see if I can figure it out
There's also some debugging instructions in there.
this part is correct though? ```resources:
- type: js
url: /local/custom-lovelace/upcoming-media-card/upcoming-media-card.js - type: js
url: /local/custom-lovelace/slider-entity-row/slider-entity-row.js```
Looks fine
This is making no sense to me. Is this code correct to make these two lights show next to each other? If so, why does it insist on them being on top of each other when I save it?
My guess: Because of bad indentation, but that's impossible to tell without code formating
~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
That should work
cards:
- type: light
entity: light.living_room_lamp
- type: light
entity: light.bedroom_lamp```
Just update to 0.86, when i try to edit UI i get Saving failed: Unknown error
It just puts them on top of each other. And if I enter true for panel, it disappears completely.
I'm not sure, but try adding two more spaces before each line after cards:...
yeah, it might be indentation
has tap_action on entities changed?
in 0.83 or .84 or so, yes.
ah crap
The docs are up to date
had a wonderful entities filter card that showed what lights were still on and i just tapped them to turn them off
thanks thomas, got it to work. Hadn't downloaded the raw version and when I did it still wouldn't work until I added ?v=1 to the file path. I guess that forces it to re-cache it to hass or something?
yep
Not sure on Lovelace, it must be working because it shows up as default in the URL but I canβt edit the βcardsβ from the UI and thereβs no .yaml files I can see relating to Lovelace UI
To enter edit mode click the three dots in the upper right corner and select Configure UI.
Ive just tried that and clicked on βTake Controlβ and another popup comes up saying 192.168.1.63:8123 Saving failed. Unknown error
Just refreshed the page and all's good, thanks
i haven't paid attention to yaml mode in lovelace. can you use !include in yaml mode now?
π thanks. I'm not planning to use it myself, but wanted to confirm if others asked π
@untold magnet update to 0.86.1
or restart home assistant
Or you had it fixed π
there's a 0.86.1 already? 0.86.0 wiped my built-in lovelace setup π¦
as in everything I set up is gone and now there's a single page with every sensor
0.85.1
I wasn't using yaml mode before
Oh. From 0.85? Never mind then.
Are you in storage mode?
looks like everything by default sorts itself in to a column rather than trying to organise sensibly like it did before?
Everything I do is going in a column too soggypete
Trying the below with card modder but Iβm getting the error custom element does not exist. Iβve confirmed that I have the latest card-modder and card-tools installed. ```card:
entity: light.master_bedroom_level
name: Master
type: light
style:
'--paper-card-background-color': 'rgba(0, 100, 0, 0.2)'
'--paper-item-icon-color': white
border-radius: 5px
color: 'rgb(0, 0, 100)'
type: 'custom:card-modder'
Browser log?
@violet talon you didn't get an error somewhere? In the logs?
@violet talon @mossy otter - i saw similar things last night - per tab arrangements from prior to 0.86 were gone... try reloading your browser page. if your HA page was open during & through to the upgrade that seems to be related to this. or even use a different browser and you should see the view restore to something more organized looking.
@polar kelp that is from my phone.
Then your guess is as good as mine.
I can check chrome. How would I go about sending you the logs?
Just look for anything that seems relevant: https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins#browser-log
@polar kelp you should get your own channel for your custom components π
@winter hollow nothing out of the ordinary in my logs
and strangely enough everything is back to normal
even though my phone and an incognito window were showing the "single view with every sensor"
I deleted and recreated the container π€·
oh, I spoke too soon
it actually copied my "States UI" over to lovelace
so my .storage lovelace config is gone
(which again ins't a big deal because I have a backup)
does the old groups.yaml define anything in lovelace?
That yes β was for you, @civic stream
Hm, what was? Not so proficient in discord..
Yes, in automated mode
Is that the mode I disabled when I clicked the dots to edit it visually, in the UI?
yes
yes
Ok, thanks!
Now you're in "storage mode"
If I would like to backup this whole UI config that I now make, is there I file or so..?
-I+a
@winter hollow well it was. it's like I'd never used lovelace before and migrated my states ui to lovelace
You can copy paste it from the raw editor
(β―Β°β‘Β°οΌβ―οΈ΅ β»ββ»
Ah, ok!
i swear every time I refresh the page my ui changes.
That's probably what we should recommend *makes note
@polar kelp I found the below. Uncaught (in promise) ReferenceError: cardTools is not defined at customElements.whenDefined.then (state-switch.js?v=c7dd70
Why doesn't the "main switch" for a card do anything to the switches in the card? I have this problem for a card I've created where I list all my rooms (as yaml-defined groups) so that each room has a switch to turn all the lights in the room off. Before lovelace, the main switch for the card could turn off (or on) all lights in all rooms. Now nothing happens. Anyone has an idea why?
Can you share the config?
Use a light group
Can't since I want it to also control electrical switches in the walls and on outlets, that are not defined as lights in HA
@simple jolt Does your log also say that card tools is installed? In green
And is that before or after what you found?
@mild veldt switching a group should also work right?
It should
If it doesn't that would be a bug?
It would
Iβm just saying that a light group makes more sense
iantrich: thanks, didnt know about that component
It did, however, work before.. Without using light switch
π€·
bramkragten: The actual groups in the card works individually, even if they are switches, it's just the "card main switch" that does nothing
Would share a picture but cant get it into discord
ok, can you create an issue for that?
I think there is already a bug report for it...I think...
I can try, never done it before. Where do I do that?
Those titles are not very clear π
@polar kelp this is the full error. I cannot locate anything within the console that is green. Uncaught ReferenceError: cardTools is not defined at card-tools.js?v=090958:227 card-modder.js?v=812f2d:2 Uncaught (in promise) ReferenceError: cardTools is not defined at customElements.whenDefined.then (card-modder.js?v=812f2d:
@simple jolt do you have card tools installed?
So I can no longer define groups in lovelace?
@polar kelp you should make card tools a npm
Yes I installed it under my www folder and added it to my lovelace file under resources.
@civic stream it will be fixed
Groups?
toggling groups with the header toggle yeah
Ok, nice! But what about groups in general, is there any way to define them like you did in groups.yaml?
Hm... why did that ever work? I updated card-tools, @simple jolt. Please try with the new version 297fcc7.
/** Domains where we allow toggle in Lovelace. */
export const DOMAINS_TOGGLE = new Set([
"fan",
"input_boolean",
"light",
"switch",
]);
so groups should be added, anything else?
Well, before I kind of grouped sensors together to not have to add all of them individually to the config if I used them multiple times. But maybe you're right, theres no need for that
you can not toggle a sensor right?
@polar kelp updating card tools worked. Thanks again.
@civic stream youβll just add them manually now
No group needed
But if you wanted ALL sensors in a card, you could check out the monster-card
But in my card for controlling the lights of whole rooms, how would I define them? Now I have the old groups..
Light group
Meh. I wouldnβt recommend that for a group of lights
no was for the sensors π
Ah
What do you mean, light group
Is there a group for all my lights in my bedroom?
(That I didn't create?)
That would give you one light for multiple lights
Ok, thanks. Looks like exactly the same thing that I have in groups.yaml
But itβs not
gtr
Is it still possible to divide the config or do I have to have everything in configuration.yaml?
lovelace doesn't work with configuration.yaml
If you wish to divide your Lovelace config you can specify yaml mode
Both. I assume you can use the light groups when defining cards in lovelace?
Light groups are a component, I.e. backend. They are defined in your configuration.yaml
Lovelace displays entities but is not defined in configuration.yaml
Yes, ok.
This might help https://www.youtube.com/watch?v=BAgPPdH42Ko
But scenes and automations are still defined in scene.yaml and automations.yaml, or?
Nothing has changed besides the front end display
Groups were a hack for the front end
They of course have other uses
But in terms of using to display on the front end, they were a hack
Alright
Hi everyone! Anyone with Javascript errors after upgrading to 86.1?
/frontend_latest/app-3b4bb4ed.js:365:157 Uncaught TypeError: Illegal constructor
Same error also shown on the official demo page https://demo.home-assistant.io/
I'm on Chrome 71.0.35.7898 on mac 10.14.2
Iβm getting the same also on macOS chrome
Think I got the frontend confused with everything else
Or rather, not having a clear distinction between them, hence the confusion
Hey guys, I have a couple dynamic created entities that get created like when my iCloud sign in or Alexa needs to be refreshed -- These are unusually configurator.XXX entities -- Any smart way to handle them automatically in LoveLace?
@median otter I'm not getting that error
How do the up/down arrows work in the UI editor? They seem to move the cards also between the columns and not just up or down?
@tight canopy monster-card
@median otter glad is not just me..
@civic stream they just move it up in your config. Use stacks if you want more layout control
at CSSResult.get styleSheet [as styleSheet] (app-3b4bb4ed.js:365)
at renderRoot.adoptedStyleSheets.styles.map.s (app-3b4bb4ed.js:377)
at Array.map (<anonymous>)
at HTMLElement.adoptStyles (app-3b4bb4ed.js:377)
at HTMLElement.initialize (app-3b4bb4ed.js:377)
at new UpdatingElement (app-3b4bb4ed.js:344)
at new lit_element_LitElement (app-3b4bb4ed.js:377)
at new <anonymous> (app-3b4bb4ed.js:1305)
at new <anonymous> (8ee9235853b66c6b78f9.chunk.js:1071)
at new hui_root_HUIRoot (8ee9235853b66c6b78f9.chunk.js:5370)```
This is the error that Chrome is giving me after upgrading
same here
looks like a custom card...
are custom cards in www loaded automatically?
No
well then I don't know how the error could be stemming from a custom card, since I am using 'auto' mode
How do I reference my cards?
@civic stream youβre going to have to expand on that question
@median otter I canβt replicate. Were you previously on Lovelace?
I thought I could reference the history graph card I already configured in my vertical stack
Tried clearing cache?
@civic stream no. We hope to have a copy function in a future release
Cant get the history graph card to work when I put it in the vertical stack
The same config
Check your indents and the examples in the docs
Hi everyone !
I've a little problem with the map card
It seems both device_tracker are located as it centers on my home but I can't have the picture or even the circle which should mark the device location
Any idea ?
docs don't look like the preconfigured text in the UI-editor..
no dash before type: for example
That will be the only difference. The examples are full yaml while card is a snippet. The dash is there, just not shown
@vapid field device trackers are not displayed when home on a map
@mild veldt yeah I cleared cache/all application data in the browser
Got the history graph in the vertical stack, but the name of the graph does not show?
@mild veldt what do you mean ? because both devices are at home, there are not shown on the map ?
Anyone else having issues with their cameras loading in Lovelace?
is there a way to force event if at home ?
@scenic lantern You mean when you click the camera cards?
Yeah
@vapid field event?
I have experienced that the camera does not load
sometimes
when you click on the card
Yeah can't get any of mine to load on 2 computers or my phone.
@vapid field not at this time
I think the issue is not LL related. This seems to be related https://github.com/home-assistant/home-assistant/issues/18056
@mild veldt ok ! thx
and hopefully, https://github.com/home-assistant/home-assistant/pull/20314 will fix it
It used to work....not sure what went wrong
@raven nacelle maybe, didn't have the issue yesterday though.
this issue has been there for a while. I did not experience it initially, but have experienced it off late
You could downgrade to be sure
@scenic lantern that would be a good test to rule out that it is not LL related
weirdly enough, I am using Synology cameras and I am not even sure if it is FFMPEG related
@raven nacelle @mild veldt false alarm. Looks like my Synology locked up my non-synology cameras are working.
ok...I am also experiencing with Synology. What do you mean by locked up?
@mild veldt I simulated if one of the device were far away.... it doesn't seems to change anything
what should i have in the device_tracker.xxxxx ? only gps coord is enough ?
@scenic lantern What do you mean by locked up?
@raven nacelle actually I think I am wrong. I have an open issue with Synology where my system locks up and I can't access it. I thought I couldn't but now it looks like I can. So back to the downgrade test
@vapid field need lat/lon if thatβs what you mean
@mild veldt it's in it
You have the entities specified?
device_tracker:
- platform: mqtt
devices:
yann_pixel: /yann/android/pixel/location
perrine_pixel3: /perrine/android/pixel3/location
No, in Lovelace at the map card
- type: map
entities:
- device_tracker.yann_pixel
- device_tracker.perrine_pixel3
~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
yep... i was reading it π
entities:
- device_tracker.yann_pixel
- device_tracker.perrine_pixel3```
Looks good
i send the long/lat with mqtt
You checked the states for those entities?
device_tracker.yann_pixel
state: 48.83502293,2.29956203
entity_picture: /local/yann.jpg
source_type: gps
friendly_name: yann pixel
seems ok
ohhh
oky
how do you transform what you receive on mqtt to an attibute of the mqtt sensor ? need to use json_attributes_topic ? is that right ?
@vapid field Please use this channel for LL discussion only....for generic HA discussion use #330944238910963714
can I make one entity in a card conditional?
Like a conditional row? Not in official, might be a custom for it...
yeah
okay. I was thinking a media_player that would only show up in the card if needed
It would be possible in official I guess, with some hacking
Youβre thinking hui-entity-row inside hui-conditional-card inside entities?
@dreamy tendon look up entity-filter
the terms are still new to me so I'm not 100% sure what I'm looking for. I'll take a look at that
Yeah, thatβs what I was thinking @polar kelp
the problem is that it'll make all other devices that are "off" to disappear as well as the media_player? I'd like to keep those visible
Then Iβd recommend the most common entry point into the world of plugins: monster-card
okay, I'll take a look
can I have a custom entity (mini-media-player) inside a custom monster-card? π
No. But Iβm thinking of a replacement where tht would work.
Sorry guys, but I have a stupid question to make...
alright, thanks
Is it possible to have a card take up more horizontal space than one third?
I have created my Lovelace UI with the migration add on and I see it in /config/ui-Lovelace.yaml, but when I edit it directly from the frontend, I canβt see the yaml file modified... itβ still the same. Is there another yaml file somewhere else? What am I missing here?
If you use the frontend edit mode it will be stored in a folder called .storage.. The yaml-file will not be used. If you want to use the yaml file you will have to activate yaml mode for Lovelace and no longer edit in gui.
@vapid field
Hi guys, I'm trying to have a (temperature) card in lovelace that is only shown, when the temperature is below a certain value. Is that possible?
@vapid field You can achive this using this info: https://www.home-assistant.io/lovelace/yaml-mode/
@carmine radish have you looked in to conditional cards?
the default conditional card does state or not_state
it doesn't do less than as far as I can tell
@mossy otter Yes, however it looks like the conditional card does not cover my case.
I tried something like - type: conditional conditions: - below: '3' entity_id: sensor.temp1_temperature platform: numeric_state
ah yes, it seems it's a bit restrictive
how about monster card? that has a when
bit of a work around but what about an input_boolean that goes on when the temp goes under a certain temp, and the lovelace card taking the input_boolean being on as it's condition
monster-card is also great!
Two good ideas! Thanks, will try them π
@subtle rune thank you...
I'd probably do an input_bool based on a number slider and throw that under a settings section so I could adjust it right from the front end
Thanks!
@civic stream https://www.home-assistant.io/lovelace/views/#panel-mode
Just upgraded from 85.1 to 86.1. I have an automation and device tracker that say "Entity not available" on the main screen. How do I fix this? I'm not familiar with lovelace at all.
@supple raft Just check the entity name that you have configured.
Entity not available means that you have specified an entity that is not avialable
You have that entity in your groups probably
Yes, they are in my groups.yaml
So you should fix it there or take control of Lovelace
Guess I'm confused. Do I fix it in group.yaml or ui-lovelace.yaml?
You donβt have a ui-lovelace.yaml do you?
Have you configured Lovelace to be in yaml mode?
I do have a ui-lovelace.yaml that was created by the conversion tool. Do I put lovelace in yaml mode in the configuration.yaml?
Well, the conversion was not necessary, and you can remove the ui-lovelace.yaml
It is auto generating you Lovelace layout for you now
is there any way to avoid the issue that entity filter has that it does'nt display the icons of the entitites unless you refresh the page?
Ok.
If you want it to keep doing that but want to get rid of the yellow warnings, remove the entities from your groups
Otherwise, click the Configure UI button in the top right
Take control and edit the Lovelace UI
too many options...
Ok. I've taken control. How do I let HA have control over lovelace again?
remove ./storage/lovelace
But that will give you the yellow warnings again
I want to get the yellow warning signs fixed. Both exist and HA isn't having any problem with them on the separate tabs I'm using.
How do I use custom cards via the Lovelace UI ?
If not possible, should I create the ui-lovelace.yaml (I donβt have it at the moment) and I wonβt be able to work via the Lovelace UI ?
@mild veldt And where do I configure the resource for it ? I want to use Monster card
when you have the raw config editor open, add it to the resources section if already there or make a resources section outside of views
If I try this code the raw editor I get:
YAML Error: TypeError: Cannot read property 'startsWith' of undefined
resources:
- url: /local/custom_ui/state-card-aftership.js
type: js
views: - name: Example
cards:- type: "custom:state-card-aftership-ll"
entity: sensor.aftership_sensor
- type: "custom:state-card-aftership-ll"
~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
state-card-aftership...?
Yes, from here: https://github.com/tr1plus/ha-aftership
I try to add new card, click "skip" since it's custom card and enter the code from the end for this URL: https://github.com/tr1plus/ha-aftership
I get: YAML Error: TypeError: Cannot read property 'startsWith' of undefined
Remove the -
can you go back and edit your config message to be formatted
When adding the card
type: "custom:state-card-aftership-ll"
entity: sensor.aftership_sensor```
@winter hollow Thanks. How do I add the resource ? Where do I put it ?
resources:
- url: /local/custom_ui/state-card-aftership.js
type: js
views:
- name: Example
cards:
- type: "custom:state-card-aftership-ll"
entity: sensor.aftership_sensor
Can a mod please pin that wiki?
For this code I get and error.
Is there any way to get a picture glance card to show the temperature from my Ecobee instead of the thermostat icon?
@hallow niche read that wiki I posted
@tribal linden no, you could make your own using picture-elements
oh good idea! Will give that a go, thank you!
Thanks for the help! I've the the invalid entities fixed.
can i delete my ui-lovelace file if im using storage mode
is there a way to change the color of a sensor graph line?
Yes, with Themes
@winter hollow thanks, I'll look into that
How can I hide badges in the new Lovelave UI ?
Edit the view, they are in the second tab
@winter hollow Not sure what you mean. I go to Configure UI and then..... ?
Click the pencil next to the view tab
Yes thank you!!!
Why the push for an interface at all. I never want to manage my homeassistant from the interface. It's supposed to be invisible. Is lovelace using resources if I don't open the management interface and if so can I disable it?
Not really, and no
You can disable the front end component
That used to disable the API...
Ah, cool, api is separate, but needs http: still
Disabling the frontend buys you nothing, and makes getting help rather challenging, as many of the things you'll be asked can only be found in the UI
Seems odd. My only use for the front end is to easily see the system log and to reload when developing scripts. I could tail homeassistant.log instead. If the UI is only demand driven then I suppose there's no point in disabling it. Thanks.
Is there no remote lovelace card? (remote as in https://www.home-assistant.io/components/remote/)
Probably some custom ones
@elder pendant I made a roku one, but really you just need buttons
But why do all that work when you've done it for me already? π
Did you make a remote for all the available buttons or just the ones you use regularly?
Hello, new HA user (hass.io on an RPI), first login to Discord, first question...:-) I think I've done all of the "before you ask" things... and I'm tired of beating my head against the wall and would like to move on to learning something else. My problem is that I cannot get any custom cards to work in Lovelace. They all display the "Custom element doesn't exist:" error. I suspect that means that there is a permissions issue or something, but I also don't see anything related in the HA log. I don't know if being a hassio setup has an effect or where to check. Would love a nudge in the right direction...
How are you editing your Lovelace config and adding the custom cards?
I've tried via the Lovelace UI and also by setting it to yaml mode in configuration.yaml
what custom card are you trying to use?
really any of them seem to behave the same. most recently I tried the aftership card, simply because it looked like a simple setup
Which mode are you using currently?
@elder pendant https://github.com/custom-cards/roku-card
yaml mode
I'm in the process of refactoring it though to use the new roku remote integration introduced. It is using http calls right now from the front end
Did you put the card in www/ in your config folder?
Did you restart Home Assistant after creating www/?
Just point them to this, @split granite https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins
did you copy the card the correct way? using raw button from git?
yes, www is working for other resources (image files, etc)
Oh damn I could have been using this even before 0.86 because you're just using the roku local api directly. Looks good!
i've created files manually by getting the raw git text, also git clone from git repo
I've used that guide too, @mild veldt
how did you upload the file samba?
did you check the user permission to file?
and if its not root?
@jade bough, yes, when creating manually. when cloning from github, i used the ssh and web terminal add-on for command line
i 've changed perms to be read/execute for everyone. Should be something else?
@elder pendant it has issues with CORS so going to remove all direct call in next release
i'm not sure but should this (- type: custom:aftership-card) be in colons: - type: "custom:aftership-card"
I've tried that permutation without change, @jade bough
maybe doublecheck the path, name of the file try to clear your browser cache and restart HA?
I saw a video about lovelace default on 0.86: https://t.co/LDWJaqXCcy, so ui-lovelace.yaml is not more needed?
I'll try that again, @jade bough
check casesensitive names?
@vapid field If you're using YAML mode, you'll need the file still - see the Lovelace docs π
@split granite hello, yes I am using it. So i can delete lovelace mode yaml and edit it the easy way?
Is there any "easy" way to get started with configuring the Lovelace UI? Trying to get through the whole documentation to achieve little things is overwhelming for a HA-beginner π¦
The UI editor is the easy way
... I'm a dumbass... I was always scared to press "Take Control" since it'd mean that nothing is added by itself anymore lol
THAT's what I was always wishing for, MAN why didn't I see this earlier already
Error: The edit UI is not available when in YAML mode-must delete lovelace yaml mode from configuration.yaml?
or what? there are 3 modes, but how to switch
There's automatic, UI editor, or YAML mode
but can not start UI editor:The edit UI is not available when in YAML mode-
so remove the yaml mode entry from config
@timid burrow ok will try
First time post on Discord. I've just upgraded to 0.86.1 and was expecting Lovelace to be the default UI as suggested by the release notes. However, I still just see the standard UI. Do I need to set Lovalace as the default UI in the developer information page?
It is the default now, it'll just look like the old UI by default
or you should refresh π
@timid burrow deleted mode: yaml, enabled UI editor, copied data from ui-lovelace.yaml, everything fine, THANK YOU
Oh boy this UI editor just made me excited to use Home Assistant again!
I see that it is now. Just deciding now whether I should "take control" or leave automatic
And thanks to the Demo on the Hassio website I can cheat a little π
I'm fairly new and have read about custom Lovelace cards. Can these be used in the UI editor?
Yes
Thanks
how do I clean up the ui to start clean? My ui is showing all my entities
I guess remove them by hand
replace your config in the raw editor with:
views: []
hey @polar kelp do your latest cards (ie, state-switch) have an option to auto update?
They work with the custom_updater
i'm an idiot, they showed up when i forced a refresh
Is there a way to display data from within a sensor directly on an entity card?
Or better said displaying attributes directly on an entity card
Indeed....we need a way to display attributes on cards, instead of having to creating a separate sensor for every entity to be displayed
Hey! I felt like making a lovelace plugin that actually is visible for once, not just weird stuff that's hard to explain...
So it's not yet possible?
Anyone want a color wheel card?
Cause I saw the FritzBox component, added it, then realized those are all just attributes
what are you doing @polar kelp? get back in your utility cave!
Yeah but it's not a "fancy looking" solution π
something like that should be part of HA @winter wasp
sorry
and that card is not as fancy π
@kindred dirge useful-markdown-card perhaps? https://github.com/thomasloven/lovelace-useful-markdown-card
I guess I'll just wait for official attribute support π
want to add windy.com to iframe, but get red background with windy.com address, no radar map: https://imgur.com/a/FW40mtD and this is the share address : https://on.windy.com/24rc2
Or is there a way which makes it possible to make sensors out of attributes?
templates
template sensors
Will have to read into that
The template components pretty much lets you make anything out of anything.
Just kinda hard to understand when not a programmer
Like, I want to grab infos from the FritzBox sensor attributes but I'm not sure how to start
@kindred dirge I have ton of examples https://github.com/arsaboo/homeassistant-config/blob/master/sensor.yaml#L253 for your inspiration
King of templates
This one https://github.com/arsaboo/homeassistant-config/blob/master/sensor.yaml#L350 for example, creates a sensor for the power used by Wemo switches using the current_power_w attribute
As for HA displaying attributes in cards, sure, sounds easy. Until people want advanced stuff like substrings and changing to percentages and what not or adding units. Can get messy really fast and is why we have template sensors
Is there any way to stop HA reporting the use of multiple sensor tags as an error? I like to organize things by putting them "into their own little block" just so if I decide to move something around in the future there it won't break anything
And since the config is still valid then why is it reporting an error
Well, we can stick to our no-template for LL stance, but simple attributes would be nice to have.
@kindred dirge not really a LL question but check out Frencks config
Ah whoops lol
but I see your point, given that there is no cost of creating a template sensor, we can just use them
I think a template sensor UI editor would ease a lot of the pain
and attributes can be used in other cards too....for example, humidity from thermostats on picture elements
@kindred dirge You can use a second word like sensor light_sensors: and sensor door_sensors:.
Since Lovelave isn't using yaml anymore (default) how do you add components like homekit(and others) in Lovelave?
Lovelace is just the front end
All your components are still in configuration.yaml or integrations
With Lovelace weβre taking a new approach to building user interfaces for Home Assistant. Weβre no longer storing the look and feel of your UI in your configuration.yaml
So this if fake news or am I misinterpreting this ?
You are misinterpreting it
Ok, thanks
@mild veldt If I add homekit: to my configuration it doesn't show me the pin like it used to-do. Any advice ?
@mild veldt my bad. Seems I have to delete the HomeKit_store in order to add it again. Would be nice if someone is able to make this as a integration.
Hey guys, trying to add a custom card to my config, lovelace in storage mode, on Hass.io
I've added config\www, and restarted HA. I've added monster-card.js to this directory, and added the following in raw config editor
resources:
- type: js
url: /local/monster-card.js?v=1
getting the red box saying there is no monster-card.js
thinking I'm missing something simple, lol
do you still use the groups yaml for the lovelace groups?
we renamed the tab in the configUI but how do I change the order of the tabs
@cerulean scarab did you save the card in raw mode from github?
@timid burrow sure did, copy and paste text only into ide
was getting a 404 for /local/monster-card.js in chrome developer view, so I changed the resources: section to remove /local/ now that chrome error is gone from developer console, but still can't call the card.
it's not supposed to be a module by any chance?
instead of js?
you have to have /local BTW
maybe, but not according to his README.md https://github.com/ciotlosm/custom-lovelace
eg..
- url: /local/card-tools.js?v=297fcc
type: js
thanks, will put /local back. so /local is a symlink of sorts to config/www ?
β
ouch!
cool and card-tools is config/www/card-tools.js on disk?
that hurt @mortal cape
I was just joining in
lol
it was not a slight
yeah it is @cerulean scarab
I started putting all mine in www/custom_cards but now I don't know if that was right
my www folder is a mess!
Does the custom card updater expect them to be in a certain directory?
Or...the custom card update notifier card I mean
I don't think so - it just reads the version number
ok
some custom cards have hardwired the folder
my www isn't a mess but some cards are in that folder and some are in sub-folders
@timid burrow ha, I remember trying to convince you that lovelace was worth using and here I am asking you questions now
and custom updater is happy - it's only reading the json from the repo and the version number from ui-lovelace.yaml
At the time you were all "nah I don't really have a use for that"
hahaha!!!!!! You know I was thinking about my earlier indifference to lovelace - but the additional stuff they put in makes it great now
I KNOW!!!!!!
hahahahaha
That's what I meant by mess @timid burrow I'm thinking I need to clean it up into sub-folders, having images and .js files and random stuff in there makes it look like a mess π
I have been using it for months now... only took a few custom cards to convert me
I jumped in from the start and I'm really enjoying it. Might even move to the UI editor instead of yaml
it just depends on if the folder is hardwired @buoyant portal so just be careful
well I still use the YAML but I'm configured for the UI editor.... I just load UI editor and go to raw and cut and paste the yaml if I am doing major changes
so best of all possible worlds
sounds like a good idea
yeah.. some great stuff there
lol @cerulean scarab - always a reason
lol
I really really hate that the raw editor is not IDENTICAL in format as the yaml one - if it was I would ditch the yaml in a heartbeat but it just mangles it which is a total PITA
That's a shame
I stick to yaml because I know it. I feel comfortable in its embrace
it just reorganises everything
yea, and not having a working tab/shift tab function
well yaml seems to set it out logically and with the raw editor it moves the keys around and moves stuff to the bottom of the card that you expect to be at the top.... like the TITLE and CARD type for example...
so I find it good to use yaml for major stuff but if it's just minor I can do the gui and also update the yaml
I like the UI + raw editor just fine. Some awkwardness but it will improve over time I would expect
i guess it will... they will probably kill the yaml at some point
I don't understand why they didn't just write the raw editor to look like the yaml one
guessing there's challenges to letting users do raw config without over complicating the gui stuff
thinks that's why the reformatting happens
also @mortal cape if you use custom updater, just be aware it updates the version number in the yaml file and you need to manually update it in the GUI...
@timid burrow what yaml editor are you talking about?
um.... the lovelace raw editor unless I am misunderstanding your question
"I don't understand why they didn't just write the raw editor to look like the yaml one"
oh... well the yaml editor... not the yaml editor just the data format
there is no yaml editor
I meant the data format
I don't follow? Do you mean that things get reorganized on save?
yes.. like it totally reorganises the order of everything when you save
That's just the nature of the parser we use. Nothing can be done about that
The raw editor is not really for day to day edits
Should really only need it to add resources
like the title of the card and the card type get shunted down to the end instead of being at the top and it's almost impossible to do a vertical stack and get the format right in the raw editor
so how do you add stacks using the gui editor?
Vertical stack is a hard one
Hopefully we can come up with a good UI editor in time
which I would like to not have to do anymore
well that would be great... I know you are working on improving it which is great and it's awesome but it's not easy to edit stuff unless you use yaml
For stacks, agreed. All in good time
should start seeing editors for custom cards as well
weather-card already has one
that's nice... the m.p.frankland one or a different one?
Brams
gotcha - he has done some awesome stuff. him and Thomas... so good
Lots of great custom devs
yeah. so true.
So i've now got one tab that's auto-generating (using several monster-cards) so I can have an Advanced tab while still having the main tab be family friendly
It's not the same as the old default-view, but it'll do for now
Hey, can anyone tell me how to configure a glance card, so that when I tap the entity it toggles the switch. I have both Hue light bulbs and smart plug entities on the card.
@cloud osprey you can define a tap action for each entity
looks like tap_action: toggle aught to do it
full disclaimer, haven't done it
oh my syntax is off
the last example has a tap toggle