Well done eagle eyes. I can only assume it was caused by a poorly time ^X. My bad. Thanks
The guide provided the following steps
To have Home Assistant start automatically at boot, enable the service.
$ sudo systemctl enable home-assistant@[your user]
To disable the automatic start, use this command.
$ sudo systemctl disable home-assistant@[your user]
To start Home Assistant now, use this command.
$ sudo systemctl start home-assistant@[your user]
So I did this:
klrock@orangepizero:~$ sudo systemctl enable [email protected]
Created symlink /etc/systemd/system/multi-user.target.wants/[email protected] â /etc/systemd/system/[email protected].
klrock@orangepizero:~$ sudo systemctl start [email protected]:~$ sudo systemctl --system daemon-reload
klrock@orangepizero:~$ sudo systemctl enable home-assistant@klrock
Failed to enable unit: Unit file [email protected] does not exist
klrock@orangepizero:~$ sudo systemctl enable home-assistant@klrock@orangepizero
Failed to enable unit: Unit file home-assistant@[email protected] does not exist.
Apparently I do not understand what is required for
home-assistant@[your user]
Why?
Your service is home assistant running as a home assistant user. Itâs not running as klrock.
homeassistant
itâs the user called homeassistant that you ran all those commands for and that you created the service for. Its the user that runs the service and the user that owns the venv and the config
That was the correct command, as evidenced by the reply you got in the terminalâŚ
Then you tried
Looks like you copy and pasted it from some guide or other and picked up an extra load of text, hence why it didnât work. What you wanted wasâŚ
sudo systemctl start [email protected]
If you look up at my original post with all the steps that got you this far, that is the command I typed.
All the other stuff you then went on to do, I have no idea where you got that from. Please please please donât keep running off to use other guides, just follow one set of instructions from start to finish and make sure that you follow each step correctly. If something doesnât work, double check that youâve done the step correctly and then come back here and paste the error.
Different guides may follow a completely different way of doing something that may be incompatible with the last one you tried. Hence why everyone is pointing you back towards your Linux books, so you can spot the difference
In any case, the enable command worked, so next time you start or reboot the device homeassistant will be running in the background, so long as something else youâve done since hasnât disabled it
After getting homeassistant installed and started, I did a small part of the configuration, then left it running two days while busy with other stuff. When I came back, the interface was still open but displayed âconnection lost, trying to reconnnectâ. I left it that way for a few hours and then closed the browser page and opened it again, but it has now been collecting data for several hours.
I was able to SSH into the Orange Pi Zero and attempted to start Samba found I need to learn a lot more before I can use it.
Still need to get the interface running again, but out of ideas now.
How did you install homeassistant?
Why did you create another thread with the same name as the one we were already working with you on?
I searched for the same name and could not find it, so I started a new one thinking it would be recognized. I apolgize if that created a problem.
I flashed my Orange Pi Zero with ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi. and executed the following list of commands provided generously by m> Social:
root@orangepizero:~# sudo apt-get install python3-pip python3-dev python3-venv
root@orangepizero:~# pip install awscli
root@orangepizero:~# apt install python-pip
root@orangepizero:~# sudo apt-get install build-essential libssl-dev libffi-dev python3-dev
root@orangepizero:~# pip3 install wheel
root@orangepizero:~# sudo pip3 install --upgrade virtualenv
root@orangepizero:~# sudo mkdir /srv/homeassistant
root@orangepizero:~# sudo useradd -rm homeassistant
root@orangepizero:~# sudo chown homeassistant:homeassistant /srv/homeassis
root@orangepizero:~# sudo usermod -aG dialout homeassistant
root@orangepizero:~# sudo su -s /bin/bash homeassistant
root@orangepizero:~# cd /srv
root@orangepizero:/srv# sudo chown homeassistant:homeassistant homeassistant
root@orangepizero:/srv# sudo su -s /bin/bash homeassistant
root@orangepizero:/source /srv/homeassistant/bin/activate
root@orangepizero:/pip3 install --upgrade wheel homeassistant
homeassistant@orangepizero:/srv$ cd /srv/homeassistant
homeassistant@orangepizero:/srv/homeassistant$ python3.6 -m venv .
homeassistant@orangepizero:/srv/homeassistant$ source bin/activate
(homeassistant) homeassistant@orangepizero:/srv/homeassistant$ pip3 install homeassistant
klrock@orangepizero:~$ sudo systemctl enable home-assistant@homeassistant
[sudo] password for klrock:
klrock@orangepizero:~$ sudo systemctl start home-assistant@homeassistant
klrock@orangepizero:~$
have you just tried restarting the service and looking at the logs to see if it fails?
Threads merged
First we would check if homeassistant is running, and whatâs going on.
From your privileged user (klrock in your case)
sudo systemctl status [email protected]
Tells you if it is running
journalctl -f -u [email protected]
Shows you what it is currently doing (or the last few updates in the log if itâs not doing anything)
Ctrl+c escapes you back to the command line.
If everything appears to be running correctly, itâs more likely a problem with the browser displaying the interface.
Step one with interface problems is always to clear the browser cache and refresh. Ctrl+f5 as a starter for 10, and clearing the actual cache from the settings if needed.
So it may have been interface problems. I just tried your suggestions from another PC and here are the results:
Welcome to ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi
System load: 0.00 0.00 0.00 Up time: 10:01 hours
Memory usage: 44 % of 240MB Swap usage: 6 % of 119Mb IP: 1 92.168.1.191
CPU temp: 39°C
Usage of /: 19% of 7.2G
[ General system configuration (beta): armbian-config ]
Last login: Fri Sep 21 02:44:11 2018 from 192.168.1.223
klrock@orangepizero:~$ sudo systemctl status [email protected] e
[sudo] password for klrock:
â [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; ena
Active: active (running) since Sat 2018-09-22 00:24:49 UTC; 11h ago
Main PID: 1042 (hass)
Tasks: 30 (limit: 400)
CGroup: /system.slice/system-home\x2dassistant.slice/home-assistant@homeassis
ââ1042 /srv/homeassistant/bin/python3.6 /srv/homeassistant/bin/hass -
Sep 22 11:54:30 orangepizero hass[1042]: 2018-09-22 11:54:30 INFO (MainThread) [
Sep 22 11:55:30 orangepizero hass[1042]: 2018-09-22 11:55:30 INFO (MainThread) [
Sep 22 11:56:30 orangepizero hass[1042]: 2018-09-22 11:56:30 INFO (MainThread) [
Sep 22 11:57:30 orangepizero hass[1042]: 2018-09-22 11:57:30 INFO (MainThread) [
Sep 22 11:58:30 orangepizero hass[1042]: 2018-09-22 11:58:30 INFO (MainThread) [
Sep 22 11:59:30 orangepizero hass[1042]: 2018-09-22 11:59:30 INFO (MainThread) [
Sep 22 12:00:30 orangepizero hass[1042]: 2018-09-22 12:00:30 INFO (MainThread) [
Sep 22 12:01:30 orangepizero hass[1042]: 2018-09-22 12:01:30 INFO (MainThread) [
Sep 22 12:02:30 orangepizero hass[1042]: 2018-09-22 12:02:30 INFO (MainThread) [
Sep 22 12:03:30 orangepizero hass[1042]: 2018-09-22 12:03:30 INFO (MainThread) [
lines 1-18/18 (END)
â [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-09-22 00:24:49 UTC; 11h ago
Main PID: 1042 (hass)
Tasks: 30 (limit: 400)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
ââ1042 /srv/homeassistant/bin/python3.6 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant
Sep 22 11:54:30 orangepizero hass[1042]: 2018-09-22 11:54:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:55:30 orangepizero hass[1042]: 2018-09-22 11:55:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:56:30 orangepizero hass[1042]: 2018-09-22 11:56:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:57:30 orangepizero hass[1042]: 2018-09-22 11:57:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:58:30 orangepizero hass[1042]: 2018-09-22 11:58:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:59:30 orangepizero hass[1042]: 2018-09-22 11:59:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:00:30 orangepizero hass[1042]: 2018-09-22 12:00:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:01:30 orangepizero hass[1042]: 2018-09-22 12:01:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:02:30 orangepizero hass[1042]: 2018-09-22 12:02:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:03:30 orangepizero hass[1042]: 2018-09-22 12:03:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
~
~
~
~
~
...skipping...
â [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-09-22 00:24:49 UTC; 11h ago
Main PID: 1042 (hass)
Tasks: 30 (limit: 400)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
ââ1042 /srv/homeassistant/bin/python3.6 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant
Sep 22 11:54:30 orangepizero hass[1042]: 2018-09-22 11:54:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:55:30 orangepizero hass[1042]: 2018-09-22 11:55:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:56:30 orangepizero hass[1042]: 2018-09-22 11:56:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:57:30 orangepizero hass[1042]: 2018-09-22 11:57:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:58:30 orangepizero hass[1042]: 2018-09-22 11:58:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:59:30 orangepizero hass[1042]: 2018-09-22 11:59:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:00:30 orangepizero hass[1042]: 2018-09-22 12:00:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:01:30 orangepizero hass[1042]: 2018-09-22 12:01:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:02:30 orangepizero hass[1042]: 2018-09-22 12:02:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:03:30 orangepizero hass[1042]: 2018-09-22 12:03:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
~
~
~
~
~
â [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-09-22 00:24:49 UTC; 11h ago
Main PID: 1042 (hass)
Tasks: 30 (limit: 400)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
ââ1042 /srv/homeassistant/bin/python3.6 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant
Sep 22 11:54:30 orangepizero hass[1042]: 2018-09-22 11:54:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:55:30 orangepizero hass[1042]: 2018-09-22 11:55:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:56:30 orangepizero hass[1042]: 2018-09-22 11:56:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:57:30 orangepizero hass[1042]: 2018-09-22 11:57:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:58:30 orangepizero hass[1042]: 2018-09-22 11:58:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 11:59:30 orangepizero hass[1042]: 2018-09-22 11:59:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:00:30 orangepizero hass[1042]: 2018-09-22 12:00:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:01:30 orangepizero hass[1042]: 2018-09-22 12:01:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:02:30 orangepizero hass[1042]: 2018-09-22 12:02:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
Sep 22 12:03:30 orangepizero hass[1042]: 2018-09-22 12:03:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]:
~
~
~
~
~
...skipping...
Certainly looks like itâs running from what youâve posted there
?
You tried to get to the GUI from another PC? Your results only show youâve connected to the SSH session.
So I just got back home and tried the GUI
192.168.1.191:8183
This site canât be reached
192.168.1.191 refused to connect.
ERR_CONNECTION_REFUSED
8183? Did you change your configuration yaml to listen on 8183?
Indeed.
Attention to detail is definitely a prerequisite for homeassistant
I had done the initial modifications of configuration.yaml previously and the GUI was working correctly. Just now I checked and it had been replaced by the default file. I will redo it, but am concerned as to why the first one was over ridden,
I am sure it is because you are blindly copying/pasting random commands in the console and not really understanding what it is you are doing each time. You have a config file somewhere, and your home assistant is looking at that config file. Did you move it/remove it in one of your random copy/paste sessions? Did you somehow tell Home Assistant a different location of the configuration? We donât know because your troubleshooting steps seem to be all over the place and not make any logical sense.
You need to remain focused, and attention to detail is crucial as @anon43302295 mentioned. If you donât know the details of what steps you are performing, we definitely donât know.
Work slowly, and methodically, through the installation, UNDERSTANDING each step of the way. When you come across an issue, donât just randomly copy/paste commands, learn what the error means first. Fix the error, and move along. Donât just assume that whatever command you copy/paste is going to magically fix it. Itâs YOUR system, YOU need to know whatâs going on.
Unless you are pointing your home assistant to a different config file location, or are trying to run it OUTSIDE of the python virtual environment, itâs not going to overwrite your config.