-
Notifications
You must be signed in to change notification settings - Fork 41
Possible errors
Caprico edited this page Nov 23, 2020
·
18 revisions
This is an incomplete list of possible errors and ideas on how to fix them:
redirect_uri ... invalid
- JWT Key is wrong. Create a new key as described on Step "Enable HomeGraph API" in the Readme. Check that the correct project is selected while creating the key.
HttpActions:requestSync(): error; {"error":{"code":403,"message":"The caller does not have permission","status":"PERMISSION_DENIED"}}`
- Account not linked or link became invalid. Unlink and relink your account in Google Home app.
clientId does not match!
- Client ID defined in config and in Google Actions Console do not match.
Error on loading auth storage: Error: EACCES: permission denied, open '...'
- Auth storage file (`google-smarthome-auth-*.json in Node-Red's userDir) has invalid file permissions. The file must be readable and writable by the user as which Node-Red is running.
HttpActions:reportState(): error; {"error":{"code":400,"message":"Request contains an invalid argument.","status":"INVALID_ARGUMENT"}}
- Happens when this module reports an invalid value for a device to Google. For example when we report that a window is opened 120% (only 0-100% allowed).
- Usually not critical. Should still be fixed though. Please create a bug report with the version of node-red-contrib-google-smarthome you are running and the type of devices you are using. If you can, please switch to log level
debug
in Node-Red's settings.js and include Node-Red's logfile. Especially the lineHttpActions:reportState(): states =
, followed by a JSON string.
HttpActions:requestSync(): error; {"error":{"code":403,"message":"The caller does not have permission","status":"PERMISSION_DENIED"}}
- Reasons for this error are currently unknown [Help wanted].