This happened to me numerous times in the past… and it juts magically went away after I tried and tried and tried (restarting… rebooting…)
This time around, it went down and I tried to start it back up…but it still didn’t get start up after doing all that for the last few days…
Attached is the logs, is there any PRO that could take a look and see what was wrong? I don’t see any thing obvious… but it got stuck on the last line and I even waited it out for 2 days… but nothing else starts up…
I do have several chromecasts and google home devices… but in my config, I don’t have any specific chromecast listing… as below - I tried to disable “discovery:” but it still got stuck at the same spot…
It’s been a while from the last time I messed with the configurations so I might have missed where the chromecast is listed.
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: !secret home_latitude
longitude: !secret home_longitude
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 118
# metric for Metric, imperial for Imperial
unit_system: imperial
# 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:
# Enables configuration UI
config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
# Uncomment this to add a password (recommended!)
# api_password: PASSWORD
# Uncomment this if you are using SSL or running in Docker etc
# base_url: example.duckdns.org:8123
base_url: nguyenha.duckdns.org
ssl_certificate: /etc/letsencrypt/live/nguyenha.duckdns.org/fullchain.pem
ssl_key: /etc/letsencrypt/live/nguyenha.duckdns.org/privkey.pem
trusted_networks:
- 127.0.0.1
- 192.168.1.1
# 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
# 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:
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Weather prediction
sensor: !include sensors.yaml
recorder:
purge_keep_days: 5
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
script: !include scripts.yaml
duckdns:
domain: nguyenha.duckdns.org
access_token: duck-access-token
mqtt:
broker: localhost
port: 1883
client_id: home-assistant-1
username: mqtt
password: !secret mqtt_password
protocol: 3.1
birth_message:
topic: 'hass/status'
payload: 'online'
qos: 1
retain: true
will_message:
topic: 'hass/status'
payload: 'offline'
qos: 1
retain: true
light:
- platform: group
name: Living Room Lights
entities:
- light.mqtt_livingroom_light_1
- light.mqtt_livingroom_light_2
- platform: mqtt
name: "MQTT Theater Room Light"
state_topic: "smartthings/Theater Room Dimmer/switch"
command_topic: "smartthings/Theater Room Dimmer/switch"
brightness_state_topic: "smartthings/Theater Room Dimmer/level"
brightness_command_topic: "smartthings/Theater Room Dimmer/level"
brightness_scale: 99
brightness_template: "{{ value }}"
qos: 0
payload_on: "on"
payload_off: "off"
retain: true
optimistic: false
- platform: mqtt
name: "MQTT Dinner Table Light"
state_topic: "smartthings/Dinner Table Light/switch"
command_topic: "smartthings/Dinner Table Light/switch"
brightness_state_topic: "smartthings/Dinner Table Light/level"
brightness_command_topic: "smartthings/Dinner Table Light/level"
brightness_scale: 99
brightness_template: "{{ value }}"
qos: 0
payload_on: "on"
payload_off: "off"
retain: true
optimistic: false
- platform: mqtt
name: "MQTT Hallway to Garage Light"
state_topic: "smartthings/Hallway To Garage/switch"
command_topic: "smartthings/Hallway To Garage/switch"
qos: 0
payload_on: "on"
payload_off: "off"
retain: true
optimistic: false
- platform: mqtt
name: "MQTT Livingroom Light 1"
state_topic: "smartthings/Living Room Light 1/switch"
command_topic: "smartthings/Living Room Light 1/switch"
qos: 0
payload_on: "on"
payload_off: "off"
retain: true
optimistic: false
- platform: mqtt
name: "MQTT Livingroom Light 2"
state_topic: "smartthings/Living Room Light 2/switch"
command_topic: "smartthings/Living Room Light 2/switch"
qos: 0
payload_on: "on"
payload_off: "off"
retain: true
optimistic: false
ifttt:
key: !secret ifttt_api_key
notify:
- platform: telegram
name: Vu_Telegram
chat_id: 467266232
- platform: html5
name: html5
gcm_api_key: !secret notify_html5_gcm_api_key
gcm_sender_id: !secret notify_html5_gcm_sender_id
- platform: joaoapps_join
device_id: !secret join_vu_device_id
name: GalaxyS7
api_key: !secret join_vu_device_api_key
joaoapps_join:
- name: GalaxyS7
device_id: group.GalaxyS7
api_key: !secret join_vu_device_api_key
device_tracker:
- platform: nmap_tracker
hosts:
- 192.168.1.113
- 192.168.1.112
- 192.168.1.115
- 192.168.1.191
home_interval: 1
consider_home: 180
scan_options: " --privileged -sP "
- platform: owntracks
max_gps_accuracy: 200
zone: !include zones.yaml
input_boolean:
nap_time:
name: Nap Time
initial: off
living_room_light_automation:
name: Living Room Light Automation
initial: off
vacation_time_mode:
name: Vacation Time Mode
initial: off
input_select:
trash_day:
options:
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
initial: Wed
# vacation:
# options:
# - Yes
# - No
# initial: No
# living_room_light_automation:
# options:
# - Yes
# - No
# initial: No
scene:
- name: theater light normal
entities:
light.mqtt_theater_room_light:
state: on
transition: 2
brightness: 75
- name: theater light dim
entities:
light.mqtt_theater_room_light:
state: on
transition: 2
brightness: 20
- name: theater light off
entities:
light.mqtt_theater_room_light:
state: off
transition: 2
automation: !include automations.yaml
ecobee:
api_key: !secret ecobee_api_key
binary_sensor:
- platform: workday
name: Work Days
country: US
state: TX
workdays: [mon, tue, wed, thu, fri]
- platform: workday
name: Holidays
country: US
state: TX
workdays: [holiday]
excludes: []
- platform: workday
name: Weekends
country: US
state: TX
workdays: [sat, sun]
excludes: [mon, tue, wed, thu, fri, holiday]
switch:
- platform: template
switches:
theater:
value_template: "{% if is_state('remote.theater_room', 'on') %}on{% else %}off{% endif %}"
turn_on:
service: remote.turn_on
entity_id: remote.theater_room
turn_off:
service: remote.turn_off
entity_id: remote.theater_room
telegram_bot:
- platform: polling
api_key: !secret telegram_api_key
allowed_chat_ids:
- 467266232
nest:
client_id: c16f885a-0d4f-4c58-a68e-c1b8cde2c1ef
client_secret: !secret nest_client_secret
since you had discovery enable before you might have to go into the core.entity_registry and manually remove the entries for those devices. it’s stored in config/.storage.
Thank you. I didn’t know about that. So I tried to clean that up…and restarted it… it seems to be ok… as I see the log is moving and my device tracker seems do nmap scan successfully… but… the UI doesn’t come up… any pointer?
2019-02-28 16:41:11 INFO (Thread-21) [homeassistant.components.device_tracker.nmap_tracker] Scanning...
2019-02-28 16:41:11 INFO (Thread-21) [homeassistant.components.device_tracker.nmap_tracker] nmap scan successful
It looks like you’ve got several errors in the log - plex, telegram, some discovered media players, etc. (I thought you said above you disabled discovery…)
most errors will stop the UI from loading so you will need to fix those errors before things will run.
I thought I did… but I tried again… and this time, I verified that my “discovery” is disabled in the config yaml. but the UI still not loads even when there was no error in the logs…
There are still three errors in that log file you need to try to resolve. One for Plex, one for an automation that needs to be fixed and one for Owntracks.
If there are ANY errors in the log it’s possible for that to stop the frontend from loading because HA may not actually be running.
If there are ANY errors in the log then you need to fix them. Then when you are completely error free then come back here and we can try the next thing if it’s still not working.
Plus there are several warnings for “extra keys” that won’t prevent the UI from loading but you still need to fix those or it will break things in the near future.
OK, i recommend getting it set back up to run automatically. you can still stop, start and restart manually from the command line even if you have it set to autostart. I don’t see any benefit to not having it autostart.
OK, let me know when you get the system set up to allow HA to autostart. And what the status of both the “status” command and the contents of the home-assistant.log file is.
In the meantime, I would try to also uncomment the api_password in the http: section and then change that to a !secret password. That way you have another means of logging in to HA in case the problem is with your auth log in credentials.
You also might want to redact your duckdns domain name from your post above.
as I do have it auto start before…