-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support 'always-on' in pathlight configuration setting #69
Comments
Thanks for reporting! I looked into this as well a while ago, they use internally 2 switches I believe, thus we need to map that in a different way. Would you like to be able to change this via HA? Or is it a nice-to-have? |
It certainly isn't a critical feature, more of a nice-to-have. For one thing, it would immediately show that HA is communicating with one of the Protects to toggle the light on and off. For a more practical use, I have a very dark finished basement where I normally keep the path light on. When I have family staying overnight this area is used for sleeping space, and having the path light on is a nuisance. It would be nice to easily turn the path light off during these occasions.
…________________________________
From: Mick Vleeshouwer ***@***.***>
Sent: Wednesday, April 6, 2022 10:13 AM
To: iMicknl/ha-nest-protect ***@***.***>
Cc: jeffdeal ***@***.***>; Author ***@***.***>
Subject: Re: [iMicknl/ha-nest-protect] Great integration! Pathlight question... (Issue #69)
Thanks for reporting! I looked into this as well a while ago, they use internally 2 switches I believe, thus we need to map that in a different way.
Would you like to be able to change this via HA? Or is it a nice-to-have?
—
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FiMicknl%2Fha-nest-protect%2Fissues%2F69%23issuecomment-1090322464&data=04%7C01%7C%7Cc01614eafe1f431d1fa008da17d7a624%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637848512225977922%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=AYp%2FhpfQt0sivjeKZHIMeYx3sNurlZK7qyI3OP2tlUM%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARIKP2KWAG3LPMNBSWLBGBDVDWLZFANCNFSM5SV6SE7Q&data=04%7C01%7C%7Cc01614eafe1f431d1fa008da17d7a624%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637848512226134140%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6QMx3kwd9%2BlAC73dT2LKo25Kjv5EMYRBFOMoSsmFsas%3D&reserved=0>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I think in general this is a nice one for automations. The sometimes-guest-room case is one example. Another use case: I'd like the automatic pathlight in my bedroom in winter evenings before bedtime, but don't want the cat tripping it all night long. I think exposing it as two switches would be fine, as long as the labels are clear. |
Very much in favor of this enhancement for the same reason others have mentioned. Many use cases where it would be nice to have it set to always on and to control it from home assistant. |
+1 here. Am trying to setup automation to turn on all pathlights(1 on each floor) whenever one is activated. This allows me to have light whenever i climb the stairs. |
I could really use this added to the integration - we use one path light as a night light, but only when kids are in the room so it would be great to be able to integrate it into our automations |
Description
This is an amazing integration! I have 9 wired Nest Protect devices, and have one question so far. In the configuration of the pathlight from within the Nest app, we can set it to off, on, or always on. In HA the pathlight configuration shows up as a simple toggle switch with just on or off. Is there any way to configure this as a drop-down like the brightness setting?
Device (optional)
Nest Protect (Wired) Topaz-2.7
Additional information
No response
The text was updated successfully, but these errors were encountered: