Its weird, it appears to be triggering. However, it does not work.
I have confirmed that if I short GPIO16 which is volume down, that the volume goes down, so from there everything is working fine.
[00:01:11][D][sensor:094]: 'VCC Voltage': Sending state 10.42319 V with 2 decimals of accuracy
[00:01:12][VV][scheduler:226]: Running interval 'update' with interval=300 last_execution=7334 (now=7634)
[00:01:12][V][adc:148]: 'VCC Voltage': Got voltage=2.5112V
[00:01:12][V][sensor:043]: 'VCC Voltage': Received new state 2.511174
[00:01:12][VV][sensor.filter:014]: Filter(0x3ffb99f8)::input(2.511174)
[00:01:12][VV][sensor.filter:021]: Filter(0x3ffb99f8)::output(8.286875) -> SENSOR
[00:01:12][D][sensor:094]: 'VCC Voltage': Sending state 8.28687 V with 2 decimals of accuracy
[00:01:12][D][switch:020]: 'volume_down' Toggling ON.
[00:01:12][D][switch:055]: 'volume_down': Sending state ON
[00:01:12][VV][scheduler:032]: set_timeout(name='', timeout=200)
[00:01:12][W][component:237]: Component adc.sensor took a long time for an operation (56 ms).
[00:01:12][W][component:238]: Components should block for at most 30 ms.
[00:01:12][VV][scheduler:226]: Running timeout '' with interval=200 last_execution=7680 (now=7880)
[00:01:12][D][switch:016]: 'volume_down' Turning OFF.
[00:01:12][D][switch:055]: 'volume_down': Sending state OFF
[00:01:12][VV][scheduler:226]: Running interval 'update' with interval=300 last_execution=7634 (now=7934)
[00:01:12][V][adc:148]: 'VCC Voltage': Got voltage=2.5232V
[00:01:12][V][sensor:043]: 'VCC Voltage': Received new state 2.523162
[00:01:12][VV][sensor.filter:014]: Filter(0x3ffb99f8)::input(2.523162)
[00:01:12][VV][sensor.filter:021]: Filter(0x3ffb99f8)::output(8.326436) -> SENSOR
[00:01:12][D][sensor:094]: 'VCC Voltage': Sending state 8.32644 V with 2 decimals of accuracy
[00:01:12][D][switch:020]: 'volume_down' Toggling ON.
[00:01:12][D][switch:055]: 'volume_down': Sending state ON
[00:01:12][VV][scheduler:032]: set_timeout(name='', timeout=200)
[00:01:12][W][component:237]: Component adc.sensor took a long time for an operation (56 ms).
[00:01:12][W][component:238]: Components should block for at most 30 ms.
[00:01:12][VV][scheduler:226]: Running timeout '' with interval=200 last_execution=7980 (now=8186)
[00:01:12][D][switch:016]: 'volume_down' Turning OFF.
[00:01:12][D][switch:055]: 'volume_down': Sending state OFF
[00:01:12][VV][scheduler:226]: Running interval 'update' with interval=300 last_execution=7934 (now=8238)
[00:01:12][V][adc:148]: 'VCC Voltage': Got voltage=3.1585V
[00:01:12][V][sensor:043]: 'VCC Voltage': Received new state 3.158542
[00:01:12][VV][sensor.filter:014]: Filter(0x3ffb99f8)::input(3.158542)
[00:01:12][VV][sensor.filter:021]: Filter(0x3ffb99f8)::output(10.423188) -> SENSOR
[00:01:12][D][sensor:094]: 'VCC Voltage': Sending state 10.42319 V with 2 decimals of accuracy
ok so I was able to get the web interface working,
Upon doing so, I connected to the devices we interface, and pushed the volume down button, sure enough I could see the output momentarily turning on and off.
So, im in a situation where I have manually shorted GPIO16 to GND on the ESP32, and volume goes down, confirmed that everything from there back works.
And I have now confirmed that my switch is switching GPIO16 on the ESP when the volume down button is pressed.
Iād try to switch the volume down gpio with the volume up gpio in the yaml. This will show if GPIO16 can control the up relay and if the up gpio can control the down relay. This will help narrow it down potential causes.
I have tried changing the GPIOs in the code to switch the relays,
To see if the volume_down would trigger the volume_up, have not tried changing the physical wires on the ESP for the outputs.
It must be something to do with the output not switching or switching incorrectly on the ESP as the code is working as expected, and shorting the wires does trigger a volume_down event.