Need to enter HASS every time I want to look at the GUI

Hi there,

Does anyone know how to debug why I continuously have to enter the command HASS when I want to look at the GUI? If I change from one network in my house on my phone then back some time later I simply get a error connection refused.

I’m running RPI Jessie. Played around with ufw allow 8234/TCP command but it doesn’t appear to have helped.

Posting on phone so will get the logs and repost later but maybe someone else had the same issue and knows how to fix. Don’t want to invest in anything further until I know this is fixed :frowning:
Thanks in advance

Hmm, I hope that I understand you right. You are starting Home Assistant over a connection from your phone to your Raspberry Pi and then want to access the frontend. If so, you need to use a multiplexer like screen or tmux, launch hass inside a session and detach the session. Otherwise if the session (and so, all running tools) is killed due to switching your network.

BTW, Home Assistant uses 8123 by default.

Thanks lots for the reply. Sorry I was writing that on the phone from work so probably didn’t come across well.

I can take last night as an example. Before I went to bed I entered ‘HASS’ to start the service from my laptop on terminal. Opened the UI and it appeared with no issue on port 8123. When I look this morning from the same computer it tells me connection refused.

I copied the logs but are two instances of this running at the same time?

PS. Don’t mind the taklampa TV entry in tellstick. Is a dummy one. Thanks again

Config directory: /home/pi/.homeassistant
WARNING:homeassistant.bootstrap:Colorlog package not found, console coloring disabled
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=turn_off, domain=homeassistant>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=turn_on, domain=homeassistant>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=toggle, domain=homeassistant>
INFO:homeassistant.bootstrap:Home Assistant core initialized
INFO:homeassistant.loader:Loaded logbook from homeassistant.components.logbook
INFO:homeassistant.loader:Loaded recorder from homeassistant.components.recorder
INFO:homeassistant.loader:Loaded http from homeassistant.components.http
INFO:homeassistant.loader:Loaded switch from homeassistant.components.switch
INFO:homeassistant.loader:Loaded device_tracker from homeassistant.components.device_tracker
INFO:homeassistant.loader:Loaded zone from homeassistant.components.zone
INFO:homeassistant.loader:Loaded conversation from homeassistant.components.conversation
INFO:homeassistant.loader:Loaded history from homeassistant.components.history
INFO:homeassistant.loader:Loaded updater from homeassistant.components.updater
INFO:homeassistant.loader:Loaded sun from homeassistant.components.sun
INFO:homeassistant.loader:Loaded frontend from homeassistant.components.frontend
INFO:homeassistant.loader:Loaded api from homeassistant.components.api
INFO:homeassistant.loader:Loaded tellstick from homeassistant.components.tellstick
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=recorder>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=http>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=log, domain=logbook>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=logbook>
INFO:homeassistant.loader:Loaded switch.tellstick from homeassistant.components.switch.tellstick
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=turn_off, domain=switch>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=turn_on, domain=switch>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=toggle, domain=switch>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=switch>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=zone.home, new_state=<state zone.home=zoning; icon=mdi:home, friendly_name=Home, longitude=-6xxxxxxx5, hidden=True, radius=100, latitude=5xxxxxx @ 08:22:55 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=zone>
INFO:homeassistant.loader:Loaded device_tracker.owntracks from homeassistant.components.device_tracker.owntracks
INFO:homeassistant.loader:Loaded mqtt from homeassistant.components.mqtt
INFO:homeassistant.loader:Loaded mqtt.server from homeassistant.components.mqtt.server
INFO:hbmqtt.broker:Listener 'ws-1' bind to 0.0.0.0:8080 (max_connecionts=-1)
INFO:hbmqtt.broker:Listener 'default' bind to 0.0.0.0:1883 (max_connecionts=-1)
INFO:hbmqtt.broker:Listener 'default': 1 connections acquired
INFO:hbmqtt.broker:Connection from 127.0.0.1:47843 on listener 'default'
WARNING:hbmqtt.broker:Delete session : session paho/35AA0xxxxx77A762532 doesn't exist
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=publish, domain=mqtt>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=mqtt>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=group.all_devices, new_state=<state group.all_devices=unknown; entity_id=(), hidden=True, order=0, auto=True, friendly_name=all devices @ 08:23:02 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=see, domain=device_tracker>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=device_tracker>
/home/pi/.homeassistant/lib/fuzzywuzzy/fuzz.py:33: UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning
  warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=process, domain=conversation>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=conversation>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=history>
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): pypi.python.org
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=updater>
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): maps.googleapis.com
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sun.sun, new_state=<state sun.sun=above_horizon; next_setting=19:11:59 07-04-2016, friendly_name=Sun, elevation=xxxx01, next_rising=05:39:57 08-04-2016 @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=sun>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=api>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=frontend>
INFO:homeassistant.components.tellstick:discovered 4 new switch devices
INFO:homeassistant.core:Bus:Handling <Event platform_discovered[L]: discovered=devices=[1, 3, 4, 5], config=1, service=tellstick.switches>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=switch.vardagsrum_taklampa_tv, new_state=<state switch.vardagsrum_taklampa_tv=off; friendly_name=Vardagsrum taklampa TV, assumed_state=True @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=tellstick>
INFO:homeassistant.core:Starting Home Assistant (16 threads)
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=switch.kitchen_plug_tv, new_state=<state switch.kitchen_plug_tv=on; friendly_name=Kitchen Plug TV, assumed_state=True @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event homeassistant_start[L]>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=stop, domain=homeassistant>
INFO:homeassistant.core:Timer:starting
INFO:homeassistant.components.http:Starting web interface at http://0.0.0.0:8123
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: service=restart, domain=homeassistant>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=switch.kitchen_plug_apple_charger, new_state=<state switch.kitchen_plug_apple_charger=off; friendly_name=Kitchen Plug Apple Charger, assumed_state=True @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=switch.kitchen_plug_microwave, new_state=<state switch.kitchen_plug_microwave=on; friendly_name=Kitchen Plug Microwave, assumed_state=True @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=group.all_switches, new_state=<state group.all_switches=unknown; entity_id=[], hidden=True, order=1, auto=True, friendly_name=all switches @ 08:23:04 07-04-2016>, old_state=None>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=group.all_switches, new_state=None, old_state=<state group.all_switches=unknown; entity_id=[], hidden=True, order=1, auto=True, friendly_name=all switches @ 08:23:04 07-04-2016>>
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=group.all_switches, new_state=<state group.all_switches=on; order=1, auto=True, friendly_name=all switches, entity_id=('switch.kitchen_plug_microwave', 'switch.vardagsrum_taklampa_tv', 'switch.kitchen_plug_apple_charger', 'switch.kitchen_plug_tv'), hidden=True, assumed_state=True @ 08:23:04 07-04-2016>, old_state=None>
WARNING:homeassistant.components.recorder:Found unfinished sessions

When you say you enter HASS from your laptop, are you using an SSH session into your pi? If so what’s happening is your running the server in that session, so when the session times out the Home Assistant server dies. If you want it to run continuously the best way is to follow the instructions,here, to have it start automatically as a daemon

Thanks very much. I had originally looked at this but my configs were all wrong. Copy and pasting from the internet when I should have looked at the paths relative to my setup. used this as a basis.

Thanks again. Feel free to mark as solved…

on another note I also resolved my mopidy service with the same proper path process