Recent "WARN" message " WARN - Netatmo: Error: getStationsDataError error: Status code404" freezes Homebridge

[brotkasten87]

Hello,

since some days, I'm getting an WARN error with this plugin:

[netatmo platform] WARN - Netatmo: Error: getStationsDataError error: Status code404

This freezes the whole homebridge config. I had to disable the plugin for now. Does anyone has any idea on why this suddently happened? Maybe netatmo changed their API?

I've also tried to reset the App in dev.netatmo.com and/or use a new app with new credentials. It did not help.

Thanks for your help!

[xMAIKx]

Same

[acharris76]

Same

[ronny332]

Same for me. The solution was (for now) to lower down the requests to 15 minutes and raise the cache to about 2 minutes. This does of cause not solve the issue itself (the error seems to fall through the error handling and/or isn't fetched up), but in my case it doesn't appear again.

[acharris76]

Can you explain how you do that? Sorry, not very skilled at all this! Thanks!

[xMAIKx]

@ronny332

And how do you do that?

[ronny332]

@xMAIKx

these are my current settings for the module (5 minutes delay between each update):

      "ttl": 301,
      "refresh_check": 300000,
      "refresh_run": 20000,

The cached values are used longer than the refresh_check duration is (301 seconds compared to 300 seconds), so after my understanding no extra requests can be done, what doesn't overload the API.

What's still strange is the response of Netatmo. I can't think about a situation where you send 404 for an overloaded API. IMHO an 503 or 500 would fit. Maybe it's a good idea to check what's really returned, but I haven't done this yet.

[acharris76]

This has worked for me. Seems much more stable now.

[henkhb]

[netatmo platform] WARN - Netatmo: Error: getStationsDataError error: Status code404

Got this error, that keeps whole homebridge from working properly.

Updated timing options as mentioned here doesn’t help.

Any ideas?

[nexttoyou]

Updated timing options as mentioned here doesn’t help.

You might have to wait a bit longer before doing a Homebridge restart, perhaps 15 minutes.

What happens seems to be yet another method of Netatmo to limit their server load at the expense of their users.