Thanks, but it’s missing most of the devices. If you don’t feel comfortable posting all that text here, you can dump it into pastebin.adamoutler.com, hit ctrl+s then copy the resulting link in here. I need to see the devices so I know what to target. Basically, I need to see the entire result of ls /dev
Ok. I see you have an mmc device partitioned into boot and data sections. I am familiar with this setup from development boards I have used. I believe it should be the same setup as on a normal HassOS. I’m not sure how it uses the partitions though. So I’m going to have you run some more commands to determine how that emmc is laid out.
Let’s see the eMMC structure by installing and running parted print. Parted will go away after a reboot or restarting the shell container so no need to uninstall.
apk add parted
parted /dev/mmcblk0 print
We’re looking for the Hass Boot partition as seen here.
Just to be sure, so we reduce the back-and-fourth, I want to inspect the partitions as well. Let’s mount all the potential partitions and then the next most likely partitions, then check the filesystems to determine where we need to place the files.
mkdir /tmp/b0 /tmp/b1 /tmp/1 /tmp/2
mount /dev/mmcblk0boot0 /tmp/b0
mount /dev/mmcblk0boot1 /tmp/b1
mount /dev/mmcblk0p1 /tmp/1
mount /dev/mmcblk0p2/tmp/2
ls -alR /tmp
I expect the last command to be quite lengthy so please use a pastebin. Errors in mounting are to be expected.
Just back to the Hassos on virtualbox on amd64 case, what info do you want?
1 Like
Can you do the same I asked of nappyjim? Starting with ls /dev above. After that if you have an sda1, get the parted /dev/sda print for me then mount sda1/sda2on tmp instead of mmcblk0p1/mmcblk0p2 and ls -alR
Do you need me to type it out in full? I can do it tomorrow at my computer, but not mobile.
Your device will be sda, sda1, and sda2 instead of mmcblk0, mmcblk0p1, and mmcblk0p2
I think I can do it, but its almost bedtime, so I’ll do it at a later time.
@adamoutler Plugged monitor into my HA blue and when I restart your add-on and check log, it says everything is good. But on the monitor, this pops up
/dev/sda1: Cant open blockdev
/dev/mmcblk0p1: Cant open blockdev
I will try the other things you asked
can you do this command again?
Looks like you added a tilde “~” at the end of that line and caused it to fail.
so
mkdir /tmp/1
mount /dev/mmcblk0p1 /tmp/1
ls -alr /tmp/1
HassOS says this Addon gets a security rating of 6
I did some research to figure out how the security ratings are applied and was able to game the system 
Thanks! You should be supported with v0.3.
when can we expect 0.3?
No go for me still…
- Uninstalled 0.2
- Installed add-on again as 0.3
- Used puttygen to generate public/private key combo
- Copied generated public key into configuration. Saved private key to filed on my computer.
- Restarted add-on. Below is my log
- Restarted HA.
- Pointed putty to the saved private key, tried to connect to HA on port 22222
1 Like
Wait, that’s different. Please update once again. I fixed it so it won’t throw that error on your system anymore. But I think that may be irrelevant. I can see you’re connecting so that means we created the file properly. I think you may have had a copy-paste error, using the wrong key to connect, maybe you need to reboot again, or something. You are connecting, which is impossible before a key is added. So the configurator added a key for sure.
I dont know what I can be doing wrong. If you can see an error in my process, let me know. Or else Im just gonna have to give up at this point and just chalk it up to the blue hardware not supporting SSH into port 22222
- Open puttygen, generate new pair
- Copy entire public key
- Paste key into configurtion
- Press save and it re-formats the key and asks me to restart add-on
- Check my log
6.Restart HA - In puttygen, save private key as test5.ppk
- Open putty, set address homeassistant.local: 22222
- Point Auth to test5.ppk
- Set auto login to root
- Press open
- Tries to connect, error.
1 Like
How are you restarting? There’s multiple levels.
- Configuration screen restart (Server)
- Restart core (supervisor)
- Restart Supervisor(supervisor)
- Reboot Host (supervisor)
- Hard Power Off (Physical)
4 or 5 should work.
I don’t use putty, but can we try linux instead? You have an ssh-capable linux if you installed the ssh and terminal app. Try this in the ssh terminal.
-
ssh-keygen(press enter when asked, use defaults, only enter responses) -
cat ~/.ssh/id_rsa.pubto get your key. It’s all one line and looks like this when copied properly.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDWO0Vp1MqMbcCZeXJArsZlBX6wvXPQ1zokAdFj1flVPu3E44KVkQlTakuxDGFiWzBoRhjs7GxciKPobTrbScpCaebfAjDjYBPF925Cm/AlCorQtfMDmCEXTcUdtQ4BMzvjOmo2GXyQ+TR3ACNyBj8Nc6ZmTeHbcsUki26UB0tYmhYNuL5zt3H/sVKgOkUfkyiKwNiyWA8FeLMOxvtncf9D20sIlVxpFL8GYkuCy5w3S3uLjsG/Y57nbwcMzAY+qD2v7BOlLXLJCyYRvhmeZG6oOMMXACaanL0Ix8XLvuWA1Z439HBUW9hurC8+M6VTnaAUXmn0VrbiCg7wD5pTqur9RTI6wuyL6DE6eGJ/7znbJ+++9HBSdfhuXLLFfhikNgE+2DyBwSI/hXs/EcZHcvJ/Y2jvSe2/OiuI+BVXRC0TM+MG8WnQ2K6UDPJo1H70DgPnIUabP9GUDKL+4dZ5F1mUFMWzZA4q16wYqG079nP4goQCY+yRphuMTPOwo6jWNLc= root@a0d7b954-ssh
or like this in a terminal. 
- copy the key from step 2 into HassOS SSH port 22222 Configurator
- restart the configurator
- Use Reboot Host method to restart.
- Upon restart, within the terminal app, type
ssh 127.0.0.1 -p22222
If it worked, then you were able to add your SSH key using this app and we need to troubleshoot putty. If it didn’t work then we need to troubleshoot the app.
1 Like
Edit: Nvm, just copied the key to a folder I can access from samba.
Rebooting host now
1 Like