hilbrand
December 4, 2018, 3:53pm
103
I did, but I could not find or even understand why it happend. See my previous comment:
Matthias,
I tried to reproduce your problem But I can’t reproduce it. It might be specific to hue, but can’t test that. I suspect the context this messages are given doesn’t result in any problems. It looks like it wants to register the channel as metadata. Metadata should have an unique key, so the message seems correct. But I don’t think it should do something with channel. But I don’t know why it does. Therefor can you give some more feedback:
Did you upgrade from another openHAB version a…
ptweety
December 4, 2018, 5:48pm
104
hilbrand:
Did you upgrade from another openHAB version and if so, which one?
If you upgraded can you clear your cache and restart to see if this message persists.
If the message keeps showing when starting or I guess when reloading the items page, can you enable trace log level org.eclipse.smarthome.core and provide me the log.
I did an upgrade to my docker container from 2.3 directly to 2.4M6. Clearing the cache should be done automatically by the upgrade script in docker. Anyway, I did it again manually and found the same result aka errors in the log.
Let reduce my setup to the minimum and provide a trace after that.
EDIT:
job:
@ptweety , do these types of definition still work with M6?
Color WZWL_COLOR "Wand" { channel="hue:0210:0017884f6873:1:color,hue:0210:0017884f6873:37:color" }
Switch F2WL_TOGGLE "Flur 2.OG Ein/Aus" {channel="hue:0100:0017884f6873:6:brightness", expire="10m,command=OFF"}
I tested this and the warning is gone from the logs.
