I have successfully integrated the Nest
Thermostat, but it loses connection to Hubitat just about every 6 or 7 days. I go to the SDM API App and reactivate, Discover, and done. Its reconnected and works fine, but im kinda getting tired of having to do this every week. Is there something im missing here??
Yes, stop using the nest thermostat... (sorry couldn't resist)
Aside from changing to a better thermostat, you could set up HA and then bring it back into Hubitat. If it's a nest 4 you could pair it as a matter device. The SDM can be prickly and unreliable. I have and love my nest Protects but I simply bring those in via an ecolink firefighter because I found the SDM unreliable.
Side note, I use a Honeywell z-wave pro and it works far better than our nest ever did.
2 Likes
Agreed with rlithgow1... I will never buy another product from them as long as I live, but at this point, I'm stuck with what I have because I can't convince myself to replace a working device.
Sorry, can't help you with your issue, but it took me a number of tries configuring and re-configuring the API before I got mine to work reliably. I had given up for months at a time, only to be "inspired" to try again.
1 Like
Word of caution to anyone reading this thread who continues to use Nest thermostats, especially those using them without a C wire. Get rid of them. I had a Nest thermostat kill one of my central AC compressors this past summer, during the hottest week of the season. Stupid thermostat wound up costing me over $8000. I never had an issue with either of my central air systems. My electric company offered a deal on the Nest thermostats, and like an idiot I went for them. Huge mistake.
1 Like
I agree, but unfortunately my Nest also keeps working. I am bringing it in via Home Assistant and it works perfectly. I still have the sdm-api working, but it’s unreliable and gets out of sync with the thermostat. Homebridge actually was a better integration, but I recently started having to restart Homebridge-Nest regularly due to it becoming unresponsive after working without issues for years. My next thermostat will be z-wave or zigbee. It doesn’t need to be connected to the cloud.
1 Like
To me, it seems there is a permission or API setting that needs to be fixed or changed or added.
I don't think I'll be able to really help. Over the years, I replaced my Nest with a Honeywell T6 and relegated the Nest to be a physical interface with no direct HVAC control by tricking the Nest into being a dummy thermostat (I have a thread on that somewhere in the forum). When I got fed up with the inconsistencies of that and internet issues, I finally created a virtual thermostat for the house, installed a sync app, and put the virtual thermostat into all automations. The Nest was then only for WAF and guest convenience. Then I got more $10 Nests through the electrical company and have started doing that in each room.
I'm curious how it killed the compressor? Did it keep turning it on and off in short timeframes? I though the AC had compressor protection should anything try to do that. Did an AC tech say the thermostat killed it?
I had 2 techs tell me it was the Nest thermostat. Essentially running them without a C wire, while fully supported by Nest, is not good for any HVAC equipment. The Nest thermostat for my upstairs zone, was doing 2 things. First, it started short cycling the compressor and second it likely caused the compressor to run in reverse.
I was told that both of these issues are due to Nest thermostats power stealing to maintain their battery when not connected via C wire. The power stealing can cause scroll compressors to start running backwards. It interrupts power for a split second. If the scroll is running at the time, the scroll unwinds under pressure and when the power comes back, it continues to run backwards. Also, the power stealing can cause the AC contactor to cycle on and off, which over time causes damages.
There's nothing that I could have done, short of not installing the Nests to prevent what happened. Thankfully, my 1st floor unit did not experience the same issue. When I had the failed system replaced, I had the tech connect the C wire at each air handler and I now run Ecobee thermostats with C wires.
1 Like
Wow, that is interesting. I would think they would need to add a warning about using their thermos without a C-wire. Google confirms this is a known issue.
- Pulsing the System: To charge its battery when the system isn't running, the Nest sends brief, rapid pulses of power down the call wires. These pulses are intended to be too short to activate the HVAC equipment, but some sensitive systems may attempt to start.
You would think, but they won't. One of the key selling points of the Nest thermostats is that they can be used without a C wire.
Yes, and I was a total dumbass for being swayed by the lure of a nearly free (I just paid for shipping) thermostat and not needing to worry about changing thermostat batteries. Expesnive lesson learned.
"* Lawsuit Status: A 2014 class action complaint (Hagedorn v. Nest Labs) alleged that the thermostat was defective and caused system failure. However, in 2016, a judge denied class certification for similar lawsuits, citing arbitration clauses in the terms of service that prevent class-wide litigation."
Another out for a company because you agreed to their terms of service. I can't believe lawsuits started over ten years ago and went nowhere.
2 Likes
