18 Replies
Help us Help Others!
To help others find answers, you can mark your question as solved via
Right click solution message -> Apps -> ✅ Mark Solution
Help us Help You!
Please don't delete messages or posts because it makes it impossible to understand what happened. If you don't want your messages to be seen then don't post here.
Please provide us with the version number of your client.
You can find it in the HA device info page after 'Firmware'.Make sure to provide detailed reports of bugs.
Please include error log uploads and info about the bug.
@Amadeo
@DrR0x
Copied from #🛰・general
it was a LaunchUrlCommand but the name dident change for the action, onlly for the command/"button" itself. esely created a new action with the right name
also got a crapton of these errors in the log after i run the script sucesfully:
@ewonais could you please provide the original & converted configuration as well as full log file?
where do i find the old config?
fir binary sensors the script leves "_" at the start
The compat_name task won't change the entity names if the modified entity id name doesn't match the old one (there should be a log file with "compat_names" if you can please also attach it)
Regarding old config, best case scenario you've backed it up before running the task, worst case scenario it's in the original HASS.Agent instalation config folder.
Regarding co figuration files - only sensors and commands file is needed (don't send anyone the application configuration before stripping the access token from it)
Or technically a home assistant log file right? Only the name tho
remember i backuped v1 wen installing v2
Perfect, that config folder will contain the original names before compat names run
command in v1:
{
"Id": "ed50e58f-c940-4684-80b7-5cf7de36b5d8",
"Name": "CHRISTIANS_STAT_web",
"Type": "LaunchUrlCommand",
"EntityType": "button",
"Command": "{"Url":"http://192.168.1.5:8123/lovelace/default_view\",\"Incognito\":false}",
"KeyCode": 0,
"RunAsLowIntegrity": false,
"Keys": []
},
v2 after script:
{
"Id": "ed50e58f-c940-4684-80b7-5cf7de36b5d8",
"Name": "web",
"EntityName": "web",
"Type": "LaunchUrlCommand",
"EntityType": "button",
"Command": "{"Url":"http://192.168.1.5:8123/lovelace/default_view\",\"Incognito\":false}",
"KeyCode": 0,
"RunAsLowIntegrity": false,
"Keys": []
}
for actionss i do not hasve a coppy of v2 befor fix, but in the gui it locked the same as in v1
v1:
[
{
"Id": "54061450-54d6-4b7e-b462-a4a25662f584",
"Domain": "HASSAgentCommands",
"Entity": "CHRISTIANS_STAT_web",
"Action": "On",
"HotKeyEnabled": false,
"HotKey": "None",
"Description": "web ui"
}
]
after fix:
[
{
"Id": "7d5736da-d63f-4aa5-af00-971e6e8a82ba",
"Domain": "HASSAgentCommands",
"Entity": "web",
"Action": "On",
"HotKeyEnabled": false,
"HotKey": "None",
"Description": ""
}
]
it was a LaunchUrlCommand but the name dident change for the action, onlly for the command/"button" itself. esely created a new action with the right nameok I'll need a bit more explanation, what exactly didn't change
Yeah was slightly confused by this as well. By action do you mean quick action or command?
quick action didden 't change, it had the old name. command changed
That's normal, quick actions don't have any change on HA side. They are simply a quick way to interact with entities. Like the HA mobile app.
The name is simply a name you want.
aq was linked to a command that didden't exist becouse the command had a new name. when i clicked qa mothing happend
adding a qa linked to the new name for the dommand made it work agen
Ahh, that sort of makes sense I guess. We haven't added checking for quick actions as this seemed more of a rarity.
So it's not really a bug if it failed to do the quick actions name. It's directly linked to a HA entity so it must be updated if the HA entity changes.