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.
I deleted the old milight bindings, then first installed the new alpha, ran some tests, then the second.
On both, I got the device discovery fine. It found the iBox fine. Tried to send commands using both alphas (with no result to iBox) and this is the result on the openhab log. I have copy and pasted some relevant info. Seems to be throwing quite a few errors, not sure if it has something to do with my install, or if it is the Alpha.
Any ways, let me know if there is any thing else I can do to help. As you saw, I tried to decrypt the wireless signals the other day, but did not get very far. Could not fully break through the 802.11 encryption to decode the signals.
I did play around with PacketSender though, based on the limitless dev page. I was getting some responses from the iBox, but couldn’t get the commands to work on it. second-alpha.txt.pdf (7.3 KB) first-alpha.txt.pdf (7.1 KB)
If you set the message level of OH2 to debug, there might be a lot more information about what is going on. Most of the addon messages are printed with the debug level only actually.
Sorry for the delay… Was struggling to set the Debug level, but I finally got it. Could not get karaf started based on the instructions. Finally figured it out because I was using SSH into my Pi from my main Mac. Turns out it has to be local.
Now that we have that out of the way, here is the latest. Tried to send on/off command to iBox. Here is the result.