You can send non integer numbers via yaml, I have an automation that trigger off of a input number where I use {{ (((states.input_number.living_room_volume.state | float) / 100) + 0.82) | round(2) }} to set the volume. The input number ranges from - 82db to 0.
How would I incorporate this into an automation? I have pretty much used the GUI at this point for automation. If by chance you can please share your YAML, I will try to add my Pioneer entity and adjust your YAML. I’m basically looking to set it either at a lower volume or a higher volume (at certain volumes which I can play around with once I get this up and running.)
Below is my code (the top portion is just the trigger):
alias: TV volume up/down
description: ""
triggers:
- entity_id: input_boolean.tv_volume_up_down
to: "on"
trigger: state
conditions: []
actions:
- action: media_player.volume_set
metadata: {}
data:
volume_level: 1
target:
entity_id: media_player.sc_lx502
mode: single
Ok, I went back and tried to manually raise the volume and even at 100, it’s barely turning up the volume (maybe 20% of the actual volume.) I didn’t realize this until I double-checked just now. I wonder if there is something I can put in the config yaml to allow it to go higher, as when I turn the knob manually on the receiver (or use the remote control) it goes way higher…
Yes, it’s at 100. I read a thread on here from 2017 and it seemed like people were having a similar issue with Pioneer. Apparently, there is (or was) a Onkyo.py file that can be modified to fix this, although I don’t even know if that’s applicable now. It has no problem controlling my unit, it just stops at a super low volume.
This might be the resolution, but I am not sure and don’t know where this file is even located? I’m thinking something needs to be adjusted within a file or config yaml?
OMG, that worked! 2 days of ripping any remaining hair out, lol! I have to say, it wasn’t really clear, as it just shows the IP address and submit, figuring no reason to submit that. Appreciate it!