Remove custom semantic tags in conflict with new 5.0 standard tags

Setup, Configuration and Use Migration
1

Hi everyone,

prior to version 5.0 I added some custom tags to my setup to extend the semantic model to my needs. With version 5 most of these custom tags have become obsolete due to the high number of predefined tags. As expected I do have some conflicts now that don’t really seem to be worrying but nevertheless I wanted to clean this up. However I don’t know exactly how to do that.

The situation: At OH startup I see conflicts like this in the logs:

2025-10-07 12:38:44.565 [WARN ] [ore.common.registry.AbstractRegistry] - Cannot add "SemanticTagImpl" with key "Equipment_UPS": Failed to create semantic tag
 'Equipment_UPS': tag 'Equipment_PowerSupply_UPS' already exists.

Equipment_UPS is my own custom tag that is obviously no longer needed. But how can I get rid of this custom tag? As it is not loaded into the registry I cannot remove it from the UI or the API. Is the only option to search and remove this in the jsonsdb?

2

I think editing the JSONDB might be the only way to remove it.

To be extra safe, I’d only edit the JSONDB to change the name of the tag to something that doesn’t conflict with an existing tag and then you should be able to remove it safely from the UI. This has less risk of failing to delete something (e.g. a comma) or deleting more than you should which might break the whole file.

Remember any editing of the JSONDB must be done while OH is offline.

1 Like
3

Thank you, this sounds like a good advice. So far I never had to mess with the jsondb but this seems to be the way to go then.