Frontend Doesn't Load 8 of 10 Restarts (Samba Share A-OK)

I’m about a month in to configuring HA. It’s doing a great job and I have high hopes for getting it to a point where it’s doing exactly what I want.

However, I’m having some kind of an issue that I can’t resolve. It’s similar to this issue: How to connect? Web interface, SSH and Samba not working!, but different enough that I thought it appropriate to post separately.

What’s happening is that the frontend will not load on 8 of 10 reboots (estimated), which has been very, very frustrating as I’ve been adding configurations and regularly updating, both requiring a full system restart. I always make sure the configuration is valid before rebooting. I’ve even rebuilt the entire system twice with the same results.

Here are the details:

Hardware: Raspberry Pi 3 Model B, CanaKit 5V 2.5A Raspberry Pi 3 B+ Power Supply / Adapter, Samsung 64GB 100MB/s (U3) MicroSDXC card, all within the SB Components Raspberry Pi 3 Model B+ Transparent Case.

Software: Hassio (config at bottom of post)

I use Chrome and get a “This site can’t be reached” error, specifically: ERR_CONNECTION_REFUSED. Changing browsers does not help. Same issue using http://hassio.local:8123 or http://192.168.1.100:8123 (I have my router configured to give it the same IP every time). The times the frontend does load, I never have any additional problems (shutting off, automations not working, frontend not loading w/o a subsequent restart, etc.).

I have HA setup with Samba for file sharing with my Windows 10 machine and it always works. I always truly connect to the network and never have issues accessing via file share - the issue is only with the frontend loading.

From the home-assistant log in the config folder, I do not get any errors aside from a setup delay and the occasional chromecast issue, both issues I see just as often when the frontend does load. Example from today:

2018-07-08 06:08:20 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-07-08 06:08:53 ERROR (SyncWorker_2) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

Also worth noting, I have my system connected via Ethernet to a satellite of my Orbi mesh network system (1 main router, 2 satellites in total) which works flawlessly with every other device at home.

I have rebuilt the entire system twice and am still encountering the same problem. Any thoughts? Config below FWIW (private details swapped with xxxxx), although this issue appears no matter what I have going on in there.

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: xxxxx
  longitude: xxxxx
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: xxxxx
  # 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: xxxxx
  # Customization file
  customize: !include customize.yaml

# Enables the frontend
frontend:

# Enables configuration UI
config:

http:
  # Secrets are defined in the file secrets.yaml
  # api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

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

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

# Z-Wave
zwave:
  usb_path: /dev/ttyACM0

# Includes
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

# Google Cast
cast:

# Hue Bridges
hue:
  bridges:
    - host: 192.168.1.101
      allow_unreachable: true

# Insteon Hub (local)
insteon_local:
  host: 192.168.1.102
  username: xxxxx
  password: xxxxx
  timeout: 10
  port: 25105

# Orbi Mesh Network
# Google Maps Location Sharing
device_tracker:
  - platform: netgear
    host: 192.168.1.1
    username: admin
    port: 80
    password: xxxxx
  - platform: google_maps
    username: xxxxx
    password: xxxxx

# IFTTT Integration (xxxxx)
ifttt:
  key: xxxxx

# Pushover Notification (xxxxx)
notify:
  - name: pushover
    platform: pushover
    api_key: xxxxx
    user_key: xxxxx

# Darksky Weather (xxxxx)
sensor:
  - platform: darksky
    api_key: xxxxx
    monitored_conditions:
      - summary
      - temperature
      - apparent_temperature
      - ozone
      - uv_index

# Circadian Light Sensor
  - platform: template
    sensors:
      length_of_day_factor:
        friendly_name: 'length of day factor for circadian light calculation'
        value_template: >
          {% if is_state('sun.sun' , 'above_horizon') %}
            {% set daylength = ((as_timestamp(states.sun.sun.attributes.next_setting) - as_timestamp(states.sun.sun.attributes.next_rising)) / 3600) + 24 %}
              {{ (daylength*-0.0063616)+0.11131 }}
          {% endif %}

  - platform: template
    sensors:
      farbtemp:
        friendly_name: 'circadian light - color temperature'
        unit_of_measurement: 'mired'
        value_template: >
          {% if is_state('sun.sun' , 'above_horizon') %}
            {{ ((states.sensor.length_of_day_factor.state | round (5))*((states.sun.sun.attributes.azimuth)-180)**2 + 175) | int }}
          {% elif (as_timestamp(states.sun.sun.attributes.next_dusk)) - (as_timestamp(states.sun.sun.attributes.next_setting)) < 0 or (as_timestamp(states.sun.sun.attributes.next_rising)) - (as_timestamp(states.sun.sun.attributes.next_dawn)) < 0 %}
            350
          {% else %}
            390
          {% endif %}

# Tracking zones
zone:
  - name: School
    latitude: xxxxx
    longitude: xxxxx
    radius: 175
    icon: mdi:school

  - name: Home
    latitude: xxxxx
    longitude: xxxxx
    radius: 40
    icon: mdi:home

Do you have Pi-Hole installed? Try rebooting via SSH (hassio host reboot)

Nope, no Pi-Hole. I haven’t tried connecting via SSH but will do that and then reboot that way.

I’m connecting via the SSH command in Windows 10 and it’s telling me “connection refused” at the default port (22) as well as 8123. Haven’t done this in YEARS so if I’m doing something wrong, please let me know. Executing like this:

ssh 192.168.1.100

TYIA!

I am using Putty with public key authentication.
Something I noticed is that I used to get this error when the dabatase started getting big, and it used to take way much longer on every reboot and I would get the same error until it finished loading sometimes up to 20-25min.
Also having Pi-Hole installed would cause issues loading the frontend and would break up the internet connection on my Hassio if I hadn’t set up a static for it.

1 Like

My database is only at 2 MB so that’s probably not my issue.

I just restarted the Orbi satellite I have my Raspberry Pi connected to (without restarting or doing anything to the Pi) and I can now connect to the frontend. So I think there’s an issue with the Orbi + the Hassio or Pi or HA system. I’ll keep fiddling but if anyone else has any ideas, I’m all ears.