@MARZIMA Donāt know if it can help for the QA process, but Homeseer solution can be controlled by Google assistant since last summer. Even if Homeseer have some āall-in-oneā devices, their solution is essentially web based with some plugins (equivalent to bindings in openhab) and can be installed on any machine, including a raspberry pi.
From the way I see it, there are some similarities in the overall architecture of their solution, can the process they got through be used as a reference by Google ?
In the meantime, thanks for your dedication and hard work
Thereās a couple home automation aggregators controllable now through
assistant⦠Yonomi recently got approval as well. Odds are we just need to
be patient.
I dont think that they started with the official access to the APIs. Some been there before anyone was able to integrate.
So guys, again I did my part and wait for their feedback since they been at CES.
Iam not sure if the referencing to others help, since we dont know how long they even took for QA process.
They told me there is no really official OSS smarthome integration beside one unofficial.
Checked the function logs (completely forgot about it).
I had following error:
{"severity: "ERROR"
textPayload: āError: getaddrinfo ENOTFOUND āYOUR-CLOUD-HOSTā :443
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)ā "
}
So I figured out that for some reason google functions was deployed with wrong configuration (functions/config.js). After fixing URL and redeploying āgcloud beta functions deploy ā¦ā it solved my problems and it started to work. Thank you for your advice!
I am glad you got your setup working. I still have issues ;-(
2018-01-18 15:46:48.538 CST openhabGoogleAssistant zr8uc0z0lw42 ReferenceError: data is not defined at IncomingMessage.<anonymous> (/user_code/rest.js:46:53) at emitNone ``(events.js:91:20) at IncomingMessage.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at ``_combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickDomainCallback ``(internal/process/next_tick.js:128:9) Expand all | Collapse all { insertId: "000000-9cdec294-5355-49a5-873b-0bdb34d21bf9" labels: {ā¦} logName: "projects/openhab-gassist/logs/cloudfunctions.googleapis.com%2Fcloud-functions" receiveTimestamp: "2018-01-18T21:46:57.581052675Z" resource: {ā¦} severity: "ERROR" textPayload: "ReferenceError: data is not defined at IncomingMessage.<anonymous> (/user_code/rest.js:46:53) at emitNone (events.js:91:20) at IncomingMessage.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickDomainCallback (internal/process/next_tick.js:128:9)" timestamp: "2018-01-18T21:46:48.538Z"
Two oauth IDs were created. Which one of the two are you using:
Just to be sure, the issues described here are issues to get Google Home working before official release?
Later this will all be included in Google Home Binding?
Hello i am also trying to get this beta running i am at the point where i need to fill in (url": āhttps://YOUR-URL/openhabGoogleAssistantā) what are you guys using for that can i use my duckdns,org domain or the myopenhab.org and if you are not using myopenhab site how are you securing the site apart from httpasswd?
Hi Now i am at the Account Linkage & OAuth2 where do get this info from
Client ID:
Client secret:
Authorization URL: https:///oauth
Token URL: https:///token
I think i got the client secret and client id from the google api console.
Now trying to figure out
Authorization URL: https:///oauth
Token URL: https:///token
should that be my https://duck.duckdns.org:port/oauth