I need the help from the experts for sure. I did reinstall from scratch and even started from Rasbian and installed the node.js version 8.12.0 with assistant-relay v2.1.1.
I got the message Assistant Relay is now setup and running for ram.
Getting the below error If I try to access using http://localhost:3000 or using the ip
This site can’t be reached
localhost refused to connect.
I would really appreciate if you could help me to resolve this issue. I don’t know what went wrong twice.
How can this be used with SHM or other smartapps that cant sent POST requests? Didn’t v0.1 have a device handler that created a device in ST, can that be used with v2?
Also is there a way to better sync the speaker output together, when I issue a broadcast the message is echoed thoughout my house. Each speaker is not playing the message at the exact same time.
I get the error:
Cannot find module ‘google assistant’
Install had some errors too.
Using node.js on a windows box.
Hi folks, do you think is possible to run the node.js code under a free online service?
I do not like to use another device such raspberry
i’m triyng too, it is very painfull. At th moment it is not running as well
Interesting developments are occurring with the Google Broadcast feature -
“The Broadcast feature for smart speakers and Smart Displays will now be more of a two way street than a simple broadcast. When you’re out and sending a broadcast users listening to it will be able to respond.”
Anyone know if you can run this on android using Dory - node.js / javascript?
Trying to install it and getting the same issue as above can not find module google-assistant.
Any help would be greatly appreciated.
Wont work. It needs to be Windows or Unix based platforms
Dang… had an old phone i wanted to use as a relay / smarthome controller
@ghesp, I have some update.
I just ran the command forever start server/app.js and looks like the server is running but got the below message.
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: server/app.js
When I access my local host I’m getting the message “Dude, chill, it’s quiet time!”
I did change the time values to start as 25 and end as 25 didn’t work then tried 0 and 0 didn’t help
“muteStartup”: true,
“quietHours”: {
“start”: 25,
“end”: 25
},
If I make changes to the quietHours then how do I publish the changes? It looks like it is not taking it.
My assistant relay is working now.
I had to get rid of the quiet hours logic by commending out the code from app.js.
// if (global.config.quietHours !== undefined && (global.config.quietHours.start <= now || global.config.quietHours.end >= now)) {
// console.log('Got a command during quiet hours (start: ’ + global.config.quietHours.start + ', end: ’ + global.config.quietHours.end + ’ now: ’ + now + ‘). Ignoring.’);
// res.status(420).send(“Dude, chill, it’s quiet time!”);
// return;
// }
The syncing is supposed to be fixed in later releases of Google Assistant.
As for sending broadcasts from SHM, there’s no way to do that natively but you can use a Virtual switch and “alert with lights” to turn on that switch. You can then respond to that virtual switch from something like webCoRE.
I recently setup Google Assistant Relay v2 and was also wondering how this would interact with SmartThings and have built a smartapp to handle POSTing the JSON to the Google Assistant Relay server to get notifications in the event of any of my devices changing state.
Google Assistant Relay Notifications SmartApp
https://github.com/braytonstafford/google-assistant-relay
I’d love to get @ghesp’s feedback on this as well
Is anyone currently having problems with Assistant Relay? Before I go tearing apart my end, it would be nice to clarify it’s not Google’s end. It seemed to stop a few days ago (~20 November?).
I’m posting the attached template within Postman and these are the results -
Hi, In short, Thanks for all the details, which helped me in setting this up, my Curl commands work perfectly fine, but my test piston isn’t. I am having the exact issue mentioned in [Release] Google Assistant Relay V2.0 - Google Home Audio Notifications!
Not sure what was done to fix it, per post [Release] Google Assistant Relay V2.0 - Google Home Audio Notifications!
But I am unable to make it work. Any help appreciated. Thx.
Having no issues here.
Have you guys downloaded the actual release and not just cloned the repository? There is code in the repo thats still a WIP
Greg,
Below are my Piston and logs, still unable to figure out the issue. Curl works fine, Postman also does work fine, where my GH announces the command.
11/23/2018, 10:20:56 AM +795ms
+0ms ╔Received event [Home].time = 1542990055706 with a delay of 1088ms
+407ms ║RunTime Analysis CS > 230ms > PS > 166ms > PE > 12ms > CE
+410ms ║Runtime (37277 bytes) successfully initialized in 166ms (v0.3.108.20180906) (409ms)
+412ms ║╔Execution stage started
+423ms ║╚Execution stage complete. (12ms)
+425ms ╚Event processed successfully (425ms)
11/23/2018, 10:20:35 AM +575ms
+0ms ╔Received event [Home].test = 1542990035574 with a delay of 0ms
+83ms ║RunTime Analysis CS > 23ms > PS > 47ms > PE > 14ms > CE
+86ms ║Runtime (37262 bytes) successfully initialized in 47ms (v0.3.108.20180906) (85ms)
+87ms ║╔Execution stage started
+94ms ║║Cancelling statement #1’s schedules…
+120ms ║║Sending internal web request to: 10.0.0.19:9000/assistant
+128ms ║║Executed virtual command httpRequest (22ms)
+130ms ║║Requesting a wake up for Fri, Nov 23 2018 @ 10:20:55 AM CST (in 20.0s)
+148ms ║╚Execution stage complete. (61ms)
+157ms ║Setting up scheduled job for Fri, Nov 23 2018 @ 10:20:55 AM CST (in 19.975s)
+167ms ╚Event processed successfully (167ms)
Strangely, lack of response from Assistant Relay ‘self-fixed’ after a couple of days without my intervention.
I have a mechanism that is polling the Assistant Relay with a command every 30 seconds. I’m beginning to wonder whether Google ‘kicks-off’ accounts for over-use, or has some other limit prescribed.
Everything seems fine there.
If you see the logs in Assistant Relay saying it’s triggered X, then there’s nothing wrong on this side, the issue is likely either with your account configuration or Google
