I was totally content to accept that once I saw how well it solved my problem. WiFi has a clear cut path to getting what you want accomplished which seems great from the outset, but is totally useless if it’s not reliable. I’ve found that WiFi-based projects generally need to be really, really close to an access point to be properly reliable.
As another comment mentioned though there are probably plenty of ways I could mitigate these problems, so it’s as much an issue with me trying to use a technology wrong as it is a hard limitation of WiFi.
I've found the AT modem command[3] based modules[1][2] to be fairly drop-in and usable, I was even able to pair via BT on my phone and use the BT serial TTY to send/recv without any specific software. It's pretty hard to beat ~$20 modules that you can just drop in and run over UART.
Keep in mind these are mostly for point-to-point although if I remember correctly you can also configure them for a standard LoRA deployment through that command interface as well.
[1] https://store.rakwireless.com/products/rak4200-evaluation-bo...
[2] https://www.seeedstudio.com/LoRa-E5-mini-STM32WLE5JC-p-4869....
[3] https://docs.rakwireless.com/Product-Categories/WisDuo/RAK42...
The downside to LoRaWAN is the implementation of mesh. It, generally, requires far more planning currently - but I'll be curious to see how it evolves with more mainstream applications.