Is there a reason why the sensor_class is not defined for systolic and diastolic blood pressure sensors in the android companion app? I am not able to see long-term history averages unless I customize the sensors in my config.yaml to sensor_class: measurement
Note that the Google Fit integration does define the blood pressure sensors as sensor_class: measurement.
#Health Connect blood pressure sensors sensor_class?
stuck cloak
tepid vault
taht requires measurements to be in real time but the app cannot guarantee that
google fit integration is a custom component , they are probably not respecting the definition of the state class
The state represents a measurement in present time,
stuck cloak
Respectfully, I disagree. All Samsung Health measurements are in present time, including blood pressure, VO2max, steps, and so on - otherwise there would not be a date and time associated with each measurement. Long-term tracking of these sensors is essential for many people. I will continue to use config.yaml to customize these sensors to sensor_class: measurement, and I will continue recommending to others that they do so.
tepid vault
Samsung health sure but the app has no way of knowing that and many other users may not use Samsung and their app may not offer timely updates. My pixel watch has heart rate delayed by hours compared to the calories and steps it tracks. It's too unpredictable. You need to remember health connect is not just Samsung but lots of other apps and they are not guaranteed to be timely like Samsung is
tepid vault
Date and time with each measurement is a requirement actually but still not guaranteed to be current/present
Apps can add records with whatever time range they want which makes it unpredictable as the sensor needs to register the entity information. The app can't predict which ones will be on time or not but you as a user can determine that and that is where the customize comes into use https://developer.android.com/health-and-fitness/guides/health-connect/develop/write-data#basic
stuck cloak
It is the Health Connect sensors section of the Home Assistant Companion App that are defining these sensors, not Health Connect, and they all include a date. This feature is intended to replace the Google Fit API, and as such it should have the same functionality - the sensors should have class measurement.
tepid vault
ye they include a date but the date may not be current