Not Found for url: https://homegraph.googleapis.com/v1/devices:requestSync
harolds opened this issue · 15 comments
After updating to 1.22.45 beta I get this error when refreshing the devices:
Page not found!: 404 Client Error: Not Found for url: https://homegraph.googleapis.com/v1/devices:requestSync
404 Not Found - The requested resource could not be found but may be available in the future. Typically, this means that the user account is not linked with Google. Try download a new smart-home-key.json file
Make sure it for correct project in action on google
Dont forget press test button also
Sometimes users had to restart dzga also
I've :
Created a new service account
Created a new key for this service account
Downloaded json
Uploaded json in config folder
Recreated Account Linking (Client Id, Client Secret)
Clicked "Save" Then "Test"
Updated config.yaml with this new Client Id & Client Secret.
restarted DZGA.
I still have the same issue when I click "Sync Devices"
Ok,
I made a full uninstall of dzga
sudo systemctl stop dzga sudo systemctl disable dzga sudo rm /etc/systemd/system/dzga.service sudo rm -r Domoticz-Google-Assistant
And deleted project from Google Action.
I installed latest beta branch (to see if there is a difference)
I followed all steps for set up a new Google Action Project.
After all this, I still have the same issue...
But I tried to add the new app like explained here : https://github.com/DewGew/Domoticz-Google-Assistant/wiki/4.-Connect-smart-home-devices-to-your-Google-Home-device
Then I tried to click sync again, and it worked ....
Hi
I'm seeing Page not found!: 500 Server Error: Internal Server Error for url: https://homegraph.googleapis.com/v1/devices:requestSync
after update this morning.
unfortunately I didnt note the previous version number before updating, but I am now on
DZGA Version: 1.23.2 master Domoticz Version: 2022.1
requesting a device sync from phone (Google pixel 5), or from voice command using google Home speaker responds with "Sorry something went wrong while syncing DZGA link"
happy to do further debug, just tell me what you need.
thanks for your work so far.
Further testing has shown me that after the upgrade (triggered from the DZGA webgui), SSL was disabled.
I have manually set the config file line
use_ssl: true
and this fixed the issue for me.
I am quite confident that I did not change the status of the Enable SSL Check box.
the path to the Cert files was not changed.
hopefully this may help anyone else who encounters this error :-)
I'm not using SSL because i use a reverse proxy, but I experience the same error.
Reverted to 1.11.10 (an older beta release) and everything is fine again
Same here when i update to newest version.
i have found that when i goto https://my_address/token i get page not found.
also sometimes when start dzga ssl option is set to false, i must reset it to true and restart.
Edit:
Now its working again! :)
troubleshooting steps:
- reinstalled dzga
- redo the steps on google actions
- open 443 and 80 on the router (80 is nessesery for renew ssh pem keys)
- renewed the ssh chertificate pem files
- relink account on google home (in android)
Same issue here after upgrading.
Restarted and rebooted RPI and services but no solution.
In Google Actions I only have 1 project, each time after reboot/restart I adjusted the settings but no luck so far.
So this did the trick:
The hardcoded token is removed and is randomly genarated. If you update to latest beta you need to reconnect in Google Home App:
On your mobile device, open the Google Home app.
At the top left, tap Add (+)
Set up device
Works with Google.
Select your device app e.g: "[test]Your Appname"
Search for new devices
Login
Thanks! That works. It's also described here: