#frontend-archived

1 messages Β· Page 97 of 1

vapid field
#

Suggestions ?

potent fjord
#

yeah ok, should read more carefully

split granite
#

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

potent fjord
#

that card had configuration option for background image, that fixed the issue

winter knoll
#

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

mild veldt
vapid field
#

hey folks, im seeing an error in lovelace...custom element doesnt exist: button-card

polar kelp
#

config?

vapid field
#

sorry ill grab it

polar kelp
#

That describes how to start debugging

vapid field
#
  - 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
violet talon
#

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

vapid field
#

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 {
timid burrow
#

it was recently updated - make sure you have latest version of the card

vapid field
#

yeah i just downloaded the latest version and still get that error

timid burrow
#

clear all data and cookies?

polar kelp
#

@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.

vapid field
#

Yeah I just got the latest version last night

#

@polar kelp could you link the correct version so I can triple check please

polar kelp
vapid field
#

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

polar kelp
#

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.

timid burrow
#

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

weak flume
#

Do you need quotes on a boolean?

#

ie True

timid burrow
#

I was following an example from someone else doing the exact same thing. I’ll try without.... he may have had single quotes...

weak flume
#

Yeah that was more of a question. I didnt think you needed them but I could be wrong.

viral sorrel
#

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
old karma
#

@viral sorrel

          - entity: sensor.family_room_lamp_power
            secondary_info: last-changed

is enough.

viral sorrel
#

thanks.. and it seems it's needed after each entity

lofty summit
mild veldt
#

@lofty summit cool idea! Going to add it on sharethelove

icy robin
#

@polar kelp - can we discuss secondary_info?

polar kelp
#

Sure

mild veldt
icy robin
#

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?

polar kelp
#

That's odd...

icy robin
#

I thought so too πŸ˜‰

polar kelp
#

It should work in the rc... Is it not working with the next-branch of card-tools either?

lofty summit
#

@mild veldt cool thanks! πŸ˜ƒ

icy robin
#

I tried earlier, but was on the dev branch at the time, not rc

polar kelp
#

It sounds like a ll-rebuild or rebuild-view event that's going wrong somehow.

#

Should work on dev too

icy robin
#

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?

polar kelp
#

In short it causes a card to be rebuilt after a custom element has loaded in.

icy robin
#

.3 actually causes a different problem...the custom entityRow that I create no longer returns an updateComplete

kind shellBOT
polar kelp
#

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)

icy robin
#

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?

polar kelp
#
  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.

icy robin
#

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!

polar kelp
#

Of course. Thank you!

mossy otter
#

just updated to the latest version of HA and my lovelace frontend has completely disappeared

polar kelp
#

Great timing. Release of 0.86 is just hours away. Will it not load at all, or is it filled with different stuff?

potent fjord
#

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 ?

potent fjord
polar kelp
#

That should work so far

potent fjord
#

made selector for it by youtube guide

#

hass script check doesnt give any errors

#

then in theme folder i have material_dark_theme.yaml

hot gyro
#

@raven nacelle does your demo dashboard work on a mobile device? or do you use a custom url?

polar kelp
#

@potent fjord What's the first line of themes/material_dark_theme.yaml?

potent fjord
#

i try to change, and get this : Theme material_dark_theme.yaml is not defined.

#

aha

polar kelp
#

You're welcome

potent fjord
#

thnx, it says material_dark_green:

#

your are wiz @polar kelp πŸ˜ƒ

raven nacelle
simple jolt
#

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?

hot gyro
#

didnt check mine is downstairs so I thought I'll ask πŸ˜ƒ

polar kelp
#

@simple jolt Themeing is the official way. Card-modder can probably do it too, though.

simple jolt
#

@polar kelp yea don’t really want to create an entire theme just so I can have diff line colours.

polar kelp
sour crag
#

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).

split granite
sour crag
#

Thanks I will check that out

simple jolt
#

@polar kelp would you know which element represents the line colour to use with card modder?

polar kelp
#

Chrome object inspector

#

I think it's --accent-color...

mortal cape
#

@simple jolt there's plenty of existing themes where you could simply modify what you want

polar kelp
#

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!

forest mica
#

so with lovelace becoming the new default UI what is going to happen with all the components that turn into yellow bars in lovelace?

winter hollow
#

Yellow bars mean that the entity is not available

#

if you are in storage or yaml mode you should correct those yourself

polar kelp
#

Do you have an example? There are some components that add and remove entities dynamically.

winter hollow
#

when in generated mode, check your group config for non existing entity's

forest mica
#

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

polar kelp
#

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.

timid burrow
#

@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

icy robin
#

@polar kelp Thank you for the update! Just released the updated secondary_info plugin to go along with it.

vapid field
#

@icy robin What secondary_info plugin?

mossy otter
#

@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

polar kelp
#

Yes. That is the default behavior. Your config is still safe. Check yaml mode in the docs. On mobile, can’t link.

radiant drum
#

How will the new editor and custom cards work?

mild veldt
#

You can edit the custom cards YAML for noe

#

And card creators can make editors

mossy otter
#

hassio still saying 0.85.1 is the latest version. Guessing 0.86 will become available tomorrow?

mild veldt
#

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.

radiant drum
#

@mild veldt so i need to make a custom_cards.yaml for all my custom cards?

mild veldt
#

No

#

The authors CAN make UI editors

winter wasp
#

after upgrading to 0.86, the iOS app has started sometimes showing blank views until i force a refresh

