Configuring the MiLight/LimitlessLED/EasyBulb wireless bridge

MiLight Bulb E27 We have seen in a previous article how nice it is to control the lights in your home using the Raspberry Pi and MiLight/LimitlessLED/EasyBulb Wi-Fi enabled LED bulbs. We have also seen how you can do some automation, like replacing your alarm clock with automatically turning on the light bulbs, to wake up more gently. But there is one important device that needs to be set up correctly for these things to work well. As we know, the MiLight/LimitlessLED/EasyBulb wireless LED bulbs do not actually contain a Wi-Fi receiver. They respond to radio signals (over 2.4 GHz) which are sent to them either by a simple remote control or by the MiLight wireless bridge. So to enable controlling them over Wi-Fi, the data must go through the wireless bridge.

There are two possible problems with the MiLight wireless bridge in its default configuration, as it comes out of production:

1. It uses a dynamic IP address inside the LAN.

2. In some systems the wireless bridge is trying to communicate with the outside world, which causes the lights to automatically turn off again and again.

 

Assigning a static (fixed) IP address to the MiLight/LimitlessLED/EasyBulb wireless bridge

MiLight Wireless Bridge With Static IP

By default the wireless bridge uses a dynamic IP address allocated to it by your wireless router. This is not a problem per se, it is actually a great thing, as long as you are controlling the bridge with your phone, which automatically finds the device, because you don’t have to go through the hassle of configuring it. But if you happen to be an advanced user and wish to send commands to the MiLight wireless bridge from a computer, like the Raspberry Pi, then you have to address it with its IP address. And if that IP address is allocated dynamically, meaning that it might change every time the router or the bridge itself reboots, this becomes a problem.

So we need to allocate a static (fixed) IP address to the bridge. If you have a router which allows you to map devices (MAC addresses) to IP addresses, then you can simply go into the router’s configuration page (usually you can do this by accessing 192.168.1.1 from a web browser), find the section which allows these mappings to be defined, find the MiLight bridge in the list of devices connected to the router (using its name) and assign it the IP address of your choice.

Unfortunately some routers don’t allow mapping devices to fixed (static) IP addresses. Not all hope is lost in this case, because the devices can request a fixed IP address for themselves. The MiLight wireless bridge V3 (black label) can do this too:

1. Access the wireless bridge’s configuration page. First you have to find its current IP address by looking at the list of devices connected to the router. After that you can access the config page by going to MiLight_IP/home.html in you web browser. For example if you see the MiLight bridge in your router’s device table with IP address 192.168.1.2, then go to 192.168.1.2/home.html in your browser.

2. If the config page is in Chinese, you should see a small button labeled “EN” in the top right corner, with which you can switch to English.

3. Go to the “STA Interface Setting” section.

4. Change the “WAN Connection Type” to “static (fixed IP)“.

5. Fill the 3 fields that appear:

5.a. IP address: the desired fixed (static) IP address (for example 192.168.1.2).

5.b. Subnet mask: a suitable subnet mask, for example 255.255.255.0

5.c. Default Gateway: the IP address of your default gateway.

6. Click “Apply“.

7. Power off (unplug) the MiLight wireless bridge and wait a few seconds.

8. Power on (plug back in) the wireless bridge. after a few seconds the “Link” LED should light up and everything should work fine. The bridge will now always have the static IP address that you have assigned to it.

MiLightStaticIPAndConf

Finally, if your router does not allow assigning a static IP address to the MiLight bridge and you have a V4 bridge (not V3), then you plain out of luck, because the feature of being able to configure a fixed IP address has been disabled in the new version of the bridge (V4 – green label). In this case you cannot use the bridge with a fixed IP address.

 

Preventing the wireless bridge from communicating with the outside world and turning the lights off automatically

MiLight/LimitlessLED/EasyBulb Wireless Bridge

It seems that the MiLight wireless bridge is sometimes attempting to communicate with the outside world (send/receive data from outside the LAN). In some systems this has the unwanted side effect of automatically turning off some MiLight bulbs after a few seconds or minutes after they have been turned on. And this happens again and again, as the bridge is trying to communicate with the outside world (by the way, it’s a good question why it tries to do this and what it’s sending/receiving…). This means that we need to prevent the MiLight wireless bridge from being able to communicate with devices outside the LAN.

If your router allows it, the simple solution is to block the wireless bridge in the router’s firewall section from accessing addresses outside the LAN. If the router does not have this feature, but you have a V3 MiLight bridge, you can still do this by taking away from the bridge the knowledge of where the gate to the outside world is. In other world, giving it a default gateway address which either does not exist or points back into the LAN. Follow the steps from above, configure the bridge to use a static IP address and in the Default Gateway field (5.c.) simply type 127.0.0.1 or some not used IP address in the LAN.

Again, if your router cannot block the MiLight bridge from going outside the LAN and you have a new bridge (V4, not V3), then you’re out of luck, because the new bridge (V4 – green label) does not allow this configuration to be made.

