Tags: #<Tag:0x00007f617e18ddf0>

The only bit I cant get working with MQTT2.4 is the color. If anyone has a solution for that it would be nice to see it. By the way I am not a coder so these things can be tricky.

Hi !
I used a simple rule to implement the color part in this. Hope thats helpful.

Thanks will try it later

wled 0.8.6 is a pre release as of now. I found bugs(possibly errors from my side(I am still a noob)) using that. Better use 0.8.5 . Works perfectly.

Keep in mind, there’s this proposal open to change the MQTT structure for WLED in one of the upcoming releases. It’ll make things much easier, and I’ve been holding off from converting my LED controller project to WLED until that’s done. The only thing that concerns me about it, is there will no longer be a “group” topic (i.e. to allow you to send commands to single LED strips, or all at once), but you’ll still be able to send commands to individual LED strips, and have them sync each other via UDP…

Hi @bartus .
Yeah, the 9.0 release is scheduled to be released on 1st December. Pretty excited about it.
BTW I have subscribed to your channel. Its Really great. The first time I learned about OH was when you featured in a video with DrZzzz talking about the differences and similarities between HA and OH. And later I migrated to OH as soon as I found easy tutorials on your channel. Thanks for that BTW.


Just got WLED up and running in time for the tree to go up. I designed this case to make a neat setup with a D1 mini and am looking at how easily this can be setup in Openhab.

1 Like

Just a heads up I have spent a few hours converting my espmilighthub binding into a wled binding and it is 70% working. I should have two way connectivity with wled so any changes in the phone app will show up right away in Openhab and vice versa. Already have google voice control working through Openhab. on/off, colour and brightness.


That sounds really great ,that will be great for my rooms were I have both kinds (milights and wled)

thanks a lot. a binding for wled is all we need

No problem. The binding is ready for beta testing over in the below thread and has more functionality than the other method used in this thread…

1 Like

Thanks I’ll be using that from now on.

Is there a way to make the wled works like a touch dimmer? I build my kitchin lights whit w2812b strips and I wood like too be able to make it work whit short press to turn on and off and long press to make it dim up and down like a touch dimmer.

Yes It is Possible can do that.
Connect push button in Wemos mini Pin D2 and GND .
Then in WLED Setting page Time and Macro Page set macro
These macros can be executed using Button functionality
Button functionality have 3 action 1. Short Press 2. Long press 3. Double press


This is currently supported for the following parameters:
A, R, G, B, W, R2, G2, B2, W2, FX, SX, IX, FP, PL

ref this page :https://github.com/Aircoookie/WLED/wiki/HTTP-request-API

My SetUp:

given the WLED can be used as a http dimmer can this rule “INCREASE/DECREASE”
by toggel a push button this wood be VERY NICE :smiley:

Dimmer myDimmer "My http Dimmer is [%d %%]" {http=">[*:POST:http://www.domain.org/home/lights/23871/?status=%2$s&type=text] <[http://www.domain.org/weather/openhabcity/daily:60000:REGEX(.*?<title>(.*?)</title>.*)]"}

(Item definition from documentation)

Now to change the value, either use a slider in Basic UI or something similar, with “real” sliders, or use INCREASE/DECREASE commands and a rule to set the value:

rule "My http dimmer"
    Item myDimmer received command
   if (receivedCommand == DECREASE) {
        myDimmer.sendCommand((myDimmer.state as DecimalType) - 5)
    else if (receivedCommand == INCREASE) {
        myDimmer.sendCommand((myDimmer.state as DecimalType) + 5)

I`m still making my lights smarter diy. ,but untili have gotten the first light to work like before
i tried to make it smarter (it had a regular dimmer before) , but i like some bling bling some times to play whit,so before i can move on to more lights i have to make this work first .

After woods i will like some off this lights to work on BK Hobby`s Hasp plates for next project

Are you tested the Dimmer part? If i use your example i only see values from 0 to 100 in the topics and never 0-255.

Also would you be so kind and provide the neccessary tranformation files?

Thanks a lot



Nevermind, now i get also the complete range from 0-255. However i would really appreciate if you could provide the tranformation files. :smiley:

Hi there.
The transformation files are in the last link of the post marked as solution.
Here is that link

If you use min/max definition in the channel configuration in .things file, you can transform dimmer’s 0-100 percent values to wled’s 0-255 values. The only drawback is, there is no way to round it up to integer value, but it seems it works fine on wled side without problems.

Here is my master brightness definition:

Thing mqtt:topic:sentinel:k-led-1 "Kitchen LED 1" (mqtt:broker:sentinel) @ "MQTT2" {
        Type dimmer : k_led_1_Dimmer "Kitchen LED Brightness [%d]" [ stateTopic="wled/k_led_1/g", commandTopic="wled/k_led_1/api", min=0,max=255, formatBeforePublish="&A=%s"  ]


Dimmer  k_led_1_dimmer      "Kitchen Led 1 Brightness [%d %%]"                         (g_k_dimmer)     { channel="mqtt:topic:sentinel:k-led-1:k_led_1_Dimmer" }

Wled announces back the brightness value on /g topic after you sent the command. You can check it with an external mqtt client like mqtt.fx.

Hi everyone,

i got everything working. To make it easier for following openHAB users i forked aditya_Sharma repository and tried to adapt my working configuration files. So far i couldn’t test it in a seperate openHAB installation. I will do this in the next few days. Also i tried to put all information from this thread into the read me from this repository.



1 Like