The Samsung Factory watch faces are able to access the Samsung Health App and are able to show the heart BPM. Others have reported that they it doesn’t show it. A lot of the complications have the Title and Text mixed up for Samsung Health and that may be the reason too.
the [HR\ Tag shows the continuous heart rate for both passive and active states, this is in accordance to Wear user face guidelines. Samsung Health only updates the report every 10 minutes by default when in passive mode.
I can understand that the factory watch faces can “do more stuff” than custom WFS faces we create.
However, the fact that (a) it’s possible to select Heart Rate as a complication for this slot, using the Samsung Wearables app on my phone, and (b) the preview in the Wearables app does show the heart rate dummy data there (see my screenshot above), suggests that it’s expected behaviour that the Heart Rate complication will work in this slot.
Otherwise, I’d have to say it’s a bug that the Wearables app shows the preview correctly when it doesn’t work on the watch itself.
And it’s also a bug that the Wearables app shows Heart Rate as an available complication in the first place. If the Heart Rate complication isn’t supported on custom watch faces, then it shouldn’t be possible to select it in the first place. Right?
From the GW4 release, heart rate complication was only working on stock watch faces. Every time I asked about it I was referenced to Samsung Privacy Policy and that they can’t provide HR Complication because their Health API is private. HR complication was only working properly on GW4 pre-release units. Now this complication has Heart Rate + Red Icon, previously it only had Red Heart Icon.
They shouldn’t need to use their proprietary Health API, because HEART_RATE_BPM is one of the Data Types provided by Health Services, which WFS faces should be able to access. And that has nothing to do with Samsung Privacy Policies, as it’s a Google service.
In any case, if HR is not supported, then that makes the current behaviour a bug by definition, as I’m describing here: users are able to see HR as a selectable complication, and the preview shows it working, yet it doesn’t actually work. That’s a bug that needs fixing.
There are countless discussions about same exact things. You don’t know how many times I asked them to finally support these features because I mainly do watch faces with custom complications For some reason, that complication works fully only on stock watch faces.
Stock watches have access to the Samsung Health API. When I read the Samsung Health forum one big complaint is that Samsung does not share all data with Health Connect and probably not to Health Services either.
Also note that sharing with Health Services is something the end user has control over. I think you need to agree to it in the initial set up.
Good news - I just installed the new firmware R960XXU1AWK4 onto my Galaxy Watch6 Classic, and now the heart rate complication correctly displays the heart rate data!
This proves my point, that it actually was and should have been possible to display this data, that it had nothing to do with Privacy Policies, and that it was in fact a bug.
Great that the devs have finally fixed this!
I noticed that the Sleep complication also now correctly shows its data too, where it wasn’t doing so previously.
That’s interesting - for me, both the [hr] tag and the Heart Rate complication have been working fine for the past few months (with my watch face from WFS), and both accurately using the data from the Samsung Health app and showing a constantly-updated, live heart rate on the watch face. I remember Samsung fixed this a few months ago - there was a thread somewhere here discussing it.
You are correct, while the Heart Rate was never broken, it didn’t sync with Samsung Health or continuous reading. That was fixed with WFS 1.4.13 and the tap action to read the HR was removed.
@GermanKiwi and @r.liechty_SDR the complication of heart rate used to only show a icon (heart nvr the value) but now selecting the heart rate value its shows the icon and the value (which refreshes base on what we set)
As for hr tag it was always countinous refreshing not the base on samsung health settings
@GermanKiwi the fixed was applied to gw 6 in nov. (Not a few months ago, a month ago)
But not gw 5.
Different country/ different watch update comes different times
As for hr tag it was always countinous refreshing not the base on samsung health settings
Just to be clear we are talking about WFS designers complications not the Health app supplied complications
Fortunately for you, you started with a newer version of Watch Face Studio.
The tag [HR] by default would use the Wear Health Services continuous data. for heart rate. Some people thought this was using up memory. It wasn’t. But there was a issue that it did not sync with the Samsung Health settings as expected. This was corrected by an update to Samsung Health app.
In earlier versions a designer set interval was added as a project setting.
In the previous versions of WFS there was a HEALTH tab in WFS Project Settings for how often to check heart rate and another one for the step count goal. The Step count goal now defaults to Sync with device. The [HR] tag would show the last recorded and another tag would show that last recorded time.
There also was a tap action to measure the heart rate.
The release notes for 1.4.13 say
Removed HR measurement including Tag expression, action and interval in Setting.
This topic started with 1.5.7 btw the new version.
So?
Huh? What you mean? wfs designers dont create complication within wfs. We create complication slots right? then select the complication from watch which in turn didnt display any results but only heart icon before our watches was updated. This is health app supplied complications no?
Nothing about wfs designers complications in orignal post @r.liechty_SDR
It did talk about both [HR] tag and heart rate complication (in orignal post he was choosing complication on the watch). So dont think i off topic here. Dont undestand what you mean.
I was explaining or recalling the two issues @GermanKiwi orignally posted
Anyway i think the issue here is this topic is months old and we forgotten what its all about or some watches updated earlier so it seem solved. If i not wrong gw 4 still not updated
For some reason, that complication works fully only on stock watch faces.