I just did the same - new protocol (bidirectional, command sequencing, checksum, discovery…). Didn’t find any binding and am wondering if this is planned. At the time being, I’d prefer openhab 1.xx.
I ordered the V5 bridge which is the “newest, most reliable” having the old protocol the binding was written for. However seeing that V6 is out and V7 is announced this is becoming relevant for openhab. I also do not think that going over the “amazon cloud server” they mention between the lines should be the way forward as LAN communication is superior.
@hmerk => anything in your plans? what’s your view on this. I’d be willing to test it.
Did I understand correctly: you don’t want to continue the development of the milight for openhab 1.xx and 2.xx because you decommissioned your milights? Or just not for openhab 1.xx?
Threre might be further development for the 2.xx version of the binding, but that version was ported by @David_Graff, so it is not my decision.
On the other hand, while developing other stuff, I realised that it is difficult to test if you don’t own the according hardware.
As I am no longer using the MiLights, I am not going to buy the new bridge just for developing.
any news on this topic? I am using 4 old bridges with openhab and would like to replace them with the new annouced v7 that should support more than 4 zones.
I am new to OpenHAB and recently purchased the iBox and RGBW bulbs hoping to use that with it. Did not realize that the iBox was not supported with the current bindings. Had I realized that and found this thread before ordering, would have gotten the older style.
@David_Graff - If you are thinking about updating the binding to include the iBox, I would absolutely help in testing. I am new to OpenHAB, but would say I am fairly tech savvy in general.
the addon will definitely be updated. But at the moment I’m travelling Oceania and have no reliable internet connection nor any milights with me. Contributions to the addon are more than welcome, I might add some boilerplate code in the next days if time and wifi permits.
I was trying to use WireShark to intercept the commands between my iPhone (using the app) and the ibox, but unfortunately, couldn’t get the wireless signals properly decrypted. My wireshark skills are rather rusty.
Based on the iBox’s internal web server page, it is still looking for port 8899. However, if you look at the dev page from limitlessled, they are calling for UDP 5987.
I am out of my depth here. If you give me some direction to help you, I can research and figure it out. Or I can also easily just help test when you are ready.
Moral of the story - We all appreciate your work David! Take your time and thank you again!
I recently put Milight downlights throughout the house (colour temp adjustable white) and some RGBW lights outside. I’ve paired each individual light to a separate channel (15 bridges required all up!).
Looking forward to seeing this binding updated to support the iBox so I can make some use of them!
The example app from milight as you can find under the link of JMacIV isn’t working with this controller. The app can discover the ibox a readout the wifi-data (ssid, bridge-ssid, router make, etc.) but isn’t able to control any light - but this is working via the milight v3 app under android. Strange.
If it is helpful, I can upload some Wireshark captured data, looking like:
Could you post the log messages especially the “Sent packet … to bridge…” messages? I do not have an iBox at hand and therefore can not test with real hardware unfortunately.
Not looking good. I could delete then discover the device again. All devices come online. The following things are created:
Milight iBox Bridge
All Color
Color (iBox)
Color (Zone 1)
to Zone 4
But:
Callback errors.
Command not confirmed error
No additional functions appear to be working.
I’m just doing a full reboot with a new log file. I’ll then post the old and fresh log files.