←back to thread

280 points RyanShook | 1 comments | | HN request time: 0.201s | source
Show context
z3ugma ◴[] No.45146109[source]
This is one of the reasons I am working on an enclosure-compatible open-source version of the 2nd gen Nest thermostat. It reuses the enclosure, encoder ring, display, and mounts of the Nest but replaces the "thinking" part with an open-source PCB that can interact with Home Assistant. Nest has been pretty-badly supported in Home Assistant for over a year anyway, missing important connected features.

I've got the faceplate PCB done and working; the rotary encoder and ring working; and the display working but with terrible code with a low refresh rate.

I need to ship at the end of October to beat the retirement date. Plans to get some regular development report-outs and pre-orders are coming quite soon.

It's open source, and uses ESP32-C6 so it can be Wifi, BLE, or Zigbee, whatever software you intend to load onto it.

replies(5): >>45146122 #>>45146565 #>>45147869 #>>45151208 #>>45156001 #
pcl ◴[] No.45146565[source]
What language are you writing in? I recently did some rotary encoder work for a round display on an ESP32, and found the dev kit micro python stuff to be terribly slow. I’ve had good luck with LVGL in C++, and my “ick” feelings about c++ are pretty much totally resolved by a healthy dose of AI chat bots.

Send me an email if you’re interested in more info.

replies(1): >>45148508 #
1. z3ugma ◴[] No.45148508[source]
Oh, good to know. I have been using Toit for all the business logic, but the display can have special handling for performance if necessary. Toit can also adapt into custom C++ code if needed. https://docs.toit.io/language/sdk/display