How to control Mi-Light LED strips with ISY

[Ryan S]

I'm looking for some assistance to get my ISY to turn On and Off my Mi-Light LED strips.

I currently use the RF remote and also have the Mi-Light Wifi iBox Controller (Model: iBox 2) to turn them on and off with my phone.

I have searched the forum and see posts from people who have been able to do this but, unfortunately I am not a programmer and most of the jargon goes over my head.

I don't need to send commands to change the colours, just basic On / OFF will do to get started.

If someone who has figured this out can take a screen shot of what they all typed in the Networking tab or walk me through it would be much appreciated!

Thanks,

Ryan

[markv58]

There is a NodeServer that can do that and more if you are v5 on the ISY. It requires setting up a Polyglot on Raspberry Pi.

Fairly easy to do.

[larryllix]

Welcome to the forums!!!

If you have the Network Resources module this turns one group of bulbs on. I am not sure which one as each controller controls up to four groups of bulbs.

I haven't used NRs for a long time (the NRs are all removed)  and now have all my MiLight bulbs and strips in a box unused.

All MiLight commands are three byte codes and you would install a NR for each group of bulbs x an On/Off/ and Set NR.

 

[Ryan S]

Thanks for posting that screen shot.  I copied what you had and replaced the Host with the IP address of my wifi controller but when I try to test it, the Resource Response returns N/A and no lights turn on.  Any other suggestions?

 

 

[larryllix]

The controllers do not send any response and udp protocol doesn't include a response anyway, so N/A is the expected response.

IIRC the bulbs have to be addressed by turning them on first. Then levels can be assigned next. If your bulbs were dimmed to 0 before turning them off they will return to 0 when turned on again.
After turning them on you need to wait 100+ mSec before sending the next command. Since ISY cannot support 100 mSec, Wait 1 second must be used between each NR sent.
Each NR command contains three bytes. A command byte,  0,  sync byte 
The command bytes are composed of a command code + 2 * bulb number(1-4)
Note: The 0x numbers below are hexadecimal and must be converted to decimal for the ISY NRs.

# MiLight UDP command codes
cmd_on = 0x45
cmd_off = 0x46
cmd_alloff = 0x41
cmd_allon = 0x42
cmd_dim = 0x4E
cmd_hue = 0x40
cmd_allwhite = 0xC2
cmd_white = 0xC5
cmd_effect = 0x4D
sync_byte = 0x55

So to turn on bulb 1 you would use a NR substituting
0x45 or 69 + 2*1 = 71
0x00 = 0
0x55 = 85

The screenshot above, should have been for bulb 2 On (0x45 or 69 + 2*2)
If you don't have a group 2 then the code sent would not affect anything

 

[larryllix]

I found this old thread that may help more.

 

[Ryan S]

So I have been trying to get this two work for the past two days with every command code possible and still no luck.  I only have 1 controller with 3 groups so something I tried should have worked by now.  I double checked the bridge's settings and it all looks good (please note I reset the controller from my original post and it was assigned a new IP address from 123 to 101).

Is there different program I can try to send UDP codes with to see if I can get it to work, or if you have any other troubleshooting suggestions would be much appreciated.

 

[larryllix]

I have to wonder if they changed the port number on the newer hubs. The port number was changed once before early in their development.

Try finding a packet sniffer and monitor some packets from the app. The sniffer must run on the same cpu as the app as switches don't pass packets to uninvolved devices.

Sent using Tapatalk