Not sure if this is a SW or a user issue - I've installed Hassio-Access-Point on a Raspi 2B with HAOS 12.4 (latest today). Not an expert in networking - but using defaults, changing the interface name and enabling DHCP allowed me to connect with my smartphone instantly. Nice.
I've then set one Shelly (WiFi IoT device) to also connect only to the new AP - using the same credentials like the phone - only for it not to connect. I've used the Android app Vernet to scan the WiFi for devices, and it only shows the Raspi 2B and the smartphone itself. The log only shows the smartphone connecting (initial start to reboot clipped) -
Starting Hass.io Access Point Addon
Warning: nmcli (1.46.2) and NetworkManager (1.44.2) versions don't match. Restarting NetworkManager is advised.
Warning: nmcli (1.46.2) and NetworkManager (1.44.2) versions don't match. Restarting NetworkManager is advised.
Add DNS: dhcp-option=6,192.168.178.1
rfkill: Cannot open RFKILL control device
wlu1u3: interface state UNINITIALIZED->ENABLED
wlu1u3: AP-ENABLED
wlu1u3: STA e6:f7:73:9d:51:71 IEEE 802.11: authenticated
wlu1u3: STA e6:f7:73:9d:51:71 IEEE 802.11: associated (aid 1)
wlu1u3: AP-STA-CONNECTED e6:f7:73:9d:51:71
wlu1u3: STA e6:f7:73:9d:51:71 RADIUS: starting accounting session 4472D21501398C0F
wlu1u3: STA e6:f7:73:9d:51:71 WPA: pairwise key handshake completed (RSN)
wlu1u3: EAPOL-4WAY-HS-COMPLETED e6:f7:73:9d:51:71
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
wlu1u3: interface state ENABLED->DISABLED
wlu1u3: AP-STA-DISCONNECTED e6:f7:73:9d:51:71
Stopping Hass.io Access Point
wlu1u3: AP-DISABLED
wlu1u3: CTRL-EVENT-TERMINATING
nl80211: deinit ifname=wlu1u3 disabled_11b_rates=0
ifdown: interface wlu1u3 not configured
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting Hass.io Access Point Addon
DNS is probably from the Ethernet connection - the Raspi uses 192.168.99.1 upwards.
A reboot of all devices gives the same result. How to go on from here troubleshooting?
Not sure if this is a SW or a user issue - I've installed Hassio-Access-Point on a Raspi 2B with HAOS 12.4 (latest today). Not an expert in networking - but using defaults, changing the interface name and enabling DHCP allowed me to connect with my smartphone instantly. Nice.
I've then set one Shelly (WiFi IoT device) to also connect only to the new AP - using the same credentials like the phone - only for it not to connect. I've used the Android app Vernet to scan the WiFi for devices, and it only shows the Raspi 2B and the smartphone itself. The log only shows the smartphone connecting (initial start to reboot clipped) -
DNS is probably from the Ethernet connection - the Raspi uses 192.168.99.1 upwards.
A reboot of all devices gives the same result. How to go on from here troubleshooting?