@jacobkuriakose
it looks like you do not really understand what you are doing, please read this thread and others to understand how OH works… i cant do everything for you - please use your brain
you are using my LED Controller ID “A020A61D34BE” and not yours “600194955766”
every setting you need to know is already in this thread, please check over and over till you get it to work…
I’m facing a new problem, after I restart OpenHAB, my LD No. changes to LD686 to LD382A automatically. I have to assign it every time I restart the OpenHAB. Could you please help me out in this problem…?
It remains a tricky process.
initially I had it working without a things file
then it ceased to work
added a thingsfile ->worked again
then it ceased to work again
in my paperUI config things it says: Status: UNINITIALIZED - HANDLER_INITIALIZING_ERROR No enum constant org.openhab.binding.wifiled.handler.AbstractWiFiLEDDriver.Protocol.LD741
Reinstalling the binding solved it
Sadly it is a recurring error
This time I noticed after a while that the “Thing” in paper UI had disappeared, added it again… working again
I understand the firmware also caters for timers, not sure whether or not the binding supports those
I want to use the YL5 Led Controller with this binding. Autodiscovery works and detects the controller. The status is shown online only if I am choosing the Fading mode. On Classic mode, it does not show as online.
The problem is, that the status is not detected and therefore cannot be changed:
08:09:00.321 [ERROR] [rnal.common.AbstractInvocationHandler] - An error occurred while calling method ‘ThingHandler.thingUpdated()’ on ‘org.openhab.binding.wifiled.internal.handler.WiFiLEDHandler@3d505’: null
java.lang.NullPointerException: null
at org.openhab.binding.wifiled.internal.handler.WiFiLEDHandler.dispose(WiFiLEDHandler.java:96) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.thingUpdated(BaseThingHandler.java:206) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
[…]
at org.openhab.binding.wifiled.internal.handler.AbstractWiFiLEDDriver.getLEDState(AbstractWiFiLEDDriver.java:123) ~[?:?]
... 65 more
in the LEDState.java file is defined as follows:
public LEDState(int state, int program, int programSpeed, int red, int green, int blue, int white, int white2)
is this correct, that state should be integer? I thought it should be either ON or OFF.
I’m using magic home LED Controllers on my aquarium and they work well. But I have one question that I was hoping I could get some help with. My controller does not have a static ip option and in case of a power failure its ip address can change and openHab loses connection with it as the binding uses the older ip address. One solution to this can be using a router allowing me to bind the mac id to a static ip but my router does not have this option. Can you recommend me an alternative way?
i do not have any issues with connections, the cheap controllers just died…
the sunix one is still working and YES it works with the LED Binding.
only thing is, you need to switch from LD 382 to LD 686