Unless I’m reading something wrong here, you should be looking for the boot partition, not the folder. (If writing the my-network file to the SD card directly). Mounting read-only is done by certain distributions when auto mounting file systems, there’s probably a reason for it but in this case it’s fine to remount in read+write mode.
Have a go at finding the Hass.io boot partition (using fdisk), mounting it in read+write mode (which is standard if you manually mount I believe) and creating the folder CONFIG/network on that boot partition. It shouldn’t take you much over 20 minutes if you’re new to it all. You have to learn at some point, might as well be now. Double check you are working with the SD card and not a local drive and there isn’t much to go wrong.
Also, you probably already found out, but Linux and its filesystems are case-sensitive.
If you want, can you paste the output of sudo fdisk -l /dev/sdcardpointer (substitute the actual device name of the SD card of course) so someone can reply with the correct mount command.
Hi again,
I used the partition identifier and it returned the following:
kevin@kevins-linux:~$ mount -v | grep “^/” | awk ‘{print "\nPartition identifier: " $1 "\n Mountpoint: " $3}’
I can’t see sdc1 as that is the fat16 partition (hassos-boot) which is the only 1 visible in windows. In there I tried creating a CONFIG/network/my-network file also with config/network/my-network. I tried CONFIG/network/hassos-network (also lower case) as that is the id in the second line of the file.
All failed.
I am not sure which of the remaining 7 of the 8 partitions I should enter the CONFIG into to achieve a WiFi connection.
I have also tried the USB stick again with the various formats of the file, no joy.
Could it have anything to do with the UUID? I’m not sure.
Okay all, I’m a bloody idiot! I’ve spent the past few days tearing my hair out over this WiFi setup and have just realised that the speck of dirt on my screen by the file “network” was actually ’ and thanks to the small view on my display, I didn’t see my mistake!
Only on a different folder view in linux was I able to realise the error of my ways.
The Pi ZeroW is ticking along nicely now and downloading what it needs, phew!
Many thanks and apologies to @wutr for all the help. It looks like I’m off to a real rocky start with home assistant but on the plus side it can only get better! (I hope!)
Thanks again all, sure it won’t be the last question I have but hopefully the rest won’t be so schoolboy error orientated!
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.
