Unit [email protected] not found

Configuration
1

I was just installing homebridge and homebridge-assistant and I decided to restart and I accidentally did this command:

“sudo nano sudo systemctl stop [email protected]”

instead of:

“sudo systemctl stop [email protected]”

I noticed it gave me some daemon refresh and now I can’t run it.

Edit:

So I can now no longer run the automated service and have to run it manually. Does anyone know of a fix? I would definitely appreciate it!

Edit 2:

I figured it out.

What I did:

cd /etc/systemd/system

sudo nano [email protected]

input this:

[Unit]
Description=Home Assistant
After=network.target

[Service]
Type=simple
User=%i
ExecStart=/srv/homeassistant/bin/hass -c "/home/homeassistant/.homeassistant"

[Install]
WantedBy=multi-user.target

saved it

did a daemon reload

sudo systemctl --system daemon-reload

then I could use this again:

sudo systemctl start home-assistant@homeassistant

13 Likes
2

Thanks! I’m not sure what happened, but i woke up this morning with this issue. I followed the steps you posted and I’m back up and running.

1 Like
3

I’m glad to hear that and I was able to help! :slight_smile:

4

Just installed PS4-Waker and got the same issue? Service completely removed…
anyways… followed your guide and all i can say… is Thanks buddy!

5

Installed npm and had the same issue, all fixed with your instructions. Thanks!

6

Thanks, my config file disappeared as well after an npm install (why???) to get dasher installed. Your instructions got my installation working again!

7

This actually helped me rebuild the home-assistant service after the installation of node-red broke the home-assistant service!

Thanks!

8

Thanks. Worked well for me today after I shut off my server and moved it into a different closet.

9

Happened to me on a fresh install of HA on top of Raspbian Lite. The iOS app had a tokenmanager error. After searching this forum found you!