I have a Meditation-Minutes goal that is unfortunately not working so well due to technical issues
I meditate using Headspace and the Breathe app on the Apple Watch
The data from both of these apps get pulled to Apple Health and labeled as “mindful minutes”
The Beeminder iPhone app pulls data from my Apple Health stats and sends it to this “meditation” goal.
The problem is that the Apple Health data is not being correctly transferred to Beeminder.
I’ve done several tests and I’m confident that the issues happen when I meditate several times a day and Beeminder goes nuts and doesn’t log everything correctly.
I’ve already reported this to @shanaqui and @Andy_Brett but I’m anxious to be able to trust my Beeminder system wholeheartedly again.
Does anyone have any creative idea of how to get my data from Apple Health being transferred to any other app/system and then have this app/system sending the cumulative meditated minutes to Beeminder at the end of the day?
I have a bunch of goals fed this way. Usually I have the shortcuts set up to be triggered manually but in your case maybe you could set up ‘automation’ to run the ‘log my meditation for the day’ shortcut once per day at a set time.
I’ve already invested an hour on this but I didn’t make much progress @ubdhtvqeakj9 , would you be so kind and help me out by sharing with me your Shortcuts (especially if they pull Health Data)and also how you set it up on Beeminder?
(since I’m not a dev and relatively unfamiliar with APIs, I was thinking of sending the Mindful Minutes to IFTTT every night and connect my goal to iftt instead of receiving the data directly from the shortcut. I know… it’s not the most efficient way but sounded like the easiest to me now. If you send the data directly to Beeminder, I’d love to learn how you did it!)
I’ve put in at least 3 hours on it already but I’m having troubles with pulling the Mindful Minutes data using the Shortcuts app.
I’m following this guy’s tutorial on how to create a shortcut that pulls Health Data.
I’m following his steps on my Shortcuts app and It works perfectly with steps, sleep, heart rate… all different sorts of data BUT the godamned mindful minutes.
Doubtless you’ve thought of this, but before adding the complexity of looping in Zapier, make sure using the Show Notification step in Shortcuts that you’ve found the data on device. That way, you can quickly cycle through the different available fields and figure out what’s got data.
In the case of Mindful Minutes, the data seems to be in the Duration field rather than the Value field. Testing with a manually-entered datapoint in Health, five minutes is shown as 5:00 in my notification of the duration field.
Ah, thanks for the tip, @philip. That worked for me.
A ‘find health samples’ followed by
a ‘get details from samples’
(Previously I was using just the find samples and not also the get details. The output appeared blank but would contain more blanks when including a wider search range, so I should have know something was being found.)
Was able to pull out the almost 18min mindfulness session (here 17min and 37sec).
And now that I look more closely at my own mindfulness goal, I see a day where there were two sessions on a single day and the value of the datapoint created by the official Beeminder app is off, showing, in this case, fewer minutes than available in Health.
The value that Shortcuts sends is exactly 1:00, with the “:”
When IFTTT sends this value to Beeminder, it causes an error to occur. How do you convert minutes to numerals or even delete everything that comes after the “:”?
Can I do it on Shortcuts level? IFTTT level? How? (I told ya, I’m a newbie)
Once I get this done with IFTTT, my next step will be getting rid of IFTTT and sending the data directly to Beeminder
Someone commented on my personal blog and his/her comment led me abandon IFTTT sooner than later.
I’m now able to get data from my health app and post directly on my Beeminder goal!
The problem I was having with IFTTT’s value not being recognized by Beeminder is now gone.
I suspect that by setting the “value” field as a number and sending directly to through the API fixes this. IFTTT most likely sends this as a string/text and when the value includes “:” it breaks.