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

  • CompactFlax
    link
    fedilink
    English
    arrow-up
    11
    ·
    3 days ago

    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
      link
      fedilink
      English
      arrow-up
      11
      ·
      3 days ago

      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
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 days 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
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

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