Nest Fan Service

[saverchenkov]

Added a separate "Fan" service to control nest fan. Works as expected. Unfortunately, there is no way to set fan timer, but basic on/off states work as expected. I tested this with latest homebridge.

[djensenius]

Is the reason that timers can't be set a limitation of HomeKit? It appears possible in the Nest API unless I'm misreading it?

[zeve-zz]

@saverchenkov i integrated your code

I'm now seeing two separate items for my nest. one for thermostat as it was, and now one that has a fan icon which is a power on/off toggle

however, the fan item isn't operable ('no response'). when i run the ac, or the fan via the nest app, the fan icon will update and begin to spin, but i can't actually interact with it. did i miss a step here?

edit:
seeing the following now in my logs. this is new.

Aug 28 21:28:28 raspberrypi homebridge[538]: FIREBASE WARNING: set at /devices/thermostats/bjThYz57rt_21QJnOsB871nYKoB9bDtC/fan_timer_active failed: blocked

and

Aug 28 21:29:25 raspberrypi homebridge[538]: FIREBASE WARNING: set at /devices/thermostats/bjThYz57rt_21QJnOsB871nYKoB9bDtC/target_temperature_high_f failed: blocked

[saverchenkov]

Thank you for merging and apologies for the delay in response.

Second device is normal. This is as intended. Homekit does not seem to have a "fan" feature on a thermostat, so I exposed it as a separate device.

"Blocked" sounds like a rate limit exceeded issue. Can you try again? Do you have a way to catch the exact HTTP status code? Alternatively, this could be permissions issue, but for as long as your app has read/write for thermostat, it should work.
https://developers.nest.com/documentation/cloud/error-messages

I use this feature daily on my home thermostat.

[chrisjshull]

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 believe this PR is merged in that repo. If not, please submit a new issue/PR there.