winter hollow
#

If they don’t you can edit the yaml from the UI

vapid field
#

@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!!!

mild veldt
mossy otter
#

so let me get this straight, lovelace no longer uses what's in your ui-lovelace.yaml file?

vapid field
mossy otter
#

oh awesome, thanks!

#

am guessing that custom components can't be used on the yaml mode?

#

non yaml mode rather

vapid field
#

if you switch back to yaml mode, everything works as before

mossy otter
#

Can you use yaml mode AND use the editor in the frontend?

vapid field
#

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

mossy otter
#

makes sense

#

but custom resources will only work with the yaml mode right?

vapid field
#

I dont think so, but have not tried it

#

check the blog

mossy otter
#

will do!

#

thanks for the help

vapid field
#

you are welcome

winter hollow
#

UI/storage mode has a raw yaml editor that allows to add custom resources

ornate mason
#

Well, this is annoying. Conditional cards don't accept empty string for state and state_not.

mossy otter
#

@winter hollow that sounds interesting. CAn you tell me a little more about that or point me towards some docs?

winter hollow
mossy otter
#

ah this is absolutely brilliant!

#

thanks again

timid burrow
#

@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

mortal cape
#

@timid burrow it's rare for qemux86-64 to be last. I think we got put on some list.

timid burrow
#

yeah I know right

#

lol

#

we are on the naughty-list

tepid locust
#

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

timid burrow
#

i am.. working for me

tepid locust
#

do you have the tooltips setting enabled?

timid burrow
#

yes

tepid locust
#

damn, mind sharing your config for the card so I can have a look at it and see if I messed something up?

timid burrow
#

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

tepid locust
#

is card-tools required for this card?

timid burrow
#

nope

tepid locust
#

hmm dont know why but as soon as I enable tooltips: true card dissapears again, even tried adding javascript: latest to config.yaml

timid burrow
#

you got the new version from today?

tepid locust
#

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

timid burrow
#

ok. weird

#

I am using that one as well

#

m.p.frankland is on the forum right now.... he might reply

tepid locust
#

ah last forum post helped me find an error thanks, will post in thread

timid burrow
#

sweet!

tepid locust
#

did you have to setup the slots for the tooltip popups to work?

dire salmon
#

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 ?

half osprey
#

yes

dire salmon
#

hmm...

#

im getting


