Hi,
I installed Home Assistant yesterday and I installed Hassio. After the installation I installed the SSH Server addOn for being able to login to my Pi and install the NoIP DUC.
I used Putty and connected to my RPi and tried to login to my RPi using “pi” and “raspberry” but: Access denied!
It is possible to login by using “root” and “password” to reach core-ssh:~#
What have I missed?
Thnx in advance for your efforts to help me!
The ssh password for Hass.io is root. But if I remember correctly, you need to set a password in SSH Server Add-on.
Under Options you can insert
{
"authorized_keys": [],
"password": "YOUR_PREFERRED_SSH_PASSWORD"
}
Or, for more security, create RSA Keys, and put the content of your public key in the authorized keys container. If you choose to do this, leave the password option blank.
By default, you will not be able to ssh into the resion OS, what you mention is SSH into the homeassistant docker.
If you want ssh access to the pi itself, read this: https://home-assistant.io/developers/hassio/debugging/
Is it okay/possible to use the Pi for other things using this login method without disturbing the Hassio installation?
You cannot use the PI for anything else unless it is running inside a Docker container/HASSIO add-on.
HASSIO is NOT a generalized OS, it is a very minimal ResinOS and you have NO tools available to you within the host OS.
This is because you installed HASS.IO. There is no pi user, there is no raspbian underneath. You are not going to be able to add things to ResinOS like you would a normal pi.
If you want to use your rpi for other things as well you might be better off installing Hassbian or checkout the available addons for Hassio
That was an answer that will give me some rest. It explains why it fails.
So there is an restriction in Hassio that prevents this login.
So in this case, with Hassio installed, it won’t be possible to use Noip’s DNS without an Add-on?
I very new to all this. I kind of figured Hassio was limited to itself, but not familiar with it’s underlying O/S or Docker. I understand Hassbian is available also, but from what I read it had some restrictions, thus I chose the Hassio route. Maybe I’m not understanding the differences. If I spin up Hassbian, will I still have the same interface in the UI that I see with Hassio? I assumed not. I thought I read that if you didn’t use Hassio, some of the add ons might not work.
You will not have a ‘HASSIO’ tab, but every other part of Home Assistant is the same.
There are no add-ons unless you are using HASSIO. Addons are nothing more than preconfigured docker containers that interact with home assistant. You can set the services and functionality they provide on your own without hassio.
Hassbian is a standard raspbian with Home Assistant pre-installed and running.
HASSIO is a docker system (think of it like an appliance, like your home router), that offers ‘plugins’ in the way of add-ons. There is nothing that you cannot accomplish with add-ons that are not capable of doing yourself, should you understand what you need and why. HASSIO will not give you access to the underlying OS in the same manner as hassbian. you have EXTREMELY limited functionality with hassio/resinOS
Thank you everyone, I get it now! What a great community!
I feel kind of silly for posting this question, but I’m having the same issue as Spokenberg. I’m running Hass.io on a Raspberry Pi 3 (No VM, no docker, no Raspbian). I also installed DuckDNS with Let’s Encrypt.
My Options under Hass.io SSH are:
{
“authorized_keys”: [],
“password”: “XXXXXXX”
}
I get the following errors (when trying to log into my Pi from a Mac Terminal
Permission denied, please try again. (i get this error 3 times)
[email protected]: Permission denied (publickey,password,keyboard-interactive).
Is the Let’s encrypt key expected in the Options? I’m sure I’m missing something very simple. Ayy help is appreciated.
If you’re running hassio, you’re running docker.
As expected. There is no ‘pi’ user on hassio.
@fabaff this is the kind of stuff we’ve been talking about
Lightbulb ! I got it.