Validate all entity names used - scripts, automations, lovelace,

[myT]

Sometime the entity names of integrations may change which may have an unexpected effect on many scripts, automations, frontend lovelace configs etc.

Is there a way to validate all these files to see if any non-existing entity name is used in order to be able to fix them?

Maybe by fetching all existing known entity names and comparing it with all entity names used in any script/automation/lovelace?

[NathanCu (Nathan Curtis)]

Watchman is what you are looking for

Watchman - keeps track of missing entities and services in your config files

Would like to present a custom integration to identify entities and services in your configuration files that either no longer exist or have a wrong state. Along with a few sensors, it may create a text version of the report or send it via notification service of choice. Please don’t be afraid of the documentation volume, I’ve tried to keep the balance between versatility and simplicity of use during development, so all parameters are optional: https://github.com/dummylabs/thewatchman Example…

[myT]

nice, thanks for the quick reply!