Milight problems

I’m having a few issues with the milight binding in OH2 (this is my first attempt to use an OH2 specific binding, so the learning curve is steep! - I’ve followed the migration tutorial upto now, but following advice to use OH2 bindings where they exist, I’m heading down that path).

.things:

Bridge milight:bridge:AC*********3E [ ADDR="192.168.*.***", PORT=8899] {
	Thing whiteLed 0 "Lamps" @ "Lounge"
	Thing whiteLed 1 "Front Lamp" @ "Lounge"
	Thing whiteLed 2 "Rear Lamp" @ "Lounge"
	}

OK, first issue - I get the following warning, presumably because there’s something wrong with the .things definition:

2016-11-16 06:57:01.608 [WARN ] [milight.handler.MilightBridgeHandler] - BridgeID not known. Version 2 fallback behaviour activated, no periodical refresh available!

I then have the following items defined in .items:

Switch	Light_LoungeLamps		"Lounge Lamps"						(gLights)	{ milight="milight:whiteLed:AC*********3E:0" }
Dimmer	Light_GF_Lounge_Front_B	"Lounge Front Lamp - Brightness" (gLights)	{ channel="milight:whiteLed:AC*********3E:1:ledbrightness" }
Dimmer	Light_GF_Lounge_Front_C	"Lounge Front Lamp - Colour" (gLights)	{ channel="milight:whiteLed:AC*********3E:1:colourTemperature" }
Dimmer	Light_GF_Lounge_Rear_B	"Lounge Rear Lamp - Brightness" (gLights)	{ channel="milight:whiteLed:AC*********3E:2:ledbrightness" }
Dimmer	Light_GF_Lounge_Rear_C	"Lounge Rear Lamp - Colour" (gLights)	{ channel="milight:whiteLed:AC*********3E:2:colourTemperature" }
Switch	Light_GF_Lounge_Front	"Lounge Rear Lamp" (gLights)	{ channel="milight:whiteLed:AC*********3E:2:nightMode" }
Switch	Light_GF_Lounge_Rear	"Lounge Rear Lamp" (gLights)	{ channel="milight:whiteLed:AC*********3E:2:nightMode" }

Things and items (Karaf console):

openhab> smarthome:things
milight:bridge:ACCF2339A93E (Type=Bridge, Status=ONLINE: V2 compatibility mode, Label=null, Bridge=null)
milight:whiteLed:ACCF2339A93E:0 (Type=Thing, Status=ONLINE, Label=Lamps, Bridge=milight:bridge:ACCF2339A93E)
milight:whiteLed:ACCF2339A93E:1 (Type=Thing, Status=ONLINE, Label=Front Lamp, Bridge=milight:bridge:ACCF2339A93E)
milight:whiteLed:ACCF2339A93E:2 (Type=Thing, Status=ONLINE, Label=Rear Lamp, Bridge=milight:bridge:ACCF2339A93E)

When I first tried to test, the lights came on in either a very low brightness setting, or directly into nightMode. What I found was that I could increase the brightness without a problem, but everytime I reduced the brightness, the lamps turned off completely.

Now I’m having the problem that none of the commands work at all…

I’m using either the default sitemap - I haven’t defined a new sitemap yet, or the karaf console:

openhab> smarthome:update Light_GF_Lounge_Front ON
Update has been sent successfully.
openhab> smarthome:update Light_GF_Lounge_Rear ON
Update has been sent successfully.
openhab> smarthome:update Light_GF_Lounge_Front_B 50
Update has been sent successfully.
openhab> smarthome:update Light_GF_Lounge_Rear_B 50
Update has been sent successfully.
openhab> smarthome:items | grep -i GF_Lounge
Light_GF_Lounge_Front_B (Type=DimmerItem, State=50, Label=Lounge Front Lamp - Brightness, Category=null, Groups=[gLights])
Light_GF_Lounge_Rear_B (Type=DimmerItem, State=50, Label=Lounge Rear Lamp - Brightness, Category=null, Groups=[gLights])
Light_GF_Lounge_Front (Type=SwitchItem, State=ON, Label=Lounge Rear Lamp, Category=null, Groups=[gLights])
Light_GF_Lounge_Rear (Type=SwitchItem, State=ON, Label=Lounge Rear Lamp, Category=null, Groups=[gLights])

Cheers
James

There is a Problem with your bridge config. If You have a V3+ bridge, please use auto discovery for getting the right paramters for the thing definition.

I took the details from the inbox before, I can’t see what I’ve got wrong.

Here’s the smarthome:inbox output:

