Could you please share it again, link is no longer available:
Sorry, the link has expired.
Could you please share it again, link is no longer available:
Sorry, the link has expired.
Iāve updated the link
Thanks.
But the error appears again:
Error while identifying all modules: Rest call failed: statusCode=MAXIMUM_USAGE_REACHED, message=User usage reached
After upgrading to OpenHAB 4.2.3 the netatmo binding works without problems.
Confirm, 4.2.3 solved it.
Still the same problem occurs with the Netatmo-binding Netatmo-Account:
COMMUNICATION_ERROR
Maximum usage reached. Will try reconnection after reconnectInterval seconds.
Iām working with Openhab version 4.3.1 and followed all previous steps.
The binding goes online and after a while offline until the reconnect intervall goes off.
Iām running 4.3.0 and the core binding, and donāt seem to have issues with the communication.
Iāll try to upgrade soon to 4.3.1 and report the status.
Iām running two OH 4.2.3 instances and it works stable for me since month.
however, the one thing i noticed long time back when I had the issue as well,was the following.
innitially, i configured both of my OH instances to use the same Netatmo āappā (same client id / secret), which finally caused this issue. after creating a unique Netatmp app (client id/secret) for each OH instance, the issue was gone. so seems like Netatmo is accepting only one unique application connectng to one Netatmo client-id/secret pair.
just thought I share this experience as it might also apply to other people having this issue.
Iāve had no issues with the binding after 1 day having upgraded to 4.3.1
@glhopital Hi, Iām experiencing the same issue, not sure why as the number of API calls are far below the limits (https://helpcenter.netatmo.com/hc/en-us/community/posts/28272276247058-API-Rate-Limit-clarification-request. https://helpcenter.netatmo.com/hc/en-us/community/posts/29846852785298-Inconsistent-Rate-Limits-for-Netatmo-Home-Control-API). My impression is when something wrong happens, the message from Netatmo binding is ācommunication error, max usage reachedā. And itās an issue with the Binding, no with Netatmo servers, as their app is working fine. If I disable and enable again the things, everything works fine again till the next time. I donāt see any correlation till now, but Iām still troubleshooting.
Any clue?
openhabian with OH 5.2.0.M1
Andrea
update: it seems something related to netatmo WAF thresholds. Also other integrations fail: Netatmo error Maximum api usage reached Ā· Issue #158845 Ā· home-assistant/core Ā· GitHub
@ariela : this PR should handle more gracefully this API limit issue. The problem is not completely sorted but Iām working on this situation.
A valuable alternative to avoid the Netatmo cloud, might be the Homekit binding. See here for some examples: HomeKit integration of Netatmo CO2 sensors
I used the netatmo binding for several years and @glhopital did a very good job. But I think that thereās a huge problem on the bticino side. They have a lot of problems with their app also. So i finally gave up and switched to homekit binding and itās the perfetct solution to avoid any external call. The only problem is that it doesnāt expose all the things included in the netatmo binding (battery status, for example) but I can live with thatā¦
Unfortunately only V3 of the station is Homekit compatible: https://helpcenter.netatmo.com/hc/en-us/articles/360010155399-Is-my-Station-compatible-with-Apple-HomeKit
V3 or higher. For V3 you need an iPhone to get the pairing code, for V4 itās printed on a sticker at the back of the device.