Exact same situation. Got a new rpi 3B+ last night and flashed hassos_rpi3-2.2.img on a 32GB micro SD Card. Booted up to the web interface with no issues. Then when I clicked on one of the links in the menu, it stalled out with the following messages in the browser on a different machine: ‘Site can’t be reached’ and ‘took too long to respond’. And I see the two messages repeating on the monitor connected to the rpi:
IPv6: ADDCONF (NETDEV_UP): wlan0: link is not ready
brcmfmac: power management disabled
I figured out that I was using old instructions for install (a bit frustrating that instructions dated in July are outdated). Wifi is working (seen on my router) but still no web interface.
I finally got everything up and running, too. Config file was different on the second install, for some strange reason. After I spotted the difference it was smooth sailing (relatively).
The issue is not related to Samba or DuckDNS as I had direct access via keyboard and the issue came up right from the beginning of the install before doing any kind of customization.
I’m not using any IPv6 on my network and Hass.IO works fine … its just a bit annoying that I don’t have a local command login
I tried the 32bit and 64 bit version with the same result … now back on 32bit.
And I also have the same problem, tried three different Pis and network cables. The device gets an IPv4 address from DHCP but refuses to use it, instead continually looping around WLAN.
Looks a lot like my problem.
Tried it on 3 RPI3B+ several image (32bits) downloads and 3 different, new, sd cards.With and without the official Pi PoE hat.
Just neverending loops around:
IPv6 ADDRCONF(NETDEV_UP) wlan0: link is not ready
brcmfmac: power management disabled.
I didn’t thing wlan would be necessary, since it’s powered from a working ethernet interface…
IPv6 ADDRCONF(NETDEV_UP) wlan0: link is not ready
brcmfmac: power management disabled.
If I setup eth0 same issue.
Try for both 32/64 iso v2.2 same result.
Plugged on 5V/3A btw.
Obs: durring my attempts install doesn’t seem to fail at the same moment, sometimes the install works a long time (with living things in output) sometimes it’s quickier. At the same time community website thrown 504 errors.
I think the problem is with eth0 on RPi3+.
I tried installing it one more time. This time with a USB stick with a configuration file setting the wlan ssid and password, to force it to use wlan and forget eth0 for a while.
IT WORKED! Now i´ve come one step further.
Tried to follow the instructions in the video in an earlier post.
I also installed configuration - ok.
But after installing Samba with parameters saying to use eth0, it didn´t start after reboot! So I´ll run without it for a while.
Seems like it´s an Ethernet problem on RPi3B+.
Experience: I took bakups of the MicroSD after each major step. Took some time, but definitely worth it.
Note: When you make the configuration file on a windows pc, make sure it´s saved with Unix-style line endings (LF, not CR LF). This can be selected in most good text editors (Notepad++, Textpad etc).
NOW it´s time to go forward and get all my z-wave devices up and running. And some zigbees.
I had the same problem during the install with the Hass.oi installation on Raspeberry Pi 3 B+. First on the 64 bit version and also on the 32 bit version. But found the solution for the 32 bit version:
Thanks for your solution but I would like to complete the installation using the WiFi . I followed the steps mentioned above on my new Rasp 3 B+ on a 32 bit version and get this message repeated:
Pv6 ADDRCONF(NETDEV_UP) wlan0: link is not ready
brcmfmac: power management disabled.
My USB matches the one listed above and I created it under the network directory. My USB Was formatted in FAT32 labeled CONFIG.
i am curious if someone has a different solution for this problem. i tried loading from file. i even tried the solution from Ruimatos with firefox but the thing is on my pi the webpage never gets started.
my pi worked fine got it setup and it worked for a week then i did something wrong i must emit.
but now im looking at the same problem as any of you guys hassio starts fine but for some reason is not able to start configuration because of the wlan0: link not ready
I’m following this thread for a while now, as I’m having the same problems. I discovered that “hassio” is connected to my router, but still the added display says:
IPv6 wlan0: link is not ready
power management disabled
I’m trying to leave the Raspberry on during the night to see if that has any effect.