I personally sincerely hope that in the next versions of the MiLight/LimitlessLED/EasyBulb wireless bridge the feature of configuring the bridge from the web browser will be re-introduced and it will allow again to be configured with a static IP address. I don’t really understand why they have removed this feature in the first place… Well, anyway, if your wireless bridge can be configured using one of the above methods, then you can easily control it from a computer (like the Raspberry Pi) and enjoy automating the lights in your home. Have fun!

 


Comments

Configuring the MiLight/LimitlessLED/EasyBulb wireless bridge — 23 Comments

  1. As for a fade-in-light-clock: How do you avoid the bulbs from starting at the memory brightness? If I switch off at max and start the fading process then the light turns on and fades down to fade up again. Thats annoying 🙁

    • Hi Tom! I don’t think you can avoid this. It bothers me too a little bit. This is something that the manufacturers should fix. I don’t know if they know about it… try letting them know.

      • Seems not to work for me…
        That keeps me from configuring my milight device… What can I do now? I tried user together with admin, user together with password, admin together with password… It’s just not working and really annoying…

        Anybody having the same struggles or a solution?

  2. Hi! Great guide. On my way to set up some automated controls for my milight, but I can’t find the IP adress of it. It doesn’t seem to be the default. The wierd thing aswell is that I can connect it to my wifi and control the lights from my phone using the app(connected to my home network), but it’s not listed as a connected device. Unplugging it doesn’t lower the amount of connected devices either…

    Any clues on what might be the problem? Any other way to set a fixed IP adress? It’s black labeled but I can’t see what version it is.

    • You need to set up the milight bridge correctly before anything else. You can do this using your phone by connecting to the special WiFi network created by the milight bridge. Follow the instructions on the milight website. I can only help you if you describe in more detail step by step what you are doing.

      • I did everything that it asked me to. Connected to the milight wifi, went into the app, connected the controller to my home network, shut it, connected to my network and was able to control the lights(as I said). So everything works great and it’s connected to my wifi. But when I log into my router and check the connected devices, the milight controller is not one of them. Tried to turn the controller off and then see if there was the same amount of devices connected, and it was. Connected it again and works like a charm, but still not shown in my device”tree”. Asked the seller, who then asked the factory and responded that it has no IP. But that sounds wierd to me…

        Greatful for response, will try with another router in a few days.

        • I don’t see how it could work without an IP. that sounds like bullshit to me. Can you try using a different router and see if that one shows the milight bridge? Also, there is some kind of config page for the milight bridge where you can see its mac adress and you can use that to assign a fixed IP to it from inside your router. I don’t remember exactly how to access that milight bridge config page and I think it depends on the version of the bridge too. Check this article for some details about how you may try to access that config page: http://iqjar.com/jar/configuring-the-milightlimitlessledeasybulb-wireless-bridge/

          • Same here.
            I will, hopefully this weekend.
            The only way I know to reach the bridges config page is to know the IP of it. There might be a way to do it without already knowing it. Will research.

          • Tried with the new router! Now nothing works, after pairing it with my home network it never gets online. Tried with multiple apps, change the security settings and pretty much everything I and the internet can come up with.
            But found one app that, if able to connect, will show you the IP(new LimitlessLED app). And found the config page, easiest found when in AP mode aka before you connect it to you home network. Through there you can pair it aswell, that in my case leads to the result that it says that I’m connected and even tells me the signal strength. But it doesn’t assign an IP adress. Disabling that and setting one manually may work, but it still stays offline according to the app.

            Live in an appartment with a shared network where my router works like an AP, starting to think that it has something to do with the “base” network.

  3. Petter, try taking the Milight bridge to a friend’s house who has a normal router and try it there. Be sure to reset the bridge to make sure it looses all previous settings. It has a little hole somewhere, insert a pin and press it for 10 sec.

    • I’ve reset it about a hundred times I think 😛
      but tried at a friends house, works but still no asigned IP.
      Will ask the seller for a newer one and probly buy a rf transmitter instead. Send the same commands as the remote does. (https://www.raspberrypi.org/magpi/pi-mi-light/)

      Maybe try to find the files needed to upgrade the software of the bridge.

      Thanks a lot for your help so far, will come back if I find a solution

  4. Hi guys have been using ha bridge software as far as I no the bridge IP is always 192.168.1.3 port 8898 think that’s the port ..that works with limitless led every time its also the IP I use with ha bridge but for resone I could not get Alexa to find the ha bridge because the unpn web server IP was also set to 192.168.1.3 ..but just by chance ha bridge shut down and would not work .so reinstalled java nothing downloaded ha bridge started it clean from a batch file on port 8081 .as soon as it came up the unpn web server was now 198.168.1.14 and Alexa found it no problem .but the hex codes to controls lights are still on 198.168.1.3 but all working great now just need to have it on a raspberry pie or cloude server if that would work

    • Hi! I don’t understand your problem. Can you describe in more detail and more clearly? I’m using HA bridge with Alexa and I don’t have any problems, works fine.

Leave a Reply

Your email address will not be published. Required fields are marked *