#frontend-archived
1 messages Β· Page 88 of 1
Ah ok, but it's documented in https://www.home-assistant.io/lovelace/entities/#options-for-entities
ohhhhhhhhhhhh you're right.... I was following that PR for last_boot and didn't see it merged. but it's in the docs so must have been
... but it's not working....
@polar kelp brilliant
@polar kelp I think you use custom kiosk mode, is it not working with .84? The bar goes away, but it doesn't get rid of the space anymore...
@timid burrow Maybe manually set timestamp class for the sensor in some way?
@mild veldt OK, So I am trying it from fresh just using the editor... But how do I get /lovelace back to being default again as it just shows 404 not found. @polar kelp Love that, Looks good.
it's still not working... just tried it and it doesn't matter what you set it to it stays the same
@thorny verge I heard there were problems with it. I haven't upgraded my prod server yet, though, so I don't know.
you need to clear cache and refresh
@mild veldt Ignore that, Overview now shows the default.
and set as default as you did previously
@timid burrow I don't understand...
@polar kelp Ok, I'll just live with it for now, it clears the blue bar, but doesn't get rid of the space it takes anymore.
- entity: sensor.last_boot
format: datetime
doesn't matter what format I choose it stays the same
@brave badge
Ah, ok. Yes, it's true.
so it's either a bug or not merged..
even though in the docs
https://github.com/home-assistant/home-assistant-polymer/pull/2087 seems to indicate it is merged though
But i'm still getting 2018-12-11T16:47:51+01:00 not only date and time
I know! that's what I said. It shows like that regardless of what format you select
I might enter in an issue
maybe we can ask @polar kelp... sorry to bother you! do you know anything about the mistery of the relative format? See above
Don't tag him for that @brave badge
He's an amazing guy but I don't want us getting in the habit of calling out individual devs for help
he was the dev that approved the pr.... if not tag him for that then what?
This is probably something stupid but could someone explain https://imgur.com/cHwbPRV Thanks
What causes it to not be supported
I know the tap action stuff changed, But I thought that would be right
@timid burrow I don't think we want to get into the habit of that. Balloob wrote it and I don't think you be tagging him either. The issue filing was the right move imo
Just upgraded to .84.1 I love the new configuration options in Lovelace. My question is how do you add custom cards in the new configuration editor?
Hi, I have just updated to 84.1 , but when I go to Lovelace page, it says No config found. and there is a RELOAD UI-LOVELACE.YAML button, but it is not working
@flat timber use the editor for now
Just updated to .84.1 and now Lovelace interface not showing, just yaml
@mild veldt do you mean put it in yaml mode and continue as normal or the raw editor?
I have restarted HA, still no config found
ui-lovelace.yaml not being loaded on 0.84.1
@loud vault read the release notes it tells you how to choose which way to copy it over
thx
I am guessing that it shows that error because tap_action and hold_action are not part of the config editor yet.
@brave badge whats the device_class of your sensor?
I can't set it...
Trying to set device_class in config/Customization but timestamp is not present in the list. Trying to put it in customize.yaml
ok, it's working now!
i am using it with last_boot - filed an issue for it already
put this in customize.yaml:sensor.last_boot: device_class: timestamp
hmm....
thanks @polar kelp and sorry
using configuration->customize I can't select timestamp as device_class
@timid burrow I know, it's missing from the device class list... but putting manually in customize.yaml is working
and restart HA obviously
now I'm getting "1 day ago" if setting format to relative
Is it working for you? We can enter an issue for the missing entry in configuration->customize
yeah... just restarting as I had a template sensor... I can edit the issue I suppose
Ok, I'm satisfied for tonight. going to bed now... goodnight!
good work!
is there a way to move tabs left and right with the new UI editor?
dragging them maybe? I haven't tried
Has anyone else noticed that tap and hold actions are not working in a mobile browser? like Chrome on android.
config of tap and hold actions is changed... see https://www.home-assistant.io/lovelace/entity-button/#tap_action I had to change a lot of lines in lovelace @cunning tree
Now it's working for me even on mobile (chrome on IOS)
@cloud escarp not yet
Was
show_header_toggle: false
Changed?
~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
aww man I did '''
so why would all my header goggles show up?
entities:
- entity: light.lounge_ceiling
tap_action:
action: toggle
- entity: light.small_lamp
tap_action:
action: toggle
- entity: light.iris_1
tap_action:
action: toggle
- entity: light.iris_2
tap_action:
action: toggle
header toggles
@brave badge I think I have them the right way for toggles
In Chrome on Mac the toggles and more info work
@tame dove that looks correct for an entities card, nothing has changed there to my knowledge
I've confirmed that works still for me in an entities card for lights
@cunning tree so your actions work or not?
@mild veldt they only work in a browser on a PC not mobile.
Ok, Now they just started working on the phone as well without changing anything
Cache perhaps
Possible I did close apps and refresh a few times. At least it works now,
On some things i get
Expected a value of type `{entity,name,icon} | entity-id` for `entities.0.tap_action` but received `{"action":"toggle"}`. Falling back to YAML editor.
and others its fine, Any idead?
Whatβs the yaml that gives that error?
question, the 'default_view' is that always valid?
@lime glacier yes. As long as you donβt ever try to manually configure
Then it is user edited
We plan to have something that is always available in the future though and allow you to install to your view from it
yeah, ok. What I would like... is that this default view... isn't the default when I login.. but a different view
because this one is huge and takes a while to load on my mobile devices, etc
but I would like to keep the 'default view'
You can define different views and use paths
for reference and stuff
Canβt do that right now but there is an unused view that shows things that are not being displayed on your views
yea, ok. Is that the 'unused entities' in the options on the top right?
Yes
and this doesn't consider the 'default view'? just the other custom ones
No. It considers all views
ok, so what does 'unused entities' mean? just entities not in an automation?
Entities not in a view
ok, so then why is there anything here? I thought everything was in the 'defaultview'?
or is this stuff I have 'hidden: true' in customize?
I have no idea what you have in yours, dude
ok
Have you hit configure ui yet?
You donβt have a yaml config until you have done that
So in that case everything would be unused
@cunning tree I just did some testing with the light editor and didn't have any issues with the entity picker?
Hi, how do I open lovelace to import my config in .84?
the release notes say You can do this by opening the Lovelace UI and click on Configure UI
but I'm not seeing how to do that
@pallid needle top right corner menu
I'm trying to add the remote card from sharethelove.io but raw editor is saying !include is an unkown tag
I'm trying to do the new lovelace in .84 release but when I click on my configuration panel it says it can't load. Any ideas?
I updated to .84 and I was trying to get to the screen where I could import my ui-lovelace.yaml but when I click the Configuration panel it doesn't load and shows this message "Error while loading this panel."
chrome?
@flat timber read the release notes
you can't use !include if you want to use the UI editor
that's the trade off
@keen quartz if you're on Chrome, try dev mode F12 in chrome and then right click on refresh button and select hard reload and clear cache.... much better than deleting all settings
yes I am I will try that thank you
i got so sick of removing all content and clearing cache all the time lol
I hit F12 and see the console but I never use this. I don't see the refresh button
left hand side of address bar... not in console - just need console loaded to get the options on refresh button
ohh
@timid burrow if you have dev tools open you can disable cache
Ha that did the trick, thanks buddy
but you have to leave them open
ok. with mine it just resets that site... so you don't lose every site setting and stored passwords etc... only found out about that recently.
Thank you @mild veldt I thought I had read them all I must have missed that
So I would want to just paste all that code directly into the raw editor and it should work
So I'm in the configuration panel but I don't see where I import my lovelace yaml
hi friends,
i have a stupid question here
the little sensor circles that were at the top in the old UI, in lovelace theyre just put into a card, is there a way I can get them back up the top ?
@keen quartz in the top right menu
@flat timber from the included file? Yeah that should work
@dire salmon read the lovelace docs on badges
thank you !
The Map card for the new update only seems to have a card that is about 1 or 2 pixels high
The raw config editor - where is it saved? - want to take a backup - just to play save
If I try the new Storage-mode, isn't there a way to edit the files with sublime?
Hi all, is there a max name of sensors used in lovelace, it seems when it gets to long the whole view doesnt work
and i get an Service system_log/write called.
ah ok, thanks π
is anyone else having issues with light and sensor cards with 0.84.1?
light cards do a weird transition when you open the view
and sensor cards are not drawing the graph
gif of the light cards: https://i.imgur.com/WHrpo6h.gifv
this is in firefox btw
Hi, just updated to 0.84.1 and now all my Lovelace views are gone, everything is just on my Home view tab. The yaml file hasn't changed, but if I go to "raw config editor" the config looks completely different with one view: -path: default_view, title: Home and then badges: with all my entities
Please help
Fixed, copied all my content off ui-lovelace.yaml into the raw config editor
or you could have read https://www.home-assistant.io/blog/2018/12/12/release-84/#for-existing-lovelace-testers
@silk canyon for sensors you have to add graph: line seems that now the default is none...
for the lights... I don't know. seems a bug to me
@brave badge that line config worked great! thanks
might open an issue for the lights issue
you're welcome!
Look at https://www.home-assistant.io/lovelace/sensor/ there's some new cool options, like detail.
hey guys..... Im just starting in lovelace tonight. I have 5 input.booleans that I need to toggle when pressed. I have the logic sorted out - its just the UI doesnt work as expected. Im using a glance card, but when I press on any of the input booleans, lovelace presents me with a detail view of the boolean. What I want to do is just immediately toggle the bool. Can someone direct me with the correct sort of card. I want to use something like an entity button card, however the docs are sort of blurry - it looks like an automation rather than something to be used in ui-lovelace.yaml
correction - i dont want to toggle the bool, i want to turn it on. (it will always be in the of state)
You want to take a look at the tap_action property of the glance card entities. https://www.home-assistant.io/lovelace/glance/
What's unclear about the entity-button card? The code sample? That's an example on making it run a script when clicked, rather than toggle the entity.
AAAACHH!!! Has anyone here upgraded to .84.1?
have you read the changelog? π
Um. No...guess I need to?
I can't imagine upgrading without reading the changelog.. that would be like diving into water without first checking what's beneath the surface
Yeah....I usually do, but upgraded from the toilet this morning, lol.
I've gone foe the manual config.. but I will be switching when I get the chance
well that's why you got a shit show π
Indeed.
So, it says, "You can do this by opening the Lovelace UI and click on Configure UI". However, when I cannot do that, because my view says, "No config found". No "Configure UI".
you can.. I did it.. just trying to remember how
try turning off lovelace andoing a shift-refresh
in the info panel
You mean shift F5?
yeah
So, I did....No "configure UI"
I got there somehow :/
The dev team are usually spot on, but I think someone screwed the pooch on this one....I cannot fine how to get to Configure UI....
Try out the new Lovelace UI
>> Remove lovelace as default page on this device <<
yiu need to remove it I think
and then shift refresh
on the main overview
how is it you can paste the image and I couldn't? π
and you went to overview and what did you get?
no ... ?
I am special....as in special ed....
A bunch of crap, not lovelace...but can't see Configure UI there.
crap? what does it look like?
I just got a message that there was no lovelace-ui or something like that I think.. originally
oh yeah.. that's normal.. what happens if you now go to /lovelace ?
AHHHH, still looks like shit, but now I got the "Configure UI". Thanks bud. I think I'll have it from here. Stay tuned.
now you either control it and set the configuration to yaml (I'm doing that for now) or jumpo straight to the ui based config and just copy passte the config from your yaml file via the new ui.. which is what I will be doing as soon as I get the chance for the added flexibility
I want to see the improved ui config π
you're welcome. I think next release in a month or so will have lovelace as default ui
I've been defaulting to it for a month or two now....took me a minute to get used to it, but love it now. I am hoping this rev will allow me to arrange my cards without having to use stacks, OR if I have to use stacks, I can still edit UI in the GUI if I do.
Oh, wow...play with it...this looks pretty great, imo.
only if you don't "control it". not sure the extent of the flexibility if you don't and use the ui instead
Well, I can move cards up and down in a column so far....
if you go manual you get The edit UI is not available when in YAML mode. when you try to use configure ui
I don't quite follow about "yaml mode"...what do you mean? The raw config editor?
Yes, but when I stumbled on the answer to my current problem, I got distracted. SQUIRREL!
that's a very Zak McKracken thing to say
Yeah, I just read that section. I'm not going to do that. YAML mode, that is. Doesn't he have a brother, Phil McKracken?
And a cousin named "Release"?
if you're not doing yaml mode then you're not controlling it
Zac McKracken was a deep cut.. you're probably too young
No, probably too old.
No idea who that is/was, except for the wiki I just looked at about him.
it's a reference to a game from 1988
I wasn't playing that sort of game in 1988....was busy with other things.
that makes it sound like you were after the ladies.... π
yeah, lol
oh shit.. that's 30 years now.. from 1988
indeed
hence this.. https://www.youtube.com/watch?v=yGgQwKa8f6g the most widly off topic thing I have ever pasted... with english subtitles no less.
Will watch that later today....right now, got some residual maintenance to do partly because of upgrade, and partly because of my current home assistant project I am fine tuning.
anything interesting?
Weather station via RTL-SDR
ahh.. I have am RTL-SDR somewhere I was going to use to track commercial airplanes..
are you implementing the weather station? or are you sniffing an existing one?
I just got one....about two weeks ago....sniffing the 433 off of it.
Those readings are taken about 20 feet from my house
96% humidity?
Two reasons for that....1. I am in Texas. 2. It is raining.
is Texas humid? I expected it to be dry.. but rain would do it..
Texas is gigantic. The part I am in is classed as sub-tropical. West of here, about 500 miles, say, it would be arid/desert.
damn.. i need to look at a map
Lol. Almost takes me as long to drive from my house to El Paso as it takes to drive from my house to Chicago
don't worry.. we have distances here too
Where's that?
Australia
Ahhhh. Yeah. 3/4 of your country is exactly like Mars, right?
I'm surprised any of Texas falls into the tropical zones.. but I guess the climate is all over the place lately..
yeah.. there's a few population centres here and then very little else
Always been that way where I live. Here, we get I think about 45 inches of rain per year on average. 80-90 ft trees everywhere.
I think we've gone WAY off topic for #frontend-archived π
You could be right...SO, back to lovelace...if I use "edit UI" to manage my view....does ui-lovelace.yaml even do anything any more?
I don't think so.. I think it gets put in the hidden storage directory along with the entity_registry and other stuff
Ahhh. Because, the only thing I don't seem to be able to manipulate is which column something falls into...I can move cards up and down, just not side to side.
that sounds like a weird limitation..
that's what she said....
I would have expected it to be ordered vertically, but that would still allow movement horizontally if you were to imagine it as 1 column wide internally
heh
Looks like the following, to me....before, if you DIDN'T have an entity ID for each card, it broke your shit. So, I generated a random 32 character hex value for each. NOW, it looks like THAT is breaking my shit. π
holy crap.. it's almost midnight and I have to get up early.. next time we talk maybe I'll have some experience with the new ui configuration
I wou;d have throught that they'd get stripped if not needed
Ok, sleep well.
if I read correctly comments do
Gonna strip one out, and see what happens.
good luck and good night
Hi, on 0.84.1 all my binary sensor, device class door,window, movement and presence, now have state off/on instead of closed/open/movement/home. Any ideas?
Realized now that the issue is only in Lovelace interface. The original one is ok
And it's not working only after a refresh of chrome. Not on the first opening of the page
@brave badge maybe clear your browser cache for the second problem
you have set lovelace as primary ?\
Yep
and if you add /lovelace to the url ?
I use Lovelace from the beginning... so yes
sorry
never mind... π
didn't know that :), i have no other ideas, no error in the log ?
Any way to define a min/max or high/low for a history graph? ie monitoring disk array usage and making it show 0-100% rather than like 50-95%
Have a problem. After upgrading to 0.84.1 from 0.83.3 my HA ignores the whole ui-lovelace.yaml file. Even deleted it, no errors. When going to /lovelace its shows the default frontend with some diffrent cards.
Read the release notes
lovelace: mode: yaml
In your config. Its in the newest release notes.
Damn didnt see that, thanks for help.
@weak flume what is the big difference between your option, and dumping the content in the raw gui ?
Im not sure how the storage option works. If its throw into the database or what. I just prefer the yaml option.
the raw gui seems also to be yaml, only upside down.
@weak flume storage option puts your config in .storage in json format
You then only use GUI for edits
Got ya. I figured after it would be via GUI. I guess Im just old school
Nothing wrong with that but you wonβt get to use all the fancy new tools π
Are all the cards with the latest 0.84.1 moddable without using the custom card-modder?
Define Moddable
hmm, where can i place my resources for lovelace in the latest update ?
i had one already installed, but i cannot file a file where it is configured
or in the raw config editor π
found it
@raw brook I mean using css styles and so on...
Some of theme have a theme option but you cant inject css styles like you can in the card modder
@raw brook ok, where to see which can have a theme?
Ok, thanks
Ok, trying to make heads or tales of how to manage the order of cards using the "Edit UI" feature. Just when I think I have it figured out, it does something which makes no sense. So, is this feature still beta, or is this SUPPOSED to work correctly? Because it does not.
Oh. then busted.
So it moves the card up within the index of the view. But the sorting of cards algorithm doesnt just use the order. IT takes the next card and places it in the column that is the "shortest"/ smallest cards sizes.
I figured out that that was what it is TRYING to do...but it does not always do that.
Unless you have stacks then it does
I don't have stacks.
The algorithm uses the size the card returns which is a single integer.
So 1-4/5 right now
It is awful. FOR example, I had 4 cards in the right column, right were I wanted them. I move one card in the right column up (not one of those 4) and it moves TWO of the ones which were previously in the right column to the left column. Just awful.
If the thermostat card is 4 and in column 1 and the next two cards are size 2 then the next two will be in column 2 instead of column 1. (this assumes a two column layout
I have three columns
Probably not...however, from a PRACTICAL USE standpoint....it is awful.
We are going to be working on a better use case. In the mean time π€·
I'm gonna just let the cards be willy-nilly random, until a better method comes out.
Just as there are up down arrows in the edit, there should be left right arrows. Make the up down ONLY do up down, and make the left right only do left right. Forget any algorithm (or at least make it possible for a user to turn that off) and let me simply say "move this card over one, up two", "move that card down three".
Thats what we are going for
Ok. I'll be more patient. Nice first try, and some of the features are great....it is just results I get right now are nearly impossible to predict. I know that in the backend the system thinks it is doing things perfectly logically, but it is extremely chaotic in appearance.
ITs been this way since Lovelace was created
Its a really nice way to organize cards
Use stack cards if you want to organize your layout
Is there a way to set the lovelace ui as default and remove the old one?
Yeah, but if I use stacks, I can't edit in the UI.
So, they fixed that?
You can edit it via YAML
Editing the horizontal stack pulls the YAML for the cards within
Hi. Is there a way to add a picture to the plant-status card?
With .84 can we no longer have nested !incldues (an !include in an !include file)?
If you use YAML mode you can
I am, and I can't, every file that was working in .83, is no longer working. If I include a single !include in ui-lovelace.yaml that also has in !include, then lovelace loads the old views (from groups.yaml)
Hi all. Iβm having an issue with the configure UI card configuration. I believe the pop up is broken on my end. There is only one labeled field (title) and then a blank line to type in. A friend has fields for entities and other variables when adding the same type cards.
Iβm receiving the error 2018-12-13 11:14:23 ERROR (MainThread) [frontend.js.latest.201812110] https://MYHASSIOADDRESS/frontend_latest/bf7146608f595468a214.chunk.js:3157:1377 Uncaught TypeError: Cannot read property 'name' of undefined
~share
Please use https://www.hastebin.com/ or https://paste.ubuntu.com/ to share code.
Im sayong post your config
Entire config yaml?
THe YAML for the broken card
Itβs when attempting to add a card.
Hi! Is it possible to add other entities then "climate" to the "thermostat" card?
And after clicking through all of the possible cards - entities and glances are the only ones that look
Correct*
@torn dirge we donβt have UI for all cards yet, we are working on that
If we donβt have UI we show a yaml editor where you can enter the config
Alright @winter hollow thanks for the feedback. I appreciate what yβall do.
I do have the editor. Thank you!
@torn dirge whenever it seems stuck, clear cache or ctrl+shift+r...I've found that the add card button doesn't do anything sometimes until I do this
Hi, I'm on 0.84.1 and all of my binary_sensor, device class door,window, movement and presence, now have state off/on instead of closed/open/movement/home.
I realized now that the issue is only in Lovelace interface. The original one is ok.
Nobody noticed this? Only @cloud latch and me?
Having a tough time getting the custom media player working. Keep getting this no matter what I do:
Custom element doesn't exist: mini-media-player.
@winter hollow @brave badge does this have anything to do with wrapping on and off?
Or is that only when using yaml mode
I've followed the readme (as short as it is) correctly IMO
https://github.com/kalkih/mini-media-player
nah, that shouldn't have anything to do with it
I've copied the mini-media-player.js to my config/custom_components/ directory, and added
type: module```
to my resources field in ui-lovelace.yaml
But lovelace UI still says mini-media-player doesn't exist. The logs dont mention it either (saying that it's a custom component, and thus not supported) so it might be right, but why isn't it being picked up?
Does the location of the js file really matter that much when I keep it consistent with my resources URL?
yeah, I tried that first, with no joy.
Though that was perhaps before I noticed this
"Make sure you have javascript_version: latest in your configuration.yaml under frontend:."
you specified your resource as /local/custom-lovelace/mini-media-player-bundle.js?v=0.9.7
so your path should be the same as what you specified in your config
i.e. config/www/custom-lovelace/mini-media-player-bundle.js
Ok. Moved it. Restarted. Same again...
I have it in my config/www/ directory now, and my resources url is - url: /local/mini-media-player-bundle.js?v=0.9.7
and the file name matches?
the readme says to download from the release, not the file directly
mini-media-player-bundle.js is not mini-media-player.js
the readme is accurate
I just did a git clone
I've followed the readme (as short as it is) correctly IMO
IMO
^lies π
Crucial
My opinion was wrong obvs
Cheers though. I'm gonna go rm -rf / my nuc now. I don't deserve nice things
Can't have any HA errors if you don't have a HA
@winter hollow @mortal cape Yes, yaml mode, but tried Gui method too, same result. Italian language.
I'll try with english
... same thing
@brave badge I see it now in mine after a restart
@mortal cape Ok, I'm not crazy....π
yeah first look is ok, after a refresh it's wrong
Anyone have this working https://github.com/maykar/custom-lovelace/tree/master/compact-custom-header
No matter what I try , I get nothing.
@raw brook don't think so... it's not a translation problem. It's on/off instead of open/closed in a device_class: door for example
π
but it's wrong with any device_class
can lovelace handle nested includes now?
It can do anything configuration.yaml can
The biggest question today: Yaml or Storage mode? I can't decide which is better.
Do you want to use the UI?
EZ question
I think so
@winter hollow I have many nested includes, none work.
Is there a trick, as all worked on .83
@winter wasp if you use !include you will not be able to use the new UI editor features
Yaml mode here... untill raw editor will show spaces and colors like configurator add on
@thorny verge did you transition to storage?
No
did you follow the release notes on yaml mode? https://www.home-assistant.io/lovelace/yaml-mode/
Yes, everything is working, even includes, but no nested includes.
@brave badge Never will show spaces. We may be able to update the text editor eventually.
I'll love it
hmm, i tried using nested includes and now it won't load the lovelace interface at all π¦
I get the same thing, although i've been told by multiple people it works, but I can't get them to.
If I configure as storage mode, ui-lovelace.yaml is no longer used?
@mild veldt In .storage there is a lovelace file, so it must have used storage on first start, can that be deleted, and is that maybe why nested includes don't work?
for nested includes, use mode: yaml I believe
@winter wasp If I try nested includes, I get the default views from groups.yaml, but in lovelace
you can't use the ui editor with nested includes
@mortal cape I am using mode: yaml
but you can use lovelace
nested includes breaks my Lovelace UI with yaml
@raw brook Don't get me wrong, I think you did a wonderful work with the new UI... but i like yaml for the copy/paste capability. Not everybody is nerd like us...π
@brave badge you can still copy/paste yaml in the raw editor found in the UI
I want to stay .yaml because I constantly break hass, and I can roll back any changes with my backup solution.
@thorny verge I would try deleting it in .storage
@mild veldt Yeah, but for now it's a little too... raw. I like the configurator add on
to each their own
I prefer everyone use the new tools so that you can help guide us and provide feedback/bugs
However I tried to go back and forth from yaml to storage... It's very simple, and can be done in 2 seconds by pasting the yaml in raw editor.
To get the best from the two methods
so I can reproduce Lovelace failing to load when I use an !include within an included file in YAML mode
it seems to silently fail and fall back to my legacygroups.yamlconfig
@mortal cape Do you think that we can post an issue for the open/closed -> on/off problem?
Did you replicate it?
@brave badge I thought flamingmoe might have, I haven't checked
Check https://www.home-assistant.io/docs/configuration/splitting_configuration/ for include options
not there when I go to /states, no
Why is it inconsistant?
I would have expected all of them to be off π€
@wheat current It's VERY inconsistent!
If an entity changes state become ok, after a refresh it's wrong again
That is just wierd, you should open an issue if one does not allready exist
Can someone help me? I clicked on Configure UI (and some acknowledgement too) in the frontend and now HA does not load my ui-lovelace.yaml. How do I revert?
I think
lovelace:
mode: yaml
should get it back, but if it's the correct way π€·
@wheat current I'm looking for one but can't find. However my english is so bad. I hope someone else will open it
I'm on yaml mode
That was for @sour snow π
Ops... ok
It is probably fixed but we are not sure
Awesome!
Thanks very much, that was killing me. Found the doc now https://www.home-assistant.io/lovelace/yaml-mode/
@wheat current
@winter wasp So I figured out the problem with nested !include files. It seems before .84 all of the include paths were relative to /config, but now they are relative to the location of the file they are inlcuded in. So, if I add the full path to the inlcue, ie. /config/lovelace/views/kitchen.yaml , it now works
@winter hollow what are you referring to?
Seems that if it can't find the include, yaml mode fails, and it defaults to the other mode (not storage, the autogenerated one)
@thorny verge yep, works great using the relative path from the included file
In .84 this stopped working:
- entity: light.yeelight_lights_1
name: Yeelight 1
tap_action: toggle
type: entity-button
It shows the correct state, but does not change light on/off
action: toggle
Perfect.
Same for hold_action, and then anything that goes with the _action is indented as well, like navigation_path, or servce-call data
Can now have 2 service calls, or navigations for same button, it's awesome.
would i be best to remove lovelace before i upgrade i have only dabbled with it
@thorny verge Wow, that sounds great, good to know.
@twin kelp the auto-generated dashboard is the best route to start, IMO
i.e. remove π
@mild veldt I did use the auto dashboard . But never used it after . I had so much trouble with the last update , so I will remove Lovelace and remove then yaml file and go back to normal setting .then upgrade thankyou
Is there any component in Lovelace which is able to toggle between two services?
With 0.84, is lovelace doing some sort of caching with the config? The thing I loved about lovelace was I was able to edit the yaml and reload and the changes were instantly reflected. Since updating to 0.84, I'm noticing I need to restart HASS to see the changes
@vagrant spear are you clearing cache?
Browsers always cache by nature of their design
@tacit cave yep, tried that, updates aren't reflected still. (Using YAML mode btw)
@near crypt what do you toggle? One thing that can call different services?
@vagrant spear Yaml here too, but changes only need a page reload, as always on lovelace
@vagrant spear youβll only need to restart if yaml changes occur outside Lovelace-UI.yaml
Sry on phone, it auto capitalized crap
If the files are included using !includes then a reboot is needed? I am using includes for everything, but that I didn't need to restart in previous versions
Not sure, donβt use includes
I like to search for things for hours in my yaml files
I'll have to do some testing. Thinking maybe some behavior changed in regards to how the includes work
@vagrant spear scroll up a bit or search include there has been some recent discussion
Anyone have issues with not being able to migrate over to the new lovelace in 0.84
Says open the lovelace UI and click on configure ui
But my lovelace UI won't load to allow access to the configure UI.
Or do I need to access this via the orignail page
Original*
did you try the yaml mode?
Yes just did yaml mode and lovelace worked
Doing a reboot now with yaml mode # out to see if I can get the configure UI from the none lovelace screen
Side question while it reboots. I assume the pi 3 b+ will boot slot quicker then the pi2b
Ok found my issue. Need to switch back from Lovelace being default
All sorted.
Can I delete the ui-lovelace file
Yes, you can (if you are not using the yaml mode). Keep a copy, just in case.
Thanks
Just playing with the editor but can't edit my automations/script/etc pages. Is this a limitation at the moment or do I need to re add these via the UI for them to work?
Figured my automations issue as I have them seperated in a folder (split files) but since this new UI editor is in I guess they won't be needed either
@mild veldt I want to toggle XIaomi Yeelight moon mode, which is set by light.yeelight_set_mode --> mode: moonlight. To turn off moon mode: mode: normal. I am thinking in something like a toggle, if off= mode: normal, if on = mode moonlight.
I'm playing with setting up cards to run some scripts. An example would be
- type: entity-button name: " " tap_action: call-service entity: script.apple_tv_play service: script.apple_tv_play icon: mdi:play-pause
I'd like to make sure the card is of equal height and width. Is that possible?
No
I'm having a similar problem as cogneato (Today at 4:21 PM), but with a device trackers, sometimes they are "Home" others "home", same with sun and moon, some times the are properly formatted, and other just show the raw state "Below horizon" vs "below_horizon"
@wintry zinc I should retract that. With outside tools you may be able to. Possibly card modder? That's a pretty powerful custom card
Good afternoon
how do I switch to using lovelace?
when I'm in the normal mode, I don't see the three dots in the upper right hand side
if I change lovelace to yaml I get the 3 dots, but when I click configure UI it says you can't configure from yaml config
I just upgraded to .84 from .82
oh I think I got it
for some reason earlier /lovelace was redirecting me
NEWB: can someone take a look at this and tell me what Im doing wrong??? It comes up as blank in the UI.
@weary karma being thoughtless, posted a message that is more than 15 lines. It is now available at: https://paste.ubuntu.com/p/st82J76SHr/
@wintry zinc @mild veldt but the button card can call a script. You can distinguish between tap and long press even
How do I add a tapaction to an entity in the new lovelace config editor?
I toggled to yaml
- entity: light.mudroom_lights
- entity: switch.driveway_lights
- entity: switch.deck_lights
tap_action: toggle
title: Mudroom
type: glance```
@mortal cape I don't follow. What does that have to do with button height?
Expected a value of type `{entity,name,icon} | entity-id` for `entities.2.tap_action` but received `"toggle"`.
Falling back to YAML editor. ```
oh
lol I was literally reading the docs
I didn't see that you had to add it under action
wait that didn't work either
@mild veldt so like this?
- entity: light.mudroom_lights
- entity: switch.driveway_lights
- entity: switch.deck_lights
tap_action:
- action: toggle
title: Mudroom
type: glance```
cause that doesn't seem to work
Is there an easy way to add in custom components in the storage lovelace? I keep just pasting into the raw config editor when I need to add something
is it possible to use custom python components that way @past falcon
@mild veldt I totally missed the equal height/width thing.
I just finished a lovelace ui and don't want to migrate to storage lovelace until I need to tbh haha
I figured I'd give it a try and see what breaks haha I always have that fallback
@past falcon that's the only way for now. We have some ideas but nothing final yet.
@livid shell custom components don't apply to Lovelace?
no problem just making sure I wasn't missing something
@mortal cape we're you referring to @near crypt question on toggling between services? I figured he wanted an actual toggle not separate actions
@mild veldt sorry whatever the nomenclature is now for lovelace - you can still load scripts from /config/www in resources right?
@livid shell yes
Quick question re: picture-entity: is it possible to have state_images to non-binary numeric values, i.e. temperature?
cards:
- type: picture-entity
entity: sensor.pws_temp_c
state_image:
"4.0 Β°C": /local/resources/images/mirror/EMERGENCY3.gif
"3.0 Β°C": /local/resources/images/mirror/EMERGENCY3.gif
"2.0 Β°C": /local/resources/images/mirror/EMERGENCY3.gif
"1.0 Β°C": /local/resources/images/mirror/EMERGENCY3.gif```
This just seems to display the actual temperature sensor value instead of the associated image.
(And if anyone can point me in the direction of using greater than / less than options for numeric values using state_image, that too would be shiny)
Q: Captions on device-trackers inconsistent. Sometimes "Home", refresh -> "home"
Same with sun: "Below horizon" , after refresh "below_horizon"
@rose sluice create a tpkate sensor with string states for the ranges you want
@royal spear lots of similar discussion on the topic in here today.
Should be fixed in the next hotfix. I believe
@mild veldt Hm, I've not had to use template sensors yet. Looks like I have some reading to do. Thanks kindly!
So.... I read the change notes and updated my HA from .82 to .84
You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode. This will unlock a new option in the menu called βraw config editorβ.
When I try to open the lovelace UI, I get my normal HA UI
Anyone else run into this?
@wary dust If it's not Lovelace, add the "/Lovelace" and then use the 3 dots in the top right
To the URL I mean
Ah!
Thank you
Oh no
Does that mean I just lost all my lovelace stuff?
Oh good, I backed up before updating
Wow, I'm really confused now
Read the patch notes
If you are freaking out you didnt read it enough
Look into YAML Mode
I clicked the wrong thing, not raw config editor. All good now. Phew
I love this idea, actually
So I get full control of my yaml thru the browser now
that's minty
If I notice an error in the documentation, who should I tell?
@wary dust open a PR in the repo if you like
I'll try, never done that before
great way to get your feet wet
yes, unfortunately it was my error π
yeah, that was totally my intent
hi all, does anybody know if there is a way in the lovelace UI in glance card for example to display a specific number of decimal places for sensor values, without having to edit the original sensor precision?
That's a great question. I don' t know the answer though
@faint gyro no, you'll need to create a template sensor on the backend
I've been testing lovelace, and have my ui-lovelace.yaml file. Now I'm on 0.84, and adding lovelace to the URL doesn't load the ui-love... any more. Docs say to add:
lovelace:
mode: yaml
but, to where? in configuration.yaml? if so, under frontend? I'm confused.
I'm well away yet from committing to "storage"
Just in configuration.yaml
Thx, whilst waiting, I managed to copy my config info to lovelace storage. I presume I can delete the new 'lovelace' and 'core.restore_state" files and start over later when I'm ready?
is it possible to resize lovelace cards? https://community.home-assistant.io/t/resize-lovelace-cards/84736
@fresh forum check docs on panel in views
@fresh forum I think we are trying to do similar things - grrr.... Im trying to do something simple:
cards:
- type: glance
title: house mode
show_header_toggle: false
column_width: calc(100% / 6)
entities:
- entity: input_boolean.ib_early_mode
- entity: input_boolean.ib_morning_mode
- entity: input_boolean.ib_daytime_mode
- entity: input_boolean.ib_evening_mode
- entity: input_boolean.ib_late_mode
- entity: input_boolean.ib_night_mode
and it gives me 5 input_bools on one line and the 6th on the second line
~share
Please use https://www.hastebin.com/ or https://paste.ubuntu.com/ to share code.
Im really hating lovelace
spent half a day on this and its really not doing what it says on the side of the packet
GRRRRRRRRRRRRRR....... so all well and good to make breaking changes but its no good if YOU DONT UPDATE THE MAN PAGES!!!!!
an obscure reference that has taken 6 hours and countless google searches and in the last 3 mins i find this!!!! "On Home Assistant update 0.81.0 the column_width variable has changed to columns So, for the example above, you would set the variable and the value as follow: columns: 3"
The docs are up to date? https://www.home-assistant.io/lovelace/glance/
So not sure what your complaint is @weary karma
Hey lovely people, Is there a way to show an updating/loading/refreshing image while waiting for state change?
My smart lock takes 15-20s to update its status in HA once the service is called. I want to be able to show a loading gif/ at least a different icon after the service is called and we're waiting for a status update. Is that possible?
Hi everyone, I updated HA this morning from 0.83.X to 0.84.1, since then my Lovelace UI doesn't work anymore.
Heres my ui-lovelace.yaml: https://gist.github.com/Bouni/61836746b187400fe1440823d8d8be68
I don't see anything in the logs, I get the old UI but the URL says /lovelace/default_view
Hi, I have the same issue but upgraded from 0.82.X ..
I've just figured it out after writing my last post π€¦ You need to add
lovelace:
mode: yaml
Can't see any entities
to your configuration.yaml
That does not seem to fix my issue, it says "no entites" under state as well.
Do you see any errors in your logs?
No, there is no error at all.
And it says, 52 Loaded Components
Not sure why all the entities have disappeared after update.
anyone successfully using the storage mode with imported raw config? i can't edit most of my cards it just gets stuck in loading "card configuration"
I tried to use the card-modder with an iframe card but i got 'unexpected error' in the frontend. Maybe it's not possible to use the card-modder with an iframe card?
And in the log i got:
https://hastebin.com/upefacenek.sql
Works for me. And that error looks quite unrelated to card-modder.
@polar kelp I got also this error:
2018-12-14 12:09:56 ERROR (MainThread) [frontend.js.latest.201811211] https://xxxxxxx.duckdns.org/local/card-modder.js?v=b44fb3:45:20 Uncaught TypeError: Cannot read property 'forEach' of undefined
And this is the card:
hi all - is there anyone available to point me to the best documentation on how to structure (aka tame) the grid system in lovelace? it seems like the cards on the grid have a life on their own.
It'll auto-flow unless you use a mix of horizontal and vertical stack to lock your chosen layout
@foggy tendon Your version number seems off... I'd guess you're running version bc9061 which had this bug. Try the latest one.
@polar kelp Hmmm ok, but strange as i update it automatically with custom updater....
@vital kernel there's a bit of explanation on the logic behind it here: https://github.com/thomasloven/lovelace-card-modder#forcing-size
I believe that the best approach for most people is to let lovelace do its thing, and to keep the number of cards per view low, to get a simple overview.
But of course, different people have different needs.
I get this error, maybe custom ui is not anymore supported?
2018-12-14 12:54:27 ERROR (MainThread) [frontend.js.latest.201812110] https://xxxxxxx.duckdns.org/local/custom_ui/state-card-custom-ui.html:27:15926 Uncaught TypeError: Class extends value undefined is not a constructor or null
Just installed 0.84.2 and the map card is not anymore shown.
My card is:
- type: map
aspect_ratio: 100%
entities:
- device_tracker.s8_s8
- device_tracker.fha_fha
And i see this in the frontend:
https://imgur.com/a/bXdxkSU
What happened?
There might still be a problem with aspect ratio. Try aspect_ratio: "1:1"
@polar kelp Yes solved.. i disabled the aspect_ratio option... But everytime i open lovelace frontend i get the error regarding custom ui.... must i disable it?
No idea
@polar kelp I tried again to add a card-modder to an iframe card:
https://hastebin.com/inayozepaj.pl
But nothing changed in the card and mor ei still get the same error about custom ui
That is not card-modding an iframe card. That's card-modding a stack - which has no modifiable content.
@polar kelp hmmm... so how to mod the iframe card in that context?
By wrapping the iframe in card-modder, and not the stack.
But you'll never be able to mod the stuff in the ifram itself. Only the tiny tiny border and shadow around it.
@polar kelp Yes, i'm studying CSS. Can you tell me how to change with CSS the font and the font color in that style i quoted?
The font and font color of what?
Of the text i have in the cards
Text in the cards should work the way you did it. Text in the iframe is impossible to change, as I just explained. Think of the iframe as a picture.
@polar kelp Yes, i was meaning text in other cards... but i cannot change the font and the font-color
what is preformatted text and what ti put in place of that
You need to find the correct variables for some cards. Like --primary-text-color for seting text color of headers. Try the chrome object inspector. That can give some aid.
Unfortunately some things are still unstylable with card-modder. There's incomplete support in browsers for some kinds of css variables.
You can also look here for a list of variables to experiment with: https://github.com/home-assistant/home-assistant-polymer/blob/master/src/resources/ha-style.js (linked from card-modder docs if you want to find it again later).
@polar kelp I changed into this, but got errors:
https://hastebin.com/xutugumuqe.pl
I think you may benefit from this: http://thomasloven.com/blog/2018/08/YAML-For-Nonprogrammers/
I already tried with and without dashes for the three cards, but got always the same error... maybe that's not the culprit?
It's card, not cardS.
Ah.... so i must add a card-modder for every iframe i have that?
@polar kelp Ok, solved.... π¬
@polar kelp This is what i get, but i'd like to change font type and font color...
https://imgur.com/a/lumhNo3
i just noticed a weird behaviour on my fire tabled running fully kiosk browser. why does this code work in chrome everywhere but not in fully kiosk browser? https://www.hastebin.com/iyubuvumoy.css
fire tablet has an outdated android webview that doesn't support some of the lovelace features
eww. that comes unexpected ^^
yeah its kind of lame π¦
i never cared because it only came up with simple-thermostat, which is a custom component π
So, first time to start using Lovelace... what to think about @split granite .. guide me in the dark cave like Gandalf guided Frodo!
anyone can help me to understand lovelace raw config editor
j/k .. but will deffo have alot of questions coming along the way : )
Start by reading the docs, and the pins @minor viper π
@split granite excuse me what? i thought you we're going to hold my hand do everything for me : O
So, here's Mr Grenade. He'll be your friend. All you have to do is pull the pin and then hold him next to your ear while listening for the earth shattering kaboom...
πΏ
Haha π
So, dumb question.. (one of the many) lovelace.yaml will be like my new "customisation.yaml combined with configuration.yaml" for ONLY frontend correct?
so i know what to focus on, and where
Ish
customize: still plays a role
Otherwise though, yes, it's the thing for configuring your frontend (sorry, no trees)
for entities correct?
Well, yes, but that's the case for the current UI Too
HA is entity centric (mostly)
guys but when Im saving my lovelace config and then I will open with raw editor it will be writed in another format
i'm getting confused
Pick YAML or UI editing
Ok, then i understand the whole idea of Lovelace UI π Practicly you want to separate Configuration and Customization into a separate frontend file
@split granite how?
Yes, the aim is to allow the backend not to care about the frontend
it's a great way to test out things without "breaking" your whole setup! so... great work! i
@naive tulip By making a decision to use one, or use the other?
basicly becomes like a sandbox pretty much
One you can reload on the fly too
Is custom UI still supported by lovelace?
(i hate coding btw, hence why i decided to work as a DBA and a infrastructure) but now when i get the whole purpose of Lovelace i start to like it instantly!
And how to disable custom ui?
@split granite I want to disable it but don't know how...
maybe deleteing customiza_glob.yaml is enough?
I know nothing about custom UI - have you tried reading the docs for it
Yes, but nothing about disabling it....
@split granite I read it but I wanted to understand what's better Yaml or storage? on storage mode I'm gettinc crazy π
Whatever you prefer
Thx for explaining the questions i had Tinker! Made my life much easier π
Better is very subjective @naive tulip - depends on whether you want to only use the GUI for editing, or hand edit
@split granite mixed mode? π cause some things is better to do by hand like sensors or map card.. something can be managed from the UI without problem
Then please read the link I posted
hi there guys. as of the last update ui-lovelave.yaml seems not to be used anymore. its not in .storage/lovelace. My question is now how can you add custom cards to this file? also: any easy way to convert my ui-lovelace.yaml to the new filestructure?
ah thank you. so its not possible atm to use custom cards with the ui editor right?
where is the storage/lovelace located then?
is there a way to aggregate historical data? for example power consumption, summed, grouped per day
I'm using hassio in docker
checking under /usr/share/hassio and cant find anything with storage in there
only got lovelace.yaml on a fresh installed 0.84.1
@open vine idk I'm trying to understand it
@naive tulip okay π kinda like the ui editor tbh
@open vine use the raw editor in the UI if you need to add custom cards
ahhh i see. ill try it
ideally that will get better as we evolve, but that's it for now
i really like it π
Having a problem with Kiosk mode in 84.1 tried both storage mode and reverted back to yaml mode same result. Page url now shows up as https://mydomain:8123/lovelace/0 was https://mydomain:8123/lovelace/home-kiosk before. How can i change the default url to include the id. Id is correct in yaml file? Thanks in advance for your help on this issue.
@minor viper it is a hidden folder .storage in your main config folder. You shouldn't need to touch it
@static cloud read the updated view docs. https://www.home-assistant.io/lovelace/views/
path
@mild veldt ok it will be better but everytime I add some component to the UI after save they will be reformatted in another way
if you add it from the UI editor, yes, we parse and store it in json and it comes back out to yaml for editing in the preferred parse way. why does that matter?
@mild veldt ty lad! i was just wondering if i did properly. Cause i used the Addon for Lovelace Migration. Then on the (!) i checked in "Use lovelace as my default UI" and it seems to be working as it should π
that's like the most easiest way i could come up with π
that addon shouldn't be needed anymore...I think?
will check, thanks
i dont know, but it worked like a charm for me atleast!
@mild veldt okay.. but how I can edit it?
it auto created the ui-lovelace.yaml and i guess it used that one when i choose to use it as default through the Info page
for example if I need to add a sensor card
if you were to delete everything in .storage and ui-lovelace.yaml and reboot, you should be able to generate a default view from going to dev tools and selecting to try lovelace, for future reference
@naive tulip from your lovelace page, open the top right menu and select 'configure UI'
i think it's running fine as it is right now actually, the frontend is loaded with lovelace ui, and it use the ui.yaml file as it should aswell
if will use the yaml file only if you have yaml mode set in your main configuration file
@mild veldt ok but when I select configure UI I can't add Map card or sensor card.. maybe I'm doing something wrong
what is your definition of 'cant'?
what are you presented with
there is not a ui editor for those yet, so you'll still need to enter yaml in the presented dialog
cant see anywhere in the configuration.yaml that it should use lovelace tho
@minor viper did you select to 'take control' of your UI in lovelace?
if not, you're just looking at the default generated view
once you select take control you are then in storage mode
if you wish to be in yaml mode, read this https://www.home-assistant.io/lovelace/yaml-mode/
didnt see any option of Take control in the UI
If we use custom_updater... I assume we have to use the yaml lovelace?
So how do you properly setup Lovelace then?
@minor viper top right, select 'configure ui'
carefully
so I switched to the Storage method and it still did tell me there was a new card... I updated and the tracker card shows everything correctly. However, when I look at the Raw UI, it still has the ?v=OLDVER
update card can't update the config in storage
if that's just an academic thing, then I won't worry about it
updater and storage do not work together, yet, right @wheat current ?
right, but does it need to?
to fix this lovelace issue (losing config after new update). I used the raw editor and did copy paste of my ui-lovelace.yaml there. Was easiest way to fix.
Correct @mild veldt , and I will not make it work, Home Assistant should be the only system that controlls files there
as long as the components are getting updated in /custom-components/ it should be ok?
Can someone point me to any docs on making lovelace my default?
@worthy kiln so you did what the release notes said to do?
Yeah i've got the top right Select Configure UI, does that mean Lovelace is properly setup then?
I could not find any release notes, still talking about lovelace π¦
they are on the main site
@restive flicker go to "i" in the left pane
@minor viper actually select it
i did π
@wheat current π
@hallow spruce .... that was easy π Thanks
@minor viper and if you haven't set yaml mode in your config you are then in storage mode
oh sweet, as it should be then π
i guess storage mode is the way to use it now then correct? i mean since 0.84.1
didnt use Lovelace before!
@wheat current as long as the cutom_updater is actually updating the component files, does it matter if the versions sting is out of sync in the .storage/lovelace file?
yes
oh....
that serves as a cache buster, so it does not serve an old file
So I guess I'll go back to yaml management. I liked being able to make minor config tweaks with the in-GUI editor, but oh-well, I loves me my custom stuff more
you could still use ui editor, but you would have to do some work to update
if it was me, I would keep my old ui-lovelace around and just strip it down to my resources
and then when I run an update from the tracker card, just copy/paste the updated resources from ui-lovelace to my managed config in the raw editor in the ui
Suddenly log full of these errors:
https://hastebin.com/gapohovuwa.rb
Meaning? How to solve?
magic
Carefully
there is a way for sort what I see in the raw config editor, cause some time it display the things in the right order some time not
I asked a few months ago, but now that we are on a .84, is there any way to disable/suppress the toast notifications?
Pain in the butt for lovelace when using for a tv remote, and say volume is on bottom line, notificatin on top for a second.
@naive tulip what is your definition of "right"?
@thorny verge I still like the idea, but no, not yet
We've been pretty busy trying to get lovelace production ready
feature requests will be in the new year
π€
Awesome, thanks. Love the work!
Is there a card length max?
I am trying to display group.all_automations, all_switches etc. using the custom group-card and it only draws so much then the browser window hangs.
@mild veldt as mentioned in the lovelace documentation.. For example I'm adding a map badge as described in thendocumentation.. After I save it and open again the rwa editor I see all the entities in another order
@winter hollow As always... but after updating HA asked me to login and i logged as always
did you click the remember login in the right bottom?
@winter hollow no, now how to logout and login again?
But i see i am logged as owner with my name
i restarted ha but always getting that error
but only with lovelace...
ok i logout then login again and saved the login...
@winter hollow https://hastebin.com/bihuwovupi.py
what happens?
@brave badge Thank you for the commentary about sensors needing graph: line
How does one share the new UI Lovelance if it is edited via the online editor?
Using Lovelace config editor in 0.84.2. In the initial config, how are entities ordered on a entity card and how can I change the order in the editor? Is it possible?
i don't anymore get the request to login with legacy API password. Why?
@sinful flax for a particular card you can Toggle Editor or for sharing your full config use Raw Config Editor found in the menu after enabling Configure UI
@summer pasture not through the UI editor alone. You'll need to Toggle Editor and do it in the yaml for now
@mild veldt any ability to share the file via git? or will it require copy & paste
copy/paste
The file in .storage is actually json now and system managed
If you want that, you'll need to enable yaml mode, and you won't be able to use the UI editor then
Thanks!
@mild veldt Got it. Thanks!
Please help me... i get tons and tons of errors like i posted before.. is it an authentication error ? And if yes how to solve?
i always logged in with legacy API password, but now i don't get that type of so i enter my legacy credentials but it seems them are not valid anymore
if i login in local i get the request of API password but with duckdns not anymore
Why do you use legacy?
Then switch to the new auth system? I don't know what the issue is exactly, but I would try it π
i switched as it was the only system i am asked... but getting all those errrors
how to know the credentials of the new system?
maybe i lost username and password?
but i can enter the HA frontend
ctrl + f5
@foggy tendon https://www.home-assistant.io/docs/authentication/
and β
everytime i do a refresh i get this:
Error handling message: {'id': 4212, 'type': 'subscribe_events'}
18:21 components/websocket_api/commands.py (ERROR)
Error handling message: {'id': 4211, 'type': 'subscribe_events'}
18:21 components/websocket_api/commands.py (ERROR)
and the ID is growing every minute
Why i get this:
Login attempt or request with invalid authentication from 2.xx.xx.xxx. It's my IP address
@foggy tendon did you read through my link?
Yes i read and still don't know why i get those errors... If you can explain me this i will understand
have you moved to the new auth setup?
removing legacy?
really, should just remove the full auth_providers section
we're way off lovelace, let's move to #330944238910963714
Wondering...
Is there anyway to do templating (or show state of a sensor) in the Title of a Lovelace card?
I want my Lovelace Entity Card to have a dynamic name.
I had tried something like this...
cards:
- type: entities
entities:
- entity: sensor.road_condition_1_name_start
- entity: sensor.road_condition_1_name_end
- entity: sensor.road_condition_1_conditions
show_header_toggle: false
type: entities
title: '{{ states.sensor.road_condition_1_name_start.state ~ " to " ~ states.sensor.road_condition_1_name_end.state }}'
(Spacing MAY be off a bit, that's just due to me bringing into here.)
But I'm guessing the title doesn't allow templating?
no...title cannot be templatized
Nothing in lovelace can be templated.
where do hassio write the changes for lovelace if you edit via UI?
.storage
Hi, I've updated to 0.84.1 and I'm having trouble with lovelace. I'v 'uploaded' my configuration in the 'raw config editor' and got my interface back, but when I try to edit in the 'configure UI alpha) it says I have no IDs. When I click 'migrate config' I got a message with 'Migration failed: Unknown command.'
EDIT: OK got it. had to delete the original ui-lovelace.yaml and restart HA.
any hints on how to solve this?
@raven nacelle @polar kelp Thank you.
Can anyone provide me with a tap action example that uses the toggle action for the new lovelace format?
I'm having trouble getting it to work
- entity: light.mudroom_lights
- entity: switch.driveway_lights
- entity: switch.deck_lights
tap_action:
- action: toggle
title: Mudroom
type: glance```
I tried also just ```entities:
- entity: light.mudroom_lights
- entity: switch.driveway_lights
- entity: switch.deck_lights
tap_action:
action: toggle
title: Mudroom
type: glance```
Both provide similar errors Expected a value of type `{entity,name,icon} | entity-id` for `entities.2.tap_action` but received `[{"action":"toggle"}]`.
Expected a value of type `{entity,name,icon} | entity-id` for `entities.2.tap_action` but received `[{"action":"toggle"}]`.
well identical errors
The second one shouldn't have square brackets in the error... Are you sure they're identical?
let me check again
Anyway, that error code comes from the UI editor... I think things should still work, just not be editable...?
I haven't played around with it yet
Oh my god, I just figured it out
ok so I had the first config saved
usually when you edit the config it validates right away
however changing - action to action doesn't trigger a validation
so the error stays there
the latter is actually valid
saving the config without the - the action works as expected
@polar kelp thanks for pointing that out, that's what made me thing to save it and reload with the other config, I thought it was validating on the fly like with other edits
it gives this error: Your config is not supported by the UI editor: Expected a value of type `{entity,name,icon} | entity-id` for `entities.1.tap_action` but received `{"action":"toggle"}`. Falling back to YAML editor.
but seems to work
Hi guys. Just now switching over to Lovelace based on the intent to make it the default UI soon. I am having some weird glitches. Running 0.84 and using two custom cards (Darksky custom and the group card by ciotlosm). https://imgur.com/a/Xufz8M1
The UI seems to reload itself and it will scroll back to the top and cause certain text to move. Any ideas why? Not familiar enough with how Lovelace works to troubleshoot.
Hey guys - just messed up - managed to use the new editor UI, and cleared the ui-lovelace part. Now, when I load lovelace, it throws up an exception. How can i get back to editing the file again? I merged into the memory version, and not the yaml file anymore
I can't get back to the raw config editor π¦
If you have a backup of the file maybe you can do this? https://www.home-assistant.io/lovelace/yaml-mode/
Thought has crossed my mind - but would ideally just want to find the .storage part to change it back to a valid version again.
I'm still trying to figure out how to switch between the different modes "auto-generated, storage, and yaml". Can't find any documentation
I found .storage but doesn't seem to help to edit lovelace file in there
how is it possible to create a lovelace page and have it hidden on the menubar? It would still be accessable from entering the url directly or create a menu item on sidebar.
@feral nymph I would think you could use the approach you had in your link to run STORAGE mode or AUTO as well?
@feral nymph back in lovelace now, will stick to YAML file for a while π
@small gyro yeah I am also going to stick with the yaml mode for awhile as well. It is a pain to use the UI editor for anything else other than the most simple additions/edits.
In reference to my earlier message about the UI "glitching", it seems that this was caused by the "custom:group" card by @ciotlosm. [https://github.com/ciotlosm/custom-lovelace/blob/master/group-card/group-card.js]
If anyone might know how to prevent the aforementioned "reloading" problem please let me know as I really like to keep using that cutome card so that I can use the preconfigured groups.
did anybody managed to make 3 light cards in a horizontal stack looking good on mobile also ?
top: desktop, bottom: mobile
Does anyone know if you can change the time span of the built in graphs in the UI to more (or less) than 24 hours?
Is anyone a pro at using Picture Elements? I have panel: true but it does not scale my floorplan correctly.
Icons move around?
I have an odd issue, I think I should correct before upgrading to 0.84... I removed some some sensors I no longer need from my configuration.yaml and my ui-lovelace.yaml. Yet, the card still shows up and reads: "Entity not available: sensor.den_temperature." Multiple reboots and it's still there.
Clear your cache as well
Yeah, I did. And had issues with multiple browsers.
But I just solved it. Looks like it was a cache issue, just not browser related.
VSCode must have not been communicating as I just opened it up again and the lovelace entry was there again. I have been having some issues with using the hostname with samba lately. Must have been that.
Thanks though.
Can you template items in lovelace cards? Like the URL of an image in a picture card?
When using "panel: true" is there anyway to limit the height? My vertical floorplan does not display well on a horizontal screen currently.
Is it expected that the UI Editor is not aware of the entity type divider?
Your config is not supported by the UI editor:
Expected a value of type{entity,name,icon} | entity-idforentities.2.typebut received"divider".
Falling back to YAML editor.
Really n00bish question... How do I set the size of a picture-elements icon please?
So yesterday I had to restart a fresh copy of hassio...I cannot get my custom cards to show up. I have cleared my cache but still getting an error. Error says it cannot find my .js file. Any ideas?
@marsh forum quite possible
@short willow using "width: XX%"
@short willow css in the style field
@tiny trellis do you have the source files after doing your fresh install?
Yes. Placed then in the www folder and subfolders as needed
@mild veldt Change my image? Shouldnt there be someway to scale the card with CSS?
Meaning impose a maximum height
Okay so I've tried that - used top: and left: to position them... https://imgur.com/a/I5qsVee
They are just placeholders right now, but want them to be double that size. I'll try a bigger width:
Nope, tried 5%, 10%, 50%, 75%, 150%. Icon stays the same size, just moves to the left
@short willow Sorry, if it is an icon then there are different parameters
--iron-icon-fill-color: "#11AB7D"
--iron-icon-height: 40px
--iron-icon-width: 40px
i think
Ah nice, thanks
Yeah, and as you can guess, fill-colour will come in once my parts get here from sunny China
Perfect, thanks @feral nymph
@feral nymph you could use the custom card-modder
@ornate pollen far from a pro, but I started out with only mobile LL views. Might get you some ideas. https://community.home-assistant.io/t/my-lovelace-screens-themes-mobile-pc-views/84271
In preparing to upgrade I managed to break my favorite custom cards that were working fine. Is it possible to delete a custom card, .js files and resource info and basically reinstall the card?
tried clearing everything on all the browsers still get the error for custom cards
custom element doesn't exist :slider-entity-row
@atomic glacier if you added files then of course you can remove them...?
are you sure the path and file name match what you have defined in resources?
@tiny trellis
I wasn't sure if those would affect the version #'s when I reinstall them.
I don't follow
is there any way to group entities so they don't have a border?
eg. light or entity-buttons
If you make changes to a custom card file, you should increment the version number or clear your cache to get the change reflected
@brittle ingot ui is card based
you could try using card-modder
@mild veldt do you have a link to card-modder handy?
but if I delete and then reinstall does that apply? or can I just use the version they are on when I remove & then reinstall? I'll give it a try. Thanks!
yes, google.com
@mild veldt I am giving up on it for the night was a waste of two hours trying to get it to work. Will try again tomorrow sometime
@tiny trellis I was just having that issue
turned out I downloaded the js files wrong from github
they were more like html pages rather than the true js file
clone/download to a zip and then move it over to your hassio or use the cli and wget
@quasi mist I went as far as copying the text from the js files
yeah I did that as well but the underlying file was still corrupt
when I downloaded a zip from github and moved it over without touching the files it worked
Hey. Home someone can help out. Frontend doesn't seem to be loading. I get "Unable to connect to Home Assistant" when I try to go to home assistant but Ariela (an app for home assistant) works and I can control my devices from that. I am also able to connect to Cloud 9 hosted through hassio. Any ideas?
Nothing in home assistant.log other than an error about influxdb
@gray marsh did you figure out your issue? If not does the error continue through reboot cycles?
does anyone here use geo location events? I have added these to a card but it only lists the group (I added that as the entity since the entity id's are not static/fixed) and I just get one line with the group... can click on that and it shows the entities but the docs seem to show the individyual entities on the main card??