IFTTT sleep duration trigger not working

[Mellifluous]

Attempting to set up an IFTTT applet that sends a notification email if I'm asleep longer than 11 hours. The applet keeps firing and failing with the error message "There was a problem with the trigger. "

I've tried deleting the applet, deleting my Fitbit connection in IFTTT, then recreating both. No change. Error keeps persisting.

[Gordon-C]

Hi @Mellifluous 

I'd like to try to reproduce the behavior that you're seeing.   Would you please provide me with detailed steps of how you set up the IFTTT routine?   Please provide the services and triggers that you selected in the "IF" and "THEN THAT" steps.

Thank you!

Gordon

[Gordon-C]

Also, I did some testing and was having problems getting my IFTTT widget to work with sleep.   After some investigation, it looks like my consent to IFTTT got stale.   So, I re-authorized consent and it worked.    Please try these steps

1. go to https://ifttt.com/fitbit
2. click on the "settings" button
3. you should see your name listed.   Click the "Remove" link.
4. Go to https://www.fitbit.com/settings/applications.   You might need to log into your Fitbit account
5. Check to see if IFTTT is listed.    If it is, press the "Revoke Access" link next to IFTTT and confirm the action.
6. Go back to https://ifttt.com/fitbit
7. Press the "Connect" button.
8. Select the scopes that you want to share with IFTTT and press "Allow"

Now, recreate the IFTTT trigger and see if it works.   If it doesn't, please provide the steps to create your trigger and requested above.

Gordon

[Mellifluous]

Thanks Gordon, I've reset both connections and will see how it does.

The applet is very simple, the only services are Fitbit and Email. The Fitbit "Sleep duration above" trigger with "11" for the target hours, and the native Email "Send me an email" action with the subject "[Name] has been asleep for more than 11 hours" and the body "[Name] has now been asleep for more than 11 hours. Chances of unavailability for the rest of the day are high."

[Mellifluous]

Hey @Gordon-C , sorry for coming back to this so late (had to have enough use cases to make sure what was going on). The trigger worked about twice, and then returned to being broken:

It's attempting to run every day, so it seems strange to me that the authentication would grow stale between one day and the next.

[Gordon-C]

Hi @Mellifluous 

That's strange because my connection for activity daily summary has been working since we last chatted.   Although, it could be the applet.   When the applet fails, are you sleeping more or less than 11 hours?   I don't sleep longer than 11 hours so I'll try to reproduce the problem using a sleep duration that represents my sleep pattern.

Gordon

[Mellifluous]

Hi @Gordon-C 

It worked for the first day (when I slept 11+ hours), worked the second day (didn't trigger, but no error) when I slept less than 11 hours, then broke (threw an error) the third day (when I slept less than 11 hours) and remained broken past that point, regardless of whether I hit the threshold or not.

[Mellifluous]

Hey again @Gordon-C , it just went back to firing again today! I'm going to go back through the other days where I hit the sleep limit and it didn't fire to see if there's a difference between today's record and the other ones. It might be that it isn't triggering if Fitbit thinks I'm awake/too restless during the sleep period?

[Mellifluous]

@Gordon-CWent back through my sleep logs starting March 21 (when I most recently reconnected the applet) and got the following info on days where I passed the 11 hour limit:

• March 24 - 17h 53m: Applet fired (3h 1m/14% awake)
• April 2 - 15h 38m: Didn't fire (2h 19m/13% awake)
• April 3 - 13h 3m: Didn't fire (2h 18m/15% awake)
• April 21 - 11h 44m: Didn't fire (1h 44m/13% awake)
• April 25 - 11h 48m: Didn't fire (1h 58m/14% awake)
• April 28 - 13h 19m: Didn't fire (2h 50m/17% awake)
• April 30 - 19h 4m: Applet fired (3h/14% awake)
• May 7 - 12h 42m: Didn't fire (1h 57m/13% awake)

Some of these times were within the same day while others crossed over the midnight mark to the next day. I can't seem to find any patterns in which ones go through vs which ones don't.

I also haven't received any errors or successful triggers since April 30 at this point.