Try a restart of OH I guess my I don’t have a lot of ideas. I’ve never done this myself.
Same here:
Could not update element with key _tags:MY_MQTT_SONOFF in ManagedMetadataProviderImpl, because it does not exists
I have still not got this error to go away
FTR: This is only a warning, no error and as far as I can tell, you can simply ignore it. I agree that it isn’t nice to have the log full of it, though…
This “error” (Warning) is due to using underscore in the item name…
I have the same problem in this thread:
I dont think its got anything to do wiht underscores as I get these errors also and none of my items have underscores?
22:05:38.452 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Cpu_Load' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.461 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Storage_Used' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.467 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Cpu_SystemUptime' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.470 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Network_DataSent' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.471 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Memory_Available' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.472 [WARN ] [core.common.registry.AbstractRegistry] - SwitchItem with key 'KitchenReset' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.474 [WARN ] [core.common.registry.AbstractRegistry] - SwitchItem with key 'LivingRoomReset' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.492 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Storage_Available' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.497 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Memory_Total' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.500 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Memory_Used' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
22:05:38.501 [WARN ] [core.common.registry.AbstractRegistry] - NumberItem with key 'OpenHAB_Storage_Total' already exists from provider GenericItemProvider! Failed to bulk-add a second with the same UID from provider ManagedItemProvider!
I’m still having this problem
Me too and don’t use any underscores either. Very frustrating as this deletes my Homekit items every time I update the item file
i resulted in just putting the affected items into there own items file so it does not get updated when can be helped
Thanks, that’s actually not a bad idea, at least for now. I was planning to move them all to nodered (as that works fine) but I might indeed move them to a separate items file.
Thanks for the suggestion.
Glad too help it’s been working fine for me but obviously it still messes up when modifying that item file
I’m also facing this underscore issue (oH2.3 stable on raspbianpi) 
Unfortunately it affects all temperature values which are provided by my MAX thermostats.
They are shown as – in the sitemap.
I really hope that there will be a bug fix soon.
I’ve got the same issue.
The problem started when I added the Google Home Assistant tags into my item files. In my case, I migrated (back) from the PaperUI towards items files so I can easily add the tags. But I don’t believe it has anything to do with cache or so. Since I’ve got also an existing item file with tags, that also spit out the Warning. In my knx items, I’m using underscore. But in my default item file not, see example below.
default.items
Group:Switch:OR(ON,OFF) LightsWO "Lichten Woning [(%d)]" <light> [ "Lighting" ]
Group:Switch:OR(ON,OFF) LightsAT "Lichten Atelier [(%d)]" <light> [ "Lighting" ]
Group:Switch:OR(ON,OFF) LightsBU "Lichten Buiten [(%d)]" <light> [ "Lighting" ]
Group:Switch:OR(ON,OFF) LightsALL "Alle lichten [(%d)]" <light> [ "Lighting" ]
Log output:
2018-10-30 14:31:49.177 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'default.items'
2018-10-30 14:31:49.233 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:LightsWO in ManagedMetadataProviderImpl, because it does not exists.
2018-10-30 14:31:49.236 [ome.event.ItemUpdatedEvent] - Item 'LightsWO' has been updated.
2018-10-30 14:31:49.351 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:LightsAT in ManagedMetadataProviderImpl, because it does not exists.
2018-10-30 14:31:49.353 [ome.event.ItemUpdatedEvent] - Item 'LightsAT' has been updated.
2018-10-30 14:31:49.389 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:LightsBU in ManagedMetadataProviderImpl, because it does not exists.
2018-10-30 14:31:49.391 [ome.event.ItemUpdatedEvent] - Item 'LightsBU' has been updated.
2018-10-30 14:31:49.426 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:LightsALL in ManagedMetadataProviderImpl, because it does not exists.
2018-10-30 14:31:49.429 [ome.event.ItemUpdatedEvent] - Item 'LightsALL' has been updated.
Everything is working, so no big deal. Just sad that with every item file update, all status and so on get resetted.
Let me know if I can help in any way…
I’d also like this too be solved and can confirm it’s deffinitly related too the itemtags for the google home
I have resorted too moving my Google home items too a separate file so it doesent get updated as much
But updating this file does cause a reset very anoying
1 Like
Hi,
Just upgraded for 2.2 to 2.3 today and I am also seeing the following errors but not all items have “_” so guess it’s not the name per say but any items with the GHA tag.
2018-11-03 18:03:35.655 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:ALLState in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.662 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:LivOverride in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.694 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:SF_Study in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.702 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:SF_ST_ZW_Socket_1 in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.768 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:SF_ST_ZW_SW_1 in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.779 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:SF_MB_ZW_Socket_2 in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.786 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:HolidayMode in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.794 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:NASMode in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.803 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:Kiosk1Power in ManagedMetadataProviderImpl, because it does not exists.
2018-11-03 18:03:35.811 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:Kiosk1Reboot in ManagedMetadataProviderImpl, because it does not exists.
The main issue for me is the items stop showing there actual state through the “Classic” interface and IOS app which is a frustration.
Kevin
And Hue emulation does not work, meaning Alexa does not find any switch anymore…
has this been fixed. I have the same issue and it sets some of my values to null
Removing all underscores from items names (in .items file) that are related to Google ASssistant (i.e (Switchable) solved my bug a few minutes ago.
Hi,
Sadly this doesn’t work for me as not all of my affected items have “_” in the name but I still get the same errors.