**Supervisor Panel deprecated in HA 2026.5 — rebuilt it**

Share your Projects!
1

HA 2026.5 removed the hassio-main panel. Restart Core, Restart Supervisor, Reboot Host, Shutdown Host are gone from the UI. Built a replacement custom sidebar panel using the HA WebSocket API and native System Monitor entities. It willl make its way to github and HACS but wanted to get it out for those that need it while waiting for HACS Approval.

Install:

  1. Create super-panel.js in /config/www/
  2. Paste the code from the link below into it
  3. Add to configuration.yaml:
panel_custom:
  - name: super-panel
    sidebar_title: Supervisor Panel
    sidebar_icon: mdi:home-assistant
    url_path: super-panel
    module_url: /local/super-panel.js
    require_admin: true
  1. Full HA restart required

Requires Supervisor (HAOS or supervised install only)

supervisor panel
supervisor panel1643×1148 566 KB

3 Likes
2

Looks great! When will it be in HACS (as I'd prefer installing from there so I automatically get notificaiotns about updates)?

3

If you look here you can add it to HACS:

2 Likes
4

I love it - thank you

1 Like
5

Good morning everyone,
You've done a great job with the integration.

I noticed it's not tracking CPU usage on my system.
What can I do to get it working?

Thanks.
Daniele

ScreenShot560
ScreenShot5601920×1247 359 KB

6

Check your "System Monitor - Integration", Load (1 min) must be enabled.
sensor.system_monitor_load_1m

(or any other entity that matches one of these names)

7

See image.

How do I insert the CPU sensor?
sensor.processor_use.

ScreenShot561
ScreenShot5611239×237 54.6 KB

8

I tried to insert the sensor but it still doesn't read it

  const cpuLoad = this._findSysMonEntity(states,
    ['load_1_min', 'load_1m', 'processor_load', 'processor_use', 'load1'], null);
9

Its on github (careful the config.yaml is a little different) and it's in the queue to be released fully in hacs, but that can take months with their huge backlog.

10

The Supervisor Panel looks for specific entity ID patterns to find your CPU load sensor. I can only have so many automatically found and I think we've done a really good job of getting >90 percent to hit. If yours doesn't, the easiest fix is to make a template sensor. What will happen is the sensor will mimic your CPU sensor, but it will have a known name supervisor panel will hit on.

If your entity is sensor.processor_use, it won't be recognized automatically.

The fix is to create a template sensor in your configuration.yaml:

yaml

template:
  - sensor:
      - name: "Processor Load"
        unique_id: processor_load_template
        unit_of_measurement: "%"
        state: "{{ states('sensor.processor_use') }}"

MAKE SURE YOU CHANGE THE "SENSOR PROCESSOR USE" TO YOUR OWN SENSOR

This creates sensor.processor_load which the panel will find correctly. Restart HA after adding it. This is listed in the github repository pjarbit, in the sensor panel readme.The example there is for disk use, but the CPU is the same, just need different terms to hit on.

11

One can enable the "real" core cpu-usage via the supervisor-integration.
The "cpu-sensors" from the system monitor integration are for the whole system, not for core only.

The search pattern should look first for: sensor.home_assistant_core_cpu_percent i think.

12

Thanks, it works.

ScreenShot562
ScreenShot5621920×1278 393 KB

Thanks, it works.

It would be nice if they added:
the "%" symbol for the CPU
a slash like for RAM
real-time reading