-
Notifications
You must be signed in to change notification settings - Fork 4
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
invalid jsonConfig in console #18
Comments
Hi, I do not have this problem with your reported software versions. Was it possible for you to authenticate using the button "AUTHENTIFIZIEREN SIE SICH BEI NETATMO"? Do you get data from the cloud (actual data in the datapoints for adapter netatmo-energy)? |
Hi, please try to install V2.7.2 and retest the adapter. |
Wow. |
I testet it. This is in the Console: |
Hi, please set the debug level to silly and send me the log. kr |
Hi! |
Even with these settings I do not get any data displayed. When looking at the logs, you can see that the API request If you call up the URL (incl. token, etc.) directly in a browser, data is also returned. |
This is my log set so silly:
But, there is no silly line. I also tried a new API key. |
Hi, I'm back from vacation and was able to reproduce the error. Everything should work now. |
Describe the bug
The netatmo-energy Plugin isn't working. I don't have my smart thermostat in the Overview.
I have a warning in the console
To Reproduce
Just start the Plugin
Expected behavior
See my smart thermostat in the Admin-Tab.
Screenshots & Logfiles
Console warning:
netatmo-energy has an invalid jsonConfig: [{"instancePath":"/items/tabLogon/items/authenticate","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"window"},"message":"must NOT have additional properties"},{"instancePath":"/items/tabLogon","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
Screenshot:
Versions:
The text was updated successfully, but these errors were encountered: