We will find out in the next hack.
domi
joined 2 years ago
It's more about visibility, their spins tab is fairly hidden and most users won't find it unless they know about it.
Their KDE version definitely deserves a spot beside their GNOME version.
Same here, VRR and HDR support on Wayland were the main reason I switched to KDE.
(I also quite enjoy not having to install any extensions now.)
Figured it out, Home Assistant automatically grabs the ICE candidates from Frigate so it works out of the box for local network and works after forwarding port 8555 (TCP and UDP) either directly to Frigate or through a reverse proxy.
I wasn't quite onboard with turbo granny being back as cute cat last episode but she's turning out to be a pretty entertaining character.
Was anyone able to get WebRTC to work behind a reverse proxy with Frigate? I couldn't find out where the documentation for this feature is.
Especially since many Linux related organizations like SUSE and KDE are based in the EU.
Do you use a USB bluetooth adapter? If so, try to use a very short USB A to USB A cable, it gets rid of most 2.4 GHz interference.
then just use that as a filter on the grabber.
That's pretty smart. In that case nothing is wasted, no.
Well, now the ending makes sense. It was turbo granny all along.
You should have absolutely no issues with that hardware on Fedora.
Could you try switching the display cable out? If that doesn't work try switching the cable to a different type (e.g. DisplayPort instead of HDMI or vice versa). If that also doesn't work, try with a different display if you can.