Domoticz

BazsoDombiAndras wrote: ↑Wednesday 13 November 2019 1:24 Hi All!

First of all, thank you DewGew for this Python server, looks like a very promising project!

I'm trying to set it up, but I'm stuck on setting the URLs as per the instructions:

Code: Select all

Navigate back to the Actions on Google Console.

On the top menu click Develop, then on the left navigation menu click on Actions.
Enter the URL for fulfillment, e.g. https://<YOUR REVERSE PROXY URL>/smarthome (replace with your actual URL), click Done.
On the left navigation menu under Account Linking.
Select No, I only want to allow account creation on my website. Click Next.
For Linking Type, select OAuth.
For Grant Type, select Authorization Code for Grant Type.
Under Client Information, enter the client ID and secret from earlier.
Change Authorization URL to https://<YOUR REVERSE PROXY URL>/oauth (replace with your actual URL).
Change Token URL to https://<YOUR REVERSE PROXY URL>/token (replace with your actual URL).

Let's say that the Domoticz Python server is running on 192.168.0.200:3030
I have an Apache reverse proxy and I have set up some redirects like:
domoapp.mydomain.com -> 192.168.0.200:3030/smarthome
domoappoauth.mydomain.com -> 192.168.0.200:3030/oauth
domoapptoken.mydomain.com -> 192.168.0.200:3030/token

The problem is that the above links don't even work on the local server, I mean if I enter 192.168.0.200:3030/smarthome into a browser, I get "not supported". If I enter 192.168.0.200:3030/oauth into the browser, I get "response_type must equal "code". If I enter 192.168.0.200:3030/token into the browser, I get "Page not found!: '/token'".

Could you please clarify what the proper target URLs are on the local server for the smarthome, oauth and token endpoints that need to be specified to Google? I mean what URLs should the reverse proxy redirects point to on the local machine on which the Python server is running? In other words, what are the endpoint URLs to which the Python server responds? Where should the reverse proxy direct the traffic to?

Another thing that is not clear: what should the OAuth credentials (U_NAME and U_PASSWD) be in the config.py? Can I enter any username and password there and something will ask for them? Or should these values be taken from somewhere from Google?

One final thing:

Code: Select all

Select No, I only want to allow account creation on my website. Click Next.
For Linking Type, select OAuth.
For Grant Type, select Authorization Code for Grant Type.

This part never came up during the Google setup process. The Google settings must have changed since the instructions were put together. Now there's no way to say "No, I only want.." and there is no field for specifying Grant type. This is what the Account Linking page looks like today:

accoutnlinking.png

Thank you!

Select No, I only want to allow account creation on my website. Click Next.
For Linking Type, select OAuth.
For Grant Type, select Authorization Code for Grant Type.

BazsoDombiAndras wrote: ↑Friday 15 November 2019 11:03 The DZGA server is not on the same machine as the Domoticz server, but they are on the same high-speed local network (both on WiFi). I guess I could try to move the DZGA to the Domoticz machine, but the requests would go through the current DZGA machine anyway, because that one operates the reverse proxy (and I can't move that). This 4-5 second timeout is a bit unreasonable. I've read that it's a Google setting.

tage wrote: ↑Saturday 16 November 2019 11:54 Hi

i also have some trouble to get this to work.
domoticz -> raspberry
Domoticz-Google-Assistant -> linux pc
and reverse proxy (pound) same linux pc
router portforward port 443 to linux pc
reverse proxy listen port 443 send that to port 3030 (Domoticz-Google-Assistant)
double check and have make new projects on google console just to make sure that is okey.
when try add "test" project in google home i come to login page and when type username and password i got this in domoticz-google-assistant log :

Code: Select all

192.168.0.10 - - [16/Nov/2019 11:36:10] "POST /login HTTP/1.1" 301 -
192.168.0.10 - - [16/Nov/2019 11:36:11] "GET /login?client_id=574522741018-46vmha139e9vi049mlucupdiq49dp3gt.apps.googleusercontent.com&redirect_uri=https%253A%252F%252Foauth-redirect.googleusercontent.com%252Fr%252Fmitt-projekt-259118&redirect=/oauth&state=AB8b_TOhbrqakbQy04zp9D8Xt-5pgNQmUuVDQiDdFNP4rthBSz9OXZ5Fw1Y8mDAV7Sv7KzgBurXetyTqwrb8T-kRuQ2TdTblyVdUTR_zhffPz5tipNx0EpzUvZzgGe6r3yhtl7ciO5gC5agRvoENE9pYGOEl6tCaW754HqjxM6g8FdjAaXlKWvZpYhqi_19eIKk-tnEeww0QjmXB-OuMDdBJWgi7GGu-C4vu2agewbPHQtBvxGl14rdAAk6WgcOj-U7Jjn2CUHUy8OcP8rKflBm17e7XgYQfQ_GNhz62wL7SC_WBKsWW7ueHlcTheEUc2yIH_2LUsohOaXf1k5zL3ZouS3GmzjyvUDWuproy4NTssaSy0OLniMwJsT5q2r2BUJxqVHIDdWAUVjkPma8scgF1VbwupfDy0UYARNbkm2EP-Ad1aMpoYqLhKN9ibuCEKIbpfpg80rAWg2dbzCtZbRiApVj6S5QiDAjsLe6LVsfo2NSM0YH_mXqmpJ6FgetML4Ae3VaN8uniwe9BhaoylEwfaK2bX1fIyxqE56CsUwQ3G-G48KHi4t8ldnsuQo2qhg89ysNH9OcrrxFczUNxUnhNoYbOpBo-7ayvwJmwlL_35_aeQUcbteA HTTP/1.1" 200 -

and got back to add new device app.
when try again and select my test app this shows up on phone/tablet :

Code: Select all

Page not found!: '/https%3A%2F%2Foauth-redirect.googleusercontent.com%2Fr%2Fmitt-projekt-259118'

then i have to kill python3 pid and start it again to come to login page when trying again .

/tage

I need some more feedback on dzga server beta try beta:

EscApe wrote: ↑Thursday 21 November 2019 21:30 @DewGew

I need some more feedback on dzga server beta try beta:

Thanks again.. just pulled the latest beta. I ran into some trouble, but that might have been my own fault. The previous beta was working fine, but after updating my devices would show offline. Removed and re-added from google home and all is fine again. I did change my username and password a couple of weeks ago, so maybe that was the cause? I had no problems restarting the service (within those couple of weeks), but an update might be different(?)

Anyway, the latest beta seems to be working just fine.

Probably every single user has this issue, but it feels I'm the only one who noticed and had issues with it (due to IR).

EscApe wrote: ↑Sunday 24 November 2019 13:53

Probably every single user has this issue, but it feels I'm the only one who noticed and had issues with it (due to IR).

Looks like you are right. I did not notice it, but can see the double commands in my logs.