ROBOT0-VT

Hiya, the fix for this is incoming, it's just in between a bunch of half-refactored code. If you'd like to try this fix yourself, you can add the lines @malkowski...

Hiya, thanks for raising this. Seems like the script had some bash-fu that I'm not familiar with 😂 I've reworked this in my in-progress networking refactor, so hopefully the issue...

For reference, the working fix I've applied is to use HA itself as the built-in DNS, instead of trying to pull HA's DNS servers. Still WIP though

As far as I'm aware, you can't simultaneously host a WiFi network and connect to one from the same device/interface, thus this would be intended behaviour. If you remove that...

If we do go this route, we'll have to enable NM management and figure out how we can ensure that NM allows the connection and the AP *without* causing issues...

It could be possible to configure hostapd.conf to work as a bridge... But I've got other things to work on in the short term

Wait, if a virtual interface can work, then we can allow the original interface to be managed by the system, as NM won't be managing hostap's interface :D

Alrighty, I've got it working in a local repo of mine. Unfortunately for you, I'm also in the process of refactoring the networking from the ground up, so you'll have...

From what I can see online, the pi5's wifi chip can handle up to 165Mbps as a client, but I'd imagine that would be even less when hosting the network....

Cool. Would you like me to investigate further, or can I close this?