it was the certificate i made a new one with certbot from letsencrypt after that it worked..
would be greate with a small simple howto with reverse proxy and cert. now i know how to but i guess others want that

/ tage
Moderator: leecollings
Great that its working now. I use synology. It has a reverse proxy built in.tage wrote: ↑Wednesday 27 November 2019 19:52 sorry late answer but i finally found what was wrong ..
it was the certificate i made a new one with certbot from letsencrypt after that it worked..
would be greate with a small simple howto with reverse proxy and cert. now i know how to but i guess others want that
/ tage
Code: Select all
bash <(curl -s https://raw.githubusercontent.com/DewGew/dzga-installer/master/install.sh)
Hello DewGew, this latest version works fine, thank you for keeping it uptodate and improving it. Just a few minor issues that i have faced updating from previous version:DewGew wrote: ↑Friday 29 November 2019 9:57 New update on github dzga v1.3.2.
- Configuration in yaml file
- Improved color temperature
- Graphical user interface
Try out latest, For rpi/ubuntu users, just open a terminal window and execute this command. Thats it!
- Auto install for rpi/ubuntu
Code: Select all
bash <(curl -s https://raw.githubusercontent.com/DewGew/dzga-installer/master/install.sh)
For manual install klick here
Thank you for your feedback. I created 2 issues github with your post. Github Issue #47 and Github Issue #48lzwfkv wrote: ↑Monday 02 December 2019 6:30Hello DewGew, this latest version works fine, thank you for keeping it uptodate and improving it. Just a few minor issues that i have faced updating from previous version:DewGew wrote: ↑Friday 29 November 2019 9:57 New update on github dzga v1.3.2.
- Configuration in yaml file
- Improved color temperature
- Graphical user interface
Try out latest, For rpi/ubuntu users, just open a terminal window and execute this command. Thats it!
- Auto install for rpi/ubuntu
Code: Select all
bash <(curl -s https://raw.githubusercontent.com/DewGew/dzga-installer/master/install.sh)
For manual install klick here
Regarding installation:
- Had to map all the settings from previous config.py to config.yaml, in particular it is time consuming for Device_Config; it is tedious, but nevermind i have done it by now.
- Had to remove "pkg-resources>=0.0.0" from pip-requirements.txt because pip could not find such a module and gave errors. By the way, as i understand, it is not needed to explicitely declare such a module as a dependency.
- In the installation procedure, I couldn't find pip command installed on the system, i have pip3 only and i used it successfuly. Using pip3 would also ensure python3 is used.
Functionality:
- pyngrok shoudn't be a mandatory requirement, because i use Caddy Proxy for exposing DZGA to Google Assistant and i don't need/want to set up a tunnel with ngrok proxy, but i am forced to install pyngrok anyway.
It would be wonderful if you could look into restoring the fail back of device_config with config.yaml configuration, because i think it is by far preferrable to have all the devices' configurations centralized into one place, rather than having them spread across multiple devices in Domoticz, with the risk to forget or miss where device are configured or not, and which devices are configured.
- voicecontrol device configuration is not failed back to the settings in config.yaml when tags are not found on the Domoticz device's description. It only checks for device description tags <voicecontrol> in Domoticz, if not found then devices customization is not synch'ed with G Home even if they are configured in config.yaml in Device_Config section.
Thank you again.
Google requieries a ssl connection with a valid certification. You can use your own domain or reverse proxy with a dns provider. I should update the readme and wikiProfaNe wrote: ↑Sunday 01 December 2019 14:32 First of all, thank you for building this app.
I tried configuring Google Assistant with domoticz but i found some issues and vague steps in the manual.
First step is to clone the project and install the requirements with "pip install -r". The next step is to start the project with "python3". Shouldn't the "pip install -r" be "pip3 install -r" just to be sure the python packages for python3 are installed?
When i start the project with "python3" there is still a package missing named pyngrok. This could be my setup only. Also i think you can remove pkg-resources from the requirements list.
I can start the app with "python3" and everything works so far. I can go to /settings and edit everything. I can see my devices from domoticz appearing in the app.
When i sync the devices i can see a 404 in the log:
2019-12-01 13:57:03 - DEBUG - https://homegraph.googleapis.com:443 "POST /v1/devices:requestSync?key=******************* HTTP/1.1" 404 None
When i open google home on my android device the "[test]appname" does appear but when i click it it does nothing. I wont get a login or anything. I dont see anything in my logs on my raspberry pi. There seems to be no connection between google and the domoticz app on my raspberry. When i click "test" on the "actions on google" console i get a error "something went wrong". Should i see any logs on my raspberry when i test the action on "actions on google"?
I have run trough the manual multiple times and all the settings should be correct. Could using my IP without a certificate cause any problems? I use nginx as proxy with https but without valid certificate. Since i have already a app running on port 443 on my raspberry pi iam running nginx on port 444 and portfoward 443 to 444 on my router. Are there also any privacy settings on my google account i should check?
Edit: i fixed it now by using the ngrok tunnel. I guess using my public IP without valid certificate wont work. Will it work when i use a domain name with valid certificate? Also, is it possible to hide devices from google home?
There is one issue with my milight lights. I have them setup as a switch in domoticz and my milights appear in google home but with the following error:
Error handling message {'requestId': '1786981529328158506', 'inputs': [{'context': {'locale_country': 'NL', 'locale_language': 'nl'}, 'intent': 'action.devices.EXECUTE', 'payload': {'commands': [{'devices': [{'id': 'ColorSwitch21'}], 'execution': [{'params': {'on': False}, 'command': 'action.devices.commands.OnOff'}]}]}}]}: {'errorCode': 'unknownError'}
127.0.0.1 - - [01/Dec/2019 15:32:07] "POST /smarthome HTTP/1.1" 200 -
Response: {
"requestId": "1786981529328158506",
"payload": {
"errorCode": "unknownError"
}
}
This is the milight when i sync devices:
{
"willReportState": false,
"deviceInfo": {
"manufacturer": "milight"
},
"traits": [
"action.devices.traits.OnOff",
"action.devices.traits.Brightness",
"action.devices.traits.ColorSetting"
],
"attributes": {
"colorTemperatureRange": {
"temperatureMinK": 1700,
"temperatureMaxK": 6500
},
"colorModel": "rgb"
},
"name": {
"name": "Slaapkamer Lamp"
},
"type": "action.devices.types.LIGHT",
"id": "ColorSwitch21"
}
I can still use my voice commands to turn on/off the light but google home mini says there is an error each time. The google home app says it is not responding.
Brilliant, i see they are already closed. Many thanks and keep up the good work.DewGew wrote:Thank you for your feedback. I created 2 issues github with your post. Github Issue #47 and Github Issue #48lzwfkv wrote: ↑Monday 02 December 2019 6:30Hello DewGew, this latest version works fine, thank you for keeping it uptodate and improving it. Just a few minor issues that i have faced updating from previous version:DewGew wrote: ↑Friday 29 November 2019 9:57 New update on github dzga v1.3.2.
- Configuration in yaml file
- Improved color temperature
- Graphical user interface
Try out latest, For rpi/ubuntu users, just open a terminal window and execute this command. Thats it!
- Auto install for rpi/ubuntu
Code: Select all
bash <(curl -s https://raw.githubusercontent.com/DewGew/dzga-installer/master/install.sh)
For manual install klick here
Regarding installation:
- Had to map all the settings from previous config.py to config.yaml, in particular it is time consuming for Device_Config; it is tedious, but nevermind i have done it by now.
- Had to remove "pkg-resources>=0.0.0" from pip-requirements.txt because pip could not find such a module and gave errors. By the way, as i understand, it is not needed to explicitely declare such a module as a dependency.
- In the installation procedure, I couldn't find pip command installed on the system, i have pip3 only and i used it successfuly. Using pip3 would also ensure python3 is used.
Functionality:
- pyngrok shoudn't be a mandatory requirement, because i use Caddy Proxy for exposing DZGA to Google Assistant and i don't need/want to set up a tunnel with ngrok proxy, but i am forced to install pyngrok anyway.
It would be wonderful if you could look into restoring the fail back of device_config with config.yaml configuration, because i think it is by far preferrable to have all the devices' configurations centralized into one place, rather than having them spread across multiple devices in Domoticz, with the risk to forget or miss where device are configured or not, and which devices are configured.
- voicecontrol device configuration is not failed back to the settings in config.yaml when tags are not found on the Domoticz device's description. It only checks for device description tags <voicecontrol> in Domoticz, if not found then devices customization is not synch'ed with G Home even if they are configured in config.yaml in Device_Config section.
Thank you again.
This should now work in master like it should. Just add needed settings in config.yaml:lzwfkv wrote: ↑Monday 02 December 2019 6:30
Functionality:It would be wonderful if you could look into restoring the fail back of device_config with config.yaml configuration, because i think it is by far preferrable to have all the devices' configurations centralized into one place, rather than having them spread across multiple devices in Domoticz, with the risk to forget or miss where device are configured or not, and which devices are configured.
- voicecontrol device configuration is not failed back to the settings in config.yaml when tags are not found on the Domoticz device's description. It only checks for device description tags <voicecontrol> in Domoticz, if not found then devices customization is not synch'ed with G Home even if they are configured in config.yaml in Device_Config section.
Thank you again.
Code: Select all
#Additional nicknames and room configuration
Device_Config:
123:
ack: true
room: 'Livingroom'
nicknames:
- 'Celing light'
- 'Smart light'
234:
room: 'Bedroom'
Scene_Config:
3:
room: 'Kitchen'
nicknames:
- 'Cool scene'
I have updated the issue on github. It is a color light but just a simple on/off would be great.DewGew wrote: ↑Monday 02 December 2019 7:59Google requieries a ssl connection with a valid certification. You can use your own domain or reverse proxy with a dns provider. I should update the readme and wiki
I have only Yeelight bulbs I put this in an issue on Github if anyone find a solution. Gitub Issue #49
I dont have any milights to test. Is it a color light?
Goto https://yourdomoticz.ip:port/json.htm?type=devices&rid=21 and copy and past output here or in the Gitub Issue #49
Code: Select all
<voicecontrol>
nicknames = Printer
room = Zolder
ack = True
</voicecontrol>
Code: Select all
2019-12-04 17:04:40 - INFO - Request: {
"inputs": [
{
"context": {
"locale_country": "NL",
"locale_language": "nl"
},
"intent": "action.devices.EXECUTE",
"payload": {
"commands": [
{
"execution": [
{
"params": {
"on": true
},
"command": "action.devices.commands.OnOff"
}
],
"devices": [
{
"id": "Light895"
}
]
}
]
}
}
],
"requestId": "407206062695795625"
}
2019-12-04 17:04:41 - ERROR - Unable to execute action.devices.commands.OnOff for Light895 - challenge needed
2019-12-04 17:04:41 - INFO - Response: {
"payload": {
"commands": [
{
"errorCode": "challengeNeeded",
"status": "ERROR",
"challengeNeeded": {
"type": "ackNeeded"
},
"ids": [
"Light895"
]
}
]
},
"requestId": "407206062695795625"
}
Did you try turning it on in english? I think the ack doesn't work so good in dutch. Google assistant should ask if you really want to turn it on or not.EddyG wrote: ↑Wednesday 04 December 2019 17:12 I have this in the description of a device that normally/manually works .This the response/error from dzga and the device does not respond.Code: Select all
<voicecontrol> nicknames = Printer room = Zolder ack = True </voicecontrol>
This is the only switch with 'ack = True'Any idea where to look for the solution?Code: Select all
2019-12-04 17:04:40 - INFO - Request: { "inputs": [ { "context": { "locale_country": "NL", "locale_language": "nl" }, "intent": "action.devices.EXECUTE", "payload": { "commands": [ { "execution": [ { "params": { "on": true }, "command": "action.devices.commands.OnOff" } ], "devices": [ { "id": "Light895" } ] } ] } } ], "requestId": "407206062695795625" } 2019-12-04 17:04:41 - ERROR - Unable to execute action.devices.commands.OnOff for Light895 - challenge needed 2019-12-04 17:04:41 - INFO - Response: { "payload": { "commands": [ { "errorCode": "challengeNeeded", "status": "ERROR", "challengeNeeded": { "type": "ackNeeded" }, "ids": [ "Light895" ] } ] }, "requestId": "407206062695795625" }
Or say the command in english
Sounds great make the pull request to beta branchProfaNe wrote: ↑Friday 06 December 2019 11:54 Just a FYI.
If you use the ngrok tunnel option without account the tunnel will be terminated after 5 or 6 hours. This will make DGA unreachable for GA. I have made some changes in your code to use a auth_token so the tunnel wont timeout. You can create a free account with 1 free tunnel. That way you can use this whole setup without domain, certificates and opening ports on your router. I will test this and create a pull request this weekend with some other, mostly cosmetic, changes.
Users browsing this forum: No registered users and 1 guest