Add-on: Create a Wi-Fi access point with Hass.io Access Point

HI! @mattlongman

I’m having problems installing and starting this add-on, causing my Raspberry Pi 3B+ to completely freeze. Forcing me to force a restart. (If hass.io’s “start on power on” option is on, the only way to exit is to format completely and start over)

I’ve tried 8-9 times, all with completely clean installs and with just the text editor and terminal.
Every time:

  • I start the add-on
  • I also see the access point from my devices (even if I can’t get an IP, both with DHCP active and not)
  • The Home Assistant page completely loses connection and there is no way to restore it even after 1 hour of waiting (And “ping homeassistant.local” always “request timed out”)

From the terminal I tried to do ifconfig, but I don’t get any wlan0.
But if I go to Setting > Network > wlan0 > Wi-Fi > Search Access Point, it works fine and finds all available networks.

In “Configuration > address” I put the IP address reserved for my Raspberry. I believe this was meant in the github under “Config > Option > address (required): The address of your hass.io WiFi card/network”. If not, it could be one of the causes of the Raspberry disconnecting from my local network.

The problem is not attributable to the modem. Some time ago on my Raspberry with Raspian, thanks to RaspAP I had an Access Point (With and without DHCP) without any problem (which also uses the same protocols as this add-on, dnsmasq, dhcpcd, hostapd, etc…).

Could anyone help me?

In the end, the AP works with the internal wifi, and I can access HA with the external wifi. There is no bridge. But that doesn’t matter.
HA reads and writes to devices through both Wifi networks and I can read HA throught the external wifi…not a bridge but I see the state of the devices hooked to the other network.

Hello !
Sorry if my question looks over stupid, but I am very new to Hass.
I could add the repo and can see the component, but …
I which file (where) do you set all these parameters ?

Thanks a lot,

Fred

If you managed to install this add-on, go to “Settings” on the left panel, then find “Hass.io Access Point” on the list of install add-ons, click it and here you go :slight_smile:

Hi @zakarumit - looking at your config, you have DHCP off. This might be deliberate but just wanted to confirm that you’re manually setting the IP on the connected device if not using DHCP. If you’re manually setting IP, you’ll also need to manually set DNS servers. Something like:

    "client_dns_override": ['1.1.1.1', '8.8.8.8']

If you didn’t mean to have DHCP off, try enabling it.

Thanks Matt for your plugin. It seems to do the trick! I’ll be testing some more, if only because I have some 30 iop devices, each of which will need an IP adres. Hopefully my little box can handle the load.
I do have one error during startup which does not seem to prevent the AP from working, but maybe the error was seen by somebody else:
rfkill: Cannot open RFKILL control device
I do know what the rfkill dev is supposed to do, I was just wondering if this would become a problem later. Anybody ?

Hi Matt! Thank you so much for the plugin…this may be a dumb-dumb question, but is there a way to get the devices connected to Hassio communicate with the parent router? Basically, all my smart wifi devices don’t work with my cable router. Up until now, I had this big, ugly secondary router in ap mode broadcasting a separate 2.4 ghz network for these devices that I want to get rid of. I found your add-on, installed it. All the 2.4 ghz devices connect to the hassio wifi, but the home assistant itself doesn’t see them. What can I do to make them visible to the Home Assistant? Thank you again for such a cool app!

Hi, I have this installed on my hass.io Rpi4 broadcasting a local ap in my campervan. I then have a separate rpi3 setup with kiosk browser connecting over the ap WiFi to display the ha pages. It works well.

I would like to be able to setup a second WiFi connection , using a USB WiFi dongle on the rpi4, to bridge to my home network so I can do backups,updates etc.

Is there a way to run another instance of the addon to setup a second. Ap connection ?

Hello everyone,

I have a Raspberry Pi 4 running Home Assistant OS with the following details:

Home Assistant: 2023.9.0
Supervisor: 2023.08.3
Operating System: 10.5
Frontend: 20230906.1 (latest)

I installed the plugin and configured it with the following settings:

ssid: HA
wpa_passphrase: *******
channel: "2"
address: 192.168.99.1
netmask: 255.255.255.0
broadcast: 192.168.99.254
interface: wlan0
internet_interface: eth0
allow_internet: true
dhcp_enable: true
dhcp_start: 192.168.99.100
dhcp_end: 192.168.99.200
dhcp_dns: 8.8.8.8
dhcp_subnet: 255.255.255.0
dhcp_router: 192.168.99.1
hide_ssid: false