Custom element doesn't exist: monster-card.
{
  "type": "custom:monster-card",

after restarting...

mild veldt
#

@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

tepid locust
#

and now it works must have missed some entity in the card

mild veldt
#

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

dire salmon
#

@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..

mild veldt
#

I see. It does look pretty old. Are you on 0.85 by chance?

dire salmon
#

0.85.1

mild veldt
#

you have yaml mode activated?

dire salmon
#

I dont know

mild veldt
#

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

dire salmon
#

ooh I see

#

so it doesnt use the ui-lovelace file ?

mild veldt
#

ui-lovelace.yaml is not used when you are not in yaml mode

dire salmon
#

aah I see I see

mild veldt
#

if not in yaml mode, your configuration will be managed by the system

#

all edits will be done from the ui

dire salmon
#

great !

#

thanks very much πŸ˜ƒ working now

mild veldt
#

πŸ‘

timid burrow
#

@tepid locust I haven't - just defaults. as I said I can't edit lovelace until I get 0.86

tepid locust
#

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

timid burrow
#

sweet

tepid locust
#

I was using a really old version up until yesterday evening

timid burrow
#

ah....

forest mica
#

are packages going to work with lovelace?

timid burrow
#

yes

hoary ginkgo
#

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?

timid burrow
#

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?

hoary ginkgo
#

i don't seem to have anything in a side panel that says "try lovelace"

timid burrow
#

click i in dev tools down the bottom of the panel

hoary ginkgo
#

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

timid burrow
#

Info = i then look in the right at the bottom of dicplayed info

half osprey
#

@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

timid burrow
#

ah.... I might get 86.1 before 86.0 at this rate lol

half osprey
#

@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

timid burrow
#

OMG how did you even work that out! lol

hoary ginkgo
#

@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

timid burrow
#

does it say states instead? It's because of what balloob said.. a bug..

hoary ginkgo
#

yes, ok - wasn't realizing that was related to the bug too - thanks

forest mica
#

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?

timid burrow
#

because it's a clean break between frontend and backend

#

and you can display whatever you want to be displayed

forest mica
#

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

half osprey
#

86.1 has been released with the lovelace fix @hoary ginkgo

timid burrow
#

qemux86?

half osprey
#

🀷 I don't manage that one

hoary ginkgo
#

thanks

timid burrow
#

hahahaha... I bet @mortal cape we'd see 86.1 before 0.86... usually see that almost immediately actually when you post

forest mica
#

should i change from storage to auto generated?

half osprey
#

whatever you like

#

If you want to be in control, you can use storage mode

forest mica
#

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

timid burrow
#

cut and paste.... when you save it will auto refresh

half osprey
#

Just a note, Lovelace does not support having two tabs open and making changes in one and seeing it live update in the other

timid burrow
#

@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

eager pollen
#

Is there anyway to "import" a yaml lovelace ui to then use the online editing tool to make changes/future updates?

timid burrow
#

yes - just cut and paste it in raw mode editor

eager pollen
#

Thanks @timid burrow

timid burrow
#

sure

polar kelp
#

I’ll take a look at that @timid burrow. Thank you.

timid burrow
#

no thank you for the great cards!

vapid field
#

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

timid burrow
#

@vapid field include in lovelace? If you want that you need to use yaml mode

#
lovelace:
  mode: yaml

in config yaml

old karma
#

Is it possible to make a button, script or something that could refresh lovelace like in the dot menu?

polar kelp
#

Yes. But it's not easy.

vapid field
#

hey guys, if I edit lovelace via the UI editor where does it save the config?

#

nevermind found it config/.storage/lovelace

polar kelp
#

(don't poke at it)

#

(unless you know what you're doing)

#

(or really want to)

vapid field
#

just wanted to make sure it was a file I could backup before I went crazy editing πŸ˜ƒ

polar kelp
#

Sure. That works. Or you could copy out of the raw editor, I guess.

vapid field
#

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

polar kelp
#

@timid burrow I think fold-entity-row should be fixed now.

old karma
#

@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.

mossy otter
#

input booleans are not supported on lovelace?

timid burrow
#

what do you mean by not supported? mine work fine

mossy otter
#

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...

timber peak
#

input_booleans broke in my install too.

mossy otter
#

0.86?

timber peak
#

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.

mossy otter
#

ah that's a shame

#

always one step forward two steps back for me

polar kelp
dreamy tendon
#

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

placid geyser
#

Is it possible to move a view (left or right) in the UI or only in YAML?

polar kelp
#

Know what, @old karma . I'll just add it to browser-commander for you.

old karma
#

Thanks @polar kelp , just want to write that VNC is easier for me. πŸ˜„
You are GREAT!

winter hollow
#

@placid geyser no, not yet possible in the UI

placid geyser
#

Thanks @winter hollow

timber peak
#

@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.

mossy otter
#

@timber peak interesting!! What further issues are you having?

cerulean scarab
#

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?

subtle rune
#

@cerulean scarab As of right now you can't keep on autogenerating when you've taken control yourself

vital void
#

before I had customize_domain assumed_state: false to get the slider switch for *.switches, how do I do that in lovelace?

polar kelp
#

That should still work

vital void
#

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?

winter hollow
#

Yes, only for entities that have an unique id I believe

#

or that are in the entity registry

scenic lantern
#

Anyone know how to get the configurator dialogs to show up in Lovelace?

polar kelp
#

There are three dots in the top right corner. Click them and select "Configure UI"

dreamy tendon
winter hollow
#

There are three dots in the top right corner. Click them and select "Configure UI"

dreamy tendon
#

raw config editor?

winter hollow
#

Then in the same menu click raw editor

dreamy tendon
#

okay

#

can I put the resources there as well or should they be somewhere else?

winter hollow
#

No, resources go there

vapid field
#

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!

winter hollow
#

yes

vapid field
#

and the customs components I add through the UI configuration will be mantained automatically ?

polar kelp
#

What do you mean with "maintained"?

vapid field
#

the updater for custom lovelace components

polar kelp
#

Then no.

vapid field
#

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?

polar kelp
#

The only way to add a custom card to the configuration (at this point) is through the raw editor.

vapid field
#

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:
#

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 ?

polar kelp
#

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

dreamy tendon
#

thanks bramkragten, I think I'm getting the hang of this!

mild veldt
#

Famous last words

polar kelp
#

The ones before or after the comma?

indigo fossil
#

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

mossy otter
#

on the lovelace UI editor...toggle editor is always blanked out

#

is there a way to activate that?

polar kelp
#

Toggle editor?

mossy otter
#

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

polar kelp
#

That happens for cards that don't have an editor yet. Try e.g. the Entities card.

mossy otter
#

ahh gotcha

#

Ideally, I'd like to do half raw yaml, half editor but am guessing that feature doesn't exist yet right?

polar kelp
#

Getting there

mossy otter
#

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"
  }
}
polar kelp
#

@wise storm What is white? The button? The menu? The interface?

#

@mossy otter Conditions should be a list

wise storm
#

@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.

mossy otter
#

thanks @polar kelp got it working now!

wise storm
#

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.

polar kelp
#

That's... interesting...

#

Is your interface by any chance in a language that's written right to left?

wise storm
#

@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.

proper crater
#

Hey, I must be dumb or simple, but, how on earth do I set up Columns in Lovelace?

polar kelp
#

@wise storm No, they shouldn't.

proper crater
#

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.

winter hollow
#

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

proper crater
#

Ah, OK.

winter hollow
#

with the view set to panel

proper crater
#

How would one go about doing that? That sounds ideal.

winter hollow
tight canopy
#

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?

winter hollow
#

No

#

You never have to restart Home Assistant for a edit in Lovelace

dreamy tendon
#

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

winter hollow
#

put it in your www folder in your config folder

polar kelp
tight canopy
#

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

winter hollow
#

if you just created www restart home assistant

indigo fossil
#

that's how I define columns

dreamy tendon
#

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

polar kelp
#

There's also some debugging instructions in there.

dreamy tendon
#

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```
polar kelp
#

Looks fine

proper crater
#

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?

polar kelp
#

My guess: Because of bad indentation, but that's impossible to tell without code formating

#

~format

kind shellBOT
#
:information_source:
Format Code:

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

polar kelp
#

That should work

proper crater
#
    cards:
    - type: light
      entity: light.living_room_lamp
    - type: light
      entity: light.bedroom_lamp```
naive ruin
#

Just update to 0.86, when i try to edit UI i get Saving failed: Unknown error

proper crater
#

It just puts them on top of each other. And if I enter true for panel, it disappears completely.

polar kelp
#

I'm not sure, but try adding two more spaces before each line after cards:...

indigo fossil
#

yeah, it might be indentation

mossy otter
#

has tap_action on entities changed?

polar kelp
#

in 0.83 or .84 or so, yes.

mossy otter
#

ah crap

polar kelp
#

The docs are up to date

mossy otter
#

had a wonderful entities filter card that showed what lights were still on and i just tapped them to turn them off

proper crater
#

No luck.

#

😦

dreamy tendon
#

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?

polar kelp
#

yep

untold magnet
#

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

polar kelp
#

To enter edit mode click the three dots in the upper right corner and select Configure UI.

untold magnet
#

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

tired quail
#

i haven't paid attention to yaml mode in lovelace. can you use !include in yaml mode now?

polar kelp
#

Yes

#

The entire family of !include functions, in fact. And !secret

tired quail
#

πŸ‘ thanks. I'm not planning to use it myself, but wanted to confirm if others asked πŸ˜ƒ

winter hollow
#

@untold magnet update to 0.86.1

#

or restart home assistant

#

Or you had it fixed πŸ˜ƒ

violet talon
#

there's a 0.86.1 already? 0.86.0 wiped my built-in lovelace setup 😦

untold magnet
#

not giving me the option for 0.86.1 yet, still on 0.86.0

#

in Hassio

winter hollow
#

@violet talon wiped?

#

I don't think it did...

#

what version are you comming from?

violet talon
#

as in everything I set up is gone and now there's a single page with every sensor

#

0.85.1

polar kelp
#

@violet talon Your configuration is still safe

#

You need to switch to yaml mode

violet talon
#

I wasn't using yaml mode before

polar kelp
#

Oh. From 0.85? Never mind then.

winter hollow
#

Are you in storage mode?

violet talon
#

I thought the built-in editor was the "hot and new" and the way to go

#

yeah

mossy otter
#

looks like everything by default sorts itself in to a column rather than trying to organise sensibly like it did before?

proper crater
#

Everything I do is going in a column too soggypete

simple jolt
#

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'

polar kelp
#

Browser log?

winter hollow
#

@violet talon you didn't get an error somewhere? In the logs?

hoary ginkgo
#

@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.

simple jolt
#

@polar kelp that is from my phone.

polar kelp
#

Then your guess is as good as mine.

simple jolt
#

I can check chrome. How would I go about sending you the logs?

polar kelp
winter hollow
#

@polar kelp you should get your own channel for your custom components πŸ˜›

violet talon
#

@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)

