LEDENET Magic UFO?

Hi Rexbeckett,

Thank you very much for your work on the plugins. I’ve done a bit of tinkering with it and built some nice luup code to build myself a nicely multifunctional lamp with it out of a multiswitch, some lua, and some Siri/homekit voice commands.

I recently tried to get into the LED strip stuff, and found that MiLight just doesn’t have a groupable RGBW controller. I bought the FUT028 but quickly found that it couldn’t be grouped in with your plugin or the remote apps, then I inadvertently bought a CW/WW controller that can be grouped. I kept reading on the other RGBW 4-group controller that they have and found that it’s RGB+W, not RGBW, unfortunately, so I looked at some other options.

I found the [url=http://www.amazon.com/LEDENET%C2%AE-Controller-Android-Smartphone-Control/dp/B00MDKOSN0]LEDENET Magic UFO device - http://www.amazon.com/LEDENET®-Controller-Android-Smartphone-Control/dp/B00MDKOSN0[/url], which looks to be a self-contained Wifi-enabled RGBW LED strip controller. Given that the LEDENET/MiLight/Limitless LED stuff all seems to come from the same place, I’m thinking I might give it a chance, and that your plug-in might be the way to go to integrate it into my system…

Have you looked into this device at all? I’m not familiar with the control codes used to access the wifi box that the plugin currently integrates with (nor am I familiar with the code you’ve written for the plug-in), but I wanted to run this info by you.

I found this link: [url=http://www.emessaging.biz/blog/?p=629]http://www.emessaging.biz/blog/?p=629[/url] as well as this zip file of communication protocol documentation, and example python scripts: [url=https://www.dropbox.com/s/o48itl2b8k3kldw/UFO-Information.zip?dl=0]Dropbox - UFO-Information.zip - Simplify your life detailing how to talk to the unit. You know your code - how does the plugin code compare?

Thanks!

@ceefin

I have a couple MagicHouse globes that I was going to write a plugin for but to get the best out of them I think it requires a proxy. This was not something I’m ready to tackle.

Something along the lines of the upnp proxy [url=http://apps.mios.com/plugin.php?id=3716]MiOS Apps by futzle

As I do have the globes if anyone has suggestions on the best way to approach this I may still give it a go.

@zoot1612 - I’m not familiar with the MagicHouse Globe? I’m looking at the Magic UFO RGBW controller.

The documentation for this device says nothing about needing any upnp type proxies, as the unit responds to TCP packets. My hope was that the communications protocols were similar (or hopefully identical) to the MiLight/Easybulb/LimitlessLED commands that Rexbeckett’s plugin uses. I haven’t had time to compare the two directly (yet) but I’ll be working on it eventually as I ordered one of the UFOs today. If anything, I might try to use Rexbeckett’s plugin as a framework if it needs to be adapted.

Just a cursory glance at RexBeckett’s code and the communication protocols for the Magic UFO shows me that these two systems are pretty much different. I guess I’m gonna need to figure out how to write me a plugin … eventually :slight_smile:

@ceefin

The Globes are connected via Wifi and use the same protocol.

Just a mis-understanding wasn’t saying a upnp proxy but a TCP proxy installed the same way that the futzle has installed upnp proxy. The TCP proxy would handle all the connections.

Below is an excerpt from the documentation. I have changed the wording as it didn’t translate well, hopefully I have got it right: -

If all the settings are correct the device should request a connection from the internet server. After the connnection has succeeded server will receive ?ACCF232C147E,HF-LPB100-ZJ011? every 2 minutes. The server should return Bytes:0x00 to keep connection up.

Link to english Magic House API: -
[url=https://raw.githubusercontent.com/zoot1612/plugin_mh/master/MH_API.txt]https://raw.githubusercontent.com/zoot1612/plugin_mh/master/MH_API.txt[/url]

I translated that last night, myself!

I don’t think there needs to be any sort of persistent server sitting anywhere sending keep-alive signals to the LED controller. My understanding of the system is that it just responds to the TCP packets that it’s given. This system though, in a bit of an improvement over the Milight bulbs, seems to offer a status query to get the current state.

There’s a basic API written in Ruby for it here [url=https://github.com/sidoh/ledenet_api]https://github.com/sidoh/ledenet_api[/url] and this code doesn’t reflect any need for any persistent server. I’ll get around to testing this when mine gets here.

What’s your interpretation of the “0xF0 remote,0x0F local” flags in the API doc?

I did some digging this morning and found a bit more information about the Magic Home type stuff.

[url=https://github.com/vikstrous/zengge-lightcontrol]https://github.com/vikstrous/zengge-lightcontrol[/url] describes the API a little more and explains the remote mode I wasn’t sure about earlier. It does mention something about a proxy as you had mentioned before, but more from the perspective of the bulbs/rgbw controller can act as some kind of simple hub/router for some purpose.

I don’t have any need to use the remote functionality of the units, as I intend to control it from Vera (and would rather not have my lightbulbs communicating off to some unknown place, so I’ll likely be firewalling off the host it might try to connect to…)

I also managed to find the source of these kinds of products - [url=http://zengge.en.alibaba.com/]http://zengge.en.alibaba.com/[/url]