Hi I have upgraded home assitant to 0.84.1 and after thar I can´t see any devide in my home page. I also tried Lovelace UI and nothing works. I tried with the app and nothing shows.
Devices are up and ready, and automations are working normally, I can´t find any errer related at log file. These are my config files.
Configuation.yaml
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: *******************
longitude: *******************
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 0
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: UTC
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
#introduction:
# Enables the frontend
frontend:
ios:
google_assistant:
project_id: controlhogar-d9839
api_key: ***********************************
exposed_domains:
- switch
- light
- group
- scene
- cover
entity_config:
cover.fibaro_system_fgrm222_roller_shutter_controller_2_level_4:
name: PUERTA_PARCELA
http:
base_url: https://perahome.duckdns.org:19855
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
trusted_networks:
- 192.168.1.1
api_password: *******************
cors_allowed_origins:
- https://reformedreality.com
- http://reformedreality.com
# Enables configuration UI
config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true
recorder:
db_url: mysql://*******************:*******************@127.0.0.1/homeassistant?charset=utf8
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time
history:
# View all events in a logbook
logbook:
logger:
default: critical
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Homekit
homekit:
auto_start: true
# Sensors
sensor:
# Weather prediction
- platform: yr
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
I tried, but still doesn´t work. Before the upgrade I was able to see all devices in home page, I have 70 components that are loaded… This is the info screen:
Home Assistant
0.84.2
Path to configuration.yaml: /config
[70 Loaded Components](https://192.168.1.111:8123/dev-info#)
[Developed by a bunch of awesome people.](https://www.home-assistant.io/developers/credits/)
Published under the Apache 2.0 license
I copied and pasted your coed, but the problem continues. I really don´t need groups so I have commented the group line in configuration.yaml, and the home screen is still blank.
Wow, it’s now Feb 2020, one year after the above post and still no solution?
I have the same problem. I just started using HA, the latest version 0.105 and could see my cards in my main view. But as soon as I added to my config file:
lovelace:
mode: yaml
Bam, all my views are blank. Overview is blank. I refresh the page, clear the cache, try 4 different bowsers. I only see the tabs for my 4 different views that I coded.
Here is my configuration.yaml file and my ui-lovelace.yaml file.
When I go back to not using mode.yaml, I can’t put anything in my raw lovelace file. It won’t take any exclamation points so no !includes and no !secret. So unusable!!
Even with a super simple ui-lovelace file it won’t work.
The “problem” you have is nothing to do with what was reported in this thread and I have no doubt that their issue is resolved by now.
If you take over your configuration by using yaml mode the auto generated view does not appear. It’s the way it works. If you don’t like that file a feature request.