Persisent notifications and critical notifications

[e-raser]

Regarding

@HasQT

You will need to make a long lived token via your profile button in Home Assistant.

as I don’t like to have that additional piece and also bind to my user account:

What about simply using the Supervisor token as e. g. @CentralCommand does (did) with

Update notifications! Core, HACS, Supervisor and Addons (now a blueprint!)

Big update - 4/7/2022 As of release 2022.4.0 of HA, this package is now a blueprint! [Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.] Now all you have to do to get update notifications for everything is this: Click the import button Create an automation out of the blueprint Fill in the inputs based on what features you want to enable (there’s a few options, the descriptions should explain them). I’m going to leave the original p…

(first post, unfold Original Package for HA prior to 2022.4.0, unfold Update Notifications package):

command: 'curl http://supervisor/supervisor/info -H "Authorization: Bearer $(printenv SUPERVISOR_TOKEN)" | jq ''{"newest_version":.data.version_latest,"current_version":.data.version,"update_available":.data.update_available,"addons":[.data.addons[] | select(.update_available)]}'''

Looking at this part:

Authorization: Bearer $(printenv SUPERVISOR_TOKEN)

…which is pretty much following Authentication API | Home Assistant Developer Docs which is linked in the profile section at long lived tokens section at the bottom.

• Can this be used together with a rest sensor?
• Or is this specifically only for command_line sensors, as only there the SUPERVISOR_TOKEN is available in the environment the command is run?