0ff / long-live-sense

As Hello said Goodbye, this repo is in an effort to keep the Hardware alive

long-live-sense

As Hello said Goodbye, this repo is in an effort to keep the Hardware alive

Motivation

Hello, inc. yesterday announced that they'd be shutting down in the foreseeable future. As a first-minute user of Sense, I'd hate to see this beautiful piece of hardware turn into a beautiful paperweight.

This repository should become a central hub to coordinate the efforts of reverse-engineering the following parts that, in sum, make up Sense.

Parts

Sense Server

Sense API

This API is needed to allow for the basic operation of the Sense hardware. We will need to implement a custom server that provides the same calls so that Sense keeps running.

Security

Sense uses TLSv1.2 for all connections, except for time.hello.is. All communication is encrypted with a certificate for *.hello.is which let's me believe that there's only one certificat in the actual Sense hardware for certificate-pinning. Use of cert pinning was confirmed using a MITM proxy, this means we are not able to simply capture the traffic between Sense and the Sense API.

Server URLs

On startup, Sense connects to the following servers:

• time.hello.is (plain http) where it POSTs some protobuf data and receives data in return
• messeji.hello.is (TLSv1.2) this server seems to be used often, but not as often as the next one
• sense-in.hello.is (TLSv1.2) this is where most of the communication seems to happen

Todos

• Connect Sense via MITM Proxy to the server
• Confirm whether or not Sense uses Certificate Pinning: it does :(
• Document used Endpoints and existing responses
• Mock API

App API

This API is consumed by the Sense App and allows reading stats and setting up alarms.

Todos

• Connect Sense App via MITM Proxy to the server (see References)
• Document used Endpoints and existing responses
• Mock API

References

• https://github.com/fredkelly/sense-client
• https://github.com/chendo/sense-api.cr

Sense Firmware

These are the bits and bytes that power the Sense Hardware. At the very least, we will need to figure out how to make Sense connect to a custom API URL.

Todos

• Fetch existing firmware from the Sense Server
• Figure out how to change the API URL
• Figure out how to update Sense with custom firmware

Sense App

Contributing

This project will live through contributions, so please, if you have anything to add - fork it, submit a PR and be part of it.

long-live-sense's Issues

Contact with James Proud (www.sense.is)

Hey there,

I just contacted James Proud via E-Mail and he is willing to change DNS-entries for sense.is if we provide him with details so we can potentially start server communications. As I do not have really great expertise, I'd like to ask you wether this would be of any help.

Thanks and let's hope we can get this great piece of hardware to work again!

Lucas

Source code released

This might help :)
https://github.com/hello