REST burst requests on latest version (and maybe previous one?)

jprates · July 31, 2024, 10:59am

Hi all,

For some reason over the last few days I’ve been noticing some of my template sensors and dashboards are broken with unavailable values causing all kind of havoc errors, including of course automations.

Today I finally got some time to investigate the root cause, and it turns out its the REST platform that is sending bursts of the same request over and over again, a behavior that I did not see earlier, and its of course not welcome.

The portal I use has this REST API that limits the number of requests per minute, therefore I had set a scan_interval of 60 seconds to never have this kind of error.

I don’t know why, but it seems the scan_interval has suddenly become ignored, cause I already changed the config file to 3600 seconds, rebooted HASS, and still the errors keep coming back:

2024-07-31 09:41:16.361 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 09:41:16.364 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 09:41:16.406 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 09:41:16.406 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 09:41:16.409 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 09:41:16.409 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 09:41:16.413 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 09:41:16.414 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 09:41:16.416 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 09:41:16.416 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 10:41:16.273 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 10:41:16.274 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 10:41:16.356 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 10:41:16.356 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 10:41:16.395 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 10:41:16.396 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 10:41:16.428 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 10:41:16.431 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-07-31 10:41:16.454 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"exception":"Request calls within the current minute > threshold, please take note","code":104,"tokenId":"20xxxxxxxxxxxxxxxxxxxx0415","success":false}
2024-07-31 10:41:16.455 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary

Does anyone have any clue of what changed?
Maybe I missed something in some recent release note?

I just want to make sure it’s not something on my side that needs to be corrected before opening an issue on git.

One thing is for sure true: I did not change anything in these rest sensors recently, they’ve been stable for years.

Thanks in advance for your valuable inputs.

Cheers,
-jprates

jprates · July 31, 2024, 7:06pm

just to add I caught yet another example calling a different endpoint also with a burst (4 requests it seems) on the same sub-second:

2024-07-31 19:41:19.992 DEBUG (MainThread) [homeassistant.components.rest.data] Updating from https://monitoringapi.solaredge.com/site/30xxxxx5/overview.json?api_key=YG7xxxxxxxxxxxxxxxxxxxxxxx8M
2024-07-31 19:41:20.361 DEBUG (MainThread) [homeassistant.components.rest] Finished fetching rest data data in 0.369 seconds (success: True)
2024-07-31 19:41:20.361 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"overview":{"lastUpdateTime":"2024-07-31 19:37:43","lifeTimeData":{"energy":1.455535E7},"lastYearData":{"energy":4300563.0},"lastMonthData":{"energy":981943.0},"lastDayData":{"energy":32362.0},"currentPower":{"power":232.61128},"measuredBy":"INVERTER"}}
2024-07-31 19:41:20.364 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"overview":{"lastUpdateTime":"2024-07-31 19:37:43","lifeTimeData":{"energy":1.455535E7},"lastYearData":{"energy":4300563.0},"lastMonthData":{"energy":981943.0},"lastDayData":{"energy":32362.0},"currentPower":{"power":232.61128},"measuredBy":"INVERTER"}}
2024-07-31 19:41:20.368 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"overview":{"lastUpdateTime":"2024-07-31 19:37:43","lifeTimeData":{"energy":1.455535E7},"lastYearData":{"energy":4300563.0},"lastMonthData":{"energy":981943.0},"lastDayData":{"energy":32362.0},"currentPower":{"power":232.61128},"measuredBy":"INVERTER"}}
2024-07-31 19:41:20.370 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: {"overview":{"lastUpdateTime":"2024-07-31 19:37:43","lifeTimeData":{"energy":1.455535E7},"lastYearData":{"energy":4300563.0},"lastMonthData":{"energy":981943.0},"lastDayData":{"energy":32362.0},"currentPower":{"power":232.61128},"measuredBy":"INVERTER"}}

Luckely this API won’t complain about multiple requests as the other one, but still the behavior is there and it is wrong IMHO.

Anyone have a clue of what might be causing this?

By the way, let me ask:
What triggers a data pull to the endpoint?
Is it only the scan_interval defined at sensor level, or does it trigger each time the rest sensor is referenced somewhere?
What else?
Documentation is very thin to say the least, any help here from the community would be appreciated.