I appreciate the drifting semantics of names, but Wi-Fi and AWS are really not the same thing.
My cynical take has always been that this is their justification for charging a subscription fee for features that shouldn't require one (e.g. an alarm clock or the ability to change the temperature on a schedule).
There are a couple of open-source projects around jailbreaking it:
- Probably the original attempt: https://github.com/bobobo1618/ninesleep
- The much more polished and usable application built from that starting point: https://github.com/throwaway31265/free-sleep
The latter is even able to do the signal processing needed for heart rate on-device.
We work in the neurotech/sleeptech space (https://affectablesleep.com) and have a subscription service as well. We know when your subscription runs out, and have built the device to run completely offline, and even have a buffer of days if it can't connect to check you have a valid subscription.
Say what you will about subscription services, but being actively hostile to your user base because the device can't connect to a service on one night, seems like very poor planning.
I actually quite look up to 8Sleep as one of the better companies in this space, so I'm surprised this happened to them.
Interesting. So if your product cannot connect to the cloud/subscription, but still works, why is there an issue with it working fully locally?
I don't think we have an issue, 8Sleep had an issue.
Discussion: https://news.ycombinator.com/item?id=45658056
And update: https://news.ycombinator.com/item?id=45677351
jdenning•3mo ago