You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2023. It is now read-only.
I've setup a Node-Red flow to run every night to call the light_off service on my fully kiosk screen entities and it works great, but the next morning when I wake them back up, the volume settings have mysteriously been raised back up. Not really sure what's triggering that. When I create diagnostic flows to replicate the same service calls it doesn't seem to do it, but it got me thinking. If I could retrieve the current volume setting, I could write a flow to check it periodically and set it back down to 0 if it's not currently 0.
So that's the enhancement request. A number entity like the Screensaver Brightness entity perhaps but for volume.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
That would make things easier indeed. Currently I need to get the volume of the HA Companion app entity for the same device. Much easier if provided by FK directly. There's even a FK service already to adjust the volume...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've setup a Node-Red flow to run every night to call the light_off service on my fully kiosk screen entities and it works great, but the next morning when I wake them back up, the volume settings have mysteriously been raised back up. Not really sure what's triggering that. When I create diagnostic flows to replicate the same service calls it doesn't seem to do it, but it got me thinking. If I could retrieve the current volume setting, I could write a flow to check it periodically and set it back down to 0 if it's not currently 0.
So that's the enhancement request. A number entity like the Screensaver Brightness entity perhaps but for volume.
Thanks in advance.
The text was updated successfully, but these errors were encountered: