I installed the latest NUC image (i think it’s called v2.12) and it runs very smooth. Everything worked perfectly after restoring a snapshot, and i had internet connection via LAN (i use the duckdns addition, and always have with no “challenges”).
But i can’t seem to make connection to internet through WiFi. I use the USB method, which i also used on my Rpi3b+, and the Pi connects happily. My NUC will only allow local connections. A bold guess (i really have no idea) is that the NUC kinda ignores the “gateway” part of the USB drive’s network configuration. My port forwarding in my router is in place, and even when using straight external IP (no duckdns) i still can’t establish a connection.
Funny thing is that LAN worked initially (it might still do, i will check up on that), but with WiFi i hit my head against the wall. For good measure i will paste my CONFIG content here (in case i indeed made a booboo):
[connection]
id=hassio-network
uuid=72111c67-4a5d-4d5c-925e-f8ee26efb3c3
type=802-11-wireless
[802-11-wireless]
mode=infrastructure
ssid=(My ssid, concealed)
[802-11-wireless-security]
auth-alg=open
key-mgmt=wpa-psk
psk=(My password, concealed)
[ipv4]
method=manual
address=192.168.0.4/24;192.168.0.1
dns=8.8.8.8;8.8.4.4;
[ipv6]
addr-gen-mode=stable-privacy
method=auto
Some might think that it is dumb to install the NUC image in contrast to a “normal” Linux distro with a traditional docker on top, but i really want to avoid another “layer” to configure, hence me going “straight to the iron” 
Some might think that it is dumb to use WiFi when the NUC has LAN-port, and i agree. But as of now, i really need the WiFi function until i get some decent cabling routed in-house.
I am open for all suggestions But since i sport a hass.IO installation i can’t go too deep down the rabbit hole through SSH. On top of that my Linux experience is extremely sparse.
A little more info…
I see this line in my log. Not sure if it is related:
ERROR (MainThread) [hassio.homeassistant] Error on call https://172.30.32.1:8123/api/: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
Also, my “System Monitor” fails to show IP address for both LAN and WiFi:
This worked fine on my Rpi3b+ (running either on cable or WiFi). The configuration for it looks like this:
- type: ipv4_address
arg: wlan0
- type: ipv4_address
arg: eth0
Ok, i discovered that my HassOS was 2.12 (default for the image, i guess). I updated to v3.7 and now i can use \hassio for my Samba share.
Still i can’t reach my HA through internet despite all settings and configurations are exactly as when i ran my Rpi3b+. My “system monitor” still state that both my cabled and WiFi connections are “unknown” IP
The NUC ethernet port is not ETH0 like for the Raspi!
Try :
- type: ipv4_address
arg: wlp2s0
- type: ipv4_address
arg: enp3s0
You can see with the linux command:
iwconfig
1 Like
@LogisticaLux Thank you for your answer
I tried that linux command in the CLI using “SSH Server”, and this is what i get:
But i had some luck with your input about the YAML. Now i see WiFi IP, but Ethernet IP still comes up as “unknown”. And this is where i lose my sense Even though “System monitor” reports my Ethernet to be unknown, i can hotplug a cable and instantly reach HA via internet. As soon as i unplug the cable, the internet connection is gone. All the while, my IP 192.168.0.4 is shown as belonging to WiFi using “System Monitor” as prescribed.
So when i plug in a cable it is like the cable “adopts” that IP, since that IP is the only one forwarded in my router At least it shows that my port forwarding and duckdns settings are correct. Anyways, local network works all the time, both with and without the Ethernet cable.
I wonder if some properties for the network connections are pre-configured for the docker container in this NUC image? Maybe if i can circumvent the container and reach a real Terminal instead of the Hassio CLI?
Hi,
The command can’t work, because it’s not implemented in HassOS. It’s normal that the IP (if you define a fixed IP to the system) will be used by ethernet or wireless.
I have installed hassio in container, so I can use Ubuntu for using commands.
I guess your NUC has only one ethernet port?! My has only one and enp3s0 is available. I do not use wireless, because I prefer a hard wired system.
Did you try to switch off wlan and reboot with wired network? Maybe hassio does not read both ports due to the same IP they will get?!
Did you update the bios to the newest one before install? I read in a forum that this can help with ethernet port probs. Or boot up with a linux system and do the iwconfig to get the right id for it.
1 Like
It is OK for me that the Ethernet port is not showing IP address. I can live with that
My wish is for WiFi to work properly, going through Internet. I can only reach my HA through internet if i use a cable. When HA runs WiFi, there is no connection through internet. This is kinda weird Same IP, same router forwarding, same everything.
My NUC is running latest BIOS.
Regarding WiFi => I have to pass to another user, cause I do not use and donÄt have any experience in combination with hassio. And I connect to hassio with the help of nabucasa. Don’t want to use duckdns or something like this, cause I am too lazy to config. 
This issue is ongoing. Still hoping to hear from anyone who use the NUC image directly, without running Hassio on top of an ubuntu or the likes.
Can anybody inform me about who is managing this specific Hassio image? I would love to ask a few questions to get some clarity, maybe even fid a way to fix my WiFi issues
Thanks
1 Like
Did you ever make it work (NUC OS image / no ubuntu + wifi)?
Unfortunately not. I went back to my Pi, and moments later the Pi4 was released, so i jumped on that one
