Android Phone and Home Assistant Connection Issues - Temporarily Fixed by Reboot

[Galaxy]

Many of my Android apps and HomeAssistant integrations have no connection since the last update. The only reason I know it has something to do with OPNsense is because for about 5 minutes after a reboot the issue goes away entirely everything works fine.

I have no connection in many Android apps, and every HomeAssistant integration that relies on the cloud has issues connecting. When I reboot OPNsense all of the above works for about 5 minutes, but then the issue inevitably returns.

So far I've had no issues from my main PC. The issue only seems to effect certain apps on my phone, and HomeAssistant on my server.

Any help would be appreciated. I'm at my wits end trying to troubleshoot this. Attached my DNS config since that's my best guess on where this issue is stemming from.

[Galaxy]

Found something in my firewall log that might shed some light on this. It's blocking some connections to my phone, including LAN connections between my server and phone. I'm only using the default block rules on the WAN interface. Can somebody please explain what's going on here?

When I click the rid hyperlink I just get a blank page, and I don't see how to lookup by rulenr. How can I figure out which rule is doing this!!???

See attached pics. My phone is 192.168.1.150, and I have no special LAN block rules. Why the hell are connections to my phone being blocked!


[EDIT] Apparently the logs could be red herrings, and it may just be a dropped connection or something and not necessarily opnsense actively blocking a connection. The fact that everything works fine for a few minutes following a reboot leads me to believe this isn't being caused by a rule (presumably those take effect instantly). Its like something is crashing after 5 minutes and certain types of traffic doesn't get routed anymore (specifically, API connections apparently)

[Galaxy]

I won't pretend to understand how or why, but apparently this issue was somehow being caused by my Comcast rental modem. Why did rebooting OPNsense temporarily fix it? No idea, but that red herring cost me a shitload of wasted time.

I replaced the Comcast modem with a new MB8611 modem, and sure enough this goddamn API issue went away! Unfortunately the new modem also brought my upload speeds down from 100Mbps to about 2Mbps. 🤦‍♂️    I just can't win. Temporarily back on the Comcast modem since I'd rather have the API issue on some devices than garbage upload speed on everything. I'm just happy to finally know where the issue is coming from, even if I can't comprehend how a bridged modem could be causing a problem like this. Gonna return the MB8611 and get an Arris S33, hopefully that will do better with upload speed.