RSS

OpenYou hasn't really been a thing since 2012, but the project never
really got a proper closure.

Fixing that now.

I'll be archiving all of our repos (outside of
emokit, which is now community
maintained) on github. The website and repos will stay live as long as
I'm still using services that make it easy to keep them up.

If you're interested in what I'm up to, my personal site is at
kyle.machul.is.

Please do not contact me about bugs/issues on the open source OpenYou
projects, as I don't really work in the open source health tech space
anymore and do not have time to resume maintenance of them. Most of
them refer to hardware that is no longer produced, and I do not have
time to update them to new hardware. If you are interested in taking
over maintenance, please feel free to fork them, and if you would like
me to add links to the forks, feel free to reach out via one of the
contact methods on my personal site.

I hope the project was useful while it existed, and look forward to
seeing how others hack health tech in the future.

It appears Zeo, which declared it was shutting down in March, has
taken a scorched earth policy in terms of developer firmware and
libraries. All zeo websites are gone, and the sourceforge has been
cleared out. I still had versions of the firmware and raw data API
kicking around on my harddrive, and managed to fork the android
project before the github account disappeared. I've thrown all of this
on the openyou github account.

Since most developers are used to looking for these kind of libraries
on github, that seemed the best place to store them right now even
though I certainly have no plans of doing any upgrades to them. The
master branches will most likely stay as copies of the final versions
so that others can have a reliable base to fork from.

I've finally gone ahead and moved most of my health driver repos, as
well as the repo holding the openyou.org blog, to the
OpenYou Organization on github. Over an indeterminate amount of
time in the future, I'll be flipping the READMEs, and possibly the
licensing, to reflect OpenYou also.

The hope here is to get more community involvement in drivers for
health equipment. Up until now, the repositories have lived on
my personal github account, which, while great for my coderwall
badges, means that I'm primarily responsible for support. Ask anyone
who's emailed me actually asking for support, and you'll find out
how well that's gone so far.

While I do get and try to service pull requests on my drivers,
sometimes it takes me weeks or months, or else I do things out of
order and end up conflicting people's patches. My hope with moving
these to an organization setup is to allow developers that are
interested to help out with maintenance of these projects.

I'm already starting to see this in action, as there's now a developer
on the emokit project working on porting the C library to HIDAPI.
I'd like to get battery power and signals in soon too. There's a bunch
of stuff to be done on things like libfitbit and libomron
too.

Moving this stuff forward shouldn't depend on the amount of free time
I have. If you're interested in becoming a developer with commit
rights on one of these projects, file an issue in the project you're
interested in working on.

libfitbit

I'm still seeing pull requests to libfitbit! The library has become
somewhat more stable, though we're still plagued by issues with the
base station locking and not communicating until it's
unplugged/replugged. I'm not sure if this is an issue with the fitbit
base station or with my python ANT library. It's something I hope to
look into soon.

I'd also like to get a Fitbit Ultra at some point, to get altimeter
readings into the system.

emokit

As of today, Emokit for the Emotiv EEG sees a major update, at least
in terms of protocol documentation. We now have access to the sensor
quality levels and battery power levels, the two portions we'd been
waiting on in order to finish the library and release v1.0. I've
created
a protocol document that's available in the github repo,
and would like to get this pressed into code ASAP.

In less new-featurey but important maintenancey issues, I'm also
planning on moving the library to HIDAPI, which should solve a lot of
the crossplatform issues reported in the repo. I'd also like to finish
the OpenVibe bindings, which I got started but then fell off on due to
above mentioned circumstances.

libfuelband

I've been permaloaned (Sorry Barry I swear I'll get it back to you) a
Nike Fuelband to work on. I did some initial proof-of-concept code a
while ago, which found some dates and what I believe are steps
recorded down to the second (the highest granularity I've seen in a
consumer pedometer thus far).

The unfortuate news is that there seems to be no good way
to access the LED array, which was my original goal. However, the
factory wipe mechanism looks like it may be a firmware reload, which
would be super handy for possibly building my own LED access
functions.

So, that's it for now. I'll hopefully be posting more about some of
the patent battles in health technology this year soon, as things have
really been heating up.

Contrary to evidence otherwise, I'm not dead, just got busy with life
outside blog/qs land for the past 8 months. Am now working on
returning to former productivity levels, starting with a new release
of emokit and openvibe bindings ASAP, then maybe taking another look
at libfitbit and the fitbit ultra.

Before that's all done though, I'll be speaking at the
SF Data Mining Meetup March 6th at the Trulia offices. It's me
and one of the people from Basis. I think it may already be sold
out, but watch the page to see if more spots become open.