homebridge-nest
homebridge-nest copied to clipboard
chrisjshull
Nest Protect Occupancy no longer reporting correctly as of 4.6.10
Describe the bug
Nest Protect comes with an "Occupancy" accessory, which is no longer reporting state correctly within Homekit as of version 4.6.10
To Reproduce Steps to reproduce the behavior:
Implement a Homekit Automation based on Nest Protect Occupancy, ex. turn on a light
Automation will no longer fire correctly when room is occupied.
But if you happen to open the Home.app, go to the room in question within the app, occupancy will be immediately updated and the automation will fire.
Expected behavior
If occupancy is true, update the accessory, which would allow for the automation to work.
This is a bug / regression -- this has previously worked fine for years and all prior plugin versions afaik.
=> All current versions; plugin, homebridge et al.
+1 to this issue. Accessory status in HomeKit does not appear to update unless the Home app is opened, or the homebridge UI is opened. It's almost like the plugin is no longer receiving events from the Nest cloud and pushing them into apple home, and instead now only polls for the current devices state from nest and updates them when one of the clients requests it. Will revert back to 4.6.9 so my automation's start working again.
Ive started using https://github.com/n0rt0nthec4t/homebridge-nest-accfactory/#readme just in case anyone else wants to try it out
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Not stale, still needs to be fixed
On May 21, 2025, at 5:26 AM, github-actions[bot] @.***> wrote:
github-actions[bot] left a comment (chrisjshull/homebridge-nest#693) This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Same issue here and agree this needs fixing.
4.6.9: My Nest Protect's correctly notify me of occupancy from within the Apple Home App.
4.6.10: 99% of notifications never appear. Sporadically (perhaps when I've loaded the Home app in frustration?) one might appear.
Downgraded back to 4.6.9: Working perfectly again as they have for several years (I didn't have to re-auth with Nest/Google, so downgrading was easy).
Same issue with 4.6.10 here. The only way to get the presence to update was to open the Nest app (opening the Apple Home app didn’t result in any change). Reverting to 4.6.9 resolved the issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Should this remain open until @grecine fix above is included in a future update? I haven't tried the fix but remain hopeful it solves this, thanks in advance @grecine :)
Not stale
On Aug 4, 2025, at 7:18 AM, github-actions[bot] @.***> wrote:
github-actions[bot] left a comment (chrisjshull/homebridge-nest#693) This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still needs to be fixed.
On Sep 3, 2025, at 11:17 AM, github-actions[bot] @.***> wrote:
github-actions[bot] left a comment (chrisjshull/homebridge-nest#693) This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not stale
On Oct 23, 2025, at 11:19 AM, github-actions[bot] @.***> wrote:
github-actions[bot] left a comment (chrisjshull/homebridge-nest#693) This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
@chrisjshull, please can you merge the PR and generate a new release that fixes this issue?