Replies: 7 comments 3 replies
-
Currently getty is started on serial (ttyS0) via the standard systemd flow, while tty1 (graphical console) is handled by a special service |
Beta Was this translation helpful? Give feedback.
-
OK, if is't impossible to set multiple default instances the single one will be enough.
instead of two completely useless things I'd like to have only one, but useful: ha-cli@.service on ttyS0. No ha-cli on tty0, no getty on ttyS0, only one ha-cli on ttyS0 |
Beta Was this translation helpful? Give feedback.
-
May I ask what is the use case to run ha-cli on graphical console? |
Beta Was this translation helpful? Give feedback.
-
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
Beta Was this translation helpful? Give feedback.
-
stale is not a reason to close issues |
Beta Was this translation helpful? Give feedback.
-
There are actually three ways to access the HAOS shell:
Now, only graphical console on tty0 actually starts the HA CLI shell. All other cases just the bare (Busybox ash) shell. That said, on all consoles the HA CLI is available via the Also note that the SSH/Web Terminal add-on doesn't give shell access to the OS directly, but a shell in a container. You do have access to the There are a few minor downsides to starting the HA CLI directly:
Now there is one major upside when starting the HA CLI directly: The HA banner is printed, with that users sees the IP addresses etc. without typing a command. Now this last argument here is the big differentiator, and the main reason things are the way they are right now: Being able to see the IP address without having to enter a command is especially helpful for devices which have only a screen attached (e.g. on a Raspberry Pi, where you might just opt to remove the keyboard normally). For the serial console this isn't really an argument, as typically you have input and output available when accessing a serial console.
You still can: Just use the commands with |
Beta Was this translation helpful? Give feedback.
-
This issues was mainly about qemu: I don't want to have video enabled on haos guest, but I want to have full log and cli. And right now serial in qemu only shows grub, kernel messages and useless |
Beta Was this translation helpful? Give feedback.
-
Describe the issue you are experiencing
I run HAOS from haos_ova-11.5.qcow2
On ttyS0 it starts it prints kernel log and starts agetty.
On tty1 it prints boot log and starts ha-cli.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
11.5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions