FitbitSeer, a Fitbit plugin for HS3 - Need beta testers

[JimBob]

Ahh ok, scratch that.

I restarted the plugin again and it is now working.

Thanks.

[JimBob]

I've just installed 0.2.0.0 but when I enter my new authentication code nothing happens, no errors, no further info displayed. There are no messages in the HS log.
Any ideas?

[codemonkey]

I would agree, everything appears to be working as it should.

[TechHA]

So far, so good. Easy upgrade. Using the new version with two accounts and everything is running great! Thanks!

[Moskus]

Ah, I like your idea better. Cool!

I'd call it a refinement of your idea...

[codemonkey]

Ah, I like your idea better. Cool!

[Moskus]

In the future it might be nice to have the devices managed solely from the configuration page rather than from a root device.

I see your point, but I don't agree.

All the account information is stored in the root device. The beauty of that is that the devices are much easier to manage. You don't need manage some settings file or stuff like that. You can move the devices around and rename them without worrying.


BUT that being said. I can of course show all accounts in your system on the configuration page, and I can link directly to the config tab on the root devices. It's a great idea, I'll add it soon.

[codemonkey]

Figured out what I did. If you are upgrading from a previous version then you really do not want to do anything in the configuration part of the plugin. Just go to the root device for each Fitbit device you have, click on the name to get in to the device settings, then click on the Fitbit tab. there is where you reauthenitcate. The configuration page does not show a list of connected devices so you may be led to believe that they are gone. They are not. In the future it might be nice to have the devices managed solely from the configuration page rather than from a root device.

[codemonkey]

Not sure what I did wrong but I ended up with 4 account root devices (I only have one device connected.) The instructions on the front page are a bit scattered due to keeping some of the info from version one. I think I would recommend a bit of a re-write. Also the version for the plugin still shows 1.x

Tony

[JimBob]

That's great, thanks. I'll give it a go over the weekend.

[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.