How do I trace my scripts and automations inside packages

Only scripts inside scripts.yaml are editable.
Only automations inside automation.yaml are editable.

I have scripts and automations contained within almost all of my packages.

That to me was the point of using packages, so I can contain elements within each function.

How do a trace my scripts and automations inside these package yaml’s ??

I’ve been using HA for a looooong time, by now a need a little help.

How do I trace the scripts and/or automations within my package yaml’s ???

Thank You

you just need to put a unique identifier in the automation code:

alias: some automation
id: some_unique_identifier # <-- here
trigger:
.
.

I always use the resulting entity_id (minus “automation.”) as the id. That way I always know it will be unique

once you do that it will show up the automation will show up in the list to debug it.

I’m pretty sure it is the same with scripts tho I’ve never done it.

1 Like

Thank you for your reply, but sadly everyone off my automations has a unique id: like this

  • id: f12affd5-f763-496a-9ed0-21671de53c98
    alias: Any Lights On
    trigger:

and yaml scripts don’t have unique id’s that can be assigned that I know of.

So…you are saying that even if an automation is manually assigned a unique id then they still don’t show up in the automation trace section?

I just tested that and you are right.

But I also just looked and all of my scripts are in the script trace section as well even tho I never use the UI to create them and many of them are in packages.

Again, thx for your time in looking at this.

I would kindly request HA personal to show me the correct packages method to use to be able to trace my automation’s and scripts. I spent many many hours constructing them (the packages) and now I can’t debug my routines…Please…What gives.

Thanks

There really is nothing special about packages when it comes to automations or scripts.

if the automations are showing up in your “dev tools → states” list and they all have a unique id then they should be showing up in the listing of the “settings → automations & scenes” list as well.

how did you have the automations configured before you switched to packages? where (in which file) did you have them written?

I’ve been running HA for about 4 years I think. All of my automation’s and script work fine, right now,but
I switched to packages for the neat and orderly way it allows be to put all routine related domains into the same file. I thought that was nice!

Now when I try to look at a script or automation trace…NO GO. Sooo, when I write a new routine I now have no way to trace it when trouble occurs ( which of course it will ) unless a move all of the code out of the package and into the ‘main’ automation yaml called automation. Needless to say that is a BIG pain.

Unless the HA gods can tell me how to make it work i’ll need to dump all of the package work and revive the old code version.

Thx

I’m really trying hard to tell you that packages have nothing to do with the automation debug traces being available. I have automations in my packages and they show up fine in my automation page and provides debug traces too as long as they all have a unique id.

You seem to not be answering my direct questions for some unknown reason.