The API accesses the website and not the app on your android device. I suspect that the sync between the Fitbit wristband and the app might not be totally reliable since the app also misses the new battery level. I assume that the information available on the Fitbit web page would also be outdated.
Perhaps the sync between the device and the Fitbit app is not executed at all for some reason. Perhaps you could use Automagic to periodically start the Fitbit app to force a sync. Maybe this would also increase the reliability of the battery alert notification.
Fitbit battery monitor
Moderator: Martin
-
- Posts: 96
- Joined: 27 Jul 2014 10:40
Re: Fitbit battery monitor
That sounds like a good idea.
Is still like to use automagic to tell me the battery status, if you think I'll be able to configure the http get request.
Sam
Is still like to use automagic to tell me the battery status, if you think I'll be able to configure the http get request.
Sam
Re: Fitbit battery monitor
HTTP Request could work but honestly it will be so difficult to achieve that it's too time consuming for me to try to build such a flow, maybe it will even turn out to be impossible for some reason, especially the authentication requests could be tricky.
It would be much easier to create a flow in Automagic that reacts to the battery status notification provided by the Fitbit app so I would try to increase the reliability of the app.
It would be much easier to create a flow in Automagic that reacts to the battery status notification provided by the Fitbit app so I would try to increase the reliability of the app.
-
- Posts: 96
- Joined: 27 Jul 2014 10:40
Re: Fitbit battery monitor
Ok thanks Martin for all your help.
Sam
Sam
-
- Posts: 96
- Joined: 27 Jul 2014 10:40
Re: Fitbit battery monitor
Hi Martin,
My solution, as you suggested, to have automagic force the fitbit app to sync is in the flow shared.
I went further and was able to get the value of steps taken.
I'm having a little trouble thou with the execution of a condition.
I make the flow wait until the text Connected appears in a specified area of the fitbit app. When that text is present the flow should come out of the loop and execute the notification.
The problem is that sometimes when the expression becomes true automagic stops the flow and returns an error. I am confused because this is only some of the time.
Perhaps in doing something wrong, as usual... But if you have the time could you please help.
Much appreciated, Sam
My solution, as you suggested, to have automagic force the fitbit app to sync is in the flow shared.
I went further and was able to get the value of steps taken.
I'm having a little trouble thou with the execution of a condition.
I make the flow wait until the text Connected appears in a specified area of the fitbit app. When that text is present the flow should come out of the loop and execute the notification.
The problem is that sometimes when the expression becomes true automagic stops the flow and returns an error. I am confused because this is only some of the time.
Perhaps in doing something wrong, as usual... But if you have the time could you please help.
Much appreciated, Sam
- Attachments
-
- Screenshot_2014-08-15-22-23-22.png (157.67 KiB) Viewed 15243 times
-
- Posts: 96
- Joined: 27 Jul 2014 10:40
Re: Fitbit battery monitor
Oops, i didn't realise you could only post one attachment at once.
- Attachments
-
- flow_Fitbit_Steps_20140815_221555.xml
- (8.09 KiB) Downloaded 771 times
Re: Fitbit battery monitor
Hi Sam,
The flow looks good to me. Unfortunately I can not really test the flow without a Fitbit.
Could you please also post the error you get (or send a log to info@automagic4android.com)? If it's an emergency stop, you could increase the maximum number of executed actions in Menu->Options, switch to 'Specific' and select 200.
Regards,
Martin
The flow looks good to me. Unfortunately I can not really test the flow without a Fitbit.
Could you please also post the error you get (or send a log to info@automagic4android.com)? If it's an emergency stop, you could increase the maximum number of executed actions in Menu->Options, switch to 'Specific' and select 200.
Regards,
Martin