1.0.11

Eight Sleep made a backend change to require a client_secret for the OAuth2 authentication. Thanks to the other users (@mwalling, @MarcCA, @adamksmith, etc.) who were able to debug and find that there is a single client_secret being used by Eight Sleep. If the client_secret/client_id is not set manually, then it defaults to the values that are known to work for now.
However, this is not guaranteed to continue to work as Eight Sleep may change the OAuth2 behavior at any point. At that point the best way to get the client_id & client_secret will be to use a MITM, and then set the values manually when setting up the integration.

Issues fixed in this release:
#26
#25