[SOLVED] Cannot add "Metadata" with key "xxxxxxxx" on Multichannel Items

Hi Folks,

i have recently changed some of my item configurations to Multichannel Items.
Since those changes i have error messages in my openhab.log

2019-01-03 21:51:12.907 [WARN ] [ore.common.registry.AbstractRegistry] - Cannot add "Metadata" with key "channel:LED_SZ". It exists already from provider "GenericMetadataProvider"! Failed to add a second with the same UID from provider "GenericMetadataProvider"!
2019-01-03 21:51:12.908 [WARN ] [ore.common.registry.AbstractRegistry] - Cannot add "Metadata" with key "channel:LED_SZ". It exists already from provider "GenericMetadataProvider"! Failed to add a second with the same UID from provider "GenericMetadataProvider"!
2019-01-03 21:51:12.910 [WARN ] [ore.common.registry.AbstractRegistry] - Cannot add "Metadata" with key "channel:LED_SZ". It exists already from provider "GenericMetadataProvider"! Failed to add a second with the same UID from provider "GenericMetadataProvider"!

I have 4 lights in my sleeping room and configured the item to be:

Dimmer	LED_SZ			"Schlafzimmer Licht"			<slider>	(gSchlafzimmer, gLicht, gMMItems, gRestore)		["Lighting"]		{ channel="hue:0100:00178875bf63:2:brightness", channel="hue:0100:00178875bf63:3:brightness", channel="hue:0100:00178875bf63:4:brightness", channel="hue:0100:00178875bf63:5:brightness" }

so i think, the 3 error messages refer to the 3 additional channels in the item declaration.
Now i’m wondering if this will put me into trouble e.g. working with habot

any ideas?

Hi Raven,

I’ve also seen this. Try this solution for now: [OH 2.4.0 M6] Testing Results

changed definitions as you suggested, restarted OH, no more error messages :slight_smile:

@Raven : can you please point the correction you did ? I have the same issue.

HI,
if have changed this:

{ channel="hue:0100:00178875bf63:2:brightness", channel="hue:0100:00178875bf6 [...]

to this:

{ channel="hue:0100:00178875bf63:2:brightness","hue:0100:00178875bf6 [...]

so just delete the additional channel=" definitions

Unfortunately it does not seem to work when there is a profile on the second channel. But from my testings, this just a warning and it seems to be working fine.