Open dan-s-github opened 9 months ago
I’m seeing this too, but I think this is a deliberate change, see https://github.com/alphaess-developer/alphacloud_open_api/issues/54 There now appears to be a limit of one update per 24hrs. API documentation seems to confirm this change.
I’m seeing this too, but I think this is a deliberate change
I don't think so, I guess it is not intended to block read access to these values. In your linked issue @ElevenFan is talking about write access only.
See alphaess-developer/alphacloud_open_api/issues/56
I also think that the announcement on https://github.com/alphaess-developer/alphacloud_open_api/issues/54 is related to write requests but it seems that they messed up their API with blocking all requests related to the getXXXChargeConfigInfo
instead of only blocking the updateXXXChargeConfigInfo
.
Hopefully this get addressed soon
Alpha ess announced yesterday that the limit of 1x every 24 hours will be raised. However, you have expressed yourself somewhat confusingly as to how often you can now set the value for charging / discharging. https://github.com/alphaess-developer/alphacloud_open_api/issues/54
seems that the restriction on getDisChargeConfigInfo has been removed with an update last night. Usually I got an ERROR log every minute but that has no disappeared around 01:06 UTC+13
2024-01-04 01:00:51.415 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:01:54.323 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:02:57.731 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:04:00.339 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:05:03.366 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:06:06.306 ERROR (MainThread) [alphaess.alphaess] Unexpected json_response : {'code': 6053, 'msg': 'The maximum number of requests has been reached', 'expMsg': None, 'data': None, 'extra': None} when calling https://openapi.alphaess.com/api/getDisChargeConfigInfo?sysSn=XXXXXXXXXXXXX
2024-01-04 01:15:00.321 WARNING (MainThread) [homeassistant.helpers.script.trigger_update_coordinator] Trigger Update Coordinator: Running script requires passing in a context
seems that they actually read the comments on tickets
Seems that AlphaESS is doing maintenance during end of year break period
Since this morning 29/12 UTC +13 I get the following exception in my HA logs, this is when it started
and after updating core and restarting
Only getDischargeConfigInfo returns this error and all other calls work fine. Confirmed using Postman to test all requests.