Nest Integration that NATIVELY includes functionality of Homebridge nest integration

Third party integrations
1

I am currently using both the built-in Nest Integration and the custom Nest Protect integration but even the two combined lack the full functionality of the Homebridge-Nest integration.

Specifically:

  1. Nest Integration provides a solid interface to the climate functionality but the temperature recorded in the temperature entity varies depending on whether the thermostat is set to the thermostat or a remote sensor.
  2. Nest Protect integration allows one to read the temperature of a remote puck but cannot access the temperature at the thermostat.

If your thermostat is always set to use the thermostat itself for the temperature, then everything is OK since the Nest Integration reads the temperature at the thermostat while the Nest Protect integration read the temperature at the remote puck.

HOWEVER, if you ever use the remote puck to control the temperature then:

  1. You lose access to the temperature at the thermostat
  2. You have duplicate entities reading the remote puck

Even worse, if you switch-back-and-forth, then the history record of the Nest Integration temperature is some amalgam of the temperatures at the thermostat and the remote puck.

I would like to have separate entities to track the distinct temperatures at my thermostat itself vs. the remote puck.
It seems like the Homebridge-Nest integration has the ability to do this.
But that would then require adding a third nest integration plus a Docker container in which to run Homebridge – all just to get simple and distinct temperature readings from all my Nest endpoints.

This seems really ridiculous!!!

It seems like the Homebridge Nest integration works by using the Protobuf protocol rather than the REST or SDM APIs.

Is anyone working on a native version of a Nest Integration that would be able to access all the Nest features that the Homebridge integration exposes without having to run a full Homebridge server?
Said another way, would it be possible to “port” the Homebridge Nest integration natively to Home Assistant so that it can access the appropriate Protobuf protocols directly?

It would be really great if all this complexity could be hidden from the user and the requisite entities grouped under a single device would be automatically populated for each Nest thermostat and associated pucks.

It is amazing to me that something as trivial as a thermostat sensor is so hard to read in HomeAssistant – something that one would think should be so trivial…

2

Hello!
The current Nest integrations in Home Assistant lack the ability to provide distinct temperature readings for the thermostat and remote puck simultaneously, a feature available in the Homebridge-Nest integration likely due to its use of the Protobuf protocol. This necessitates running a separate Homebridge instance, which is frustrating for users wanting simple and accurate temperature data. While a direct “port” of Homebridge-Nest to a native Home Assistant integration using Protobuf is complex, it’s a potentially achievable solution that would eliminate the need for a separate server and streamline the user experience. Engaging with the Home Assistant community to voice this need can help drive development efforts in this direction.