Not really the question I was answering, but that’s not actually a health connect problem.
Withings had an issue, and the way they were connecting to it, which caused a battery drain.
To be specific, withings health mate was constantly reading health connect data, which caused a massive power drain.
I’m not aware of any other battery issues with health connect other than Withings and their Health Mate app (specifically reading, not writing).
(Edit: why, why would autocorrect change writing to riding? For shame. To me, for not noticing sooner.)
Just to be clear - it’s the API that’s shutting down, not the app. Not that Google has put in effort for the app either, it hasn’t updated since health connect afaik, but health connect is the health and fitness tooling going forward.
Fitbit has health connect support now, so even if they shift and drop Fit (I hope not, though I also hoped they wouldn’t kill the web interface), and make Fitbit the main Google fitness app, it will still work with Fitbit as the app.
I’ve got a polar h10 myself, I know their app still connects to Fit not health connect, but I’m sure they will update.
I actually made an app to make use of health connect with my polar h10 for entirely different purposes, it’s really a pretty minor backend change for them to make, so I’m sure Beat will get an update.
Worst case you could connect to Strava as a go-between should polar be far behind on health connect (again, doubt they would be).
But checking the coospo compatibility, it seems there are a ton of them that all support health connect with coospo, so you wouldn’t be shut out even if health connect wasn’t ready for Polar, you’ll have a ton of options. Including using polar to sync to something that syncs via health connect.
Which is kind of what I do btw, aside from the app for the completely irregular use case I mentioned, I sync polar to Strava, Strava to Fit via health connect. I do that because fairly often I am using polar while cycling, so that’s how I want my data to go. But I then found strength training shares nicely too, and running polar beat and my workout app, I can track all my workout routine items (jefit), which syncs via health connect, and then polar goes to Strava goes to health connect, and it all shows as a single session with great HR data.
If it uses health connect to send the data it’s still all good. And if you bought something recently made, it should.
Health Connect “beta” is a battery hog. Until they fix those issues, it’s a non-starter for anyone caring about battery life.
Not really the question I was answering, but that’s not actually a health connect problem.
Withings had an issue, and the way they were connecting to it, which caused a battery drain. To be specific, withings health mate was constantly reading health connect data, which caused a massive power drain.
I’m not aware of any other battery issues with health connect other than Withings and their Health Mate app (specifically reading, not writing).
(Edit: why, why would autocorrect change writing to riding? For shame. To me, for not noticing sooner.)
😅 ok great.
Just to be clear - it’s the API that’s shutting down, not the app. Not that Google has put in effort for the app either, it hasn’t updated since health connect afaik, but health connect is the health and fitness tooling going forward.
Fitbit has health connect support now, so even if they shift and drop Fit (I hope not, though I also hoped they wouldn’t kill the web interface), and make Fitbit the main Google fitness app, it will still work with Fitbit as the app.
I’m using polar bears. 🤞
I’ve got a polar h10 myself, I know their app still connects to Fit not health connect, but I’m sure they will update.
I actually made an app to make use of health connect with my polar h10 for entirely different purposes, it’s really a pretty minor backend change for them to make, so I’m sure Beat will get an update.
I got the coospo one, but found the polar apps easy enough to use.
Got it, checking their list of compatible apps…
Worst case you could connect to Strava as a go-between should polar be far behind on health connect (again, doubt they would be).
But checking the coospo compatibility, it seems there are a ton of them that all support health connect with coospo, so you wouldn’t be shut out even if health connect wasn’t ready for Polar, you’ll have a ton of options. Including using polar to sync to something that syncs via health connect.
Which is kind of what I do btw, aside from the app for the completely irregular use case I mentioned, I sync polar to Strava, Strava to Fit via health connect. I do that because fairly often I am using polar while cycling, so that’s how I want my data to go. But I then found strength training shares nicely too, and running polar beat and my workout app, I can track all my workout routine items (jefit), which syncs via health connect, and then polar goes to Strava goes to health connect, and it all shows as a single session with great HR data.
So yeah, you’ll be fine.