If you are finding that the script one acts different from the automation, it should be written up as a feature parity defect, but I thought they worked the same.
I tested it too. It doesn’t look like it works.
I’m thinking a “feature Parity” issue is in order maybe.
Sorry to ping you @karwosts but is there something we are missing here, or indeed is the script description visibility in the ?UI code different from the Automation description visibility in ther UI?
alias: Lighting landing
description: >-
Turns landing spotlights on and off with motion sensor. Brightness of 75%
during the day to avoid glare. 40% at night.
### Revision History
**23.4.2024** Reduced stay on time from three to two minutes.
**24.4.2024** Changed action section to choose to prevent flash when dimmed
spotlights turn off.
alias: Restart router
description: >-
Switches off routeer socket for 30 seconds, then creates persistent
notification and sends SMS. \n\n### Revision History\n\n**22.4.2024** Run
speedtest and add new download speed to SMS and notification
sequence:
I think it’s a reasonable ask for them to be treated the same, and I think it would be good for the codebase to standardize.
I’m not familiar with the history here, but I would guess that someone wrote up one or more features for the automation editor and forgot to apply it to script editor as well.
The feature request here or one in frontend (which also exists) I think is a fine place for this request.
I’ve merged a PR to add a markdown box for rendering the script descriptions in the UI editor, and there’s a second one still in the works for updating the entire script editor UI to have the same functionality as automations.