Open Wildcat1 opened 7 years ago
I am not running any beta software and I am experiencing the same issue.
Running into the same problem. I wonder if Nest changed their API..
I found on another forum (I can't locate the specific one) where a user overcame this new behavior by using the command "set cooling to 74F" rather than "change temperature to 74F." I have had luck with this method.
That is clever. Thanks!
Thanks, Amro
Sent from my iPhone
On Aug 20, 2017, at 2:22 AM, saminator8 notifications@github.com wrote:
I found on another forum (I can't locate the specific one) where a user overcame this new behavior by using the command "set cooling to 74F" rather than "change temperature to 74F." I have had luck with this method.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Hello all,
I have successfully fixed the issue, and have submitted a PR: https://github.com/KraigM/homebridge-nest/pull/136
Hope this helps you all!
Thanks @seifscape . @KraigM, could you please look at merging that PR? Thank you!
Welcome @amro, I am glad I could help :)
Just wanted to update that I did raise a bug with Apple shortly after seeing this issue and it appears this (the Apple piece at least) was fixed in beta 7 of iOS 11 as it was working again. Not sure if all of these made an impact but glad we have a fix. Thanks to everyones work and input on this !
I noticed this on iOS 10.3.3, but it would be great if someone wants to test my branch out, and eventually merge it in. I followed what Nest suggests on changing target temperature, by using previous_hvac_mode
Great news! I have taken up maintenance of the homebridge-nest plugin in npm. The source code now lives at https://github.com/chrisjshull/homebridge-nest/. To update to the latest version of homebridge-nest, simply run npm update -g homebridge-nest
.
I think this issue is fixed there, but if not please file this issue against that repo. Thanks!
Thanks for taking it up @chrisjshull!
I also want to thank you @chrisjshull for all your hard work on this nest plug in. I literally bought a Raspberry Pi and set this up the other day. I also have this issue. The same as described above changing the temp's in home kit workings perfectly, however using siri seems to change the state from "COOL" to "AUTO" which is both cooling and heating. My iOS devices are currently on iOS 11.4
Noticed in latest iOS 11 betas that if I issue a 'set thermostat to 72 degrees' command through Siri that rather than just adjust the temp it now changes from cooling mode to Heating & Cooling every time. Whether you issue the command through Siri on an iPhone or Apple TV, same thing. If you use a HomeKit app and just adjust the temp, all good, just sets temp and doesn't adjust cooling mode.
Anyone else seen this and or know about the issue ?
Thanks as always