This afternoon we started up the 2016 matrix celebration on the MacBook (which was used perfectly for 8 hours last night) and nothing... I mean nothing.
Not even the "test"runs. Absolutely nothing changed... Unicast is the same, even tried last nights nutcracker show and nothing. Then I hooked the setup to my Mac Mini and nothing (which ran before).
I then hooked up the old Windows Dell and everything is fine.... what in the world could have happened...sounds like a software issue.
Any one have any ideas or suggestions. Thanks
Couple of things to check:-
Check default gateway setting are that of your Router.
If you are Fixing IP addresses, make sure they are not in the range of the DHCP Pool.
You will find the DHCP Pool range in the router.
So if the pool starts at 192.168.1.200 for 50 address. Do not put anything fixed in 192.168.1.200 to 192.168.1.250
Allocate IPs from 192.168.1.20 etc, make sure you dont use address more than once.
I'm new to using the lighting controllers, so I'm reading this thread to get up-to-speed on assigning and using IP addresses. Thanks very much for the information that folks have posted. My Cisco Lynksys router's DHCP pool happens to be 192.168.1.100 to 192.168.1.149.
m1anh, regardless of my router's particular DHCP pool of addresses, I thought that when a router dynamically assigns a connected device an IP address from the pool, it will not assign an IP address that is already being used. I'm guessing it's a best practice to stay away from using any DHCP pool addresses for a controller, but if I don't pay attention (that's easy) and assign a DHCP pool address to a controller, will that cause an issue?
This question exposes my complete ignorance of this subject.
I'm new to using the lighting controllers, so I'm reading this thread to get up-to-speed on assigning and using IP addresses. Thanks very much for the information that folks have posted. My Cisco Lynksys router's DHCP pool happens to be 192.168.1.100 to 192.168.1.149.
m1anh, regardless of my router's particular DHCP pool of addresses, I thought that when a router dynamically assigns a connected device an IP address from the pool, it will not assign an IP address that is already being used. I'm guessing it's a best practice to stay away from using any DHCP pool addresses for a controller, but if I don't pay attention (that's easy) and assign a DHCP pool address to a controller, will that cause an issue?
This question exposes my complete ignorance of this subject.
I would not recommend using DHCP for your controllers if you are using Unicast since you could end up with different IPs based on your lease time. With multicast it's not as important - - but of course you would still need to know the IP to access the interface anyway so even there I would probably stay away from it. Of course you could set static IPs within your IP pool so that a controller gets the same IP every time - but of course that's just as much effort (actually more) than setting the static IP on the controller to begin with.
If you are putting your controller on the same network, I would set it to be outside of your pool range.
