As the restart is currently broken can your restart another way without SSH

As the title says, any other way to restart after you have charged your config file without using Putty?

Re Dave

You could create a command line switch and have it restart the service using sudo systemctl restart home-assistant.service. I thought about doing this but decided to wait until it was fixed

From what I am experiencing systemctl restart will also timeout. The only way to truly stop/restart is to use kill -9.

I recently started rebuilding my hassbian because I thought this problem was particular to my setup. Didn’t see any other postings in the forum discussing this.

Same issue here - that’s the error message I get when I restart / try to check my script with hass --script check_config:

Testing configuration at /home/homeassistant/.homeassistant
17-02-13 19:23:53 ERROR (MainThread) [homeassistant.loader] Unable to find component Configuration
Failed config
General Errors:
- Component not found: Configuration
Successful config (partial)

As I wrote in another thread - my config seems to work fine, it is in the right folder (I think) but the re-start process doesn’t find it.

If anybody has a solution on how to do this with a command line switch I’d be happy to use that instead of putty.

Tried to set it up myself but failed miserably :frowning:

switch:
  -  platform: command_line
     switches:
       hass_restart_switch:
         command_on: 'sudo systemctl restart home-assistant@homeassistant'

I’m probably thinking too simplistic here.
And being a Linux and HA noob doesn’t really help either.

Interesting. I haven’t had a problem restarting from an ssh session even after the GUI restart failed. I started with an all in one install on raspbian lite

sorry @heathpitts, misunderstanding here

I can re-start through an ssh session fine, np.

But a GUI re-start doesn’t work because the re-start process now includes the yaml-check. And because my fully functional configuration.yaml can’t be found it doesn’t execute.

I was meaning to respond to @sam

Think I have found the problem with my restarts. As I mentioned have been rebuilding hassbian from scratch.
Adding various parts of the configuration.yaml back one piece at a time. Was having no issue with restarts until I added

- platform: bluetooth_tracker

After that restarts fail/timeout. Remove that line and restarts work again.

Can anyone else confirm ?

Seeing the same here. Installed platform: bluetooth_tracker today. Didn’t notice any weird behavior so far in responsiveness, access through SSH, etc… Until my automatic restart at 3PM didn’t seem to work. I ended up doing a sudo reboot which also took more time than usual (like at least a minute) to start executing. But eventually everything comes up again and responsiveness in the GUI is as usual. Must say I am not home right now, so cannot say whether the devices actually respond or not. But at least from what I can see, nothing indicates that they don’t.

Running Hassbian on the latest RPI.

UPDATE: after adding track_new_devices: false, the restart of my HASS was as before again.

Just tested on 0.38.4

Adding

- platform: bluetooth_tracker

Causes the system to become slow ( command line lagg ) and restarts to fail.

Adding

track_new_devices: false

Improves things a lot - ( less command line lagg but still some detected )

Restart still not right. Calling restart service responded faster but didn’t actually start the service properly. The original process id for hass was still showing in
sudo systemctl status -l [email protected]
but the service didn’t actually come back online. Had to kill it with
kill -9
then restart it using
sudo systemctl start [email protected].

I feel there is still an issue with using the bluetooth module so am going to remove it for now.

UPDATE: after adding track_new_devices: false, the restart of my HASS was as before again.

This to the bluethooth device tracker ???