Domoticz

DewGew wrote: ↑Tuesday 17 December 2019 10:10

rvanderven wrote: ↑Monday 16 December 2019 19:34 Does anyone have a complete uptodate description of the creation of the Google Action credentials and API keys?
To me it looks like things on the Google site have changed since the description is created.
Eg. When enabling HomeGraph for my project I could't create an API key via the credentials, only by going back to https://console.cloud.google.com/apis/c ... roject=<My project>
When clicking Test and entering a phrase I received the message that it was not possible to use this in the webbrowser.

After entering all details in config.yaml I started dzga service and after login with the /settings url I was able to login.
Clicking on the Sync devices resulted in the message: "Homegraph API key not valid!"
The dzga.log mentions error 404
2019-12-16 19:10:00 - ERROR - {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}

I tried all kinds of things, but I am completely stuck.
I have setup my own domain and installed a reverse proxy on my synology encrypted with Letsencrypt.
I can reach the dzga installation from outside and am able to login.

Maybe you missed to enable the Homegraph API

Edit: I updated wiki

lzwfkv wrote: ↑Sunday 12 January 2020 12:53 Hello DewGew, i think i have found a bug in the update switch (OnOff trait devices) status, in that whenever the status of a switch/light/etc. is changed either through google assistant voice command or in Domoticz itself, the updated status is not passed correctly to Google Assistant by DZGA.
In particular, upon investigation i think i have identified the issue in the fact that DZGA does not synch the devices status with Domoticz and keep storing the initial status of the switches that it got from Domoticz upon the latest Sync, therefore DZGA send stale status to Google Assistant after a query from the latter.
The simplest and quickest way, though probably a dirty one, that i have found to fix the issue is to force an update of the Queried device from Domoticz to DZGA whenever a query for device's attributes is submitted to DZGA (Smarthome) by adding the following code line (in bold) in smarthome.py:

def smarthome_query(self, payload, token):
"""Handle action.devices.QUERY request.
https://developers.google.com/actions/s ... vicesquery
"""
devices = {}

for device in payload.get('devices', []):
devid = device['id']
_GoogleEntity(aogDevs.get(devid, None)).async_update()
state = aogDevs.get(devid, None)

if not state:
# If we can't find a state, the device is offline
devices[devid] = {'online': False}
continue

e = _GoogleEntity(state)
devices[devid] = e.query_serialize()

return {'devices': devices}

After some tests the above change seems to work and to fix both the cases described above where i have been able to observe the issue raising.

frankdep wrote: ↑Sunday 12 January 2020 17:41 Related to the above. I had some issues because GA had a wrong status. I tried to open my garage but GA was telling me that it was already open
This issue is not improving with the Report_state feature. So I'm triggering a manual "http://localhost:port/sync" on an important device change or time change event in Domoticz. Had to bypass the userinfo and useragent check in syncDevices and forceDevicesSync routines in smarthome.py.
The status is updating instantly in GA.
I think it is an interesting feature to trigger updates from Domoticz.

Spoiler: show

