EspMilightHub new binding for milight limitlessLED and easybulb

You can do that with sitemaps, as mentioned you will need to create an extra item that is a Dimmer and link it to the same color or level channel (not sure which one, they should both work?) and this item can be placed into the sitemap as a Slider. But I am now very rusty on sitemap syntax. Best to follow the docs here…

EspMilightHub - Bindings | openHAB

Also please note that it is best to not spend too much time learning sitemap IMHO. Sitemaps are only for backwards compatibility and I have no idea how much longer they will be in openHAB, so it is best to learn the new UI way/method of doing things.

Now the binding is merged, I’ll probably look at doing some widgets to display the lights in a nice compact format that I like.

If you believe what your seeing is a bug, then please create a github ticket and I’ll take a look when I have some time. I dont know the raw data packets, only the mqtt messages and what the openHAB event bus states is happening is what matters.

Only it does not open for me?

It was not merged until after 3.0x stable was created so just to make it harder to find and to break links you now need to go to

1 Like

Sorry for my dummy request but where do I find a version for openHAB 2.5 of this binding? No way to find it anywhere in the KAR or on GitHub, Feature:intall in Karaf does not find anything neither.
Thank you for your support

I had the github marked private and have changed this for you.

Do not use these versions on openHAB V3.1+ as from that version it is built in and there are breaking changes between the two versions. So make sure you read the at this github instead of the official openHAB doc pages.

Releases · Skinah/EspMilightHub (

Great! Thank you! It will help until I can complete the migration to OH3.

A heads up for all users of the binding and rgb-cct globes that they can now have the white leds triggered from the colour wheel controls if your using 3.2 Milestone 1 and newer. It can be disabled and configured to a threshold value that you prefer. You have to read the NEXT version of the docs to get the information on this which is linked from the release notes.

Release openHAB 3.2.0 Milestone 1 · openhab/openhab-distro (

I use a WL-Box1 (because the iBox2 isn’t available anywhere) to control my led strips with 4 dimmers type Fut036. Is it possible to control my dimmers with this esp bridge? Or is possible to control the WL-Box1 via openhab tuya and mqtt?

A few times a month I have to restart openhab because my ESP milight doesn’t respond anymore. It is not a MQTT issue, because I have other non milight MQTT items which continue to work. If I control the bulbs by the web interface of of the ESP then everything just works fine. I enabled the debug logging for all the MQTT things, but I don’t see any ESP milight in the openhab.log
Do I need to add an additional logging to see the communication between openhab and Mosquitto? I do see the commands sent to other MQTT items.

my current log settings:

Logger level=DEBUG name=org.openhab.binding.mqtt.espmilighthub/
Logger level=DEBUG name=org.openhab.binding.mqtt/
Logger level=DEBUG
Logger level=DEBUG name=org.openhab.binding.mqtt.generic/

I probably did not add the raw data to the logs of the binding as it is very simple to get this. I’ll assume your using Linux and Mosquitto…

Type this into the linux command

mosquitto_sub -u usernamehere -P passwordhere -p 1883 -v -t 'milight/#'

You will then see all traffic in both directions.

I am running both openhab and mosquitto on a windows machine running as a service. I just enabled the Mosquitto logging in the mosquitto.conf file, but it looks like there is no way to capture the topics.
I found a solution to use “mosquitto_sub” to write to a log file.

mosquitto_sub.exe -v -t milight/# -F “%I %t %p” >c:\openhab\userdata\logs\milight.log

Heya, just updated OH3 from OH2 trying to get installed with the latest release: https :// Releases · Skinah/EspMilightHub · GitHub

but getting an error:
10:59:36.143 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.espmilighthub-3.0.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.espmilighthub [258]
Unresolved requirement: Import-Package:; version=“[2.2.0,3.0.0)”

at org.eclipse.osgi.container.Module.start( ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start( ~[org.eclipse.osgi-3.17.200.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle( [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles( [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles( [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess( [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process( [bundleFile:3.7.4]
at [bundleFile:3.7.4]

guessing it has something to do with latest OH3.x update. would love to get this working++

From what I’m reading some apache commons dependencies were removed in 3.3.x

As far as I can see, from what I’ve scoped so far is that this file:

Uses the requirement.

Line 32:


and line 575 uses IOUtils from that package:

String response = IOUtils.toString(httpConnection.getInputStream());

I would imagine this would simply require changing it to use the Java equivalent code to accomplish the same thing without needing to import

I think it’s something like this, but I’m no expert on these things…

String response = new String(inputStream.readAllBytes(), StandardCharsets.UTF_8);

not sure if there is more.

The binding has been merged in V3 and is now part of the mqtt binding. Just install the mqtt binding and follow the documentation. Glad your hep bit it’s already done.

Doh! I guess I’m a little behind on the times. thanks++

Oh, also, I’m running my own MQTT independent of OH on the same Pi as OH, better, to disable it and Use the OH binding instead for these purposes?

** EDIT. ah, I see the binding is not actually a broker. just a client. got it++ never used it

The binding used to be both, but the mqtt built in server was removed as the library used was discontinued and not maintained. Welcome to V3 and please take the time to go through the tutorials that were created to help ease you into the new ways of V3 especially the model.

thanks. it works great+ and yeah, V3 it was time. been slacking on it, been a few bumps in the road but not too bad…

thanks again for your efforts++

If anyone uses Homekit or wishes to have nicer switching to white LEDs with a single colour control, they should check out this PR made by someone else great work, which has a jar you can download and use in the latest post. Since we are getting close to the next STABLE release, it would be great if some people can test the changes out.

[mqtt.espmilight] Automatically convert color values to color temp by ccutrer · Pull Request #13578 · openhab/openhab-addons (