#OpentWRT crashes when connecting to Frigate proxy in Home Assistant android app.

1 messages · Page 1 of 1 (latest)

unique quail
#

Hello, Each time i'm accessing Frigate from the home assistant mobile app or the web page from my mobile, my router hangs and need to be rebooted to gain network access again.
It doesn't happen when accessing Frigate from a wired computer thru it's own URL or home assistant.
Frigate is installed as app in truenas scale 25, Home assistant in instance (vm)
hardware acceleration working : rx580
cameras are POE, wired to a dedicated switch connected to a single cudy WR3000 router running latest openWRT firmware. Router is part of a mesh (802.11s)
each cam is running 1080p output in H264 at 15fps, VBR 3500 Kbps except one outputing in h265 and transcoded in frigate.

The problem is easily reproducible, i just need to open the app or open HA on my web browser from my mobile, watch the feed or access recorded clips and the router become inaccessible.

vocal mango
#

Do you have external access to your HA instance?
If you do, do you have this problem both when using the app internally over your wifi and externally using your mobile connection?
Tbh I'm not sure how to use the info exactly.. but it might help narrow down whether its any time you use the HA app, or if it's only when over your wifi.

Also (as I've only recently learned), the companion app has its own logs which you could look at. Under Settings>Companion app>Troubleshooting>Show and share logs. Might not show anything more than 'lost connection', but hopefully there'll be something to go on leading up to that🤞

I've never used open-wrt, but a long time ago I used dd-wrt quite a lot and I gather they're related. dd-wrt used to have a ton of resource monitoring and logging. Hopefully open-wrt has similar these days? It could mean rigging up an external syslog server somewhere, but might help show whats going on on your router.

unique quail
#

Thanks, i just noticed it's also crashing when using the web browser and not only the app. I've been checking the router logs but i don't see anything or at least not in my expertise.

vocal mango
#

You don't see anything unusual happening on the router at all, just happily running then dead?

Have you noticed it happening when doing anything particular in frigates interface(s)?
If it happens when just viewing the Live tab in frigate (1st/camera icon down the left in a browser or along the bottom in the companion app), there are a couple of toggles that could make that less work to display in the settings, Automatic Live View and Play Alert Videos. Might change its behaviour.

Or, and its kinda clutching at straws tbh, but I'd be tempted to chop the frigate config down to the minimum and work back up from there, testing it after adding back in each piece.
(I'd just comment most of it out in frigates config editor using Ctrl+/, then do the same to turn bits back on)
Right from zero cameras.. add one back and try it, add another and try it etc see when it breaks.
As long as you take a copy of frigate.config before changing anything then you're pretty safe to wreck it.
(if you restart HA or the frigate integration while doing this, expect it to complain about missing cameras/entities if you have automations using them. It'll shut up once you've put frigate.config back as it was and restart frigate and the integration though)

Or maybe reduce the resolutions of the cameras as a test, see if the routers happy up to a certain point with that too.

Or, if you're not using it already maybe give go2rtc a try. It might be more work for you HA box to do, but it'd *change *the streams at least