I know I may sound a little negative … I am aware that openhab is a free software and many people are investing a lot of their spare time … but unfortunately I cant accept that the netatmo binding is giving me these “maximum usage reached” messages for nearly a year now.(Aftert it had worked flawlewssly for years …) I really dont understand why the binding does not implement a max request limit internally to prevent that error … sorry I am just frustrated after 4.2 broke my installation yesterday and I had to revert to a complete backup … today I have tried that special backport jar … same issue. I am really willing to help and try out a debug version of the author to nail down that bug not only me seem to be experiencing…
You are frustrated… ok.
But between your first post in this thread and the fix are only 8 days.
After the “maximum usage reached” messages you have the wait 1 hour.
The fixed jar or 4.2 does not shorten this time.
You’ve got a channel on the bridge counting requests. You can use it to switch it offline and wait some time to have it back online.
I’ve made nearly 10 PR to try to nail this issue, and I’ve some other to address. From time to time I need to work on some other things to stay motivated
3 Likes
I think I finally landed on the same issue than yours.
Having spent two days working in the dev environment, I reach user limit after two requests.
The only way I found to circumvent is to impose a 10s delay between each request.
This could be a server side issue, I found some cases on the web (https://helpcenter.netatmo.com/hc/en-us/community/posts/19767427948434-Getting-error-26-User-Usage-exceeded-for-a-few-hours-now). Maybe an option would be to use a new application.
I’ll keep you posted.
I think I’ve got it :
Remove your app from Home + Control & Security | Legrand - Netatmo - Bticino
Create a new app https://dev.netatmo.com/
Redo the grant process in openhab using your new clientId and clientSecret.
Hi,
I upgraded to 4.2.2 and now I get this error message
Rest call failed: statusCode=MAXIMUM_USAGE_REACHED, message=User usage reached
I deleted the app at dev.netatmo.com and created a new one but no success.
Before the upgrade all worked fine.
Best
Paul
There’s a bug in Netatmo Binding of 4.2.2. Correction is ongoing [netatmo] Avoid endless loop when Security claims event history by clinique · Pull Request #17484 · openhab/openhab-addons · GitHub
Is a fix for 4.2.2 (jar) already available?
Fix has been merged [netatmo] Avoid endless loop when Security claims event history by clinique · Pull Request #17517 · openhab/openhab-addons · GitHub, so I think yes it should be available. Thé fix for 4.3 is working