Thank you for your prompt replies to my post. I will give your suggestions a try. It is good to know that the “config” directory corresponds to what Ben referred to as the /.homeassistant directory.
However, I have a bigger issue now that I cannot connect to my RPI using SSH after installing the SSH Shell. After I installed the SSH Shell I noticed I lost standard linux commands, such as those needed to help find and install a Aeotec Z-wave USB stick, such as “ls /dev/ttyACM*” along with other standard linux commands. The Shell seems to limit you to only a few hass.io related commands, but removes the ability to use the standard linux commands or to access my haadmin account. So I uninstalled the SSH Shell and tried to go back to using my old haadmin account that i used when I setup the RPI, but now I am completely locked out and and keep Server refused our key errors with a pop up dialog saying “No supported authentication methods available”. I am hoping I don’t have to start all over and re-image the SD Card in order to get back my standard SSH access, but it looks like that maybe the only alternative as I run this RPI completely headless. If anyone knows how to regain “standard” ssh commands after installing or uninstalling the SSH Shell or SSH Server (I tried both from the hass.io Store) I would appreciate the guidance.
Thanks again for the support of this forum. Without it I would be completely lost I think…
If you are running hass.io you don’t get regular shell access at all so I have no idea what you were doing before but the current behaviour is as you would expect for hass.io. You need to use addons and standard components provided with hassio. Zwave should be supported with no need to inatsll anything.
Hi David. Thanks for your reply. I setup SSH right after I installed Raspbian Stretch Lite in order to finish the installation and to install hass.io. I want to maintain the ability to issue standard Linux commands to update the Pi and perform normal system maintenance and configuration. With the SSH Shell available in the hass.io store it appears you loose most of the standard Linux commands and can only call hass.io commands which is a bit redundant since most of those commands can be called from the Configuration panel.
To fix the issue I ended up having to re-image my SD Card again with Raspbian Stretch Lite and then re-install hass.io. This time I did not install the SSH Shell or SSH Server from the hass.io store. However, as you noted now I cannot access the hass.io commands. So it would appear you have to choose to be either able to use SSH for hass.io or for Linux as there does appear to be away to use SSH for both.
This release is a big one! This release merges the SSH & the Terminal add-on into one pretty and useful piece of joy. For example:
You can now pick up your SSH session from the Web Terminal (or the other way around) with ease.
Tons of software has been upgraded, including the Web Terminal. See the changelog for a full list.
Upgrade notice
You will notice, the configuration has changed a lot.
Some previous set configuration options (like your authorized key) might not be migrated correctly by Hassio. And some new options regarding the Web Terminal are added.
If you do not want to use the Web Terminal, you can simply turn it off.
So check the configuration and make sure you have everything in it.
If it really became a mess on upgrading, I suggest to use the configuration “reset” button and work from that.
I could not access my system in Winscp - I was previously using Sudo-Su in Winscp under ResinOS but now under HassOS and this new addin I can’t had to change from sudo-su to bin/bash and I can connect and list files but I can’t edit anything or delete the database etc… Am I missing something in the settings?
If I use Putty I can delete files. I could use configurator but I just think I have something not configured correctly.
I am using the defaults (with ssh enabled and an authorized_keys migrated in from old snapshot)
I’m sure I just need to change a setting but what?
I did enable it but it wouldn’t login even when I changed to SFTP in Winscp… Would I still use bin/bash or go back to sudo-su? Also, there used to be an instruction to use root as user before - is that still a requirement…
ok… maybe not sudo su… sp leave it at bin/bash then?
OK I set sftp and username root… it seems to take a long time for everything to start in the addin… maybe I was too impatient before.
I get a warning to not use root… do I need root still for sftp? It mentions root under ssh in the docs… it’s not clear if I need it for sftp.
OK so that’s what I actually did and it worked… see my post above yours… It was slow starting - it looked like it was started but wouldn’t connect. I’d say it took 90 seconds or so till it was all started and working.
In general, it is not advised to use root, as most scans/attacks are targeted against that user. The use of SFTP also lowers the security a bit. So both lower security (don’t worry though).
This release adds the bluez packages to the add-on: Tools for Bluetooth.
It gives you the possibility to find and debug Bluetooth devices, straight out-of-the-box.
With the new version the cert file doesn’t seem to want to load
[2018/07/30 09:20:37:8212] ERR: lws_context_init_server_ssl: SSL_CTX_load_verify_locations unhappy
[2018/07/30 09:20:37:8892] ERR: Unable to load SSL Client certs file from (null) – client ssl isn’t going to work