REVIEWS / THERMOSTATS / OWNER INSIGHTS
🦉 WE READ 283 OWNER COMMENTS
Google Nest Thermostat E: what owners actually say
Owners are furious that Google has cut cloud functionality on older Nest thermostats, turning a once-loved device into a case study for IoT distrust.
What owners complain about
- Killed cloud functionality COMMON
Google ended support for older Nest thermostats, causing them to lose remote control, app access, and scheduling features — not just updates. Owners report the Google Home app already stopped working for them 6+ months before the official cutoff.
- Forced Nest-to-Google migration lost features SOME
When Google forced users from the Nest app to Google Home, the replacement app couldn't perform half the functions the Nest app did. Both apps still exist because of user complaints, creating a fragmented experience.
- No local API or offline control COMMON
Owners are angry there is no local API, meaning the device is entirely dependent on Google's cloud goodwill. Multiple users demand Google be legally required to provide local control or open-source the tech when they pull support.
- Abandoned HomeKit support post-acquisition FEW
One owner invested $3k in Nest gear expecting promised HomeKit integration, which was abandoned after Google's acquisition. They describe it as the biggest home tech mistake they made.
- Promised energy savings never materialized FEW
One owner of ~10 years reports never seeing any energy savings from the learning features, only 'bullshit offers that allowed the electric company' to access their usage.
What owners love
- Quick, easy installation
Owners report installation taking as little as 5 minutes with the device working great immediately after setup.
- Built-in presence sensor on Nest E
Unlike the Ecobee3 Lite, the Nest E has a built-in motion/presence sensor that adjusts temperature based on occupancy without needing to buy additional sensors — a feature that wasn't obvious to buyers comparing models.
- Learning model handles complex HVAC setups
Owners who upgraded to the Learning Thermostat report it successfully controls humidifiers and other accessories the basic Nest couldn't manage, after running a new wire.
Surprising patterns
- A bounty of over $12,800 has been crowdfunded by owners for anyone who can get the bricked Nest thermostats working with Home Assistant, and there's a mass arbitration filing against Google over the issue.
- An open-source project (sett.homes) exists to physically replace the internals of Nest thermostats, and some owners have built their own DIY HVAC controllers using ESP32 boards and relay switches to bypass smart thermostat ecosystems entirely.
- Multiple commenters who found Nest thermostats at garage sales for as little as $5 note the previous owner sold it because it was 'too complicated' — a stark contrast to the enthusiasts who consider the device's core problem to be Google's cloud dependence rather than usability.
WHO SHOULD SKIP IT
Anyone who expects a thermostat to keep working as purchased for more than a decade, or who values local control and open APIs — these owners overwhelmingly report the device's lifespan is entirely at Google's mercy.
Synthesised from 283 real owner comments across 4 platforms. Every point is grounded in the comments — no marketing, no AI guessing. How we do it →