NEW [milight:bridge]: Milight Bridge AC********3E [thingId=milight:bridge:AC********3E, bridgeId=null, properties={ADDR=192.168.1.195, ID=AC********3E}, timestamp=Wed Nov 16 19:25:01 GMT 2016, timeToLive=UNLIMITED]

What should the thing definition look like?

I have to look into the code (the 2.0 binding was not written by me) to see, why the textual config says it is a V2 bridge.

Seems to be simple :

Thing definition fo a 3+ bridge needs an ID, so please try

Bridge milight:bridge:AC*********3E [ ADDR="192.168.*.***", PORT=8899, ID="AC*********3E" ] {

If it is working, I will update the binding doku.

Hi!

I’ve got the following MiLight config up and running:

Bridge milight:bridge:mibridge1 [ADDR="XX.XX.XX.XX", ID="XXXXXXXXXXXXXX" ]
{
	//Thing whiteLed 0
	//Thing whiteLed 1
	//Thing whiteLed 2
	//Thing whiteLed 3
	//Thing whiteLed 4
	//Thing rgbLed 5
	//Thing rgbLed 6
	Thing rgbLed 7
	Thing rgbLed 8
	//Thing rgbLed 9
	//Thing rgbLed 10
}
Group gMiLight

Color miRGB1_Color "Arbeitszimmer Deckenlampe" <mibulb> (gMiLight) { channel="milight:rgbLed:mibridge1:7:ledcolor" }
Color miRGB2_Color "Arbeitszimmer Ecklampe" <mibulb> (gMiLight) { channel="milight:rgbLed:mibridge1:8:ledcolor" }

Everything manually configured. No Autodiscover.

Thanks Both,

I’ve changed the things description, but the lights still don’t work.

I managed to get them to turn on, but when I attempted to dim them, they turned off…

smarthome:update Light_GF_Lounge_Rear_B 50
smarthome:update Light_GF_Lounge_Front_B 50

Now it just doesn’t respond at all…

In addition followed an openHAB2 restart, I now see a bunch of exceptions:

2016-11-16 20:35:35.125 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'milight:whiteLed:ACCF2339A93E:0': java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_101]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_101]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:186)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:79)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:63)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9.run(ThingManager.java:761)[105:org.eclipse.smarthome.core.thing:0.9.0.201611041332]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
Caused by: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at org.openhab.binding.milight.handler.MilightLedHandler.initialize(MilightLedHandler.java:114)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:764)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:1)
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:177)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	... 3 more

what exact version are you running. Seems to be really new. In that case, this might be related to some core changes according to initializing a bridge.
@David_Graff, could you step in and check your code for needed changes.

If it’s of any further use:
I’m using a a v3.0 controller, I’ve had it a couple of years and has been working faultlessly with OH1.8.3.
I also enabled DEBUG for the binding and restarted the bundle:

2016-11-17 06:06:03.932 [DEBUG] [org.openhab.binding.milight         ] - BundleEvent STARTED - org.openhab.binding.milight
2016-11-17 06:06:03.963 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.milight.internal.MilightHandlerFactory, component.id=212, service.id=354, service.bundleid=212, service.scope=bundle} - org.openhab.binding.milight
2016-11-17 06:06:03.970 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=milight:bridge, thing.id=milight:bridge:AC********3E, service.id=355, service.bundleid=212, service.scope=singleton} - org.openhab.binding.milight
2016-11-17 06:06:03.977 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=milight:whiteLed, thing.id=milight:whiteLed:AC********3E:0, service.id=356, service.bundleid=212, service.scope=singleton} - org.openhab.binding.milight
2016-11-17 06:06:03.983 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=milight:whiteLed, thing.id=milight:whiteLed:AC********3E:1, service.id=357, service.bundleid=212, service.scope=singleton} - org.openhab.binding.milight
2016-11-17 06:06:04.002 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=milight:whiteLed, thing.id=milight:whiteLed:AC********3E:2, service.id=358, service.bundleid=212, service.scope=singleton} - org.openhab.binding.milight
2016-11-17 06:06:04.008 [DEBUG] [ht.internal.protocol.MilightDiscover] - Discovery receive thread ready
2016-11-17 06:06:04.015 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={component.name=org.openhab.binding.milight.internal.discovery.MilightBridgeDiscovery, component.id=213, service.id=359, service.bundleid=212, service.scope=bundle} - org.openhab.binding.milight
2016-11-17 06:06:04.031 [DEBUG] [org.openhab.binding.milight         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=360, service.bundleid=212, service.scope=singleton} - org.openhab.binding.milight
2016-11-17 06:06:04.042 [DEBUG] [ht.internal.protocol.MilightDiscover] - Discovery receive thread ready
2016-11-17 06:06:04.042 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.045 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'milight:whiteLed:AC********3E:0': java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_101]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_101]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:186)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:79)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:63)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9.run(ThingManager.java:761)[105:org.eclipse.smarthome.core.thing:0.9.0.201611041332]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
Caused by: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at org.openhab.binding.milight.handler.MilightLedHandler.initialize(MilightLedHandler.java:114)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:764)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:1)
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:177)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	... 3 more
2016-11-17 06:06:04.067 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'milight:whiteLed:AC********3E:2': java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_101]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_101]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:186)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:79)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:63)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9.run(ThingManager.java:761)[105:org.eclipse.smarthome.core.thing:0.9.0.201611041332]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
Caused by: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at org.openhab.binding.milight.handler.MilightLedHandler.initialize(MilightLedHandler.java:114)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:764)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:1)
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:177)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	... 3 more
2016-11-17 06:06:04.065 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'milight:whiteLed:AC********3E:1': java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_101]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_101]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:186)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:79)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:63)[98:org.eclipse.smarthome.core:0.9.0.201611041332]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9.run(ThingManager.java:761)[105:org.eclipse.smarthome.core.thing:0.9.0.201611041332]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_101]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
Caused by: java.lang.NoSuchMethodError: org.eclipse.smarthome.core.thing.Bridge.getHandler()Lorg/eclipse/smarthome/core/thing/binding/BridgeHandler;
	at org.openhab.binding.milight.handler.MilightLedHandler.initialize(MilightLedHandler.java:114)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:764)
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:1)
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:177)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
	... 3 more