With this configuration, I can connect a device, acquire an IP address via DHCP, and establish an internet connection for a few seconds. After that, the device can only ping 192.168.99.1, effectively remaining within the local network. Interestingly, from the HA terminal, I can ping the devices connected to the AP, but these devices can’t ping anything outside their local network. This leads me to suspect the issue is related to routing, although I can’t pinpoint the exact problem.

Here are some logs for reference:

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...
Set nmcli managed no
/run.sh: line 75: nmcli: command not found
Network interface set to wlan0
Deleting iptables
MASQUERADE  all opt -- in * out eth0  0.0.0.0/0  -> 0.0.0.0/0  
ACCEPT  all opt -- in eth0 out wlan0  0.0.0.0/0  -> 0.0.0.0/0   state RELATED,ESTABLISHED
ACCEPT  all opt -- in wlan0 out eth0  0.0.0.0/0  -> 0.0.0.0/0  
Configuring iptables for NAT
MASQUERADE  all opt -- in * out eth0  0.0.0.0/0  -> 0.0.0.0/0  
ACCEPT  all opt -- in eth0 out wlan0  0.0.0.0/0  -> 0.0.0.0/0   state RELATED,ESTABLISHED
ACCEPT  all opt -- in wlan0 out eth0  0.0.0.0/0  -> 0.0.0.0/0  
Setup hostapd ...
Setup interface ...
Resseting interfaces
ifdown: interface wlan0 not configured
Setup udhcpd ...
Starting DHCP server...
udhcpd: started, v1.36.1
udhcpd: can't open '/var/lib/udhcpd/udhcpd.leases': No such file or directory
Starting HostAP daemon ...
Interface stats:
wlan0     Link encap:Ethernet  HWaddr E4:5F:01:E8:9B:B2  
          inet addr:192.168.99.1  Bcast:192.168.99.254  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:12072 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1964094 (1.8 MiB)  TX bytes:620921 (606.3 KiB)
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED 
wlan0: STA xx:xx:xx:xx:88:57 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED xx:xx:xx:xx:88:57
wlan0: STA xx:xx:xx:xx:88:57 RADIUS: starting accounting session BAA60F09228B776D
wlan0: STA xx:xx:xx:xx:88:57 WPA: pairwise key handshake completed (RSN)
wlan0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:88:57
wlan0: STA xx:xx:xx:xx:71:47 IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:71:47 IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:71:47 IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:71:47 IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:a9:cb IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 96:96:b4:ce:a9:cb
wlan0: STA xx:xx:xx:xx:a9:cb RADIUS: starting accounting session 2A1A9B579D7D1B5E
wlan0: STA xx:xx:xx:xx:a9:cb WPA: pairwise key handshake completed (RSN)
wlan0: EAPOL-4WAY-HS-COMPLETED 96:96:b4:ce:a9:cb
udhcpd: sending OFFER to 192.168.99.192
udhcpd: sending OFFER to 192.168.99.192
udhcpd: sending OFFER to 192.168.99.106
udhcpd: sending ACK to 192.168.99.192
udhcpd: sending OFFER to 192.168.99.106
udhcpd: sending ACK to 192.168.99.192
udhcpd: sending ACK to 192.168.99.106

Do you have any ideas for solving this issue?

thanks for the plugin / Addon but now i confirm the settings from the Plugin, i write the ip to gave at start from 199 and i confirme it but now i had the problem, i can found my HA.

Now i like to know, it´s right that i can use the cable rj45 LAN betwen the wlan from pi like a hotspot ? What i Had to write in ?

  1. is the SSID of the Pi WLAN that is created for my Localtuya integrated  brightness sensor since the integration is on my main instance.
    
  2. The WLAN key of the Pi WLAN.
    
  3.  is the address of the Pi, right? In my case, http://192.168.0.4:8123
    

3-1 My subnet mask.

  1.  Don't know what should be entered.
    
  2.  Don't know what should be entered.
    
  3.  Don't know what should be entered.
    
  4.  Don't know what should be entered.
    
  5.  Don't know what should be entered.
    
  6.  0 because DHCP is off, as my Fritzbox already provides the DHCP.
    
  7.  The IP of my Pi.
    
  8. The last address assigned by the DHCP of the Fritzbox.
    
  9. Don't know what should be entered.
    
  10. 11.1 Don’t know what should be entered.
  11. Don't know what should be entered.
    
  12. Don't know what should be entered.
    
  13. Don't know what should be entered.
    
  14. Don't know what should be entered.
    
  15. Don't know what should be entered.
    
  16. Don't know what should be entered.
    

Can anyone help me what i does wrong ? I don´t like to buy a little Accespoint for this, i think a Rebpsrry Pi Homeassistant Pi can do this Job together, to opened a wlan hotspot analog to the cable connection where the pi got the internetdata.