-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shutdown and reboot commands broken in "Terminal & SSH" #2767
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I observe this issue with |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
When attempting to reboot my RPi via "Terminal & SSH" with a fresh install of Home Assistant OS, neither
shutdown
norreboot
works.What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Terminal & SSH
What is the version of the add-on?
9.6.1
Steps to reproduce the issue
haos_rpi4-64-9.3.img.xz
on a Raspberry Pi for this.whoami
and note that you are root, so restarting the host should be within your power.shutdown -r now
: No such file or directory bashio
/usr/local/bin/shutdown
and note that it seems to have Windows line terminations.reboot
parse error: Expected string key before : at line 1, column 4
andERROR: Unknown HTTP error occured
...
System Health information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: