CorrectAlias

This. I have a Garmin watch and it works perfectly with Gadgetbridge.

I would switch tonight but there’s not voice chat in the self hosted version yet.

Bummer that it doesn’t have voice chat yet in the self hosted version. Hopefully soon - I would probably switch if they had that.

I dropped it after the devs response was to be silent about what actually happened “to focus on the f-froid builds”. It’s still unclear, and because of the way they’ve set up the GitHub repo, it’s still possible for the apk to be compromised.

Another person beat me to it, but it’s basically an open source app for wearables and other related devices. It aggregates all of my health metrics and made it so I never once had to connect my watch to Garmin’s cloud services. All of my data is just stored locally on my phone.

You can see the supported devices here: https://gadgetbridge.org/gadgets/

I bought a Garmin watch over Fitbit because it works with Gadgetbridge.

I know, but it seemed like there was confusion about my intended point, which is that you should never expose it to the open internet. It wasn’t a question I really intended to be answered since I know that was their intention. My confusion is why do that when there are secure alternatives, some of which are easier than opening a port.

There are far better, more secure ways to do this. You could use a reverse proxy. You could use tailscale. You could use wireguard.

The last thing you should do is open Frigate’s port to the net.

I’m not sure why anyone would want to expose Frigate of all things to the open internet.