Hassio-Access-Point
Hassio-Access-Point copied to clipboard
mattlongman
Unable to start AP
Hello,
I was trying to get this up and running to keep track of my Bluetti battery in my camper. I followed some directions to get Armbian running on an OrangePi and supervised HA. Any help would be appreciated.
Core 2024.7.4
Supervisor 2024.08.0
Frontend 20240710.0
Hass.io Access Point 0.5.2.1
Starting Hass.io Access Point Addon
# Setup interface:
Add to /etc/network/interfaces: iface wlan0 inet static
Run command: nmcli dev set wlan0 managed no
Warning: nmcli (1.46.2) and NetworkManager (1.42.4) versions don't match. Restarting NetworkManager is advised.
Run command: ip link set wlan0 down
Add to /etc/network/interfaces: address 192.168.99.1
Add to /etc/network/interfaces: netmask 255.255.255.0
Add to /etc/network/interfaces: broadcast 192.168.99.255
Run command: ip link set wlan0 up
# Setup hostapd:
Add to hostapd.conf: ssid=TinyLittleCamper
Add to hostapd.conf: wpa_passphrase=********
Add to hostapd.conf: channel=6
Add to hostapd.conf: ignore_broadcast_ssid=0
Add to hostapd.conf: macaddr_acl=0
Add to hostapd.conf: interface=wlan0
# DHCP enabled. Setup dnsmasq:
Add to dnsmasq.conf: dhcp-range=192.168.99.10,192.168.99.20,12h
Add to dnsmasq.conf: interface=wlan0
Warning: nmcli (1.46.2) and NetworkManager (1.42.4) versions don't match. Restarting NetworkManager is advised.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Hi, I have the same issue, but it only occurs when there was no internet connection available during the boot of Home Assistant. Does your HA instance have internet access when you're trying to start the Access Point? This might help in diagnosing the issue.
Any insights or workarounds would be greatly appreciated.
Thanks in advance!
It did have Internet when starting. I was using eth0 providing LAN access and using the wlan0 for the AP.
I connected a usb wifi adapter and confirmed that armbian can connect via that. Though I was able to connect prior on wlan0
frank@OrangePi:~$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: end0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 02:07:46:11:09:f5 brd ff:ff:ff:ff:ff:ff
3: wlx801f027c6e3c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 80:1f:02:7c:6e:3c brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 50:d4:e6:88:ff:3a brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:27:76:39:5c brd ff:ff:ff:ff:ff:ff
6: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:85:d4:39:8d brd ff:ff:ff:ff:ff:ff
8: veth4acef5c@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 82:a3:c0:0b:5b:83 brd ff:ff:ff:ff:ff:ff link-netnsid 0
10: vethbf5c99e@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default
link/ether 3e:20:fa:b5:e5:03 brd ff:ff:ff:ff:ff:ff link-netnsid 1
12: vethc7cd207@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 66:d7:06:3a:1b:c8 brd ff:ff:ff:ff:ff:ff link-netnsid 1
14: vethcdf47ed@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 5e:8c:05:4b:54:2e brd ff:ff:ff:ff:ff:ff link-netnsid 2
16: vethb75ef14@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 2a:ec:06:cf:bc:c9 brd ff:ff:ff:ff:ff:ff link-netnsid 3
18: veth2d6f894@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 3e:85:1a:97:a6:d5 brd ff:ff:ff:ff:ff:ff link-netnsid 4
24: vethd17f0f3@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 32:56:e8:e2:ac:d3 brd ff:ff:ff:ff:ff:ff link-netnsid 5
frank@OrangePi:~$ nmcli device status
DEVICE TYPE STATE CONNECTION
wlx801f027c6e3c wifi connected Supervisor wlx801f027c6e3c
lo loopback connected (externally) lo
p2p-dev-wlx801f027c6e3c wifi-p2p disconnected --
p2p-dev-wlan0 wifi-p2p unavailable --
docker0 bridge unmanaged --
hassio bridge unmanaged --
end0 ethernet unmanaged --
veth13439f2 ethernet unmanaged --
veth2d6f894 ethernet unmanaged --
veth4acef5c ethernet unmanaged --
vethb75ef14 ethernet unmanaged --
vethbf5c99e ethernet unmanaged --
vethc7cd207 ethernet unmanaged --
vethcdf47ed ethernet unmanaged --
wlan0 wifi unmanaged --
frank@OrangePi:~$ nmcli connection show
NAME UUID TYPE DEVICE
Supervisor wlx801f027c6e3c 0866fea1-86e2-4c54-8955-3b597d943258 wifi wlx801f027c6e3c
lo 35071640-e174-4afd-ac26-8b32dcd00641 loopback lo
So oddly enough if I leave wlan0 alone and use a usb dongle I can connect no problem.
Is this still an issue? I assume the OrangePi would work in the same way, but can't really help with specifics.
i can reproduce on rpi4. when HAOS has no network at all, the AP does not come up. It does not log an error either.
My whole usecase for this plugin was to run HAOS in a remote location that has not even a router available. This kinda breaks that
Update: Resolved my issue by setting a static DNS server. See https://github.com/ex-ml/Hassio-Access-Point/issues/79#issuecomment-3504688114.
I believe this is the same issue as #79