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
Specify motion sensor to wake up the display #1687
Comments
that would be awesome for home assistant too |
Please tell me more about your current automation... It wakes up the panel and then you leave to the panel's routine to sleep again or do you have a command to sleep in your routine? I think if we create this, the panel should be awake while the movement/presence persists, or at least have an option for this, but this makes it a bit more complex, as the sleep process will have to change. Which is not that hard, but then we will have two places to set sleep time and one will be ignored. |
Please tell me more about your current automation... It wakes up the panel and then you leave to the panel's routine to sleep again --> Yes it does that exactly. So if I walk into a room the sensor detect motion and the display turns on, then after the normal timeout (60 sec) the display goes into sleep mode again. This is enough time to read the time /temperature etc from the display. I have this in most rooms. I also have node red automations for:
/R |
Nice. |
Yes, just keep it simple to start with, it think it will be a good start. /r |
Implemented in |
That's great to hear. Amazing how fast ! Thanks, |
that is an absolutly beautiful commit @edwardtfn - Thank you - cant wait to patch it and try out! |
I will close this for now and we can reopen if it isn't working well when released. |
We just released a patch with solves this: v4.2.5 - Celebrating 1000 Stars with Enhanced Functionality and UI Improvements |
Hi,
I now have a node red automation to wake up the display when motion is detected.
Would be nice if you can specify this in the blueprint.
just an idea.
regards,
R
Originally posted by @rbr101 in #1684
The text was updated successfully, but these errors were encountered: