Ah ok. This web-interface didn’t exist on older Milight bridges.
You need the UDP mode.
Are you going to add it in as a binding and fix that bug
and what is udp mode.
The binding does say ibox 2
First: Please watch your language. Nobody here is paid to “add anything as a binding” or “fix a bug”! Or react instantly on your messages!
Second: This is not a bug! This is your milight bridge configured wrong by yourself! Because the default mode is UDP, or at least was UDP. Not sure about newer firmware versions to be fair.
With “mode” I mean what is called “Protocol” in your screenshot.
See the default values for “protocol” and “port” here:
You do talk about a bug in the binding in one of the post and I will try udp this is the flimware V1.0.08 do I still have to add it in and when I charge it to the other pi it does this UNINITIALIZED - BRIDGE_UNINITIALIZED so I might used the old one into this gets fix
Hey @David_Graeff - Sorry to add confusion to mix, but wanted to point out how my iBox settings are. Granted - I do not recall what all settings I changed when I originally set this up, since I was trying a lot of different things when you were creating the binding. All that being said, I doubt mine are default.
Mine is web version 1.0.14, but “software” 1.0.08 in “Upgrade SW” tab.
Mine has been working flawlessly though thanks to you 
why mine its not I try a lot of thing there maybe a bug software I am try the old bridge can you tell if you can update the flimware
I hope the bug in the auto-discovery failed of new bridge bliding can be fix because the old bridge auto-discovery failed works fine
Again. There is no bug in the auto discovery. It works as expected. The mentioned bug is of a different nature.
Old bridges and ibox bridges work totally different. If you don’t fiddle with the settings and have no UDP firewall enabled, auto discovery works. Please stop mentioning the old bridge as if that magically make it work for this other hardware.
1 Like
Anyway I using this bridge below and it does work with are new mi light bulbs because auto discovery on does not on ibox so I using bridge below
can you update the flimware by download on Ibox and I am useing this bridge because auto discovery does work. 
can anybody address this
hi,
i would but i don’t know how or where exaclty…I’ll try 
strange that nobody else has my same issue
bye
Hello David,
I am using 2 Milight YL5 wifi led controller for led dimming. I want to connect these controllers (over port 8899) to the milight binding in openhab. When I configure as ibox/ibox2 bridge, I get the following status:
Status: OFFLINE - CONFIGURATION_PENDING SESSION_WAIT_FOR_BRIDGE.
Would you please give me an advice for that? The controller can be controlled by the MIlight Cloud App without any problems.
Thanks!
I have reworked the milight binding and fixed many problems with the ibox support. I’m currently in the testing and observing phase but if I had to take I guess I’d say the code will be available for review by end of the week and merged within two weeks.
Cheers,
David
3 Likes
Hey David - Thanks for your continued hard work!
If you need any assistance with testing, I am down to help out.
My milight set up is iBox2 bridge with 3 zones of rgbwwLEDs.
Thanks,
JMac
I have a problem since updating yesterday.
I was running the ‘Testing’ branch and MiLight was working fine. Yesterday I updated my system and MiLight stopped working.
The bridge and zones were appearing as online but when I tried to control a light the log showed port closed error for the bridge.
After trying a few things I removed the bridge and zones from the items using paperui. I then uninstalled and reinstalled the binding. It immediately found my V3 bridge but now zones were detected.
I then switched to the latest snapshot today but have the same results i.e. I have a bridge item showing as online but no zones.
Also the log show the bridge is constantly being updated.
2018-12-04 13:41:47.800 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV3:ACCF233F8E3A’ has been updated.
2018-12-04 13:41:47.895 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:41:57.905 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:41:58.038 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:41:58.164 [vent.ItemStateChangedEvent] - Date changed from 2018-12-04T13:40:58.138+0000 to 2018-12-04T13:41:58.143+0000
2018-12-04 13:42:08.057 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:08.183 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:18.227 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:18.424 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:28.449 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:28.631 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:38.648 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:38.769 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:46.838 [me.event.ThingUpdatedEvent] - Thing 'hue:0106:001788b42696:4' has been updated.
2018-12-04 13:42:48.817 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:48.878 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:52.752 [me.event.ThingUpdatedEvent] - Thing 'hue:0106:001788b42696:9' has been updated.
2018-12-04 13:42:58.215 [vent.ItemStateChangedEvent] - Date changed from 2018-12-04T13:41:58.143+0000 to 2018-12-04T13:42:58.145+0000
2018-12-04 13:42:58.894 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:42:59.053 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:09.071 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:09.283 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:19.322 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:19.502 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:29.520 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:29.645 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:39.662 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
2018-12-04 13:43:39.885 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV3:ACCF233F8E3A' has been updated.
Any ideas?
Read the change log and see the binding no longer adds all possible bulb things.
They now have to be manually added - makes sense.
It seems the binding works for a while and then starts getting socket closed errors. If I restart openhab it starts to work again for a short while.
I’m busy at the moment. I can’t promise anything for the 2.4 release. The V3 code also does not work with multiple V3 bridges. If someone wants to have a look please feel free, the code is well structured and changes are probably only required in one file.
Cheers, David
Are you saying as a result of recent changes the milight binding no longer works with multiple bridges?
I’m currently running 2.2 with two V3 bridges and it works fine. If this is true then it needs to be listed as a breaking change.