FitbitSeer, a Fitbit plugin for HS3 - Need beta testers

[Moskus]

FitbitSeer 0.2.0.0 is out now! Check the first post!

[Moskus]

No sadly, sleep is only updated after the sleep is stopped. There's nothing I can do about it, but I would also like a sleeping/awake status device.

[wkearney99]

Well done, Moskus!

Ideally it would be awesome if there is a single device stating whether the user is awake/not cheers

Agreed, nice work. We have two chrage hr bands and an scale. I'd be glad to test betas.

I'd also like simple ways to deternine wake/sleep states.

[LeoS]

Well done, Moskus!
Btw i'm late to this party and j'm very interested in joining (right now wearing Basis Peak, looking to move to Charge HR maybe)... and i have one question:

Ia it possible to determjne whether the user is awake or asleep? (With the 5 minutes update delay). I can see there are devices stating when the user falls asleep and when they woke up, is that generated on the fly and can we act upon that?

Ideally it would be awesome if there is a single device stating whether the user is awake/not cheers

[Moskus]

A little more internal testing now, and we're ready for the next "public" beta!

However, there are a few caveats:

• I think you need to delete all existing Fitbit devices. I can't make it work while upgrading, so I apologize deeply to those of you that have huge HStouch projects using FitbitSeer. (But don't delete your devices quite yet! I'm trying something...)
• OAuth2.0 is weird, and I have to specify a callback URI to get my "Fitbit application" approved. That's a problem, because you all have your own servers! A workaround is in progress.
• As OAuth2.0 for Fitbit is so "very super secure", tokens doesn't last longher than maximum 8 hours. That means that if FitbitSeer is stopped (for one reason or another) for more than 8 hours, you need to re-authenticate all accounts.

But I do have some good news too.

• OAuth1.0a didn't permit me to get heart rate, but now I should be able to.
• In the new Fitbit.NET library there are new kinds of data available too, like locations and settings. I'm not sure I'll add it all, we'll see.

At the moment though, the authenciation is the most important thing, so we'll see how that works.

[Moskus]

Thanks, I'm going to need beta-testers. I've found a way to authenticate, but 1) it needs testing and 2) I don't know how long an authentication will last (until the auth. token expires), so we'll need to figure that out.

[codemonkey]

Happy to beta test for you.

[TechHA]

Yup, going to miss this while it's gone. It's been a nice addition to the touch screen info page...my wife and I competing to see who has more steps each day.

[JimBob]

Thanks for the update. We all really appreciate the time your putting in to this.

Tony

+1

[codemonkey]

Thanks for the update. We all really appreciate the time your putting in to this.

Tony

[Moskus]

... and there it is: Gone.

But luckily, after bother people at the Fitbit boards, I got help from the Fitbit.NET developers directly! Much better! I hope to update the plugin soon, but it might take a few days (or even a week).

[cbabkirk]

Messages

Hello MOSKUS,

The messages thing is not urgent but one of those "nice to have if possible" things.

Certainly the auth conversion should be your focus. Don't beat yourself up over an Aug 1st deadline. We all appreciate what you have accomplished so far so take a deep breath and take the time needed so you will be satisfied with the result.

I agree on the messages to the watch version but for those with the Charge and earlier models, we must get by on these for now. I am satisfied with what the Charge gives me and probably will be for quite awhile before I swap that out for something fancier.

[Moskus]

I was wondering if it is possible via the API (or other) to send the FitBit messages? They would, of course, be short unless there is a scroll capability. I know that currently when someone calls me, the number is somehow (bluetooth) communicated from my phone to the FitBit. I could see a use via the plugin to send HS device status or conditions to the FitBit much like the HS speak function is used now via an event. Perhaps name of a zone that has faulted in my security system. I don;t always check text msgs sent to my phone and sometimnes don't have my phone on me but the FitBit is worn like a watch; always on me.

I'll see about this. It might be possible, but I think that Fitbit should add notifications to their watches instead.


And I'm still deep in frustration about the OAuth 2.0 conversion. I won't make it to August 1st....

[cbabkirk]

FitBit Messages

I was wondering if it is possible via the API (or other) to send the FitBit messages? They would, of course, be short unless there is a scroll capability. I know that currently when someone calls me, the number is somehow (bluetooth) communicated from my phone to the FitBit. I could see a use via the plugin to send HS device status or conditions to the FitBit much like the HS speak function is used now via an event. Perhaps name of a zone that has faulted in my security system. I don;t always check text msgs sent to my phone and sometimnes don't have my phone on me but the FitBit is worn like a watch; always on me.

[Moskus]

This is a great idea. Very Well done.
This is something I am interested in although need to get one! But will gladly test too.
Do you currently have an idea which fitbits it supports and which ones it does not? (I don't own one yet, sorry if I have misunderstood how it interacts)
I can see from the website: Zip, One, Flex, Charge, Alta, Charge Hr, Blaze, Surge, Aria (Scales)

Is this something you plan to put in the BETA section of the plugins?

Really nice work

The plugin does not read directly from the Fitbit devices, it just gathers data from the Fitbit database, so any device should work. The devices have some differences though. For example, some support heart rate logging, others don't. Some support stairs climbed count, others don't.


I'll put it in the updater eventually, but I've known for a while now that at some point I had to update to OAuth2. I just didn't know it was so soon...