I have a Hegel amp which supports ip control. I am looking to automate the following processes:
switch the amp off when there is no signal from any of the input sources
designate an input source as default when the amp is switched on
switch the amp on at a certain time and set input source.
Not sure the easiest and most robust way to do this. I see a lot of discussions about ip2ir control using something called iTach? Seems a bit too much for what I am looking to do. Looking for a simpler robust solution.
@gassgs Using telnet on my laptop, I was able to connect to the amp and do some basic stuff. However, it seems that, to do anything with telnet on hubitat, I need to build a driver ? I have zero groovy programming experience and not sure how i will be able to do this. I was hoping that it was a functionality built into RM, and I can use if and else statements to interact via telnet with the amp.
What are my options here? Is it possible to use RM to do this at all? I'd like to do the following:
At 6 am , check if the amp is on, if not, turn it on and switch input source to #1
At 6.30 am switch to input source #4
At 8 am, power off amp
Send connection reset every 2 minutes to keep connection alive
There are telnet codes above for each of the above items. Seems pretty simple to require writing drivers for.
Messages returned are not retained by the driver, but will display on the device page. Enter the IP address and port number, click on connect, and then type the command (-p 1, -p 0, etc) in the Send Message box and click it to send. Click disconnect when done.
Well if this allows you send it commands and it responds, it would be a simple matter of expanding upon it to make it a specific driver for the amp, i.e. encapsulating the amp commands with a driver equivalent that could be exposed to RM, etc.
Clear as mud. As I said, no groovy programming experience, so not sure what you just said. My question was, how do i setup the device on hubitat before applying the above driver code to it? as a virtual device and what type of device? Or am I looking at this all wrong?
LOL, this gets installed as a device driver (copy code to the Driver's Code area, go to Devices and create a virtual device with it as the device type). Then, if it allows you to connect and send commands (I'd try the on/off -p 1 and -p 0) and it responds, I can quickly adapt it to be the device driver for you.