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

invalid jsonConfig in console #18

Closed
CherryKing93 opened this issue Jan 9, 2024 · 12 comments
Closed

invalid jsonConfig in console #18

CherryKing93 opened this issue Jan 9, 2024 · 12 comments

Comments

@CherryKing93
Copy link

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:
image

image

Versions:

  • Adapter version: 2.7.0
  • JS-Controller version: 5.0.17
  • Node version: v18.13.0
  • Operating system: ubuntu 23.10 in proxmox 8.1.3
@Homemade-Disaster
Copy link
Owner

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)?

@CherryKing93
Copy link
Author

Hi,

The authentication worked and is OK:
O Auth OK

Even in ioBroker there is an “OK”:
OK

Nothing can be seen in the objects. Everything is at "(null)"
Objekte

@Homemade-Disaster
Copy link
Owner

Hi,

please try to install V2.7.2 and retest the adapter.

@CherryKing93
Copy link
Author

Wow.
Thanks for the fast Update.
I will try it tomorrow and give an update afterwards.

@CherryKing93
Copy link
Author

CherryKing93 commented Jan 19, 2024

I testet it.
I don't have any thing in Objects.

This is in the Console:
2024-01-19 17:40:50.395 warn netatmo-energy has an invalid jsonConfig: [{"instancePath":"/items/tabLogon/items/Information/size","schemaPath":"#/patternProperties/%5E.%2B/allOf/4/then/properties/size/type","keyword":"type","params":{"type":"number"},"message":"must be number"},{"instancePath":"/items/tabLogon","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]

@Homemade-Disaster
Copy link
Owner

Hi,

please set the debug level to silly and send me the log.

kr

@xpunkt-torie
Copy link

Hi!
I have the same issue on v2.7.0.
No erros. Only the "netatmo-energy has an invalid jsonConfig:" warning in log.
Auth is ok.

@Homemade-Disaster
Copy link
Owner

Please try to change your setup. Check the last two options ...
image

@xpunkt-torie
Copy link

Even with these settings I do not get any data displayed.

When looking at the logs, you can see that the API request
"https://api.netatmo.com/api/homesdata"
is then logged with many
"Event triggered: ....".
On the other hand, the call
"https://api.netatmo.com/api/homestatus"
is also logged with
"Netatmo API-Status:200"
but then with many
"Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }".

If you call up the URL (incl. token, etc.) directly in a browser, data is also returned.

@CherryKing93
Copy link
Author

CherryKing93 commented Jan 25, 2024

This is my log set so silly:

netatmo-energy.0 2024-01-25 05:30:14.501 debug API Request homestatus jeweils an API gesendet 180sec

netatmo-energy.0 2024-01-25 05:27:15.058 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.027 debug API-Anfrage beendet

netatmo-energy.0 2024-01-25 05:27:15.027 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.027 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.027 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.026 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.026 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.026 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

netatmo-energy.0 2024-01-25 05:27:15.024 debug Netatmo API-Status:200

netatmo-energy.0 2024-01-25 05:27:14.797 debug Anfrage: https://api.netatmo.com/api/homestatus?access_token=MYTOKEN&home_id=MYID

netatmo-energy.0 2024-01-25 05:27:14.796 info API-Anfrage starten: homestatus

But, there is no silly line.
Only debug and info.
Still no connection.

I also tried a new API key.

@Homemade-Disaster
Copy link
Owner

Hi,

I'm back from vacation and was able to reproduce the error.
The issue is fixed in v2.7.3.
Please install this version (already published) and test the issue again.

Everything should work now.

@CherryKing93
Copy link
Author

Hope, the vacation was restful.
But it seams so. Now it works perfectly.
Thank you for the perfekt support.

image

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

3 participants