Can someone help. Many of the cards I am interested in have the toggle editor greyed out: What am I doing wrong here. I can’t find any useful guides or videos online. I upgraded from 85.1 to 86.3
I looked at the card page on the HA website bit it just gives you a overview of which each card is.
I’ve been successful in getting Lovelace configured for my needs. My recipe for success was to
Ignore “Config UI” and use “Raw config editor” to build what I wanted one step at a time.
I dont have a lovelace,yaml file so how do I access the raw editor. I want to know why toggle editor is greyed out for all the cool cards.
just create an empty ui-lovelace.yaml file. From what I can tell, the file simply acts as a flag. Mine started empty and is still empty … but my raw config looks like this:
views:
- path: status
title: Status
- path: weather
cards:
- type: weather-forecast
entity: weather.forecast
- entities:
- sensor.outdoor_temp
- sensor.next_sunrise
- sensor.next_sunset
- sensor.sun_angle
- sensor.us_air_pollution_level
- sensor.us_air_quality_index
show_header_toggle: false
type: entities
title: Current Conditions
title: Weather
- path: controls
cards:
- entities:
- light.bedroom_lamps
- light.chair_lamp
- light.couch_lamp
- light.desk_lamp
- light.office_lamp
type: entities
title: Lighting
- entities:
- light.shop_fan
type: entities
title: Other
title: Controls
- cards:
- entities:
- binary_sensor.boiler_power
- sensor.boiler_ckt1
- sensor.boiler_ckt2
- sensor.boiler_ckt3
show_header_toggle: false
type: entities
title: Boiler
title: Monitors
- cards:
- entities:
- sensor.google_wifi_status
- sensor.speedtest_download
- sensor.speedtest_upload
- sensor.speedtest_ping
- sensor.google_wifi_uptime
- sensor.google_wifi_last_restart
- sensor.google_wifi_current_version
- sensor.google_wifi_new_version
- sensor.google_wifi_local_ip
show_header_toggle: false
type: entities
title: WiFi
- entities:
- media_player.family_radio
- media_player.kitchen_radio
- media_player.wardrobe_radio
show_header_toggle: false
type: entities
title: Audio
- entities:
- media_player.exercise_tv
- media_player.family_tv
- media_player.kitchen_tv
- media_player.master_tv
- media_player.office_monitor
- media_player.office_tv
show_header_toggle: false
type: entities
title: Video
- entities:
- media_player.exercise_speaker
- media_player.family_room_speaker
- media_player.kitchen_display
- media_player.laundry_speaker
- media_player.master_speaker
- media_player.office_display
- media_player.shop_speaker
- media_player.wardrobe_speaker
show_header_toggle: false
path: chromecast
type: entities
title: Google Home
title: Google
title: Home
Correction: I dug around and found out that the ui-lovelace.yaml file does have a purpose beyond acting as a flag … Here’s a link to a file that is populated: You mgiht find the entire github repository interesting … I sure did: https://github.com/arsaboo/homeassistant-config/blob/master/ui-lovelace.yaml
So, it appears that you don’t need to populate the ui-lovelace.yaml file to get started with Lovelace, but it can be used to enhance the interface.
Well, if you look at the configuration variables of the picture glance, you’ll see that there’s a required variable entities.
If you add the propper options to the code editor it will change to the wanted card.
In the moment there is no UI editor for every card type.
The devs work hard on it.