Using the id: allows me to go directly to that tab on my web browser by addressing the id I specified. (i.e. a title tagged “id: calendar”).
http://pi3:8123/lovelace/calendar
Using the id: allows me to go directly to that tab on my web browser by addressing the id I specified. (i.e. a title tagged “id: calendar”).
http://pi3:8123/lovelace/calendar
Where i can find this ‘edit’ GUI in lovelace? I’m on 0.82.0
I finally got mine to work after stumbling across needing to add this to my configuration.yaml:
frontend:
javascript_version: latest
I already had that in my config as I needed it for iOS app. Always something to bite you huh?
I’ve gone back and edited them into english. That didn’t appear to break anything.
Unfortunately that didn’t work for me.
did you add the card to resources? did you restart HA?
yes and yes.
0.82? Check out my lovelace file here
It has to be something to do with haw you are showing the card…
also check… the config means that the migrate-card.js is in the /www/custom-lovelace/migrate-card/ folder… It’s somethjing simple like that I think
After including the java thing in configuration.yaml. I modified my ui-lovelace.yaml to have the resources as the first line and the card as the first entry to my home page. It looks like this:
resources:
- url: /local/custom-lovelace/migrate-card/migrate-card.js
type: module
views:
#######################################
# Home Page
#-|---|---|---|---|---|---|---|---|---|
- title: Home
id: home
icon: mdi:home
cards:
- type: custom:migrate-card
- id: weather_forcast
type: weather-forecast
entity: weather.smithville
- id: people_location
type: entities
...
@DavidFW1960, @Dixey Thanks to both of you. still not working though. I have this (with the .js
in the correct foldrer. I’m sure it is something simple that I don’t have right…
resources:
- url: /local/custom_ui/tracker-card.js?v=0.1.5
type: js
- url: /local/custom_ui/dark-sky-weather-card.js?v=1
type: js
- url: /local/custom_ui/mini-media-player-bundle.js?v=0.9.2
type: module
- url: /local/custom_ui/migrate-card/migrate-card.js
type: module
views:
- title: Migration
cards:
- type: custom:migrate-card
so you have a folder in custom_ui for migrate-card but the mini-media player is in the custom_ui fiolder… as is the tracker and dark-sky… so the migrate card is the only js file in it’s own folder under custom_ui?
Wow. How can I miss that???
thanks
Wow, thanks for that, exactly what I needed…
This should be builtin HA in the configuration section IMO…
I think it is going to be. In 0.84, Lovelace will be the default…
EDIT: The migrate card button for cards that have no ID is included in 0.83.
could this be the cause for my Lovelace not loading anymore and things getting mixed up?
please see: 0.84.1: Lovelace and regular HA mixed-up?
Don’t know where this is documented or how to change anything in the setup, but I was still using regular HA as default and point my ui-lovelace.yaml to my Lovelace files in a dedicated folder /config/lovelace… As of 84.1 Lovelace shows my regular files (which are the groups with view: yes)
Lovelace seems to have moved to .storage… Isn’t is reading the ui-lovelace.yaml any longer? Or, posed differently, how can I set it to use that again…
—Update–
found it:
lovelace:
mode: yaml
Hello,
Being a bit confused now.
Is it built-in now or not? Any need to include and download any script anymore?
Would like to add the IDs into my yaml file as there are no IDs so far.
Running hassbian and latest HA version 0.85.1
Thanks in advance
/Ralf
It doesn’t use ID’s anymore and in fact if you do use them Lovelace won’t load.