5 comments

[ 4.1 ms ] story [ 21.6 ms ] thread
I love the idea of this. Keep perfectly working things from being made obsolete artificially. They should look at the old Nest Protect next.
I immediately recognised many of the commands, both their names and byte values, as exactly the same as those of the Philips PCF8833 from 2 decades ago, an extremely common LCD controller for the tiny displays on mobile phones of the time.

The displays have 320 x 320px square addressable pixels, but only the circular portion is displayed - that is to say you can draw pixels as though they were there in the lower corner, past the radius of the circle, but nothing gets drawn.

Always thought round LCDs (and rounded corners on displays and now GUI windows) were stupid, and this explains exactly why. What would otherwise be perfectly usable pixels are missing, and the panel itself is still square.

Author here, if anyone has deeper questions
I would love to see an open source/Home Assistant native version of the Nest, if the author or anyone else has further ambitions.

IMHO the Nest is hands-down the best thermostat hardware out there. It's a case study in simplicity, elegance, and intuitive UI. I have bought a couple of them, and am likely to buy more in the future should I need another thermostat for any reason.

Google locking it down more and more, and bricking old hardware versions, is a case study in hardware enshitification. For this reason I am very hesitant to buy more.

Pre-ordered! Thanks for the reverse engineering work!