-
Notifications
You must be signed in to change notification settings - Fork 129
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
ESP32 S3 Box only turn on screen when Assist is in progress #126
Comments
hm... yes, I think having a "switch" or something to decide if you want the "sleeping" screen (display = on) or if the display should be off by default would be a nice option to have. This would also allow to decide for each device how you want it to behave. |
I've got this working for the most part, but since I just got a Box Lite tonight and have also barely done any ESPHome yaml programming stuff, I could use some help testing this in general and on the Box [3]. Could y'all help me with some testing before I propose a change set via pull request? Assuming that you've got the device adopted or otherwise are capable of modifying the yaml to install, should be easy enough for us to do some beta testing with a repository that I'll set up tomorrow.
Oops. I just noticed that turning off the LCD Backlight option may not be adhered to (e.g. keeping it off when voice activated) and turning idle display back on does not immediately turn the display back on, but I'll work on those two too. IMG_1628.MOV |
Alrightie! I think it is in a stable enough place for others to give it a whirl and I ported the changes over to the S3 Box / 3 which I have not been able to test since I have a S3 Box Lite, but reads like it should just work. This assumes that you've Adopted the device in ESPHome or previously Installed a firmware so that you can Edit the device yaml configuration which should be similar to the following:
Make sure to use the file specific to your device:S3 Box 3
S3 Box
S3 Box Lite
To have a look at the diff between the As this is a device switch, you can of course automate turning off/on Idle Display as part of a goodnight routine, at 9pm, or whichever other events or conditions you deem fit. Open questions:
|
Based on interactions with the original post, tagging individuals potentially interested in no S3 Box display when idling: @TheZoker @ChristophCaina @jpenschuck @the-mentor @pixeye33 |
Another totally viable but apparently not apparent option is simply using automations. My good friend @whoinow not only gave me this device, but also made this simple and totally logical suggestion. Great idea fine sir. Automation: Box: turn on display on assist
Automation: Box: turn off display after assist
This accomplishes virtually the same outcome as the code changes with some very minor exclusions. For example, the display will not be off by default unless you voice activate/deactivate. But! No code changes required. |
Hi, thanks :) I think, that should be OK for some tests, but I would prefer to use the original source, if something might change here... ;) So my thoughts: |
Yup, temporary change as part of a request for testing. I can only verify behavior on the Lite, so while it reads like the changes set should be fine on all others, confirmation would be appreciated. What do you think about the automations approach versus code changes? Since a number of us weren't aware of this option, I do wonder if the more prudent change might be proposing a documentation update instead. |
@kevireilly You could also do it as a single automation in HA, which triggers being progress on and off, then a conditional action (not using conditions before the action section, but the if/then action). Mine:
|
Nowadays, it seems the But anyway, I also had the same idea and built my own automation before I stumbled upon this post, so I'm sharing what I did with the current state of affairs. This works even after booting up - the screen goes off as soon as it changes to Nonetheless, it has a tiny bit of lag and, given this could be easily processed by the ESP32 itself, it would be awesome to have this feature baked into it. alias: Ligar/desligar tela do assistente
description: ""
triggers:
- trigger: state
entity_id:
- assist_satellite.escritorio_assist_state
conditions: []
actions:
- choose:
- conditions:
- condition: state
entity_id: assist_satellite.your_assist_entity
state: idle
sequence:
- action: light.turn_off
target:
entity_id: light.escritorio_assist_screen
data: {}
- conditions:
- condition: not
conditions:
- condition: or
conditions:
- condition: state
entity_id: assist_satellite.your_assist_entity
state: idle
- condition: state
entity_id: assist_satellite.your_assist_entity
state: unavailable
- condition: state
entity_id: assist_satellite.your_assist_entity
state: unknown
sequence:
- action: light.turn_on
target:
entity_id:
- light.escritorio_assist_screen
data: {}
mode: single |
I think the title says it all:
Allow the screen to only be turned on, when a Assist is in progress.
I have one box in the bedroom and the turned on screen is not optimal. Would be nice if it only turns on when needed.
The text was updated successfully, but these errors were encountered: