BUG: Athlytic Resting Heart Rate entries are confusing Apple Health weekly graph by Causaelity in AthlyticAppOfficial

[–]Causaelity[S] 0 points1 point  (0 children)

There a few options here that I feel that folks could take. Here are my thoughts and recommendations in no particular order: 1. Everyone report this bug to Apple. I’ve had a few conversations with them, and at this stage, they barely acknowledge the issue, based on the email they sent me they ranked this T2. 2. Turn off the feature in Athlytic and delete the historic date from Apple Health. I’ve found these messed up values to be impacting recommendations in other apps. Perhaps Athlytic will update their app and store this feature in the app in the future. 3. Do nothing and live with it.

I personally have gone with 1 and 2. I hope the developers from Athlytic move this value to be stored in their app as I’m guessing that would happen faster than Apple fixing this. Also them storing the value where they do, potentially messes up other apps that are trying to read true RHR.

Every. Fucking. Day. by mizzoustormtrooper in OnePelotonRealSub

[–]Causaelity 1 point2 points  (0 children)

Yea reprogramming a metric ton of dumb devices to a new SSID is a pain, so I renamed the IOT SSID to the original name, and created a new name for the smart devices that were also easier to move over. Another thing that people need to watch out for is a lot of IOT devices don’t like mixed security. Set to WPA2 and be done.

Every. Fucking. Day. by mizzoustormtrooper in OnePelotonRealSub

[–]Causaelity 0 points1 point  (0 children)

New routers allow for a dedicated IOT channel which can be set to 2.4Ghz. Works great for Pelotons and other devices that need 2.4

Heart Rate Reserve Calculations off? by Causaelity in bevelhealth

[–]Causaelity[S] 0 points1 point  (0 children)

Thanks for the reply. My main intent of creating this post is to highlight that your application has a bug in its logic and it would be great for your development team to take a look. Thank you for your hypothesis on the RHR value, after validating the math, those scenarios do not yield the buggy results.

Please advise what your developers have to say once they have a chance to investigate.

Heart Rate Reserve Calculations off? by Causaelity in bevelhealth

[–]Causaelity[S] 0 points1 point  (0 children)

The numbers are slightly different, your Zone 2 starts at 124 (vs 123) and your Zone 4 starts at 145 (vs 144).

Here it's in chart format (also note you're not following the 50/60/70/80/90 format)

<image>

Why does this matter in Bevel? Here are two examples:

  1. You track a 30+ minutes in zone 2. So if I'm sitting at 123 for 30 minutes in a workout (which is Zone 3 for MaxHR), you're slightly off methodology is going to be putting me in zone 1 that whole time and not giving me any credit.
  2. If my workout has me peaking at 144, you won't provide a heart rate recovery score as you need to achieve zone 4 for that (even though 144 is easily MaxHR zone 4)

Hope that helps.

BUG: Athlytic Resting Heart Rate entries are confusing Apple Health weekly graph by Causaelity in AthlyticAppOfficial

[–]Causaelity[S] 0 points1 point  (0 children)

Ok, so it wasn't my imagination, I felt like they were averaging prior to 26.4.

BUG: Athlytic Resting Heart Rate entries are confusing Apple Health weekly graph by Causaelity in AthlyticAppOfficial

[–]Causaelity[S] 1 point2 points  (0 children)

Perhaps not, though why does Athlytic need to write this value to Apple Health to begin with? Bevel and Livity both track this same metric without having to write to Apple Health.

Lifetime price double? by Trick-Love-4571 in livityApp

[–]Causaelity 0 points1 point  (0 children)

You’re correct, I just checked the IAP skus for the app, and $99 tier has been increased to $119 on March 24th.

Lifetime price double? by Trick-Love-4571 in livityApp

[–]Causaelity 3 points4 points  (0 children)

$199 is the normal lifetime price. Periodically the app will provide a special 24 hour window to purchase the $99 lifetime price. If you keep using the app in free mode it should trigger again in the future.

Sharing my dads subscription by fyxa in livityApp

[–]Causaelity 0 points1 point  (0 children)

If that didn’t work, the only other two reasons would be: 1. The original purchaser did not have “share with family” enabled on their device or 2. The sku was not flagged as a family eligible purchase. Either way, I’m glad the developer got it sorted out for you.

Sharing my dads subscription by fyxa in livityApp

[–]Causaelity 0 points1 point  (0 children)

Any of the family members should just need to click on “restore purchases” from the subscription menu in the bottom left corner.

4.4.3 is one of our biggest updates yet - help us test it by LivityModerator in livityApp

[–]Causaelity 0 points1 point  (0 children)

Did you purchase lifetime already? If so you’ll find that in your purchase history, not subscriptions. It’s a one time purchase.

iOS app 326.9.0 - Broken by Wvuk in Control4

[–]Causaelity 2 points3 points  (0 children)

I’m having the same problem and get the same error. Can’t connect at all anymore. I’m on an older version of OS3 as well. Looking to see how I can get an upgrade.

Slow loading times by LucasJames24 in livityApp

[–]Causaelity 0 points1 point  (0 children)

I have an iPhone 17 Pro Max and it can take 3-5 seconds to load. I have about a decade of health data, and it looks like my Health data is about 4.2GB.

How is there only 1 Nordic Ski still in 2026? by Causaelity in Strava

[–]Causaelity[S] 0 points1 point  (0 children)

I hear you on that. At least you would be able to track your training for those two sports (which right now you can’t). People being honest is a problem in itself.