Hey Stefan,
I do not use the Milight Binding myself. You should have opened a new thread with a speaking title so users would actually see “milight” and say "Hey, I know that!"
Maybe @Kai or @hmerk can help, they are the authors of http://docs.openhab.org/addons/bindings/milight/readme.html
In the mean time you should look into other bindings. In the beginning I had to learn a lot of things by playing around… Look into astro, network or some weather binding to make progress.
@Stefanseiner on first sight, it looks as you are mixing configurations here, old openHAB 1.x binding configs and openHAB 2.0 channel configs for the same item.
What version of the milight binding are you using. If it is the 2.0 version, you don’t need a milight.cfg in conf/services. if it is the 1.x version, please remove the leading milight: in the config file.
As @ThomDietrich already pointed out, please open a new conversation for questions around a specific binding, or search if the same question already might have been asked and answered.
No, openHAB 1.x uses the prefix as it is a config in openhab.cfg.
Thats what the readme says.
Using a 1.x binding with seperate .cfg file, the prefix is not needed, thats by design of openHAB 2.
Edit : Sorry @ThomDietrich, just saw that you are refering to the openHAB 2 binding doku. I that case, you are right, this needs to be updated by @David_Graff.
In this case I believe your configs should look like:
services/milight.cfg
#Host of the first Milight bridge to control
bridge1.host=192.168.178.49
bridge1.port=8899
#Host of the second Milight bridge to control
bridge2.host=192.168.178.73
bridge2.port=8899
items/milight.items:
// Licht EZ
Dimmer dEZ_Licht "EZ Dimmer Brightness [%.0f]" {channel="milight:rgbLed:ACCF2353D5E4:7:ledbrightness"}
Color cEZ_Licht "EZ Colorpicker" {channel="milight:rgbLed:ACCF2353D5E4:7:ledcolor"}
//Switch wEZ_Licht "Weiss" {channel="milight:rgbLed:ACCF2353D5E4:7:ledcolor"}
Version 2.0 of milight Binding does not need services/milight.cfg at all.
Newer bridges can be discoverd in PaperUI. Configuration of old and new bridges can be done there as well, or in .things file, see discussion here.
Will try to update the V2.0 binding doku asap.
Thanks.
Actual I’m testing the PaperUI build-in rule module, because when I’m getting this running maybe I’ll won’t need confuguration files (and at PaperUI all milight functions including linking are working out of the box).