I want to do the same with my Pro version but I’m stuck. The Fellow app only updates the kettle and doesn’t control it, so I can’t easily capture the commands.
I’ve got a BLE sniffer and Wireshark, and I’m using nRFconnect on iOS to connect to the kettle.
Anyone got experience with BLE reverse engineering who can point me in the right direction? Really want to get this working with my home automation setup.
Ok, semi good news. I figured out how to establish a read and write connection. I’m able to read the temperature, the unit type and how to restart the kettle. I’m also able to change the temperature and change the unit type.
However the most important thing is to be able to toggle between stand-by mode. I tried to read the commands after factory reset and also looking into the commands of the schedule functionality. As that toggles the stand-by into heating. However, I’ve not been successful yet.
Anyone else has idea on how to fetch the standby-toggle?
FYI, pressing the big button to toggle stand-by does not provide any data. The device does not share any commands that I can see with my ble sniffer in wireshark.
I’m starting to think that the physical button might be independent of the BLE system (a direct hardware control), which would explain why I haven’t found a way to toggle standby via BLE.
Update: I can turn on and off the heating. However, I have not figured out yet how to switch the display mode from stand-by to heating. This means when I turn on the heating it still shows the stand-by mode. The other problem is that the command that I found doesn’t consider the set temp and will always boil to max heat.
I’m able to turn on the kettle from standby to heating. However I’m using the ‘schedule’ command approach. The downside of this is that this affects the time on the kettle which is problematic for other reasons. Next to that, to toggle back to ‘stand-by’, the only thing I found is sending the ‘reset’ text command, which works but does disconnect the kettle for a bit.
Overal I’m trying to dissect the schedule command and see if I can find out what byte/value activates the heating mode without affecting other settings.
I’m about a step behind you at the moment. I came to that same conclusion–that the scheduling method is the only way to get around the physical button dilemma–though now that I’m playing with it today, I’m not having the same success sending commands that I was last weekend. Last weekend, I could easily change the unit system, hold time, chime volume, target temperature…
Ok, it was nothing a little coffee couldn’t fix. I’m an idiot. Anyway, I’m working on capturing the previous state of the kettle when I change the schedule to turn the kettle on, that way I can restore the previous schedule after I manage a cup of tea. Still not sure how to go back to standby gracefully though. That’s next on my list.
To go back to stand-by you can send ‘reset’ text command. But yes, that’s a pretty blunt solution. I’m currently trying to throw a bunch of text commands against it and see if anything sticks. Kind of out of option atm
