Milight

[troy.lynch]

I got a Milight hub and Light to check out. I think I got it all setup properly the groups everything shows up on the isy side and logs are showing it sending out to the hub by the looks of it but the light doesnt do anything? I tried tcp-server and udp on the hub look like it needs to be udp? I kinda recall someone saying that the hub 3.0 has issues am I correct on this?

[io_guy]

UDP.

 

Mines a hub 5.0, not sure what to tell you since unfortunately UDP gives very little ability to troubleshoot and the Hub does not return any information.

[troy.lynch]

I did a packet capture and not seeing anything going to the milight hub. :/  I've got the Ecobee working fine which is what is strange.

[larryllix]

I did a packet capture and not seeing anything going to the milight hub. :/  I've got the Ecobee working fine which is what is strange.

Can you capture UDP packets?

[io_guy]

Power outage woke me with wonky house actions, couldn't sleep, bored, did some router packet analysis...

 

FYI, for anyone using a MiLight wireless bridge and is paranoid, they phone home.  Pretty basic/harmless but anyways.  Found a Reddit article that describes it all as well.

https://www.reddit.com/r/homeautomation/comments/5ya5ev/no_surprise_milight_wifi_bridge_v4_calls_home/

 

I blocked all outgoing from the MiLight on my firewall, unit still functions normally.

[larryllix]

MiLight does have a local and a remote mode where they attempt to con the installer into thinking remore access is necessary (may just be bad Chinlish).  I may have turned on remote access for a few of my bulbs in the beginning.

 

I am not sure if this would be the swtch for this, but it is good to know it is probably harmless anyway.

 

I now have a hub that is starting to crash and needs to be power cycled every few days. Luckily I have a spare hub.

[automationgeek]

Does it support the V6 hub ?I brought a few lights and can't seem to get them to work in NodeLink.

 

Here a sample of the UDP traffic send to the light bulb using http://www.limitlessled.com/apps/

Start Wifi Bridge Session...
Send UDP commands to 172.16.50.26 port 5987
Sent: 20 00 00 00 16 02 62 3A D5 ED A3 01 AE 08 2D 46 61 41 A7 F6 DC AF D3 E6 00 00 1E
listenEndPoint udp datagram received length is 22
Received: 28 00 00 00 11 00 02 F0 FE 6B 72 BC A0 54 07 7A 08 00 01 DA 01 00
LimitlessLEDWifiBridgeSessionID1 is DA (receivedBytes[19])
LimitlessLEDWifiBridgeSessionID2 is 01 (receivedBytes[20])
The incoming UDP Packet received was from listenEndPoint.Address IP 172.16.50.26 (send-to IP could have been a broadcast IP .255, so we don't know how many bridges might respond)
MAC Address is F0:FE:6B:72:BC:A0 ( (receivedBytes[7]..receivedBytes[12])
Send Packet in this format [ 80 00 00 00 11(length in hex) (17 01)(WB1WB2) 00 SN 00 (31 00 00 08 04 01 00 00 00)(v6CommandString) 01(zone) 00 3F(chksum) ]
v6CommandString for this button is: 31 00 00 08 04 02 00 00 00
Length is: 17 cmd[4] = cmd.Length - 5; set packet length (excluding 5 packet header bytes)
WB1 is: 218 cmd[5] = (byteWifiBridgeSessionID1)
WB2 is: 1 cmd[6] = (byteWifiBridgeSessionID2)
Sequence Number is 0D cmd[8] = SequenceNumber
Checksum is 3F For i = 10 To 20 {intChecksum += cmd[i]} byteChecksum = CByte(intChecksum & 0xFF); cmd[21] = byteChecksum; 
Sent: 80 00 00 00 11 DA 01 00 0D 00 31 00 00 08 04 02 00 00 00 00 00 3F
Command SUCCESSFUL.
Received: 88 00 00 00 03 00 0D 00
Command completed.

[io_guy]

http://www.limitlessled.com/dev/

 

Nope, was built for bridge V4.  V6 is totally different.

[automationgeek]

http://www.limitlessled.com/dev/

 

Nope, was built for bridge V4.  V6 is totally different.

Nooo Any plan to support V6 ?

[io_guy]

Not really. These things are a pain to get working properly so I'd really need one in my hands (and have no need to buy another).

[larryllix]

Nooo Any plan to support V6 ?

Do you have a link for purchase of one of these units?

I have two v4? units and they only support 4 groups each. Since I boundary on 5 or more groups and my current single hub is starting to disconnect from NodeLink, it may be nice to have a new unit that can handle more groups of lighting units.

 

 

BTW: I purchased five YeeLight bulbs. They suck. The colours are terrible. Red is loud and bright. Blue is almost non-existent like the Hue, Green is only lime-ish. White is very good with good luminence and changeable for K temps. They really remind me of Hue bulbs in characteristics.

They will become gifts for the non-HA family using on Alexa devices as they respond to

• Alexa. Turn On XXX to Red, Green, Blue,

[automationgeek]

 

Do you have a link for purchase of one of these units?

I have two v4? units and they only support 4 groups each. Since I boundary on 5 or more groups and my current single hub is starting to disconnect from NodeLink, it may be nice to have a new unit that can handle more groups of lighting units.

 

 

BTW: I purchased five YeeLight bulbs. They suck. The colours are terrible. Red is loud and bright. Blue is almost non-existent like the Hue, Green is only lime-ish. White is very good with good luminence and changeable for K temps. They really remind me of Hue bulbs in characteristics.

They will become gifts for the non-HA family using on Alexa devices as they respond to

• Alexa. Turn On XXX to Red, Green, Blue,

 

 

This is the box I bought on Amazon. I'm using it to control my MR16 is actually not bad, but now I need to find a way to control them using ISY. 

[larryllix]

This is the box I bought on Amazon. I'm using it to control my MR16 is actually not bad, but now I need to find a way to control them using ISY. 

Thanks. I see no mention of how many groups this box will handle.

 

I would just install NodeLink and try it with that hub. I doubt the protocol has changed at all except maybe to add some new effect to the list of fun-to-try-but-useless-5-minutes-later, effects.

 

If not feasible at this time,  I have python code that can be triggers from ISY's NRs through a RPi1 python3 compiler, or you can send them directly using NRs inside ISY.

 

Here is the API support site. With a quick glance I see no code changes are needed so NodeLink is your easy go-to. Note the name of the website is another brand name for the product.

 

http://www.limitlessled.com/dev/

[automationgeek]

Thanks. I see no mention of how many groups this box will handle.

 

I would just install NodeLink and try it with that hub. I doubt the protocol has changed at all except maybe to add some new effect to the list of fun-to-try-but-useless-5-minutes-later, effects.

 

If not feasible at this time,  I have python code that can be triggers from ISY's NRs through a RPi1 python3 compiler, or you can send them directly using NRs inside ISY.

 

Here is the API support site. With a quick glance I see no code changes are needed so NodeLink is your easy go-to. Note the name of the website is another brand name for the product.

 

http://www.limitlessled.com/dev/

I did try NodeLink it and it was a no go, like io_guy mentioned it was build for v4. they were a big change between v5 & v6 and broke the legacy code.

 

Mine can handle 4 group.

[automationgeek]

For those coming in this thead later on, I came up with a workaround using the HomeAssistant and have those lights exposed to ISY using the Network Module. 

 

If you ever change you mind, I would not mind pitching in to get that feature added to NodeLink. By the way the program is amazing and so easy to use.