Glad you got it fixed (you are not the only one who has done that I’m sure)!
For people who are still struggling to do it via Linux:
hassos-boot is visible in Windows because it’s FAT. Windows doesn’t show anything it doesn’t support.
On Linux (and in your case Ubuntu?) It doesn’t automount 4 out of 8 paritions on the SD card. Why, I don’t know, there is probably an explanation, but to fix it you have to mount hassos-boot (which in your case is /dev/sdc) as FAT as follows (you may have to create a directory for the mountpoint):
sudo mount -t vfat /dev/sdc1 /media/kevin/hassos-boot
Also, I mentioned using fdisk before, but I suggest using lsblk --fs instead to find out which device/partition to mount (which in this case was /dev/sdc1).
@wutr
I’m having the same problem as everyone here: hassio doesn’t connect to wifi
I’ve spent hours going through the various threads on here but to no good.
I’m on a mac running mojave v10.14.2
Here are my steps:
downloaded the 32 bit image from the official page, and flashed it to an sd card.
like the documentation says, I formatted a usb stick (using the exFAT file system I think).
After hooking up the SD card and usb stick and running the pi it repeats the log “wlan0: link is not ready”, and I also can’t find the connection when viewing my router; so it’s not connecting (hassio.local:8123 doesn’t work either). Am I missing something obvious?
As @cogneato mentioned, the procedure for using a USB drive differs slightly from creating the file directly on the SD card.
If using a USB drive: name it CONFIG (partition label) and create a folder on that partition called network and the my-network file within there.
If using the SD card you wrote the hass.io image to: create the folder CONFIG on the boot parititon and within it a network folder and my-network file.
My mistake, the USB drive is actually named CONFIG as the instructions specify. I formatted it with the mac disk utility and renamed it by right clicking the menu item and changing it there. I’ll check if this actually renamed the partition label, which may be where the issue lies if it didn’t!
ssh into hassos (not the home-assistant instance) and the file is, I believe,
/etc/NetworkManager/system-connections/default
Alternatively connect your pi to a monitor and keyboard and log in there.
PS Why TF anyone wants to run something like HA on wifi is beyond me. When you get it going it runs your life and your house. Reduce points of failure!
Good point @nickrout, but in my situation I don’t always have direct access to the router.
My pi is hooked up to a monitor which is how I’m able to view logs, and it doesn’t look like it’s accepting input. How would I be able to log in manually? Also how can I ssh into hassos if my pi isn’t connecting to the wifi, and what would the username / password be if I was connected via ethernet?
It’s not a matter of wired vs. wireless. I 100% agree that wired is the way to go for a reliable connection. The RaspberryPi 3 has the great feature of ethernet and wifi. Maybe someone would like to run HA on ethernet but have wifi sensors on a different network. There are dozens of network variations out there done for very legitimate reasons. Hassio’s network configuration is a total nightmare for accommodating these.
I spent 3 weeks bashing my head against the wall trying to get WiFi to work. Starting from scratch reformatting SD at least 20 times with 32b or 64b HA87 or HA88 and trying various combinations of wifi configs and filenames. Believe me, I was about to throw in towel after this last attempt… I formatted USB FAT32 and it worked! The following is NOT in the “Getting Started” instructions.
The config file must use UNIX end-of-line (LF)
The config file data must be ANSI encoded.
The WiFi config file is stored in the “my-network” file name, and WITHOUT a file name extension.
The USB must be formatted FAT32.
At least, this is what finally worked for me… WOW… this was painful ! PLEASE… someone update the “Getting Started” with these findings so that others (inexperienced Linux folks) don’t have to go through this.
To complement the link, also check out my reply, regarding the importance of setting the channel<=10 of the SSID in your router before performing first-boot.
