Is homebridge-nest still maintained?

[demonbane]

I don't see any new commits since last September, and a number of PRs have been sitting around for months without any updates. Has anyone been keeping an updated fork somewhere with some of these changes merged in?

[cosmosified]

It doens't appear to be. I've been adding fan control but i think i will see what i can pull together from the PR's and such. It's the most important piece of homebridge for me.

[pedroserano]

@cosmosified Have you had any luck with adding fan control? I noticed it is now in the Nest API (hooray! originally it was not)

[rmolina811]

Hey guys, I did also see that Nest added fan control to the API.. can we get someone to add it into homebridge? :D Id love to set up rules to run the fan from triggers

Fan

Many HVAC systems have integrated fans, which means that the fan cannot be controlled independently. There is no off mode for integrated fans, because the fan needs to run when the heating or cooling is on.

However, if the HVAC system is compatible, the fan can be explicitly turned on via the API, in order to make occupants more comfortable, without engaging the full HVAC system.

If the fan can be controlled independently, has_fan will be set to true, and the following data values can be set with Thermostat read/write permissions:

fan_timer_active - boolean, returns true if fan timer is engaged for a pre-programmed duration fan_timer_duration - int, the length of time (in minutes) that the fan is set to run Use these values together to initiate the fan timer (turn the fan on) for a specific period of time. You can also use the fan_timer_timeout value to determine the timestamp of when the fan is set to stop running.

Note that you can always change fan_timer_duration - it is independent of hvac_mode or structure occupancy state (away).

You can expect these responses on success or fail:

200 OK 400 Bad Request If the command to turn the fan on doesn't produce the expected result, it may be because the fan is already engaged (either manually by the user, or on a schedule, or because of an HVAC heat/cool cycle).

[chrisjshull]

@KraigM, if you aren't going to maintain this project anymore can you transfer ownership to someone else?

[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.

[dswee999]

Getting the below error when homebridge starts and the nest and fan etc aren't pulling into the home app.

[Nest] Skipping device Q4NijrabRX2jCc_jYpNCySnarQ8n6g8Y because it is not in the required structure. Has liIBNkQ-EzMZGTgt-SZj1pECy0-CazUaHd-qTSWleH0gg5Q3Q5qBmA, looking for your structure's ID.

Please help?

[chrisjshull]

@dswee999, please file news bugs on the new repo: https://github.com/chrisjshull/homebridge-nest

However, I'm guessing you have an invalid structureId in your homebridge config. In the section for the Nest plugin delete the "structureId" line (it is optional).

[dswee999]

@chrisjshull will do. I apologize, I'm new to all of this and github. You were correct. Deleting that line corrected the issue. Now I'm trying to figure out why the temp it shows in the Home app is not the same temp it shows on the actual Nest. Will file it on the new repo.