I am trying to implement volume up/down buttons and gauge. I explored tcp command and found that it is only sensor and it is increasing volume continuously. Glad I figured out and removed without damaging receiver. It is mistake of my understanding on sensor and that tpc provides.
It seems options are to use shell command or command line. Let me know what would be better. I have two receivers of same type and it would help better develop kind of parameters for each ip. Otherwise, it is fine to specify 4 commands. These are high level steps that I assume
Modify configuration.yaml to have shell_command or command_line for 4 commands to send up/volume for two IP addresses(receivers)
Write script that invokes above
put button on dashboard and invoke those scripts
Let me know if I am on right path. Also, these commands return response containing current volume. How do I set for the gauge.
Appreciate to validate and for the direction.
I see command_line integration supports switch, but it is required ‘command_on’, and ‘command_off’. Since I need just one action on button press, not sure if I can use this or not.
I guess I need to send this command
echo -n ‘Z1VUP;’ | nc 192.168.4.5 14499
Thanks. I will define 4 shell commands and create 4 scripts to call from 4 buttons. it seems it gets response also and can be parsed to display in gauge.
May be there is better way to not to create so many scripts, but I can try with it.
I tried enough these commands without luck. I want to explore anything else. Does mqtt allows to send tcp commands to receiver? Is it good idea to setup and learn and try mqtt. Appreciate it.
Home Assistant integrates with tens of thousands of devices and can use more than 2500 different integrations… It might help others to help you if you follow the Question Guidelines so that we have all pertinent information.
What is the actual goal?
What are the brand and model of the device?
Provide a link to relevant documentation
Is there an integration for the device?
Describe your HA installation type and any pertinent network details