Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Error 400 after external update [INVALID_ARGUMENT on ColorTemp lights] #65

Closed
Aragur opened this issue Nov 23, 2020 · 6 comments

Comments

@Aragur
Copy link
Contributor

Aragur commented Nov 23, 2020

HttpActions:reportState(): error; {"error":{"code":400,"message":"Request contains an invalid argument.","status":"INVALID_ARGUMENT"}}
@Caprico85
Copy link
Collaborator

INVALID_ARGUMENT errors happen, when an invalid device state is reported to Google. For example a window that is opened 120% (only 0-100% allowed). These errors are usually not critical. The worst thing that can happen is Google saying/showing an invalid value. Should be fixed nonetheless.

To investigate this further can you please increase Node-Red's log level to debug (set "level" to "debug" in settings.js) and post the last few lines from Node-Red's log output before the error is logged. There should be a line like "HttpActions:reportState(): states = ...", followed by a JSON object. I especially need this JSON object.

@Aragur
Copy link
Contributor Author

Aragur commented Nov 30, 2020

@Caprico85
Copy link
Collaborator

Somehow the most interesting lines were not printed. Let's please try something else. I released v0.0.48, which now shows a more verbose error message on the debug panel. Please copy this error message. I especially need the "states" object in there.

image

@Aragur
Copy link
Contributor Author

Aragur commented Dec 1, 2020

chrome_2020-12-01_20-47-31
PS: nice to see another German Dev here :) Got you by "komischerwert"

@Caprico85
Copy link
Collaborator

Thank you for the screenshot. I'm finally able to reproduce this. The node creates a wrong state report to Google. Only color.temperatureK is allowed by Google, not the temperature value outside of color. I'll see what I can can do.

PS: Erwischt. Grüße aus dem schönen Sachsen 😄

@Caprico85
Copy link
Collaborator

Should be fixed in v0.0.49.

@Caprico85 Caprico85 changed the title Getting Error 400 after external update Getting Error 400 after external update [INVALID_ARGUMENT on ColorTemp lights] Dec 5, 2020
@Aragur Aragur closed this as completed Dec 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants