search

Homemade-Disaster / ioBroker.netatmo-energy

Netatmo Energy API connection
MIT License
7 stars 4 forks source link

invalid jsonConfig in console #18

Closed CherryKing93 closed 8 months ago

CherryKing93 commented 9 months ago

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:

Homemade-Disaster commented 9 months ago

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 commented 9 months ago

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 commented 9 months ago

Hi,

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

CherryKing93 commented 9 months ago

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

CherryKing93 commented 8 months ago

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 commented 8 months ago

Hi,

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

kr

xpunkt-torie commented 8 months ago

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 commented 8 months ago

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

image
xpunkt-torie commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

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

image