Thanks a lot for replying! I tried this already, can’t get it to work. Do I have to change (audio) to a value? My sonos are completely silent with this piston ^^
Was on the ancient 1.0 version of Assistant Relay forever, but had to reset my Pi so I’m updating to 3.3.
Is the version of Node limited to what’s spec’d in the install instructions - v 10.13.0, or can I install the current LTS - 12.13.3 ?
Thanks!
Would this allow me to create a virtual toggle/button in ST that sends a command to Assistant Relay to run a Routine with Google/Home Assistant?
The SDK doesn’t yet allow you to trigger routines
ah, ok, thanks!
Can’t all of this be done much easier with cast-api?
No, you can’t cast webpages with cast-web. Only media.
Using this w/the broadcast pistons that I have been updating, and it works great. Thanks VERY much for creating this!
1 Like
My pleasure. I figured this would be easier to maintain than separate pistons and a bunch of Global variables. Glad it’s working for you! 
Absolutely.
I did notice one odd thing - check the Help-Assistant-Relay Discord, I put info and screen shots there.
Can you use this driver with GAR 3.31?
It’s posted in a “3.3” thread so I would expect it to work.
One issue I did notice, and don’t know if I did something to cause it or if it’s a issue w/the DTH, but after you create the virual device using the DTH, check that the values you entered in the DTH code before you saved/published it, were properly transferred to the virtual device.
In my case I had to edit the device settings to re-add the IP address info, etc., that I had previously put into the DTH. Again, I may have screwed something up, but just in case you run into a similar issue…
DTH w/values entered into DTH when I created it:
But the device didn’t seem to get the values:
Edited device and found that the values were there, but not in the fields for some reason - I entered them into the fields and saved and all was well.
Thanks. I’ll check it out.
I had the same issue with the values crossing over correctly to the device. Thanks for the heads-up. Works for me too after adding the values into the blank fields for the device preferences.
1 Like
Cool, thanks for confirming. Should be an easy fix for @Ryan780.
LOVE not having to define the variables in every piston. 
What?!? You enter the properties after you create the device. Not in the DTH. The DTH can support many, many devices. I have no idea what you are talking about.
That is how you enter device settings. LMAO
There’s nothing to fix. That’s how devices work. You enter the value in after you create the device. How would you put the values in before?
LOL…I edited the DTH to add the device info, thinking that was part of the setup process. From your aghast response I clearly misinterpreted the setup process.
I edited the Preferences section in the DTH before I published it:
preferences {
input(name: "serverIP", type: "string", title:"Server IP Address", description: "192.168.20.6", required: true, displayDuringSetup: true)
input(name: "serverPort", type: "string", title:"Server Port", description: "3000", defaultValue: "3000", required: true, displayDuringSetup: true)
input(name: "user", type: "string", title:"Assistant Relay Username", description: "Dana", defaultValue: "", required: false, displayDuringSetup: true)
input(name: "defaultDevice", type: "string", title:"Display Device IP or Name", description: "192.168.20.33", required: false)
When I tried to use the driver in a piston at first it didn’t work, and it happened that the first place I looked for a reason wa in the DTH, and when I saw “Preferences” there I said “AHA! I forgot to put in my preferences.” Your original post didn’t mention adding the preferences to the device so I jumped to the wrong conclusion.
Also apologies to @smartxray for taking you down the wrong path. <oops!>
As my father says, when you find yourself in a hole, the first thing to do is put the shovel down. 
I’ll put it down now.