I am unable to connect to my Raspberry Pi running Octoprint 1.4.0, Octopi 0.17.0. The wireless adapter is able to see the network and connect to the network from a Pi 3 (dont have mico hdmi adapters). The wireless only address is 169.254.166.16 which is not a valid address.
I have tried googling around for more information. The only way I can connect to the pi remotely is by having the ethernet plugged in. I have attempted disabling dhcpcd (dont it breaks and you have to rescue it with a monitor), looking at the network settings, tried moving the country code to above the network block in the octopi-wpa-supplicant.txt file. I have also attempted to set a static IP on the router for the pi
Logs (syslog, dmesg, ... no logs, no support)
Not sure which logs will be useful but I keep seeing multiple lines that seem to point to a configuration issue, just not sure where:
Apr 23 20:54:22 octopi dhcpcd: wlan0: using IPv4LL address 169.254.166.16
Apr 23 20:54:22 octopi avahi-daemon: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.166.16.
Apr 23 20:54:22 octopi avahi-daemon: New relevant interface wlan0.IPv4 for mDNS.
Apr 23 20:54:22 octopi dhcpcd: wlan0: adding route to 169.254.0.0/16
Apr 23 20:54:22 octopi avahi-daemon: Registering new address record for 169.254.166.16 on wlan0.IPv4.
This is the route information:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 202 0 0 eth0
link-local 0.0.0.0 255.255.0.0 U 303 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
The network is functioning fine, all other devices have valid IP addresses. When the Pi is plugged in with ethernet it seems to get a valid IP address. Overall to me, this seems to point to an issue wit dhcpcd but the config file looks to be just the base config file.
Any help is appreciated. If more logs are needed, I will happily grab them.
Thanks for any advice.