I am sorry to ask the question, my EISY has been running pretty flawlessly for years and I simply cannot remember where I saw this: "Somewhere" I remember seeing that EISY "must" use a specific IP address or use an IP address that is greater than ??? I remember when I first bought my eisy years ago I had to fiddle with the router and change the DHCP range so that EISY could use the address that it needed. I remember something about that it was at a static address so people wouldn't mess with it and cause a ton of support tickets for UD when they screw it up. I cannot remember where I saw this! I can find the eisy on the network, with IoX, eisy works - everything is good - nothing is wrong with the eisy. I do not want to change the IP address but I thought it was like a static address of like X.X.X.150. I just remember a screen where it showed that either the eisy IP address had to be X or had to be greater than X but for the life of me I cannot remember where I saw that. I don't think it I saw this via ssh (I do not believe that I have ssh enabled). I do not have an hdmi monitor connected (nor USB keyboard or mouse) to my eisy. I have a new fiber modem and I want to find that setting that I saw years ago so I can set the static IP range and DHCP range appropriately on this new modem. Do I need to plug the eisy into my TV? I do not remember ever attaching the eisy to my tv to view anything. Thank you.

Just to clarify, according to my router the eisy is at 192.168.1.41. I'm not asking what address my eisy has, I'm asking what range does it need to reserve it's IP address.

I do not believe that there is a range or a < or >.

The related topic is that you can give the eisy a static IP address, or use DHCP, where your router will assign it. Three points

1. If you use a static IP address for eisy, and you change your internet service/router in the future, there's a good change you'll lose contact with your eisy based on the different subnet choices different router manufacturers use. This is the support headache you mentioned

2. In the early days of node servers, they could run on a separate box and needed the exact (=static) ip address of the ISY. If you're not using older node servers and you are not running them a separate computer (Rasberry Pi, etc)... this problem no longer applies to you and there is no reason to use static up addressing any longer

3. If you want your ISY to have a specific IP address, the DHCP features of most routers allow you to define a specific address for network devices like the eisy

4. The eisy only needs to be on your network, ideally one of your router's switch ports to minimize network hops.

ANSWER: It's best to go into the config tab of iox and make sure your IP address is NOT static and is DHCP and let your network and eisy take care of themselves.

Edited yesterday at 11:32 AM1 day by paulbates

I also never saw anything for eisy requiring a specific IP address.

UD wants you using DHCP to reduce support issues.

16 hours ago, paulbates said:

I do not believe that there is a range or a < or >.

The related topic is that you can give the eisy a static IP address, or use DHCP, where your router will assign it. Three points

1. If you use a static IP address for eisy, and you change your internet service/router in the future, there's a good change you'll lose contact with your eisy based on the different subnet choices different router manufacturers use. This is the support headache you mentioned

2. In the early days of node servers, they could run on a separate box and needed the exact (=static) ip address of the ISY. If you're not using older node servers and you are not running them a separate computer (Rasberry Pi, etc)... this problem no longer applies to you and there is no reason to use static up addressing any longer

3. If you want your ISY to have a specific IP address, the DHCP features of most routers allow you to define a specific address for network devices like the eisy

4. The eisy only needs to be on your network, ideally one of your router's switch ports to minimize network hops.

ANSWER: It's best to go into the config tab of iox and make sure your IP address is NOT static and is DHCP and let your network and eisy take care of themselves.

