3 ms·
It's interesting to see the discussion here focusing mainly on "open from the producer/manufacturer" side, when what I think is the really important point here
by userbinator 6y ago
It's interesting to see the discussion here focusing mainly on "open from the producer/manufacturer" side, when what I think is the really important point here is that "opening from the consumer/user" side can be easy and empowering: companies and services will come and go, but your ability to take control effectively depends only on your willingness to discover and explore.
I avoid a lot of "smart" products in general, but feel comfortable with working on the equipment I do have --- whether it's maintenance, repair, or modification --- and I think that's the most important thing to keep in mind; to not be scared of treating things as anything other than mysterious black boxes. It seems that a lot of people treat "reverse engineering" as some equally mysterious and imposing idea, when it's really just about problem solving or figuring out how something works.
Also, I don't think the RPi is necessary here; the bike is a Bluetooth device, so any computer with a Bluetooth interface can receive its data and process it. I'm not an RF expert, but rebroadcasting BT seems like it would create more interference.
- ohazi 6y ago> your ability to take control effectively depends only on your willingness to discover and explore. This should be the limiting factor, and this is often the case when a product was designed sensibly and the interface just wasn't documented. Reverse engineering a device like this is relatively straightforward. But more often, companies deliberately obfuscate, encrypt, or booby-trap their interfaces in order to actively prevent reverse engineering, and this is the reason for the frustration you're seeing in the other comments.
- usrusr 6y ago> Also, I don't think the RPi is necessary here; the bike is a Bluetooth device, so any computer with a Bluetooth interface can receive its data and process it. I'm not an RF expert, but rebroadcasting BT seems like it would create more interference. The rebroadcasting is done because the goal was to get the data into a proprietary piece of software that expects data to come in over Bluetooth. And rebroadcasting will actually be just fine on the air medium because right after receiving is exactly the time when the bike won't send another message. The RPi is complete overkill of course, a tiny $3 nRF52 module could do that job just fine.
- noisy_boy 6y ago> your ability to take control effectively depends only on your willingness to discover and explore. Lots of folks have additional constraints of time due to family/other responsibilities etc. I can afford to spend an hour or two if the API is open from the manufacturer's side to write a script or setup a simple service; I definitely cannot afford to spend time on packet sniffing or such low-level reverse-engineering.