2016-11-17 06:06:04.060 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.161 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.212 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.263 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.315 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet
2016-11-17 06:06:04.358 [DEBUG] [nal.discovery.MilightBridgeDiscovery] - Milight bridge found MiLightkitchen.home AC********3E
2016-11-17 06:06:04.418 [DEBUG] [nal.discovery.MilightBridgeDiscovery] - Milight bridge found MiLightkitchen.home AC********3E
2016-11-17 06:06:04.462 [DEBUG] [nal.discovery.MilightBridgeDiscovery] - Milight bridge found MiLightkitchen.home AC********3E
2016-11-17 06:06:04.467 [DEBUG] [nal.discovery.MilightBridgeDiscovery] - Milight bridge found MiLightkitchen.home AC********3E
2016-11-17 06:06:04.469 [DEBUG] [nal.discovery.MilightBridgeDiscovery] - Milight bridge found MiLightkitchen.home AC********3E
2016-11-17 06:07:23.684 [ERROR] [ht.internal.protocol.MilightDiscover] - Sending a discovery packet failed. null
2016-11-17 06:07:24.689 [ERROR] [ht.internal.protocol.MilightDiscover] - Sending a discovery packet failed. null
2016-11-17 06:07:25.691 [ERROR] [ht.internal.protocol.MilightDiscover] - Sending a discovery packet failed. null
2016-11-17 06:07:26.697 [ERROR] [ht.internal.protocol.MilightDiscover] - Sending a discovery packet failed. Could not update status, because callback is missing
2016-11-17 06:08:04.034 [DEBUG] [ht.internal.protocol.MilightDiscover] - Sent discovery packet

The “NoSuchMethodError” exception shows that there is a problem in the code related to some core changes.

I’ve never seen the NoSuchMethodError before with the MiLight binding. And I am using a pretty recent Snapshot. I think I updated either last weekend or the weekend before that.

What I sometimes suffer from is that the MiLight things will get stuck in the Initializing state forever. I usually have to restart at least the MiLight binding to get them to work.

I don’t know if this is related to your problem though since I can’t find NoSuchMethodError in my logs even if they get stuck in Initializing.

I will investigate on this.

This has something todo with an inner ESH core change:

Milight seems to be fixed here:

But I am developing a new binding right now and have to dig into this, too. I don’t understand everything about the change yet…

Do I interpret this right?

ESH did some changes and now some/most/all bindings have to be adapted? So this is not an exclusive MiLight problem? Could this affect Homematic for example too?

Anyway, I’ll update my Snapshot tonight and see if it still gets stuck in initialization.

Hi,

i apears i am having the same problems anybody has a solution to this?

Hi,

During start i’m getting and exceptions with milight on latest snapshots:

[ERROR] [org.openhab.binding.milight         ] - [org.openhab.binding.milight.internal.discovery.MilightBridgeDiscovery(24)] The activate method has thrown an exception
java.lang.IncompatibleClassChangeError: Expected static field org.openhab.binding.milight.internal.discovery.MilightBridgeDiscovery.scheduler

Anyone has it?