Hi all,
I really appreciate all your efforts to show me a way to access the console. Still, we are going in circles here. I am not looking for a particular workaround for a specific task.
I try to explain it in detail. The GUI is absolutely great stuff. The appliance is generated for easy deployment and short installation time as well as to have everything in one place and matching everything. Have a perfect base for updates and so on. Good job, really!
Still, there will be some tasks which has to be performed on the command line. Take the 1-wire add-on as an example. Of course I can create a second VM to workaround the issue with direct database access. But there might or will be another add-on which requires console access for whatever task. So then the external database does not help. I will still need console access then.
So what I am looking for is how to get console access to perform the task needed for the 1-wire device. Which acts as an example!
The link from @ludeeus provides a lot of good information. It states:>
You can also access the Home Assistant Operating System via a directly connected keyboard and monitor, the console. To log in to the physical console the username is
root, with no password.
Indeed I tried this. This is the result:
So the topic might be misleading. I do not need the password. I can login as root without password. But I only have limited access through the ha console. I still can not do the steps needed.
Enabling ssh throug add-on does not allow me to leave the docker image. So not helpful, either.
From my point of view it is a great idea to completely remove shell access in order to have a more stable environment. In this case it was not thought through to the end as there are (and possibly will be) add-ons which require console access for whatever reason. This is why I called the ova “crippled” as it refuses to use add-on which require console access for configuration. Even if it is advanced configuration.
/KNEBB
BTW:
I just found the database add-on to do it for my particular issue. Still, the question for shell access remains.