I don't think it will work -- as it used a google-owned backend "project" sdm-prod in GCP...
Changes are in-flight -- Hoping to have something ready later today.
Yeah, I just realized that after I tried it... Thank you for all your hardwork!
App version 1.2.0 released which allows custom topic input. I've updated the README with the pub/sub creation details referenced in the HomeAssistant setup as well. Give it a whirl and let me know if you see any issues!
1 Like
Working great for me now. Thanks!
Welp - the final glimmer of hope (if you still had any) that Google might integrate the Nest Protect Smoke/CO Detector into the API has been extinguished 
This sucks! The protects were the best out there. Anyone try the owl yet?
There's still a working Home Assistant integration for Nest Protect. I use it and it works great, so, it CAN be added to Hubitat too but someone will have to do the work..
Yeah I have mine connected directly to HomeKit and use virtual devices in hubitat exposedbthrough homebridge for sensor triggers. I also saw the nest homebridge plugin was recently updated to support homebridge v2.x as well which was a positive sign.
Hello, not quite sure what the issue is. I was using another nest HE app for a couple years but I started having some issues and saw it was deprecated, so I uninstalled and found this one. So I installed it and it works and I see it but it's not running the temperatures by my modes that I have set, so I have to manually change the temps.
Here's my primary temperature control app I'm using with Rule 5.1
Here is the thermostat details...
I notice it doesn't really matter what I put in the set cool setpoint or set heat setpoint it changes it back to 72 and 78, when I'm home at least which should be 72-75. I completely uninstalled the app and spent two hours with the whole google web/cloud setup again in case I screwed something up but still seems the same.
I'm not an expert with HE but I've had pretty decent success with the app that I created by modes which is changing modes when I get home or leave correctly but for instance when I leave I want the house to go into eco basically 68-78 for heater/ac, when I return I want it to keep the house between 72-75 again heater / ac pretty simple but I'm seeing when I leave it goes 72-78 and I manually make it 68-78 while I'm gone then I come home it goes 68-75, so I manually change it again to 72-75. Anything. you can see or more info I need too post here to why this is messing up.
Now if I hit update rule in the app, it briefly changes my phone homekit icon with the temperature to 72-75 but then it changes right back to 68-75. The 72-75 would be correct when I'm home so it's like something is overriding it back.
Appreciate any insite to what I'm doing wrong here. Thanks,Russ
Is there any errors popping up in the logs from this app? What about your actual Nest app settings? If you had eco/leave/arrive configured in that app, it would be fighting what what you are trying to change in Hubitat.
I just turned on the debugging logs this morning, so I will check again later this afternoon. I don't use the Nest app ever but I did open it up this morning and I have the presence, schedule, eco, arrive, depart all of it off. I did have a preset for cold and hot at 68 and 78 which is the temps I use on HE but I went ahead and turned those off in the Nest app as well, and thought that must be it then. But I left to a dentist appointment and pulled up my Homekit app and it went to 72-78 while I was gone still as show here.
And in HE app on phone here.
Simulating I left while at home and pulling up the events in the app..
My guess is the 68 and 78 is coming from my app I created New Thermostat Control with Away Mode turning it to 68-78 but why just above that is Google SDM API saying 68, 78, but then 72 which is exactly what I see on my app while away 72 and 78. Or put another why is why is the heatsetpoint being showed/changed twice at the same time basically, the 72 overrides my 68 from the app I created.
Is it because this box here is over riding with the 72 in it?
I've tried to delete those temps and just keep the box blank but it won't let me.
I'd check the logs when you did that manual toggle. You'll be able to see what was sent to Google for the temp change. You will also see if Google rejected something, which would explain it not changing.
On those driver screen shots, what you see there is either defaults or what Google was last set to. If you don't click the "set" buttons, then nothing happens with those numbers.
This was the time at 3.47 does of any of this look out of place, maybe the one warn flag?
Heres my thermostat control app running...
The thermostat itself log in that time..
The Google app running log...
It looks like you have something hammering Google twice, which is why only one is sticking:
The first one is the 68F/75F, the second right after at 72F/78F. I'd check your rules on how you are controlling the temperatures. The Google SDM allows for heat/cool to be passed as one item. I'd guess the RM is setting heat first, and then cool second (independently), and google is borking on it.
I did a quick check, and this might be a limitation on how the rule machine issues the temperature commands. Google expects a heat & cool temperature setpoint if the thermostat is configured for both heating and cooling.
If you just do a "set cool" or "set heat", the Google SDM will bundle the last setpoint for heat or cool that that one so that the pair is delivered to Google to configure the thermostat.
What the rule machine needs to send is the set heat/cool which I don't think it does:
I did up my own app for controlling my automations, and just use the above to trigger temp changes.
To use the rule machine, you'd have to set one of the setpoints, delay and then set the other I suspect.
Thank You for the replies back. I pulled some of my screen shots, I was informed it had had all my user id info in there. I will try and play with some variations of the RM to run this, like you said maybe it's the capabilities of what it's trying to send and do. I wonder if you might post your app you created to run your temperature changes maybe I can use that as a template somewhat for my needs?
Thanks,
Russ
1 Like
To use the rule machine I think you just need to set the heat, add a couple second delay, and then set the cool. That should work for what you are looking for.
The app I did didn't do exactly what you are doing. I was just bumping the heat up or the cool down, and then just letting the dead band drive the other setting if required. But it would just be something like this:
input "thermostat", "capability.thermostat", title: "Select the thermostat devices", required: true, multiple: false
void changeThermostatSetpoint(heatTemp, coolTemp) {
thermostat.setHeatCoolSetpoint(heatTemp, coolTemp)
}
Have a picker to grab your thermostat, and then call the 'changeThermostatSetpoint' with the desired temperatures.
The integration seems to be working alright, expect for the images. The images when motion / presence is detected are not being saved. Not sure where to start troubleshooting ...
First - there are preference toggles on each device which control whether images are captured for the relevant event. These settings default to true, but perhaps they've been switched off.
Beyond that, use the logs and event history to validate if the App/Device is successfully receiving and processing the events from Google