Ahhh, I think that is what I am remembering! In IoX the "Use DHCP" check-box is greyed out (can't be turned off, at least easily) - and (see below) EISY always gets the first (lowest valid value) DHCP IP address.

And now that I adjusted my fiber router I find that eisy always takes the first IP address in the DHCP range. This happened in the past regardless of the internet provider modem I was using - EISY ALWAYS grabbed the lowest DHCP address. I wonder how EISY does that. I thought DHCP was like: "hey, give me an IP address", "okay, here you go, it's valid for x minutes", "okay, thank you".

I did not realize that this new Optimum router I got, which you can only manage through the optimum.com website, has only 1 setting where you can set "the valid range of IP addresses" - unfortunately, what they should have said was "DHCP range of IP addresses". By default, the range (dhcp range) starts at x.x.x.15. I was having crazy camera problems where a camera would go down and then the washing machine would grab that IP address, and then the camera never works again (and worse). I did not know all of this was happening until today. All of my cameras use static IPs for nvr. So today I changed this config setting to start at x.x.x.151 upward for DHCP. And then I got all of the dishwashers, laundry machines, Feit floodlights, Chamberlain garage door openers, etc to give up their IP addresses and make new DHCP requests and get everything out of what I thought I was using as the static IP range. I finally have full inventory of every network interface MAC address, wifi or wired, static or DHCP. Most importantly, every camera works once again. This wasn't the point of this original post, I was just surprised that my EISY was at a very low IP address...lower than I had ever seen before....which thankfully then led me to discover this "mislabeled IP range". I then started querying all MAC addresses and map them to the corresponding IP address.

I figured out what was going on by, I would get the MAC addresses of one camera and then I found its corresponding MAC address mfg-ui was not for the mfg that I thought was using that IP address - because another device was taking over the IP address of what I thought was a static IP. Finally, I was able to fix every issue with every network device (most problems were for the outside cameras). And now I can watch every bird at all of the feeders and bird houses (I have a large bird environment outside). In summary, EISY led me down the correct path for fixing this camera insanity.

7 hours ago, raymondjiii said:

Ahhh, I think that is what I am remembering! In IoX the "Use DHCP" check-box is greyed out (can't be turned off, at least easily) - and (see below) EISY always gets the first (lowest valid value) DHCP IP address.

And now that I adjusted my fiber router I find that eisy always takes the first IP address in the DHCP range. This happened in the past regardless of the internet provider modem I was using - EISY ALWAYS grabbed the lowest DHCP address. I wonder how EISY does that. I thought DHCP was like: "hey, give me an IP address", "okay, here you go, it's valid for x minutes", "okay, thank you".

I did not realize that this new Optimum router I got, which you can only manage through the optimum.com website, has only 1 setting where you can set "the valid range of IP addresses" - unfortunately, what they should have said was "DHCP range of IP addresses". By default, the range (dhcp range) starts at x.x.x.15. I was having crazy camera problems where a camera would go down and then the washing machine would grab that IP address, and then the camera never works again (and worse). I did not know all of this was happening until today. All of my cameras use static IPs for nvr. So today I changed this config setting to start at x.x.x.151 upward for DHCP. And then I got all of the dishwashers, laundry machines, Feit floodlights, Chamberlain garage door openers, etc to give up their IP addresses and make new DHCP requests and get everything out of what I thought I was using as the static IP range. I finally have full inventory of every network interface MAC address, wifi or wired, static or DHCP. Most importantly, every camera works once again. This wasn't the point of this original post, I was just surprised that my EISY was at a very low IP address...lower than I had ever seen before....which thankfully then led me to discover this "mislabeled IP range". I then started querying all MAC addresses and map them to the corresponding IP address.

I figured out what was going on by, I would get the MAC addresses of one camera and then I found its corresponding MAC address mfg-ui was not for the mfg that I thought was using that IP address - because another device was taking over the IP address of what I thought was a static IP. Finally, I was able to fix every issue with every network device (most problems were for the outside cameras). And now I can watch every bird at all of the feeders and bird houses (I have a large bird environment outside). In summary, EISY led me down the correct path for fixing this camera insanity.

Most routers allow you to "reserve" an IP within the DHCP range for a specific MAC. That way it cannot get reused. It seems like more and more devices don't allow the setting of a fixed IP (newer Foscam cameras for instance). But by adding it to the reserved list (once it has grabbed an IP), you can be guaranteed it won't get usurped by another device. IP reservation is usually somewhere deep in your advanced settings.