DewGew wrote: ↑Tuesday 17 December 2019 19:43
Note that this is still in beta..
New function is report state. With this dzga reports state to google to reduce quiering amount and time. So google reports back latest known state. This is might not optimal for some devices like temperatures. So I added function to disable report state on specific device.
Just add
to "Device_Config" in configuration or <voicecontrol>report_state = False</voicecontrol> in device description. That device should query direct from domoticz.
I haven’t tested fully yet.
Edit: If you want use dzga as before, just delete json file and add the homegraph_api_key.
OK, clear to me. I noticed that Google rounds the Temperature to 0,5 degrees.
So 21,3 degrees is pronounced as 21,5 degrees. Google does not know how to pronounce the other digits.
If you can get a hls or mp4 stream from your camera or from a survailance program you can send stream to chrome cast or view stream in a google nest hub
I have seen that example, but it creates a file on /var/www/html/cam
That file grows, and I don not have the space.
I would like to stream without a file or pipe directly to Google.
Setted up everything following the wiki. When I go to google home and try to set up the new device, I can reach the login page.
When I enter the credentials nothing happen.
When I go to myhost:3030:settings and try sync devices I got: Homegraph api key not valid!
On the raspy consol I get an error code 404 Requested entity was not found
I checked on google and the HomeGRaph API is enabled. Any help?
Raspberry PI 4
Domoticz: V2023.2
- Aeotec Gen5 EU
- Neo CoolCam Door Detector and plug
- FIBARO FGWPE Wall Plug
- 6 FIBARO System FGRM222 Roller Shutter Controller 2
- Kodi SamnsungTV Yamaha plugin
- pluginn manager
- Netatmo
lupo2a wrote: ↑Wednesday 25 December 2019 19:15
Setted up everything following the wiki. When I go to google home and try to set up the new device, I can reach the login page.
When I enter the credentials nothing happen.
When I go to myhost:3030:settings and try sync devices I got: Homegraph api key not valid!
On the raspy consol I get an error code 404 Requested entity was not found
I checked on google and the HomeGRaph API is enabled. Any help?
lupo2a wrote: ↑Wednesday 25 December 2019 19:15
Setted up everything following the wiki. When I go to google home and try to set up the new device, I can reach the login page.
When I enter the credentials nothing happen.
When I go to myhost:3030:settings and try sync devices I got: Homegraph api key not valid!
On the raspy consol I get an error code 404 Requested entity was not found
I checked on google and the HomeGRaph API is enabled. Any help?
What version are you running?
dzga v 1.3.8 on a raspberry pi3. Any hint for debugging?
Raspberry PI 4
Domoticz: V2023.2
- Aeotec Gen5 EU
- Neo CoolCam Door Detector and plug
- FIBARO FGWPE Wall Plug
- 6 FIBARO System FGRM222 Roller Shutter Controller 2
- Kodi SamnsungTV Yamaha plugin
- pluginn manager
- Netatmo
lupo2a wrote: ↑Wednesday 25 December 2019 19:15
Setted up everything following the wiki. When I go to google home and try to set up the new device, I can reach the login page.
When I enter the credentials nothing happen.
When I go to myhost:3030:settings and try sync devices I got: Homegraph api key not valid!
On the raspy consol I get an error code 404 Requested entity was not found
I checked on google and the HomeGRaph API is enabled. Any help?
What version are you running?
dzga v 1.3.8 on a raspberry pi3. Any hint for debugging?
Restarted from scratch (git get, google action, API, etc..) now it works. Great!
Raspberry PI 4
Domoticz: V2023.2
- Aeotec Gen5 EU
- Neo CoolCam Door Detector and plug
- FIBARO FGWPE Wall Plug
- 6 FIBARO System FGRM222 Roller Shutter Controller 2
- Kodi SamnsungTV Yamaha plugin
- pluginn manager
- Netatmo
I have an issue, I setup the application, I can see my domoticz device on the UI, I setup the google cloud API. But when I link the service in Google Home, I can login but no devices show up. I made a PCAP trace but I cannot see whats wrong https://drive.google.com/file/d/1uSLALB ... sp=sharing
rezo552 wrote: ↑Thursday 02 January 2020 14:10
Hi,
I have an issue, I setup the application, I can see my domoticz device on the UI, I setup the google cloud API. But when I link the service in Google Home, I can login but no devices show up. I made a PCAP trace but I cannot see whats wrong https://drive.google.com/file/d/1uSLALB ... sp=sharing
Any idea? Thanks
Z.
it looks like what happened to me. I restarted from scratch and it works. Could be the HomeGRaph API key.
Raspberry PI 4
Domoticz: V2023.2
- Aeotec Gen5 EU
- Neo CoolCam Door Detector and plug
- FIBARO FGWPE Wall Plug
- 6 FIBARO System FGRM222 Roller Shutter Controller 2
- Kodi SamnsungTV Yamaha plugin
- pluginn manager
- Netatmo
Hi,
Is it normal that I have to add the import of fanDomain in smarthome.py at every update?
I have a Fan definition in the image override section of config.yaml.
By The Way : great development and improvements in the settings page.
Thanks!
For some strange reason when I ask for a room temperature sometimes Google comes back that the device is not reachable.
In the debug log I see a request and response in the same second. If I ask a few seconds later, the response from Google is normal with a rounded temperature of 0,5 degree. The response in the logfile is exactly the same.
Any idea how that can be prevented?
frankdep wrote: ↑Monday 06 January 2020 22:57
Hi,
Is it normal that I have to add the import of fanDomain in smarthome.py at every update?
I have a Fan definition in the image override section of config.yaml.
By The Way : great development and improvements in the settings page.
Thanks!
Are you running dzga master or beta?
EddyG wrote: ↑Tuesday 07 January 2020 10:09
For some strange reason when I ask for a room temperature sometimes Google comes back that the device is not reachable.
In the debug log I see a request and response in the same second. If I ask a few seconds later, the response from Google is normal with a rounded temperature of 0,5 degree. The response in the logfile is exactly the same.
Any idea how that can be prevented?
You are running beta I assume, I m trying to get dzga working with fahrenheit so beta might not be 100% correct.
Yes, I am running beta. But it is not about the 0,5 degrees. It is about Google does not find the device, although the response in the debug logfile is exactly the same as when there is a normal answer.
I suppose that has nothing to do with you working on fahrenheit, is it?
EddyG wrote: ↑Tuesday 07 January 2020 11:09
Yes, I am running beta. But it is not about the 0,5 degrees. It is about Google does not find the device, although the response in the debug logfile is exactly the same as when there is a normal answer.
I suppose that has nothing to do with you working on fahrenheit, is it?
It has to do with this, I need to recalculate temp from fahrenheit to celsius and back !? So the temp request goes a roundabout in the code for now
Im working on a solution.
EDIT: I tested my setup. I cant reproduce your issue.
frankdep wrote: ↑Monday 06 January 2020 22:57
Hi,
Is it normal that I have to add the import of fanDomain in smarthome.py at every update?
I have a Fan definition in the image override section of config.yaml.
By The Way : great development and improvements in the settings page.
Thanks!
Are you running dzga master or beta?
=> it is beta 1.4.8
EddyG wrote: ↑Tuesday 07 January 2020 10:09
For some strange reason when I ask for a room temperature sometimes Google comes back that the device is not reachable.
In the debug log I see a request and response in the same second. If I ask a few seconds later, the response from Google is normal with a rounded temperature of 0,5 degree. The response in the logfile is exactly the same.
Any idea how that can be prevented?
You are running beta I assume, I m trying to get dzga working with fahrenheit so beta might not be 100% correct.
frankdep wrote: ↑Tuesday 07 January 2020 17:52
Hi,
Is it normal that I have to add the import of fanDomain in smarthome.py at every update?
I have a Fan definition in the image override section of config.yaml.
By The Way : great development and improvements in the settings page.
Thanks!