-
-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add remaining health connect sensors #4804
Comments
Several of these are in progress in: #4803
|
Exercise session (and related metrics) will need to have discussion around how it works or if it makes sense to add as records will be delayed since the app does not get notified for it. The Wear OS activity state sensor is better fit IMO but only applies for those watches. If we do add it the state as type will require a force update so we can update back to back records of the same type. End time will be unique but may not display well in the frontend without some effort. For cycle tracking might be best to hold off until we get a user request so we can discuss what data is best to add skin temp requires extra consideration in how to report it, do we go by average or latest record? remaining sensors should also be requested and discussed before we add them |
I'm glad this is in progress, waiting for menstruation tracking like kid for Christmas. |
The latest update with the new metrics was pretty cool. Can't wait for calories consumed to be added. |
I absolutely need the body temperature sensor exposed in HA! |
I'm excited about this work! Should I be able to see the glucose readings from health connect in the companion app yet? |
unfortunately we were only approved for a small set of permissions, we plan to go again for some of the original sensors in sometime to see if we can qualify for it. We are not confident we will be approved despite previous approval. |
Thank you. Really appreciate the work. Buzz kill they are so strict on approving this. Appreciate ya!smm
-------- Original message --------From: Daniel Shokouhi ***@***.***> Date: 1/22/25 10:17 AM (GMT-06:00) To: home-assistant/android ***@***.***> Cc: Stan Marczak ***@***.***>, Comment ***@***.***> Subject: Re: [home-assistant/android] Add remaining health connect sensors (Issue #4804)
I'm excited about this work! Should I be able to see the glucose readings from health connect in the companion app yet?
unfortunately we were only approved for a small set of permissions, we plan to go again for some of the original sensors in sometime to see if we can qualify for it. We are not confident we will be approved despite previous approval.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Has there been any consideration for a version that includes Google features that are blocked by Google? Might make the pipeline more complex, since it would require changing the manifest for play store releases to remove permissions, and ideally would include an alert for a new version to download manually. But HA is in a unique position where the Play Store isn't necessarily a barrier to user acquisition (and that's not even necessarily a strict goal) I know there is already a separate FDroid version that is missing location features. |
This request will be used to track the remaining sensors we can add according to: https://developer.android.com/health-and-fitness/guides/health-connect/plan/data-types as I am sure we will get more requests and quite possibly more will be added in the library
The text was updated successfully, but these errors were encountered: