HAOS is installed on a HP desktop. For security/privacy purposes IoT has it’s own wireless network. The UTM controls wireless and at this time do not have it setup with manual vlan that I could use a 2nd wired NIC. I have the HA server on the main network (that’s where I want it) but thought I would add a 2nd NIC (wireless) to be able to add and have better visibility to the IoT. For example, echo devices have not been discovered yet. They are on the IoT network; HA is on the internal network. I am sure someone will post about installing windows or linux and then using docker on top of the OS. No intention of doing that.
HAOS Core = 2024.6.4
Supervisor = 2024.06.0
Operating System = 12.4
Frontend = 20240610.1
I have searched the form / google for what others have done. Several things out there related to pi installs that do not apply. I could not post the link (due to new user) - but found an article that said intel cards are recognized out of the box.
Purchased the following NIC because it had linux support (supposedly) and was an intel chip - which supposedly meant it would work out of the box.
Wireless NIC purchased - amazon
Installed it and connected the bluetooth power. Upon plugging everything back in and booting up - HA autodiscovered the bluetooth and “iBeacon Tracker”. I went ahead and added both and they are showing in the integrations section. So something is working out of the box…good sign.
Under Settings → System → Network…only the original integrated card is showing.
Advanced SSH & Web Terminal (community version) is installed and Protection Mode disabled while working on this. Here are the results of some work in terminal.
➜ ~ nmcli radio
Warning: nmcli (1.46.0) and NetworkManager (1.44.2) versions don’t match. Restarting NetworkManager is advised.
WIFI-HW WIFI WWAN-HW WWAN
missing enabled missing enabled
➜ ~ nmcli radio wifi
Warning: nmcli (1.46.0) and NetworkManager (1.44.2) versions don’t match. Restarting NetworkManager is advised.
enabled
➜ ~ nmcli device wifi rescan
Warning: nmcli (1.46.0) and NetworkManager (1.44.2) versions don’t match. Restarting NetworkManager is advised.
Error: No Wi-Fi device found.
~ cat /etc/*-release
3.20.0
NAME=“Alpine Linux”
ID=alpine
VERSION_ID=3.20.0
PRETTY_NAME=“Alpine Linux v3.20”
HOME_URL=
BUG_REPORT_URL=
nmcli
eno1: connected to Supervisor eno1
“eno1”
ethernet (e1000e), , hw, mtu 1500
ip4 default
inet4 192.x.x.x/24
route4 192.x.x.0/24 metric 100
route4 default via 192.x.x.x metric 100
inet6
inet6
route6 ::/64 metric 1024
route6 ::/64 metric 100
lo: connected (externally) to lo
“lo”
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
docker0: unmanaged
“docker0”
bridge, 02:42:32:F5:6D:1C, sw, mtu 1500
hassio: unmanaged
“hassio”
bridge, 02:42:DD:D0:86:40, sw, mtu 1500
veth1d8a112: unmanaged
“veth1d8a112”
ethernet (veth), 9E:EC:BB:0F:9C:8E, sw, mtu 1500
veth1e4b017: unmanaged
“veth1e4b017”
ethernet (veth), CE:F3:49:96:FD:A0, sw, mtu 1500
veth2a8f2bb: unmanaged
“veth2a8f2bb”
ethernet (veth), 8A:6D:33:FE:98:82, sw, mtu 1500
veth562db48: unmanaged
“veth562db48”
ethernet (veth), 7A:CC:9D:A1:40:67, sw, mtu 1500
veth6a69d77: unmanaged
“veth6a69d77”
ethernet (veth), E2:30:A8:19:30:D9, sw, mtu 1500
veth9400060: unmanaged
“veth9400060”
ethernet (veth), 52:DD:15:F1:FD:2C, sw, mtu 1500
veth9fdfc62: unmanaged
“veth9fdfc62”
ethernet (veth), C6:61:1F:27:1C:40, sw, mtu 1500
vetha7a69bc: unmanaged
“vetha7a69bc”
ethernet (veth), 72:4D:DC:F0:94:FF, sw, mtu 1500
vethd1a2399: unmanaged
“vethd1a2399”
ethernet (veth), 0A:B8:26:C9:0A:87, sw, mtu 1500
wpan0: unmanaged
“wpan0”
tun, sw, mtu 1280
DNS configuration:
servers: 192.x.x.x
domains: domain.local
interface: eno1
Use “nmcli device show” to get complete information about known devices and
“nmcli connection show” to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
I’m not seeing the card…unless wpan is it? I am thinking drivers may be missing? I have rebooted since install as well. Has anyone else tried this?
Any suggestions on where to go next (other than drop the native HAOS install and run on top of something else). Thanks in advance.