I went with a old-school command_line sensor (I basically try to avoid using them meanwhile but the struggle with the REST or RESTful sensors is even worse).
Unfortunately, after initial load of the CL sensors, the value never gets updated, so the scan_interval is not respected. E. g.:
- platform: command_line
name: Home Assistant Core CPU percent
unique_id: vs-code-generated
scan_interval: 30
command_timeout: 60
command: 'curl http://supervisor/core/stats -H "Authorization: Bearer $(printenv SUPERVISOR_TOKEN)" | jq ''{"cpu_percent":.data.cpu_percent}'''
value_template: "{{ value_json.cpu_percent }}"
unit_of_measurement: "%"
The changes visuable are from reloading CL sensors:
Any idea on this e. g. @ master of CL sensors @CentralCommand ?
Meanwhile TBH I am so bugged
that I’m just ten minutes away of writing a feature request (knowing it will either not get realized or only in many months) for the Supervisor integration. The data is already there, why not exposing it for Core and Supervisor as done for all the other addons?
Update:
Is it possible that scan_interval for CL sensors has been disabled/ignored a long time ago already? Because:
- I probably have few other CL sensors which never update (only on manual reload and HA start)
- Using the
homeassistant.update_entityservice triggers the CL sensor update just fine.

