sync devices failed
Enjoy-Combi opened this issue · 2 comments
Describe the bug:
Since few days I can't sync the devices. When clicking on the button "sync devices" I get:
Page not found!: 404 Client Error: Not Found for url: https://homegraph.googleapis.com/v1/devices:requestSync
Expected behavior:
Sync devices
Logs:
Paste the dzga logs here.
2022-10-03 17:26:59 - DEBUG - Starting new HTTPS connection (1): raw.githubusercontent.com:443
2022-10-03 17:26:59 - DEBUG - https://raw.githubusercontent.com:443 "GET /DewGew/Domoticz-Google-Assistant/master/const.py HTTP/1.1" 200 1949
2022-10-03 17:27:00 - DEBUG - Starting new HTTPS connection (1): accounts.google.com:443
2022-10-03 17:27:00 - DEBUG - https://accounts.google.com:443 "POST /o/oauth2/token HTTP/1.1" 200 None
2022-10-03 17:27:00 - DEBUG - Starting new HTTPS connection (1): homegraph.googleapis.com:443
2022-10-03 17:27:00 - DEBUG - https://homegraph.googleapis.com:443 "POST /v1/devices:requestSync HTTP/1.1" 404 None
2022-10-03 17:27:05 - DEBUG - Starting new HTTPS connection (1): raw.githubusercontent.com:443
2022-10-03 17:27:06 - DEBUG - https://raw.githubusercontent.com:443 "GET /DewGew/Domoticz-Google-Assistant/master/const.py HTTP/1.1" 200 1949
2022-10-03 17:27:06 - DEBUG - Starting new HTTPS connection (1): homegraph.googleapis.com:443
2022-10-03 17:27:06 - DEBUG - https://homegraph.googleapis.com:443 "POST /v1/devices:requestSync HTTP/1.1" 404 None
2022-10-03 17:27:32 - DEBUG - Starting new HTTPS connection (1): raw.githubusercontent.com:443
2022-10-03 17:27:33 - DEBUG - https://raw.githubusercontent.com:443 "GET /DewGew/Domoticz-Google-Assistant/master/const.py HTTP/1.1" 200 1949
Desktop (please complete the following information):
- Domoticz version 2022.1
- Dzga version 1.10.9 master
- Python Version 3.7.3
Smartphone (please complete the following information):
- Device: Huawei P30 Pro
Additional context, screenshot:
Apparently a duckdns issue. See home-assistant/core#79542
I have the same issue on another raspberry with home assistant, they mention this could be a duckdns issue.
Working back without actions, definitively something out of the implementation