Thanks, i'll give this a try! What kept throwing me off is the "Parameter Type", which i thought that you had to select.
You can do this with either a virtual switch or a virtual button. Follow these steps:
Create a virtual switch or button
Allow the Amazon Echo skill access to that device
Tell Alexa to discover your devices
Use the device in your triggered rule. (When turned on or pressed, switch source)
Create a routine in the Alexa app that turns that switch on when you say your command
You don’t have to select a parameter type or a parameter that is when you have an option that requires a parameter. For example setLevel will require a level amount if you where automatically set a level there you will select parameter type number and then the volume you want to apply to the amp
Best
Jorge Martinez
1 Like
The on/off, level function should be already working via smart speakers they will treat the amp as a dimmer, the sources change the best approach will be doing a virtual switch
Jorge Martinez
Good to know, thanks!
So this what I have done to enable the use of Alexa and create a button on the HE Dashboard to switch the source of the one of the amps zones:
- Create a Virtual Switch (Buttons Don't work with Alexa interface)
- Create a New rule with Run Machine:
- Trigger Virtual Switch to be turned on
- Action 1 Set the Source
- Action 2 Turn the Virtual Switch off - Delayed by 2 Sec
- Add Switch to Alexa, then create a routine to say whatever you want.
- Add Virtual Switch to your dashboard, I change the icon so it looks like a button. When you click it will run the routine "turn on" then turn off.
Thanks for the help.
That should do it! Next is to figure out how to control Amazon Echo’s with Lutron Pico Remotes so that I can switch songs and control the volume without voice!
For that you will need a Lutron pro hub native supported by Hubitat
Jorge
I just picked up the serial to Ethernet converter and I am trying to set things up. I plugged the device into the amp and the ethernet into my router. The device manual references an ip address 192.168.2.1 but this is not accessible. The latency light is red and the network light is green no other lights. I do not see the device on my network. Any guidance or suggestions? I ordered the Cerrixian device referenced above but received a similar looking device branded Diewu.
Thanks
Mike
Im not sure if you are in the same ip range. if your device is on a 192.168.2.1 - 255.255.255.0 you will have to assign your computer an ip address in the same range manually then set up your the device an ip address inside your network and be sure your router don't assign the same ip to another device in the network I will recommend set up a reservation for the device in your router and put the device in DHCP mode
Best
Jorge
Jorge, do I actually need Sonos (or other audio source) in order to do TTS through speakers controlled by this amp? I assume the answer is YES, but then I noticed the speaker driver has commands like "Play Text", so it got me wondering.
Jorge, you still around this community? I'm trying to implement this setup for a second time (second house) but I must be forgetting a step. I have a brand new pi. The amp is connected to the pi via RS232 to USB. And the pi is connected to my local network via ethernet. That all works fine and I can access my headless rpi with Putty via SSH (but when I telnet via Putty, I get "Network error: Connection refused". I've installed ser2tcp on the rpi.
I can't figure out what the next step is. The instructions say to "Go to the Serial Port and set it....", but I can't remember where to do that. I feel like a complete moron because I did it successful the first time with no problem.
Edit: I'm clearly doing something wrong. See error log from HE hub below
Summary
dev:5942021-07-19 03:16:46.710 pm errororg.codehaus.groovy.runtime.InvokerInvocationException: java.net.ConnectException: Connection refused (Connection refused) (updated)
dev:5942021-07-19 03:16:46.698 pm infoParent MonoPrice 6 Zone Amp Controller: initialize()
dev:5942021-07-19 03:16:46.696 pm infoParent MonoPrice 6 Zone Amp Controller: updated()
dev:5942021-07-19 03:16:07.170 pm errororg.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'null' with class 'null' to class 'int'. Try 'java.lang.Integer' instead on line 159 (installed)
dev:5942021-07-19 03:16:07.150 pm infoParent MonoPrice 6 Zone Amp Controller: initialize()
dev:5942021-07-19 03:16:07.080 pm debugParent setChildzones
dev:5942021-07-19 03:16:06.417 pm debugParent createChildDevices 1
dev:5942021-07-19 03:16:06.415 pm infoParent MonoPrice 6 Zone Amp Controller: installed()
Sorry for the super long reply I was in the hospital for a wile I almos didn’t make it out I hope you figure it out already but if you didn’t I’m back to answer a question I feel like you have the wrong port and the driver check what port the ser2net is running
Wow. Hope you're doing better!
I’m good now we have a saying “bicho malo nunca muere” This saying may be literally translated as "Bad creature never dies." so no worries here😈
3 Likes
Anyone else getting buzzing in the speakers from these? Mine started buzzing after several years. It's not loud, but it's audible and annoying. If I power down a zone, it stops on that zone. Thinking maybe a ground loop, but I haven't changed anything.
I had to rebuilt my rpi (long story) this weekend. Once I re-installed this awesome driver, I keep getting this error in my HE log: "java.net.ConnectException: Connection refused (Connection refused) on line 159 (method updated)".
Any ideas?
Edit: In case it helps, I also get this error when first creating the device: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'null' with class 'null' to class 'int'. Try 'java.lang.Integer' instead on line 159 (method installed). This is after ser2net is installed.
first double check you got the correct ip and port
I will take a look at the other error tomorrow
Yep, IP address is correct.
I'm using 23 as the port, but I'm not sure where that would have been set, because there's no reference to setting the port in the rpi/linux instructions.
Is been a while since I use that but on the Pi look in /etc/ser2net.conf and see if you can see what telnet port the script is using and set the parent device on the same port
