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.
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.
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.
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.