Just curious if others see the same. I have some scripts configured for Carplay → Quick Access. When I touch them in the car, they turn “check mark” to indicate they’ve run, but they don’t run.
There is no record inside Home Assistant of them running, either.
I had renamed the script entities. I discovered the disconnect in the “unique id”? in scripts.yaml.
I have seen things like this before. Not sure this belongs anywhere, but how can it be so easy to mess up scripts by just trying to rename them? Seems like the ability to rename a script entity shouldn’t create problems… everywhere? Fixing it also removed categories I had applied, so presumably there’s issues in a bunch of places when trying to rename.
Do people just never rename/re-entity-name scripts?
Hello @billyfw,
I found your post and looks I have the same problem. I described it here CarPlay and Scripts - problem with Quick Access
But to be honest - I am not sure how did you solve it. What exaclty did you change? I have the same situation with my CarPlay and I am not able to fix it I didn’t rename scripts. Even with new scripts I have the same problem.
Just saw this. I wish I had better data. As it happens, 4 of the 6 scripts I got fixed by disabling old scripts, renaming, and trying to get entity names to be what I thought they were in the first place.
But it’s so messy and bad. I think my best suggestion might be to mass copy the script and recreate it in a new one.
That doesn’t speak to you seeing the problem with new scripts. There is some sort of “refresh” function in the companion app settings if I remember correctly; maybe that’s why you’re not seeing new scripts? Only other thing that I remember working for me at one point was searching for friendly name vs. entity name.
Overall, super messy and not easy/awesome/predictable, as of feb '25.