Closed fouriewp closed 1 year ago
I suspect this issue is related to the same problem I experience. In my case I still have API calls left, but the wrong schedule was returned, i.e. stage 8 when there was in fact no load-shedding. After deleting and re-adding the node I now get the error: "TypeError: dates.stages[(EskomSePushInfo.calc.stage - 1)] is not iterable" even though I still have API calls left. The common issue seems to be incorrect data when loadshedding has been suspended. I only saw your issue after I logged my mine.
Please upgrade to the today released version 0.0.15. If the problem still persists, please file a new issue.
Thanks Guys.
I have upgraded to 0.0.15, I will check what happens "next time when Eskom declares "No loadshedding.
When Eskom declare no loadshedding the eskomsepush node seems to consume all my Api calls and later the day when they declare loadshedding again there are no Api calls left.
"No API calls left, not checking status/schedule"
To Reproduce The problem happens every time Eskom declares no load shedding.
Expected behaviour I expect a return that indicates that there are no load shedding and that the Api calls are not used so quickly.
Software (please complete the following information):
Flow
Picture