IdrisCytron

/*
   Project: Arduino GSM GPS Device Tracker
   Board: Maker Uno
   GSM: SIM7600E
   GPS: SIM7600E
   Library:
   - Adafruit FONA
*/

#include <SoftwareSerial.h>

ali1234

#!/usr/bin/env python

#Connecting to: 08:7C:BE:8F:3C:FB, address type: public
#Service <uuid=Generic Attribute handleStart=12 handleEnd=15> :
#    Characteristic <Service Changed>, hnd=0xd, supports READ INDICATE 
#    -> '\x01\x00\xff\xff'
#Service <uuid=Generic Access handleStart=1 handleEnd=11> :
#    Characteristic <Device Name>, hnd=0x2, supports READ WRITE 
#    -> 'Quintic BLE'
#    Characteristic <Appearance>, hnd=0x4, supports READ 

katemonkeys

Top Six Things You Need To Know About The Withings API*

*where “you” is probably a developer, or at least a strange user

I should preface this by saying that I got a Withings Smart Body Analyzer for Christmas last year and I’ve been generally happy with it. It purports to be able to take my heart rate through my bare feet and that seems not to work for my physiology, but overall I’m a fan. If if their Wikipedia page is to be believed they are having a pretty rad impact on making the Quantified Self movement more for normal people and they only have 20 full time employees. Also they try hard to use SI units, which I can get behind. Anyway, on to the rant.

I originally called this post “Everything wrong with the Withings API” and I meant it. For every useful field I can extract from their “award winning” app, I have spent an hour screaming at the inconsistencies in their implementation or inexplicable holes in their data