{
"willReportState": true,
"deviceInfo": {
"model": "Raspberry Pi",
"manufacturer": "Domoticz"
},
"name": {
"name": "Verwarming"
},
"id": "Selector816",
"type": "action.devices.types.SWITCH",
"attributes": {
"availableToggles": [
{
"name_values": [
{
"name_synonym": [
"Off"
],
"lang": "en"
},
{
"name_synonym": [
"Off"
],
"lang": "en"
}
],
"name": "Off"
},
{
"name_values": [
{
"name_synonym": [
"Dagverlenging"
},
{
"name_values": [
{
"name_synonym": [
"Normaal"
],
"lang": "en"
},
{
"name_synonym": [
"Normaal"
],
"lang": "en"
}
],
"name": "Normaal"
}
]
},
"traits": [
"action.devices.traits.Toggles"
]
},

EddyG wrote: ↑Monday 13 January 2020 10:14 I have trouble to get a selector switch working. Can anyone give me the solution?
This the selector in Domoticz: Light/Switch, Switch, Selector And it is working as intended.

Spoiler: show

{
"willReportState": true,
"deviceInfo": {
"model": "Raspberry Pi",
"manufacturer": "Domoticz"
},
"name": {
"name": "Verwarming"
},
"id": "Selector816",
"type": "action.devices.types.SWITCH",
"attributes": {
"availableToggles": [
{
"name_values": [
{
"name_synonym": [
"Off"
],
"lang": "en"
},
{
"name_synonym": [
"Off"
],
"lang": "en"
}
],
"name": "Off"
},
{
"name_values": [
{
"name_synonym": [
"Dagverlenging"
},
{
"name_values": [
{
"name_synonym": [
"Normaal"
],
"lang": "en"
},
{
"name_synonym": [
"Normaal"
],
"lang": "en"
}
],
"name": "Normaal"
}
]
},
"traits": [
"action.devices.traits.Toggles"
]
},

EddyG wrote: ↑Monday 13 January 2020 17:16 I tried that but did not work. I suppose that the problem lies in the language.
If I try it in English, Google does not understand. If I try in Dutch then Google sums up all kind of Firms with Verwarming.
I keep on trying with other names for the Domoticz device.

Spoiler: show

2020-01-14 10:05:49 - INFO - Request {
"inputs": [
{
"context": {
"locale_country": "NL",
"locale_language": "nl"
},
"payload": {
"commands": [
{
"execution": [
{
"command": "action.devices.commands.SetToggles",
"params": {
"updateToggleSettings": {
"Normaal": true
}
}
}
],
"devices": [
{
"id": "Selector816"
}
]
}
]
},
"intent": "action.devices.EXECUTE"
}
],
"requestId": "3502827826391958633"
}
2020-01-14 10:05:49 - DEBUG - Starting new HTTP connection (1): 192.168.2.239:8080
2020-01-14 10:05:49 - DEBUG - http://192.168.2.239:8080 "GET /json.htm?type=command&param=switchlight&idx=816&switchcmd=Set%20Level&level=20 HTTP/1.1" 200 51
2020-01-14 10:05:49 - DEBUG - Starting new HTTP connection (1): 192.168.2.239:8080
2020-01-14 10:05:49 - DEBUG - http://192.168.2.239:8080 "GET /json.htm?type=devices&rid=816 HTTP/1.1" 200 761
2020-01-14 10:05:49 - DEBUG - {
"Verwarming": {
"state": "Set Level: 20 %",
"type": "Selector",
"willReportState": true,
"idx": 816,
"nicknames": null
}
}
2020-01-14 10:05:49 - DEBUG - Starting new HTTPS connection (1): homegraph.googleapis.com:443
2020-01-14 10:05:50 - DEBUG - https://homegraph.googleapis.com:443 "POST /v1/devices:reportStateAndNotification HTTP/1.1" 400 None
2020-01-14 10:05:50 - ERROR - 400 Client Error: Bad Request for url: https://homegraph.googleapis.com/v1/dev ... tification
2020-01-14 10:05:50 - INFO - Error handling message {'inputs': [{'context': {'locale_country': 'NL', 'locale_language': 'nl'}, 'payload': {'commands': [{'execution': [{'command': 'action.devices.commands.SetToggles', 'params': {'updateToggleSettings': {'Normaal': True}}}], 'devices': [{'id': 'Selector816'}]}]}, 'intent': 'action.devices.EXECUTE'}], 'requestId': '3502827826391958633'}: {'errorCode': 'unknownError'}
2020-01-14 10:05:50 - INFO - Response {
"payload": {
"errorCode": "unknownError"
},
"requestId": "3502827826391958633"
}

EddyG wrote: ↑Tuesday 14 January 2020 10:16 When I reset my Domoticz to NL it works partly.
The action is completed normal but Google responds with an error.

Spoiler: show

2020-01-14 10:05:49 - INFO - Request {
"inputs": [
{
"context": {
"locale_country": "NL",
"locale_language": "nl"
},
"payload": {
"commands": [
{
"execution": [
{
"command": "action.devices.commands.SetToggles",
"params": {
"updateToggleSettings": {
"Normaal": true
}
}
}
],
"devices": [
{
"id": "Selector816"
}
]
}
]
},
"intent": "action.devices.EXECUTE"
}
],
"requestId": "3502827826391958633"
}
2020-01-14 10:05:49 - DEBUG - Starting new HTTP connection (1): 192.168.2.239:8080
2020-01-14 10:05:49 - DEBUG - http://192.168.2.239:8080 "GET /json.htm?type=command&param=switchlight&idx=816&switchcmd=Set%20Level&level=20 HTTP/1.1" 200 51
2020-01-14 10:05:49 - DEBUG - Starting new HTTP connection (1): 192.168.2.239:8080
2020-01-14 10:05:49 - DEBUG - http://192.168.2.239:8080 "GET /json.htm?type=devices&rid=816 HTTP/1.1" 200 761
2020-01-14 10:05:49 - DEBUG - {
"Verwarming": {
"state": "Set Level: 20 %",
"type": "Selector",
"willReportState": true,
"idx": 816,
"nicknames": null
}
}
2020-01-14 10:05:49 - DEBUG - Starting new HTTPS connection (1): homegraph.googleapis.com:443
2020-01-14 10:05:50 - DEBUG - https://homegraph.googleapis.com:443 "POST /v1/devices:reportStateAndNotification HTTP/1.1" 400 None
2020-01-14 10:05:50 - ERROR - 400 Client Error: Bad Request for url: https://homegraph.googleapis.com/v1/dev ... tification
2020-01-14 10:05:50 - INFO - Error handling message {'inputs': [{'context': {'locale_country': 'NL', 'locale_language': 'nl'}, 'payload': {'commands': [{'execution': [{'command': 'action.devices.commands.SetToggles', 'params': {'updateToggleSettings': {'Normaal': True}}}], 'devices': [{'id': 'Selector816'}]}]}, 'intent': 'action.devices.EXECUTE'}], 'requestId': '3502827826391958633'}: {'errorCode': 'unknownError'}
2020-01-14 10:05:50 - INFO - Response {
"payload": {
"errorCode": "unknownError"
},
"requestId": "3502827826391958633"
}

400 Client Error: Bad Request for url: https://homegraph.googleapis.com/v1/dev ... tification

<voicecontrol>
report_state = False
</voicecontrol>

ddtpv wrote: ↑Saturday 25 January 2020 8:42 Hi all!
Though kill, I can’t understand what’s going wrong.
Copy - paste everything correctly. But Google Home is still a error
client_id xxxxxxxx.apps.googlecontent.com invalid

https://6522467d.ngrok.io/smarthome - not supported
https://6522467d.ngrok.io/oauth - response_type must equal "code"
http://6522467d.ngrok.io/token - Page not found!: '/token'

localhost:3030 has no errors in logfile

Xavier82 wrote: ↑Wednesday 29 January 2020 22:47 ...

Please help.
How can I fix this?
Is there anyway to run the script in the background?

pvklink wrote: ↑Thursday 30 January 2020 13:06 Does this Google assistant integration works on raspbian buster on a rpi 4?

If you used The google sdk library for your integration, this not supported anymore on buster and rpi 4.
Only the sdk service version is supported, and lacks lots off options that the old sdk-lib had...