#Alternative to lovelace.yaml for managing large changes.

1 messages · Page 1 of 1 (latest)

lapis cave
#

Hey guys does anyone know if this exist outside of lovelace.yaml
You setup a ton of zigbe, zwave or other protocol devices. Then by some unexpected circumstances, you have to change hubs or just want to upgrade to a better controller. You then have to Uninstaller and then reinstall all 100 plus devices, but in addition if you changed names/entity id's for the devices, then every card that has that device will need to be updated as well. That can be a bit much if you count 3 tablets, desktop and 6 in wall sonoff nsp panels.
Is there no way to have any entity that was associated with the old device to also update in the same way that it ask when you make a change in the device settings section?
This could work like a find and replace, but be UI based and more automatic.

jagged pewter
lapis cave
#

I guess I am a bit confused as I think this is more of a backbone/frontend matter.

jagged pewter
#

Well, you want to change what's shown in the dashboard?

lapis cave
#

No I want that when an entity is updated in the devices setting pages that when you hit the update tab that all the changes propagate throughout all you HA files that contain that entity. Sorry If that was not clear

#

this would also be just a start, it could also be leverage that when you change deviceclass that the dashboard would update any cards with that entity as well.

jagged pewter
#

There's nothing that does that

lapis cave
#

I goal would be once place to change that propagates through the system.

jagged pewter
#

Spook can kind of help, but not really

#

Of course, if you change the entity id back to the old device, nothing has to change

lapis cave
#

Yea, I am staying away from spook for a while. I have enough odd things happening already

#

Is there a reason something like this has not been implemented?

jagged pewter
#

Because nobody has put the time and effort into doing it?

lapis cave
#

It seems that it would be a natural progression for lovelace.yaml.

jagged pewter
#

Doing that safely and effectively isn't trivial

lapis cave
#

well true

jagged pewter
#

And also the devs learned before that screwing up YAML and stripping all comments annoys people 😉

#

if you've got YAML then a simple search and replace can be done

lapis cave
#

Does S&R also work for dashboards?

jagged pewter
#

if they're in YAML yes

#

And you keep talking about lovelace.yaml so ...

lapis cave
#

It's my understanding that lovelace.yaml work exactly like that. I still use a combo of UI and Yaml for my dashboards, so I will give it a try.

jagged pewter
#

Well, if you're using the UI then that's not YAML

lapis cave
#

true. That said I think the idea would be a value add in the long run.

jagged pewter
#

So... learn Python, develop the feature, get it merged into HA 😉