WebView not good in rules(((
complexity of binding or its use?
if its use, then here is another example:
if I want to make a rule that will control the LED strip divided into 20 segments, I need to send 20 identical commands to each segment, otherwise I would only need to send one to the global item
OK, maybe even try to ask the developer for a similar json example.
Then you can use group items. 
then you can send one command in either rules or move a single control and they will all Change. It can be done already.
Hey @matt1 ,
I also tried your new binding. The discovery found 2 things for my single WLED lamp. While adding one of them I got a server error. Inbox
error:
2022-02-06 14:06:20.248 [ERROR] [internal.JSONResponseExceptionMapper] - Unexpected exception occurred while processing REST request.
java.lang.IllegalArgumentException: UID must have at least 3 segments.
at org.openhab.core.common.AbstractUID.<init>(AbstractUID.java:71) ~[?:?]
at org.openhab.core.common.AbstractUID.<init>(AbstractUID.java:49) ~[?:?]
at org.openhab.core.thing.UID.<init>(UID.java:48) ~[?:?]
at org.openhab.core.thing.ThingUID.<init>(ThingUID.java:130) ~[?:?]
at org.openhab.core.io.rest.core.internal.discovery.InboxResource.approve(InboxResource.java:115) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) ~[bundleFile:3.4.5]
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) ~[bundleFile:3.4.5]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:201) ~[bundleFile:3.4.5]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:104) ~[bundleFile:3.4.5]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) ~[bundleFile:3.4.5]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) ~[bundleFile:3.4.5]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:265) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:225) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:298) ~[bundleFile:3.4.5]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:217) ~[bundleFile:3.4.5]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) ~[bundleFile:3.1.0]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:273) ~[bundleFile:3.4.5]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550) ~[bundleFile:9.4.43.v20210629]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[bundleFile:?]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:602) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434) ~[bundleFile:9.4.43.v20210629]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:294) ~[bundleFile:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[bundleFile:9.4.43.v20210629]
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:82) ~[bundleFile:?]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:388) ~[bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:633) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:380) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:386) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.43.v20210629]
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.43.v20210629]
at java.lang.Thread.run(Thread.java:829) [?:?]
The other thing was added fine and has channels (Global Brightness, Playlists & Presets) :
Not sure if this is supposed to be correct. My Wled is a v0.13.0-b5.
Thanks
Edit: Same error when trying to remove or ignore the thing. Remains in my inbox.
I did have this happen once during testing and could not get it to happen again. The thing disappeared from the inbox itself after a certain amount of time passed. Since the thing is linked to the mDNS result, it may have been leaving it turned off and not on the network whilst I did a restart that caused it to go away. Iāll take a look at this againā¦
After adding the bridge and it is online, do a SCAN from the inbox and it will find any segments that you have setup which includes the segments names if you have firmware 0.13.x
Also if you click on SHOW ADVANCED you will see more channels.
Thanks for your reply.
Tried your suggestion with no luck. removed the WLED device from Wifi, restarted as well as rebooted OH several times. The broken thing was always in the inbox. In the end I stopped Openhab and edited org.openhab.core.config.discovery.DiscoveryResult.json and removed the lines about the thing in the inbox.
After starting OH again, the Thing was gone and once WLED was powered again a few seconds later added automatically by discovery again.
Once the bridge was added a new scan also found the segment (yes, its only one)
I made a change to the binding a few days back to check the mac adress is not blank before adding the result to the inbox in case that was occurring. So recommend you uninstall and install again from the marketplace to get this change installed. Thanks for reporting this.
The pictures show it is working as intended on your system, all looks as it should.
Hey guys,
I just created two new selections based on Its based on WLED version 0.13.0-b7 for my sitemap to select all avilable 117 effects:
Selection item=FX_Kuechenschrank mappings=[0="Solid", 1="Blink", 2="Breathe", 3="Wipe", 4="Random Wipe", 5="Random Colors", 6="Sweep", 7="Dynamic", 8="Color Loop", 9="Rainbow",
10="Scan", 11="Scan Dual", 12="Fade", 13="Theater", 14="Theater Rainbow", 15="Running", 16="Saw", 17="Twinkle", 18="Dissolve", 19="Dissolve Random",
20="Sparkle", 21="Sparkle Dark", 22="Sparkle+", 23="Strobe", 24="Strobe Rainbow", 25="Strobe Mega", 26="Blink Rainbow", 27="Android", 28="Chase", 29="Chase Random",
30="Chase Rainbow", 31="Chase Flash", 32="Chase Flash Random", 33="Rainbow Runner", 34="Colorful", 35="Traffic Light", 36="Sweep Random", 37="Chase 2", 38="Aurora", 39="Stream",
40="Scanner", 41="Comet", 42="Fireworks", 43="Fireworks Random", 44="Merry Christmas", 45="Fire Flicker", 46="Gradient", 47="Loading", 48="Dual Color IN/OUT", 49="Dual Color IN/IN",
50="Dual Color OUT/OUT", 51="Dual Color OUT/IN", 52="Circus", 53="Halloween", 54="Tricolor Chase", 55="Tricolor Wipe", 56="Tricolor Fade", 57="Lightning", 58="I.C.U", 59="Multi Comet",
60="Dual Scanner", 61="Random Chase", 62="Oscillate", 63="Pride", 64="Juggle", 65="Pallete", 66="Fire", 67="Colorwaves", 68="BPM", 69="Noise Fill",
70="Noise 1", 71="Noise 2", 72="Noise 3", 73="Noise 4", 74="Color Twinkle", 75="Lake", 76="Metor", 77="Metor Smooth", 78="Railway", 79="Ripple",
80="Twinklefox", 81="Twinklecat", 82="Halloween Eyes", 83="Solid Pattern", 84="Solid Pattern Tri", 85="Spots", 86="Spots Fade", 87="Glitter", 88="Candle", 89="Fireworks Starburst",
90="Firework 1D", 91="Bouncing Balls", 92="Sinelon", 93="Sinelon Dual", 94="Sinelon Rainbow", 95="Popcorn", 96="Drip", 97="Plasma", 98="Percent", 99="Ripple Rainbow",
100="Heartbeat", 101="Pacifica", 102="Candle Multi", 103="Solid Glitter", 104="Sunrise", 105="Phased", 106="Twinkleup", 107="Noise Pal", 108="Sine", 109="Phased Noise",
110="Flow", 111="Chunchun", 112="Dancing Shadows", 113="Washing Machine", 114="Candy Cane", 115="Blends", 116="TV Simulator", 117="Dynamic Smooth"]
and all 70 palettes:
Selection item=P_Kuechenschrank mappings=[0="Default", 1="Random Cycle", 2="Color 1", 3="Colors 1&2", 4="Color Gradient", 5="Colors only", 6="Party", 7="Cloud", 8="Lava", 9="Ocean",
10="Forest", 11="Rainbow", 12="Rainbow Bands", 13="Sunset", 14="Rivendell", 15="Breeze", 16="Red&Blue", 17="Yellowout", 18="Analogous", 19="Splash",
20="Pastel", 21="Sunset 2", 22="Beech", 23="Vintage", 24="Departure", 25="Lanscape", 26="Beach", 27="Sherbet", 28="Hult", 29="Hult 64",
30="Drywet", 31="Jul", 32="Grintage", 33="Rewhi", 34="Tertiary", 35="Fire", 36="Icefire", 37="Cyane", 38="Light Pink", 39="Autumn",
40="Magenta", 41="Magred", 42="Yelmag", 43="Yelblu", 44="Orange&Teal", 45="Tiamat", 46="April Night", 47="Orangery", 48="C9", 49="Sakura",
50="Aurora", 51="Atlantica", 52="C9 2", 53="C9 New", 54="Temperature", 55="Aurora 2", 56="Retro Clown", 57="Candy", 58="Toxy Reaf", 59="Fairy Reaf",
60="Semi Blue", 61="Pink Candy", 62="Red Reaf", 63="Aqua Flash", 64="Yelblu Hot", 65="Lite Light", 66="Red Flash", 67="Blink Red", 68="Red Shift", 69="Red Tide",
70="Candy 2" ]
May be usefull for others!? I would like to add it to the documentation page here. But donāt know howā¦
I have exactly the same issue. Any solution on that?
The binding does it automatically, you do not need to do that, of course there is no harm in doing it only that you will waste time instead of using a binding to do boring repetive work that needs redoing and checking every firmware version.
Hi @matt1
Yes I just see that it works for a real item mapped to a fx channel. That is cool. I did not notice that.
But I am using 6 seperate segments in my kitchen cupboard and this is a group of the 6 channels.
Any trick to inherit this automatic feature to the group?
Or another trick to set the effect for all segements at the same time, like in the web interface?
Thanks for the binding by the way!
No idea as I have never tried to do it with a group before, it may be worth asking this in a new thread in a generic way so more people look and may reply. If the answer is NO, groups wont ever inherit the "command options" that child things have. Then we should look at adding the extra channels to the BRIDGE which @marsic was asking for this just a few posts above in this thread.
I believe you can create over lapping segments, so create an extra segment that starts at 0 LED and all the way to MAX led, then you can have a set of controls that do all segments/leds. However I have not tested this so please report back if it works or is not possible. I only pull my lights out at Christmas time so am not the best person to ask about it, but as per the posts above, I do prefer the group method as it will work for all bindings so you learn the technique once and can use it over and over again. This is why I feel asking in a new thread should be the first step to see if it is possible and if not raise it as a request to be added into the core.
Hey @olialb,
as written in the post you have to:
After that, I used the latest binding and it never happend.
Best
Hi,
I have a question about the WLED binding.
Iāve installed this for the first time and added one WLED device to my thing configuration.
To test this I also created a Color item linked to the āmasterControlsā channel.
After this I was able to control the colors of the WLED device with the color picker, this is working fine.
But when I use the brightness slider, It isnāt controlling the brightness of the WLED device but something else (I think the saturation).
How can I fix this?
What firmware is on the wled esp8266 device? What version of openhab? There have been no reports of this so I doubt it is a bug unless it is from older versions.
Lastly I would recommend using the marketplace version of the binding if your setting up as the next milestone will have that version included and it will save you from a breaking change if you start with the marketplace version that uses bridge things.
Iām using version 0.13.2-a0 build 2203191 of WLED and Openhab version 3.2.0 (release build).
In the meanwhile I also tested the marketplace binding.
I got the same result here. When I change the slider under the colorwheel, this isnāt changing the brightness of the WLED device but the saturation instead.
I also created a dimmer item linked to the brightness channel of the WLED device and this is working. But also here I see a little difference between the WLED webinterface and Openhab. When I change the brightness level to minimum via the WLED webinterface, the LEDs are on at the minimum brightness level. When I change the brightness level to minimum via Openhab, the LEDs are OFF.
When you move the control what do you see has changed when you visit ipofwled/json/state
In a web browser? Also some trace level logs would be helpful. Please post in a new dedicated thread.
The second issue you post about the LEDs turning off when you put multiple controls at minimal brightness is the firmware. I believe it may be a rounding error, from converting from 0-100% and a value of 0-255, just use the one control for brightness and not multiples when possible.
When I move the slider under the colorwheel in Openhab I see that the ācolā (color RGB value) values are changing but the ābriā (brightness) value isnāt changing.
When I change the brightness via the WLED webinterface I see that the ābriā (brightness) value is changing and that the ācolā (color RGB value) values are not changing.
The behavior via the WLED webinterface seems to be the correct one because via Openhab, the LEDs are OFF when the slider is in the first 1/3 of the slider part.
That is normal behavior. If youāre using a colourwheel control, it only sends HSB commands, so this means the binding can not tell the brightness slider apart from any commands made using the color gradient area. This was one reason I added a separate brightness channel.
If you want to emulate the GUI of the wled firmware, you would be better to use the primary color channel and the separate brightness channel. The GUI has separate controls and the separate channels should work closely to how they do. The masterControls act very differently and are made to turn a LED strip more into a standardized color changing globe.
Back to your issue of the LED turning off when the sliders are at minimal values, this is because of the ability to change the DUTY CYCLE of the leds by the following level of controlsā¦
If your telling it to be 1% of 1% of 1% of 30% then yes this is normal from my experience with the WLED firmware. It should be reported as a bug in the firmware if it is still happening as it should not turn off, but I understand the issue of programming this with a system that only has 8 or 10 bit resolution at the PWM controller.
Iāve installed the binding from the marketplace and it all seems fine, and it shows all the presets, but the names are jumbled up? The right list of names, but in the wrong order essentially. Anyone had this issue?
openHAB 3.3.0