Open kdknigga opened 2 years ago
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.
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 Fri, Nov 17, 2023, 00:12 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-1815800974, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QFATQ6MWTVPIKCI7SLYE355HAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGU4DAMBZG42A . You are receiving this because you were mentioned.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 Sun, Dec 17, 2023, 08:07 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-1859182995, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QAV46MABHCTKJ2D4B3YJ34BVAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBVHEYTQMRZHE2Q . You are receiving this because you were mentioned.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 Tue, Jan 16, 2024, 09:09 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-1893939603, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QGT5FO5MYCXQWMJNODYO2J2BAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBZGM4TGOJWGAZQ . You are receiving this because you were mentioned.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 Thu, Feb 15, 2024, 11:09 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-1946618159, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QGVE3BTEPXZUBPUNJDYTY6KZAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUGY3DCOBRGU4Q . You are receiving this because you were mentioned.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 Sat, Mar 16, 2024 at 2:07 PM github-actions[bot] < @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-2002092139, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QDGCTNB67IA6OLSXODYYSJ65AVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBQGIYDSMRRGM4Q . You are receiving this because you were mentioned.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 Mon, Apr 15, 2024, 15:09 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-2057716687, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QAQZ5AFMDFY2WQXAFTY5QXWZAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBVG43TCNRWHA3Q . You are receiving this because you were mentioned.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 Wed, May 15, 2024, 17:10 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-2113534013, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QHKURDF327KWU6AVDTZCPMNNAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJRGM2TGNBQGEZQ . You are receiving this because you were mentioned.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 Fri, Jun 14, 2024, 19:44 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-2168999156, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QHBYGABQFK5PQXEJRTZHOE6LAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJWHA4TSOJRGU3A . You are receiving this because you were mentioned.Message ID: @.***>
@kdknigga I love your persistence. Maybe this will be fixed someday. This is a feature I would really like to have. My t-stat is in my bedroom and I have a sensor in the office. It would be great if the sensor could be switched between bedroom and office based on presence.
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 Sun, Jul 14, 2024, 21:03 github-actions[bot] @.***> wrote:
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 https://github.com/chrisjshull/homebridge-nest/issues/470#issuecomment-2227593768, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJX7QASDOP26N6C74D3YFLZMMUXRAVCNFSM5IRRIAD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRSG42TSMZXGY4A . You are receiving this because you were mentioned.Message ID: @.***>
Is there a way to tell which API is being used?
Also curious if there is a way to know which API is being used. Does one just install the forked version and find out if it works?
The Nest supports using a remote temperature sensor as "the" sensor to use when making heating/cooling decisions. Changes to the active sensor can be made manually by selecting the one you want when you want, or it can be made on a schedule.
However, Nest's native scheduling system provides only very coarse control over when different sensors should be used.
It would be super neat if homebridge-nest could be used to select the active sensor so an external tool could be used to manage the schedule.
I'm thinking of something along the lines of a "node-red <-> mqtt <-> homebridge-mqttthing <-> homebridge <-> homebridge-nest" toolchain, but the rest of the toolchain doesn't really matter as long as something is able to ask homebridge-nest to change the sensor.
Awesome work, and thanks a lot!