JSON result was not a dictionary or list with 0th element a dictionary

[tteggelit]

The problem

REST sensor is generating the following warning in the logs every minute. The sensor seems to work still, but it's generating a lot of unnecessary logs.

...
2024-12-15 09:50:59.167 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-12-15 09:50:59.168 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-12-15 09:51:59.179 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-12-15 09:51:59.180 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
2024-12-15 09:52:59.196 WARNING (MainThread) [homeassistant.components.rest.util] JSON result was not a dictionary or list with 0th element a dictionary
...

This seems related to closed Issue 41753. JSONLint also seems to validate this JSON as well.

What version of Home Assistant Core has the issue?

core-2024.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

REST

Link to integration documentation on our website

https://www.home-assistant.io/integrations/rest

Diagnostics information

home-assistant_rest_2024-12-15T16-06-54.530Z.log

Example YAML snippet

https://github.com/tteggelit/ha-configs/blob/main/packages/severe_weather.yaml

Anything in the logs that might be useful for us?

No response

Additional information

This has been an issue since at least core-2024.10.0

[home-assistant]

rest documentation
rest source

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.