this post was submitted on 04 Nov 2025
114 points (99.1% liked)

homeassistant

16877 readers
8 users here now

Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 2 years ago
MODERATORS
 

They found a way to install a custom firmware and working toward getting home assistant local control. Definitely something I'm following now

top 14 comments
sorted by: hot top controversial new old
[–] superglue@lemmy.dbzer0.com 22 points 2 weeks ago (2 children)

This really needs to run locally for me to even bother. I'd rather just go get a new thermostat with proper local support instead and be done with this nonsense

[–] Damage@feddit.it 14 points 2 weeks ago

That's what HA is all about, so, yeah, that's the goal

[–] AreaKode@lemmy.world 9 points 2 weeks ago

Yeah. Self-hosted option, or I'm not going to even bother.

[–] besmtt@lemmy.world 21 points 2 weeks ago
[–] CompactFlax@discuss.tchncs.de 11 points 2 weeks ago (1 children)

Definitely very cool.

It is odd that they went to a “different” cloud instead of making it full local. It seems like that would be more work. Local control of iot is critical.

But I wonder if they dumped the firmware, edited the URLs, and reverse engineered the google API, and made their own.

[–] ThePantser@sh.itjust.works 11 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

That's exactly what they did.

The custom firmware flashes the device with modified bootloader and kernel components that redirect all network traffic from the original Nest/Google servers to a server we specify. This server hosts a reverse-engineered replica of their API, allowing the thermostat to function independently while giving you complete control over your device data and settings.

By intercepting the communication layer, the thermostat believes it's communicating with the official Nest infrastructure, but instead connects to the NoLongerEvil platform. This approach ensures full compatibility with the device's existing software while breaking free from Google's cloud dependency

[–] CompactFlax@discuss.tchncs.de 5 points 2 weeks ago* (last edited 2 weeks ago)

Well look at you reading TFA! (☞゚ヮ゚)☞

That’s why the source is locked down. It’s a copyright grey area and IANAL but - good luck!

[–] borth@sh.itjust.works 1 points 2 weeks ago (1 children)

Maybe the next step would be to have that replica API run on HA or another module and redirect the traffic locally instead.

[–] KairuByte@lemmy.dbzer0.com 1 points 2 weeks ago

Fairly certain that’s the entire idea already.

[–] cwisch@midwest.social 4 points 2 weeks ago (2 children)

I looked through the GitHub details and it talks about connecting the thermostat via USB to flash it. I really only have Chromebooks at home and I'm not sure how well that would work on Linux container.
https://github.com/codykociemba/NoLongerEvil-Thermostat]

[–] just_another_person@lemmy.world 4 points 2 weeks ago

Should be a way to work around that.

[–] giacomo@lemmy.dbzer0.com 2 points 2 weeks ago

you should be able to give a container access to the usb.

[–] EarMaster@lemmy.world 3 points 2 weeks ago (1 children)

There is also iMike78/nest-mini-drop-in-pcb which - although through putting in a new board - will hopefully make the Nest Mini speaker HA Voice compatible.

[–] glimse@lemmy.world 2 points 2 weeks ago

That is really cool. I've always liked the design of the nest