civic stream
#

does the old groups.yaml define anything in lovelace?

winter hollow
#

your lovelace in .config can't just disapear?

#

Yes, in automated mode

polar kelp
#

That yes ☝ was for you, @civic stream

civic stream
#

Hm, what was? Not so proficient in discord..

winter hollow
#

Yes, in automated mode

civic stream
#

Is that the mode I disabled when I clicked the dots to edit it visually, in the UI?

polar kelp
#

yes

winter hollow
#

yes

civic stream
#

Ok, thanks!

polar kelp
#

Now you're in "storage mode"

civic stream
#

If I would like to backup this whole UI config that I now make, is there I file or so..?

#

-I+a

violet talon
#

@winter hollow well it was. it's like I'd never used lovelace before and migrated my states ui to lovelace

winter hollow
#

You can copy paste it from the raw editor

polar kelp
#

<config>/.storage/lovelace

#

That too

violet talon
#

(β•―Β°β–‘Β°οΌ‰β•―οΈ΅ ┻━┻

civic stream
#

Ah, ok!

violet talon
#

i swear every time I refresh the page my ui changes.

polar kelp
#

That's probably what we should recommend *makes note

simple jolt
#

@polar kelp I found the below. Uncaught (in promise) ReferenceError: cardTools is not defined at customElements.whenDefined.then (state-switch.js?v=c7dd70

civic stream
#

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?

winter hollow
#

Can you share the config?

mild veldt
#

Use a light group

civic stream
#

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

polar kelp
#

@simple jolt Does your log also say that card tools is installed? In green

mild veldt
#

@civic stream use the new light switch

#

Was in 0.85 I think

polar kelp
#

And is that before or after what you found?

winter hollow
#

@mild veldt switching a group should also work right?

polar kelp
#

It should

winter hollow
#

If it doesn't that would be a bug?

polar kelp
#

It would

mild veldt
#

I’m just saying that a light group makes more sense

civic stream
#

iantrich: thanks, didnt know about that component

#

It did, however, work before.. Without using light switch

mild veldt
#

🀷

civic stream
#

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

winter hollow
#

ok, can you create an issue for that?

mild veldt
#

I think there is already a bug report for it...I think...

civic stream
#

I can try, never done it before. Where do I do that?

winter hollow
#

We should clean that list and flag them better

winter hollow
#

Those titles are not very clear πŸ˜„

simple jolt
#

@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:

mild veldt
#

@simple jolt do you have card tools installed?

civic stream
#

So I can no longer define groups in lovelace?

mild veldt
#

@polar kelp you should make card tools a npm

simple jolt
#

Yes I installed it under my www folder and added it to my lovelace file under resources.

winter hollow
#

@civic stream it will be fixed

civic stream
#

Groups?

winter hollow
#

toggling groups with the header toggle yeah

civic stream
#

Ok, nice! But what about groups in general, is there any way to define them like you did in groups.yaml?

mild veldt
#

For display? No. What’s your use case?

#

monster-card May be an option

polar kelp
#

Hm... why did that ever work? I updated card-tools, @simple jolt. Please try with the new version 297fcc7.

winter hollow
#
/** 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?

civic stream
#

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

winter hollow
#

you can not toggle a sensor right?

civic stream
#

No, but I can display them

#

In the UI

simple jolt
#

@polar kelp updating card tools worked. Thanks again.

mild veldt
#

@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

civic stream
#

But in my card for controlling the lights of whole rooms, how would I define them? Now I have the old groups..

mild veldt
#

Light group

mild veldt
#

Meh. I wouldn’t recommend that for a group of lights

winter hollow
#

no was for the sensors πŸ˜ƒ

mild veldt
#

Ah

civic stream
#

What do you mean, light group

#

Is there a group for all my lights in my bedroom?

#

(That I didn't create?)

mild veldt
winter hollow
#

That would give you one light for multiple lights

civic stream
#

Ok, thanks. Looks like exactly the same thing that I have in groups.yaml

mild veldt
#

But it’s not

winter hollow
#

gtr

civic stream
#

Is it still possible to divide the config or do I have to have everything in configuration.yaml?

winter hollow
#

lovelace doesn't work with configuration.yaml

mild veldt
#

If you wish to divide your Lovelace config you can specify yaml mode

civic stream
#

Uh, ok..

#

not getting it

#

How does it not work with configuration.yaml

mild veldt
#

Backup

#

Are you talking about the light group?

#

Or actual Lovelace views/cards

civic stream
#

Both. I assume you can use the light groups when defining cards in lovelace?

mild veldt
#

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

civic stream
#

Yes, ok.

mild veldt
civic stream
#

But scenes and automations are still defined in scene.yaml and automations.yaml, or?

mild veldt
#

Nothing has changed besides the front end display

civic stream
#

Ok, glad to hear it πŸ˜ƒ

#

Well, the groups did, aparently πŸ˜›

mild veldt
#

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

civic stream
#

Alright

median otter
#

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

civic stream
#

Think I got the frontend confused with everything else

#

Or rather, not having a clear distinction between them, hence the confusion

tight canopy
#

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?

violet talon
#

@median otter I'm not getting that error

civic stream
#

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?

mild veldt
#

@tight canopy monster-card

indigo fossil
#

@median otter glad is not just me..

mild veldt
#

@civic stream they just move it up in your config. Use stacks if you want more layout control

median otter
#
    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

indigo fossil
#

same here

violet talon
#

looks like a custom card...

median otter
#

are custom cards in www loaded automatically?

mild veldt
#

No

median otter
#

well then I don't know how the error could be stemming from a custom card, since I am using 'auto' mode

civic stream
#

How do I reference my cards?

mild veldt
#

@civic stream you’re going to have to expand on that question

#

@median otter I can’t replicate. Were you previously on Lovelace?

median otter
#

yup

#

I upgraded from 0.83 or something

civic stream
#

I thought I could reference the history graph card I already configured in my vertical stack

mild veldt
#

Tried clearing cache?

#

@civic stream no. We hope to have a copy function in a future release

civic stream
#

Cant get the history graph card to work when I put it in the vertical stack

#

The same config

mild veldt
#

Check your indents and the examples in the docs

vapid field
#

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 ?

civic stream
#

docs don't look like the preconfigured text in the UI-editor..

#

no dash before type: for example

mild veldt
#

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

median otter
#

@mild veldt yeah I cleared cache/all application data in the browser

civic stream
#

Got the history graph in the vertical stack, but the name of the graph does not show?

vapid field
#

@mild veldt what do you mean ? because both devices are at home, there are not shown on the map ?

mild veldt
#

Correct

#

Devices at home are not shown

scenic lantern
#

Anyone else having issues with their cameras loading in Lovelace?

mild veldt
#

Should add that to the docs. It’s in the panel docs

vapid field
#

is there a way to force event if at home ?

raven nacelle
#

@scenic lantern You mean when you click the camera cards?

scenic lantern
#

Yeah

mild veldt
#

@vapid field event?

raven nacelle
#

I have experienced that the camera does not load

#

sometimes

#

when you click on the card

vapid field
#

yeah it's obvious on this page ^^

#

even*

scenic lantern
#

Yeah can't get any of mine to load on 2 computers or my phone.

mild veldt
#

@vapid field not at this time

raven nacelle
vapid field
#

@mild veldt ok ! thx

raven nacelle
#

It used to work....not sure what went wrong

scenic lantern
#

@raven nacelle maybe, didn't have the issue yesterday though.

raven nacelle
#

this issue has been there for a while. I did not experience it initially, but have experienced it off late

mild veldt
#

You could downgrade to be sure

raven nacelle
#

@scenic lantern that would be a good test to rule out that it is not LL related

scenic lantern
#

@mild veldt true I try that.

#

I'll

raven nacelle
#

weirdly enough, I am using Synology cameras and I am not even sure if it is FFMPEG related

scenic lantern
#

@raven nacelle @mild veldt false alarm. Looks like my Synology locked up my non-synology cameras are working.

raven nacelle
#

ok...I am also experiencing with Synology. What do you mean by locked up?

vapid field
#

@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 ?

raven nacelle
#

@scenic lantern What do you mean by locked up?

scenic lantern
#

@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

mild veldt
#

@vapid field need lat/lon if that’s what you mean

vapid field
#

@mild veldt it's in it

mild veldt
#

You have the entities specified?

vapid field
#

device_tracker:

  • platform: mqtt
    devices:
    yann_pixel: /yann/android/pixel/location
    perrine_pixel3: /perrine/android/pixel3/location
winter hollow
#

No, in Lovelace at the map card

vapid field
#
  • type: map
    entities:
    - device_tracker.yann_pixel
    - device_tracker.perrine_pixel3
winter hollow
#

~format

kind shellBOT
#
:information_source:
Format Code:

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

vapid field
#

yep... i was reading it πŸ˜ƒ

#
        entities:
          - device_tracker.yann_pixel
          - device_tracker.perrine_pixel3```
winter hollow
#

Looks good

vapid field
#

i send the long/lat with mqtt

winter hollow
#

You checked the states for those entities?

vapid field
#

device_tracker.yann_pixel
state: 48.83502293,2.29956203
entity_picture: /local/yann.jpg
source_type: gps
friendly_name: yann pixel

#

seems ok

winter hollow
#

Nope

#

The latitude and longitude should be attributes

vapid field
#

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 ?

winter hollow
#

Not sure how that works with device trackers

raven nacelle
#

@vapid field Please use this channel for LL discussion only....for generic HA discussion use #330944238910963714

vapid field
#

yep... now i know where is the problem

#

thx guys

dreamy tendon
#

can I make one entity in a card conditional?

winter hollow
#

Like a conditional row? Not in official, might be a custom for it...

dreamy tendon
#

yeah

#

okay. I was thinking a media_player that would only show up in the card if needed

winter hollow
#

It would be possible in official I guess, with some hacking

polar kelp
#

You’re thinking hui-entity-row inside hui-conditional-card inside entities?

#

@dreamy tendon look up entity-filter

dreamy tendon
#

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

polar kelp
#

It’s in the side bar in the lovelace docs

#

A card

winter hollow
#

Yeah, that’s what I was thinking @polar kelp

dreamy tendon
#

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

polar kelp
#

Then I’d recommend the most common entry point into the world of plugins: monster-card

dreamy tendon
#

okay, I'll take a look

#

can I have a custom entity (mini-media-player) inside a custom monster-card? πŸ˜„

polar kelp
#

No. But I’m thinking of a replacement where tht would work.

vapid field
#

Sorry guys, but I have a stupid question to make...

dreamy tendon
#

alright, thanks

civic stream
#

Is it possible to have a card take up more horizontal space than one third?

vapid field
#

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?

subtle rune
#

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

carmine radish
#

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?

mossy otter
#

@carmine radish have you looked in to conditional cards?

violet talon
#

the default conditional card does state or not_state

#

it doesn't do less than as far as I can tell

carmine radish
#

@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

mossy otter
#

ah yes, it seems it's a bit restrictive

violet talon
#

how about monster card? that has a when

mossy otter
#

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

mossy otter
#

monster-card is also great!

carmine radish
#

Two good ideas! Thanks, will try them πŸ˜ƒ

vapid field
#

@subtle rune thank you...

violet talon
#

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

carmine radish
#

Thanks!

mild veldt
supple raft
#

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.

raven nacelle
#

@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

winter hollow
#

You have that entity in your groups probably

supple raft
#

Yes, they are in my groups.yaml

winter hollow
#

So you should fix it there or take control of Lovelace

supple raft
#

Guess I'm confused. Do I fix it in group.yaml or ui-lovelace.yaml?

winter hollow
#

You don’t have a ui-lovelace.yaml do you?

#

Have you configured Lovelace to be in yaml mode?

supple raft
#

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?

winter hollow
#

Well, the conversion was not necessary, and you can remove the ui-lovelace.yaml

#

It is auto generating you Lovelace layout for you now

mossy otter
#

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?

supple raft
#

Ok.

winter hollow
#

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

mild veldt
#

too many options...

supple raft
#

Ok. I've taken control. How do I let HA have control over lovelace again?

mild veldt
#

remove ./storage/lovelace

winter hollow
#

But that will give you the yellow warnings again

supple raft
#

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.

hallow niche
#

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
#

@hallow niche use the raw config editor

#

@supple raft bram already told you how

hallow niche
#

@mild veldt And where do I configure the resource for it ? I want to use Monster card

mild veldt
#

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

hallow niche
#

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
mild veldt
#

~format

kind shellBOT
#
:information_source:
Format Code:

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

mild veldt
#

state-card-aftership...?

hallow niche
#

I get: YAML Error: TypeError: Cannot read property 'startsWith' of undefined

winter hollow
#

Remove the -

mild veldt
#

can you go back and edit your config message to be formatted

winter hollow
#

When adding the card

#
    type: "custom:state-card-aftership-ll"
    entity: sensor.aftership_sensor```
hallow niche
#

@winter hollow Thanks. How do I add the resource ? Where do I put it ?

hallow niche
#
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
mild veldt
#

Can a mod please pin that wiki?

hallow niche
#

For this code I get and error.

split granite
#

Done @mild veldt

tribal linden
#

Is there any way to get a picture glance card to show the temperature from my Ecobee instead of the thermostat icon?

mild veldt
#

@hallow niche read that wiki I posted

#

@tribal linden no, you could make your own using picture-elements

tribal linden
#

oh good idea! Will give that a go, thank you!

mild veldt
#

@tribal linden that should be what you want

supple raft
#

Thanks for the help! I've the the invalid entities fixed.

winter hollow
#

@hallow niche indent is of

#

Of name in view

forest mica
#

can i delete my ui-lovelace file if im using storage mode

mild veldt
#

yes

#

you can delete in yaml mode as well (but I wouldn't advise it 😜 )

lavish lily
#

is there a way to change the color of a sensor graph line?

winter hollow
#

Yes, with Themes

lavish lily
#

@winter hollow thanks, I'll look into that

vapid field
#

How can I hide badges in the new Lovelave UI ?

winter hollow
#

Edit the view, they are in the second tab

vapid field
#

@winter hollow Not sure what you mean. I go to Configure UI and then..... ?

winter hollow
#

Click the pencil next to the view tab

vapid field
#

Yes thank you!!!

untold gyro
#

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?

split granite
#

Not really, and no

winter hollow
#

You can disable the front end component

split granite
#

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

untold gyro
#

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.

elder pendant
split granite
#

Probably some custom ones

mild veldt
#

@elder pendant I made a roku one, but really you just need buttons

elder pendant
#

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?

thorny latch
#

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...

split granite
#

How are you editing your Lovelace config and adding the custom cards?

thorny latch
#

I've tried via the Lovelace UI and also by setting it to yaml mode in configuration.yaml

jade bough
#

what custom card are you trying to use?

thorny latch
#

really any of them seem to behave the same. most recently I tried the aftership card, simply because it looked like a simple setup

split granite
#

Which mode are you using currently?

mild veldt
thorny latch
#

yaml mode

mild veldt
#

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

split granite
#

Did you put the card in www/ in your config folder?

#

Did you restart Home Assistant after creating www/?

mild veldt
jade bough
#

did you copy the card the correct way? using raw button from git?

thorny latch
#

yes, www is working for other resources (image files, etc)

elder pendant
#

Oh damn I could have been using this even before 0.86 because you're just using the roku local api directly. Looks good!

thorny latch
#

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

jade bough
#

how did you upload the file samba?

#

did you check the user permission to file?

#

and if its not root?

thorny latch
#

@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?

mild veldt
#

@elder pendant it has issues with CORS so going to remove all direct call in next release

jade bough
#

i'm not sure but should this (- type: custom:aftership-card) be in colons: - type: "custom:aftership-card"

thorny latch
#

I've tried that permutation without change, @jade bough

jade bough
#

maybe doublecheck the path, name of the file try to clear your browser cache and restart HA?

vapid field
thorny latch
#

I'll try that again, @jade bough

jade bough
#

check casesensitive names?

split granite
#

@vapid field If you're using YAML mode, you'll need the file still - see the Lovelace docs πŸ˜‰

vapid field
#

@split granite hello, yes I am using it. So i can delete lovelace mode yaml and edit it the easy way?

kindred dirge
#

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 😦

split granite
#

The UI editor is the easy way

kindred dirge
#

... 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

vapid field
#

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

split granite
#

There's automatic, UI editor, or YAML mode

vapid field
#

but can not start UI editor:The edit UI is not available when in YAML mode-

timid burrow
#

so remove the yaml mode entry from config

vapid field
#

@timid burrow ok will try

naive bear
#

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?

split granite
#

It is the default now, it'll just look like the old UI by default

winter hollow
#

or you should refresh πŸ˜ƒ

vapid field
#

@timid burrow deleted mode: yaml, enabled UI editor, copied data from ui-lovelace.yaml, everything fine, THANK YOU

kindred dirge
#

Oh boy this UI editor just made me excited to use Home Assistant again!

naive bear
#

I see that it is now. Just deciding now whether I should "take control" or leave automatic

vapid field
#

UI editor is great!!!

#

Take control

kindred dirge
#

And thanks to the Demo on the Hassio website I can cheat a little πŸ˜ƒ

naive bear
#

I'm fairly new and have read about custom Lovelace cards. Can these be used in the UI editor?

winter hollow
#

Yes

naive bear
#

Thanks

wary quest
#

how do I clean up the ui to start clean? My ui is showing all my entities

kindred dirge
#

I guess remove them by hand

winter hollow
#

replace your config in the raw editor with:

views: []
winter wasp
#

hey @polar kelp do your latest cards (ie, state-switch) have an option to auto update?

polar kelp
#

They work with the custom_updater

winter wasp
#

i'm an idiot, they showed up when i forced a refresh

kindred dirge
#

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

raven nacelle
#

Indeed....we need a way to display attributes on cards, instead of having to creating a separate sensor for every entity to be displayed

polar kelp
#

Hey! I felt like making a lovelace plugin that actually is visible for once, not just weird stuff that's hard to explain...

kindred dirge
#

So it's not yet possible?

polar kelp
kindred dirge
#

Cause I saw the FritzBox component, added it, then realized those are all just attributes

polar kelp
mild veldt
#

what are you doing @polar kelp? get back in your utility cave!

kindred dirge
#

Yeah but it's not a "fancy looking" solution πŸ˜ƒ

raven nacelle
#

something like that should be part of HA @winter wasp

polar kelp
#

sorry

raven nacelle
#

and that card is not as fancy 😜

polar kelp
kindred dirge
#

I guess I'll just wait for official attribute support πŸ˜‰

vapid field
kindred dirge
#

Or is there a way which makes it possible to make sensors out of attributes?

polar kelp
#

templates

raven nacelle
#

template sensors

kindred dirge
#

Will have to read into that

raven nacelle
polar kelp
#

The template components pretty much lets you make anything out of anything.

kindred dirge
#

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

mild veldt
#

Find examples to start

#

Then look at attributes available for your device

raven nacelle
mild veldt
#

King of templates

raven nacelle
mild veldt
#

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

kindred dirge
#

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

raven nacelle
#

Well, we can stick to our no-template for LL stance, but simple attributes would be nice to have.

mild veldt
#

@kindred dirge not really a LL question but check out Frencks config

kindred dirge
#

Ah whoops lol

mild veldt
raven nacelle
#

but I see your point, given that there is no cost of creating a template sensor, we can just use them

mild veldt
#

I think a template sensor UI editor would ease a lot of the pain

raven nacelle
#

and attributes can be used in other cards too....for example, humidity from thermostats on picture elements

polar kelp
#

@kindred dirge You can use a second word like sensor light_sensors: and sensor door_sensors:.

vapid field
#

Since Lovelave isn't using yaml anymore (default) how do you add components like homekit(and others) in Lovelave?

mild veldt
#

Lovelace is just the front end

#

All your components are still in configuration.yaml or integrations

vapid field
#
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 ?

mild veldt
#

You are misinterpreting it

vapid field
#

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
#

Pin?

#

To configure it?

#

Check your notifications

vapid field
#

@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.

cerulean scarab
#

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

thick dagger
#

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

timid burrow
#

@cerulean scarab did you save the card in raw mode from github?

cerulean scarab
#

@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.

timid burrow
#

it's not supposed to be a module by any chance?

#

instead of js?

#

you have to have /local BTW

cerulean scarab
timid burrow
#

eg..

  - url: /local/card-tools.js?v=297fcc
    type: js
cerulean scarab
#

thanks, will put /local back. so /local is a symlink of sorts to config/www ?

timid burrow
#

yes!

#

it is

mortal cape
#

❗

timid burrow
#

ouch!

cerulean scarab
#

cool and card-tools is config/www/card-tools.js on disk?

timid burrow
#

that hurt @mortal cape

mortal cape
#

I was just joining in

timid burrow
#

lol

mortal cape
#

it was not a slight

timid burrow
#

yeah it is @cerulean scarab

mortal cape
#

I started putting all mine in www/custom_cards but now I don't know if that was right

buoyant portal
#

my www folder is a mess!

mortal cape
#

Does the custom card updater expect them to be in a certain directory?

#

Or...the custom card update notifier card I mean

timid burrow
#

I don't think so - it just reads the version number

mortal cape
#

ok

timid burrow
#

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

mortal cape
#

@timid burrow ha, I remember trying to convince you that lovelace was worth using and here I am asking you questions now

timid burrow
#

and custom updater is happy - it's only reading the json from the repo and the version number from ui-lovelace.yaml

mortal cape
#

At the time you were all "nah I don't really have a use for that"

timid burrow
#

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

buoyant portal
#

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 πŸ˜‚

timid burrow
#

I have been using it for months now... only took a few custom cards to convert me

buoyant portal
#

I jumped in from the start and I'm really enjoying it. Might even move to the UI editor instead of yaml

timid burrow
#

it just depends on if the folder is hardwired @buoyant portal so just be careful

buoyant portal
#

Thanks

#

Some of the custom cards are amazing.

timid burrow
#

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

cerulean scarab
#

Hah, fixed it, had the file misnamed

#

moster != monster

buoyant portal
#

sounds like a good idea

timid burrow
#

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

buoyant portal
#

That's a shame

#

I stick to yaml because I know it. I feel comfortable in its embrace

timid burrow
#

it just reorganises everything

cerulean scarab
#

yea, and not having a working tab/shift tab function

timid burrow
#

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

mortal cape
#

I like the UI + raw editor just fine. Some awkwardness but it will improve over time I would expect

timid burrow
#

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

cerulean scarab
#

guessing there's challenges to letting users do raw config without over complicating the gui stuff

#

thinks that's why the reformatting happens

timid burrow
#

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...

mild veldt
#

@timid burrow what yaml editor are you talking about?

timid burrow
#

um.... the lovelace raw editor unless I am misunderstanding your question

mild veldt
#

"I don't understand why they didn't just write the raw editor to look like the yaml one"

timid burrow
#

oh... well the yaml editor... not the yaml editor just the data format

#

there is no yaml editor

#

I meant the data format

mild veldt
#

I don't follow? Do you mean that things get reorganized on save?

timid burrow
#

yes.. like it totally reorganises the order of everything when you save

mild veldt
#

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

timid burrow
#

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?

mild veldt
#

Vertical stack is a hard one

timid burrow
#

right! lol

#

that's why I am still cutting and pasting yaml

mild veldt
#

Hopefully we can come up with a good UI editor in time

timid burrow
#

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

mild veldt
#

For stacks, agreed. All in good time

#

should start seeing editors for custom cards as well

#

weather-card already has one

timid burrow
#

that's nice... the m.p.frankland one or a different one?

mild veldt
#

Brams

timid burrow
#

gotcha - he has done some awesome stuff. him and Thomas... so good

mild veldt
#

Lots of great custom devs

timid burrow
#

yeah. so true.

cerulean scarab
#

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

cloud osprey
#

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.

cerulean scarab
#

@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

cloud osprey
#

Yeah I saw that on the help page, I have be able to set this up on another glance card and it works, but not for this one.

#

i forgot how to isert screen shots on here

devout onyx
#

You need to declare it as an object.

#

so instead of