Page 14 of 19
Re: Domoticz-Google-Assistant (dzga)
Posted: Friday 23 December 2022 9:45
by kofec
Thanks a lot for quick reply. But probably it needs more modification. One was that I should change http -> https right ? That my fault as I didn't mentioned that I have SSL enabled
second question is regarding token. I have version DZGA Version: 1.10.9 and on settings page only one token is for Ngrok which I'm not using.
and I saw you commit:
https://github.com/DewGew/Domoticz-Goog ... /226/files
Maybe you mean this token ?
https://github.com/DewGew/Domoticz-Goog ... c8433b7a7c
Re: Domoticz-Google-Assistant (dzga)
Posted: Saturday 24 December 2022 13:11
by NilsNijenhuis
Hello DewGew and others,
I was working with dzga version 1.10.9 and update to the last master version. but cant sync devices anymore.
tried almost everything and did today a complete new install of the last master version on my raspberry and made a new project on Google.
But in the last step : in the google home app -> connect to [test] Huis
i get the sign in screen of DZGA but after using my username and password i get the following error : Could not reach [test] Huis please try again.
does anyone have a clue what can be the cause?
i am totally clueless.
Re: Domoticz-Google-Assistant (dzga)
Posted: Saturday 24 December 2022 16:50
by mark.sellwood
I'm trying to get Chromecast Notifications working, in config.yaml I have Chromecast_Name: LOunge
WHen I open
http://dzgaserver:3030/play?doorbell1.mp3 I get the following:-
Page not found!: 'NoneType' object has no attribute 'volume_level'
In the log I see ERROR - Chromecast playmedia unsuccefull, error : Chromecast None:8009 is connecting...
What Am I missing?
Fixed it, needed to add @50 to set the volume
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 28 December 2022 12:59
by DewGew
NilsNijenhuis wrote: ↑Saturday 24 December 2022 13:11
Hello DewGew and others,
I was working with dzga version 1.10.9 and update to the last master version. but cant sync devices anymore.
tried almost everything and did today a complete new install of the last master version on my raspberry and made a new project on Google.
But in the last step : in the google home app -> connect to [test] Huis
i get the sign in screen of DZGA but after using my username and password i get the following error : Could not reach [test] Huis please try again.
does anyone have a clue what can be the cause?
i am totally clueless.
i had restarted the hole pi again after the update and its linked again
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 28 December 2022 13:49
by DewGew
Correct observation. Its possible to use local ip adresses also if they are in the same network.
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 28 December 2022 14:47
by NilsNijenhuis
DewGew wrote: ↑Wednesday 28 December 2022 12:59
NilsNijenhuis wrote: ↑Saturday 24 December 2022 13:11
Hello DewGew and others,
I was working with dzga version 1.10.9 and update to the last master version. but cant sync devices anymore.
tried almost everything and did today a complete new install of the last master version on my raspberry and made a new project on Google.
But in the last step : in the google home app -> connect to [test] Huis
i get the sign in screen of DZGA but after using my username and password i get the following error : Could not reach [test] Huis please try again.
does anyone have a clue what can be the cause?
i am totally clueless.
i had restarted the hole pi again after the update and its linked again
i restarted dzga -> linking in the home app doesn't work
i restarten my raspberry -> linking in the home app doesn't work
any other tips?
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 28 December 2022 14:59
by DewGew
NilsNijenhuis wrote: ↑Wednesday 28 December 2022 14:47
DewGew wrote: ↑Wednesday 28 December 2022 12:59
NilsNijenhuis wrote: ↑Saturday 24 December 2022 13:11
Hello DewGew and others,
I was working with dzga version 1.10.9 and update to the last master version. but cant sync devices anymore.
tried almost everything and did today a complete new install of the last master version on my raspberry and made a new project on Google.
But in the last step : in the google home app -> connect to [test] Huis
i get the sign in screen of DZGA but after using my username and password i get the following error : Could not reach [test] Huis please try again.
does anyone have a clue what can be the cause?
i am totally clueless.
i had restarted the hole pi again after the update and its linked again
i restarted dzga -> linking in the home app doesn't work
i restarten my raspberry -> linking in the home app doesn't work
any other tips?
Try Goto action on google and press Test button again.
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 28 December 2022 17:19
by NilsNijenhuis
My DZGA works again, test button and the home grapgh wasn't linked to the correct project
Domoticz-Google-Assistant (dzga) chromecast notification
Posted: Thursday 29 December 2022 19:27
by lec668
Hi
I've been using dzga since the beginning, great job for controling Domoticz ! And many thanks for creating it !
I have trouble adding the chromecast notification to work on my functional dzga.
I assume manual modification of the smarthome.py is no longer necessary (as per Wiki),
as I find the code included in the current version of the script ?
I added Chromecast device or Group to the yaml file, the script display "Starting up chromecasts", domoticz control is still fine.
But when I try somethine like http://dzga-domoticz-ip:port/say?bonjour/fr
I only get
Page not found!: slugify() got an unexpected keyword argument 'only_ascii'
What could go wrong ?
Thanks for helping and merry Christmas
Re: Domoticz-Google-Assistant (dzga)
Posted: Monday 30 January 2023 10:41
by fabry91
Good morning guys,
same problem here with DZGA, when I have updated from the web interface to the v1.23.2 master all switches and etc. results offline in the Google Home app and audio control on our Google Nest didn't work.
The problem were later on solved with adding again the DZGA action project from the Google Home app.
The Sync Devices in the web interface of DZGA still don't work.
Thank you
Re: Domoticz-Google-Assistant (dzga)
Posted: Monday 20 February 2023 20:10
by paede
Hi
Fist I want to thank you for this great work.
I used controllicz for a few years, which will end its service in summer.
That's why I decided to take the effort to setup dzga.
I've got most of it working. I have a raspberry pi 3 with domoticz, nginx reverse proxy and dzga running.
First issue:
When I reboot the pi a have to login via putty and restart nginx to get dzga working. nginx is running after the bootup but the connection via XXXXX.mooo.com does not work. When I restart nginx "sudo service nginx restart" it works.
second issue:
when I execute scenes with voice on google home, the scene is executed, but google tells me that there is an error. See dzga-log:
Code: Select all
2023-02-20 18:42:15 - INFO - {
"inputs": [
{
"context": {
"locale_country": "DE",
"locale_language": "de"
},
"intent": "action.devices.EXECUTE",
"payload": {
"commands": [
{
"devices": [
{
"id": "Scene20"
}
],
"execution": [
{
"command": "action.devices.commands.ActivateScene",
"params": {
"deactivate": false
}
}
]
}
]
}
}
],
"requestId": "5882158549538026065"
}
2023-02-20 18:42:15 - INFO - Google Assistant requests an action.devices.EXECUTE
2023-02-20 18:42:22 - ERROR - 400 Client Error: Bad Request for url: https://homegraph.googleapis.com/v1/devices:reportStateAndNotification
2023-02-20 18:42:22 - ERROR - Error handling message {'inputs': [{'context': {'locale_country': 'DE', 'locale_language': 'de'}, 'intent': 'action.devices.EXECUTE', 'payload': {'commands': [{'devices': [{'id': 'Scene20'}], 'execution': [{'command': 'action.devices.commands.ActivateScene', 'params': {'deactivate': False, 'online': True}}]}]}}], 'requestId': '5882158549538026065'}: {'errorCode': 'unknownError'}
Turning on or off a lamp does work without that error.
Code: Select all
2023-02-20 19:55:48 - INFO - {
"inputs": [
{
"context": {
"locale_country": "DE",
"locale_language": "de"
},
"intent": "action.devices.EXECUTE",
"payload": {
"commands": [
{
"devices": [
{
"id": "Light236"
}
],
"execution": [
{
"command": "action.devices.commands.OnOff",
"params": {
"on": false
}
}
]
}
]
}
}
],
"requestId": "3097062509886629023"
}
2023-02-20 19:55:48 - INFO - Google Assistant requests an action.devices.EXECUTE
Do you have an idea how to solve one of these issues?
greets paede
Re: Domoticz-Google-Assistant (dzga)
Posted: Tuesday 21 February 2023 22:35
by mark.sellwood
dzga in Docker
I'm trying to get dzga working in Docker, I have followed the instructions but end up with an error as follows:
=> ERROR [3/8] RUN mkdir -p config
Im on a Pi with Bullseye
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Docker version 20.10.22, build 3a2c30b
Any pointers please?
Re: Domoticz-Google-Assistant (dzga)
Posted: Thursday 23 February 2023 10:22
by paede
Some things I found during further testing:
this is my nginx sites-enabled/default
Code: Select all
server {
listen 80;
listen [::]:80;
server_name heimautomation.mooo.com;
#change to match your address
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name heimautomation.mooo.com;
#change to match your address
ssl_certificate /etc/letsencrypt/live/heimautomation.mooo.com/fullchain.pem;
#change to match your address
ssl_certificate_key /etc/letsencrypt/live/heimautomation.mooo.com/privkey.pem;
#change to match your address
#ssl on;
#ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
ssl_prefer_server_ciphers on;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Scheme $scheme;
proxy_pass http://localhost:3030; #Local ipno to dzga
proxy_read_timeout 90;
}
location /domoticz/ {
rewrite ^/domoticz/?(.*) /$1 break;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Scheme $scheme;
proxy_pass http://localhost:8080; #local ipno to domoticz
proxy_read_timeout 90;
}
location /assistant/ {
rewrite ^/assistant/?(.*) /$1 break;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Scheme $scheme;
proxy_pass https://localhost:3030; #local ipno to dzga
proxy_read_timeout 90;
}
}
to access domoticz via
https://heimautomation.mooo.com/domoticz I had to ad a second / --> location /domoticz/ {
now that connection is working
I tried the same for the google connection --> location /assistant/ {
then I realized that I had
https://heimautomation.mooo.com/smarthome (or /oauth or /token) in google action console.
I changed that to
https://heimautomation.mooo.com/assistant/smarthome (etc.)
But now when I try to ad the [test]DomoticzVerbindung app I get a "502 Bad Gateway" error.
The same when I use a webbrowser with
https://heimautomation.mooo.com/assistant/settings
when I remove the s in nginx default settings on "proxy_pass
https://localhost:3030;" the domoticz-google-assistant settings page loads and the [test]DomoticzVerbindung connects. (not as stated in aditional settings
https://github.com/DewGew/Domoticz-Goog ... erse-proxy)
I can:
- access domoticz with https
- turn on/off lamps via google home
- activate scenes via google home (but still got the error message)
to be solved:
- get rid of the error message
- nginx service needs to be restarted after a reboot to use dzga
- add and connect the [test]DomoticzVerbindung to my wifes google home app
- [test]DomoticzVerbindung in my wifes google home app has only 1 device connected (instead of 105 devices)
update: I changed "proxy_pass
https://localhost:3030; #local ipno to dzga" to "proxy_pass
https://127.0.01:3030; #local ipno to dzga" now there is no restart of the service needed after a reboot.
What can I do to get all devices recognized in my wifes google home app?`
How can I get rid of the "error message"?
as I did not get any response here in the forum for my issues with dzga, I decided to give node-red and node-red-contrib-google-smarthome a try (
https://flows.nodered.org/node/node-red ... -smarthome)
after a few hours to understand how nodered works, I got everything working fine. I can execute scenes without any error messages
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 08 March 2023 19:39
by kofec
DewGew wrote: ↑Wednesday 28 December 2022 13:49
Correct observation. Its possible to use local ip adresses also if they are in the same network.
Can someone was able to authenticate via token ? Can give example of script (curl, wget, python script)? I tried:
Code: Select all
curl -v --insecure -H 'Accept: application/json' -H "Authorization: Bearer aAaAaAaAaAaAaAaAaAaA" https://192.168.100.150:3030/sync
* Trying 192.168.100.150:3030...
* TCP_NODELAY set
* Connected to 192.168.100.150 (192.168.100.150) port 3030 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=...............
* start date: Mar 1 10:19:19 2023 GMT
* expire date: May 30 10:19:18 2023 GMT
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET /sync HTTP/1.1
> Host: 192.168.100.150:3030
> User-Agent: curl/7.68.0
> Accept: application/json
> Authorization: Bearer aAaAaAaAaAaAaAaAaAaA
>
* Mark bundle as not supporting multiuse
* HTTP 1.0, assume close after body
< HTTP/1.0 307 Temporary Redirect
< Server: BaseHTTP/0.6 Python/3.11.1
< Date: Wed, 08 Mar 2023 18:23:16 GMT
< Location: login?redirect_uri=sync
<
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 15 March 2023 17:45
by DewGew
kofec wrote: ↑Wednesday 08 March 2023 19:39
DewGew wrote: ↑Wednesday 28 December 2022 13:49
Correct observation. Its possible to use local ip adresses also if they are in the same network.
Can someone was able to authenticate via token ? Can give example of script (curl, wget, python script)? I tried:
Code: Select all
curl -v --insecure -H 'Accept: application/json' -H "Authorization: Bearer aAaAaAaAaAaAaAaAaAaA" https://192.168.100.150:3030/sync
* Trying 192.168.100.150:3030...
* TCP_NODELAY set
* Connected to 192.168.100.150 (192.168.100.150) port 3030 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=...............
* start date: Mar 1 10:19:19 2023 GMT
* expire date: May 30 10:19:18 2023 GMT
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET /sync HTTP/1.1
> Host: 192.168.100.150:3030
> User-Agent: curl/7.68.0
> Accept: application/json
> Authorization: Bearer aAaAaAaAaAaAaAaAaAaA
>
* Mark bundle as not supporting multiuse
* HTTP 1.0, assume close after body
< HTTP/1.0 307 Temporary Redirect
< Server: BaseHTTP/0.6 Python/3.11.1
< Date: Wed, 08 Mar 2023 18:23:16 GMT
< Location: login?redirect_uri=sync
<
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):
Make sure you are using https POST method not http GET.
Re: Domoticz-Google-Assistant (dzga)
Posted: Friday 17 March 2023 16:15
by kofec
Re: Domoticz-Google-Assistant (dzga)
Posted: Friday 17 March 2023 16:27
by kofec
And it is working fine now:
curl -v --insecure -H 'Accept: application/json' -H "Authorization: Bearer aAaAaAaAaAaAaAaAaAaA" --data "SYNC" -X POST
https://192.168.100.150:3030/sync
Synchronization request sent, status_code: True
Re: Domoticz-Google-Assistant (dzga)
Posted: Tuesday 18 April 2023 20:03
by meal
Hello,
1 - Context of the issue:
Domoticz on RPI3B
Version: 2023.1 (build 15182)
Build Hash: 34815c1a9-modified
Compile Date: 2023-04-10 17:22:59
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Oct 31 2022, 14:04:00) [GCC 8.3.0]
Domoticz-Google-Assistant 1.23.2
2 -Description of the issue
I have 50 devices in Domoticz version 2022.1 which are interfaced with Domoticz-Google-Assistant v1.11.10
The interface was operating correctly so far.
I have upgraded Domoticz to version 2023.1 and DZGA to 1.23.2.
Since then for a set of devices of type "doorlock", "Selector" I can voice control the devices and it reflects correctly in Domoticz but I get the error
"ERROR - 400 Client Error: Bad Request for url:
https://homegraph.googleapis.com/v1/dev ... tification" in DZGA.LOG and the state is not reflected in Google Home which creates discrepancies between Domoticz and Google Home.
If anybody has implemented DZGA with Domoticz 2023.1 and managed to run correctly such devices of these subtype I would be interested to share the configuration.
I would be keen to share any hint to fix the issue.
Many thanks in advance
BR
Re: Domoticz-Google-Assistant (dzga)
Posted: Wednesday 19 April 2023 13:38
by Xavier82
Did you checked the wiki?
https://github.com/DewGew/Domoticz-Goog ... figuration:
Light or Switch devices can choose types from:
light, ac_unit, bathtub, coffeemaker, doorbell, dishwasher, dryer, fan, heater, kettle, media, microwave, outlet, oven, speaker, switch, vacuum, washer, waterheater, window, door, gate, garage.
For heater, kettle, waterheater, oven you can still use merge_thermo_idx to merge thermostat to control temperature.
Door Contact devices can choose window, gate or garage.
Blind devices can choose window, door, gate or garage.
Selector devices can choose only vacuum
Pushbutton devices can choose doorbell, light, outlet
These are the supported devices.
Did it worked before the upgrade of Domoticz and DZGA?
Re: Domoticz-Google-Assistant (dzga)
Posted: Thursday 20 April 2023 9:22
by meal
Hello,
Yes it was working perfectly in the previous version of Domoticz 2022.1 which are interfaced with Domoticz-Google-Assistant v1.11.10
"Door Lock" does not work any longer.
BR