Reverse engineering 'The Handy'

I want to create a virtual ‘The Handy’ device to understand and provide an open-source protocol aimed at development. To achieve this, first pairing has to be reverse engineered. The companion app connects to the device via bluetooth and pairs it to your router. Then the device connects to the server independently. The communication between the device and the server has to be understood. The server and ‘The Handy’ use HTTPS. So communication is encrypted eliminating any approaches to that as a middle-man. Instead the firmware has to be reverse engineered. However firmware updates are sent from the server to the device directly. It is still unknown, if the device ships a private key. If so, without it, a virtual device can not communicate with the server. The private key may not be readable from the device.

Are there any efforts to reverse engineering ‘The Handy’?

Some time back I regreased my handy and found pinouts: Handy Pinout?

I never messed with it due to lack of time but that could be a start to investigating.

Hmm, not much of a hardware guy. Is there maybe a link to the firmware of the handy?

We have a virtual Handy system that we use internally. I will add it to the road map to make this open for other developers.

An alternative is to just set up 20 Handys in the office with a camera on them and allow for devs to take control of them.

1 Like

@handyAlexander pease send @soritesparadox simplified models of handy1/handy2 to add to GitHub - ayvasoftware/osr-emu: An emulator for open source strokers. package

(used in https://www.ayva-stroker-lite.io/ )

ik it doesn’t really fits there but I don’t really want to use two different renderers for same purpose

Ok.

NB! it is on the roadmap, not a priority, so cannot give an excact date.