Static vs Manual IP for Hubitat via Router vs via Hubitat

🛎️ Get Help
1

Hi
I have a C-7 running the newest firmware 2.3.9.196. The router is an Asus router.
The recommendation is to assign an IP address to Hubitat, and several device integrations come with a recommendation to assign an IP address to those (Samsung, Denon AVR, etc.).

Please help me understand the difference among the following, and why I would want to do one over the other.

a. On the router, under Network Map, LIst devices, my Hubitat Client IP address shows as "Manual." If I hover on the word "Manual" it says "Mac and IP address binding." My Hubitat got that designation because when I first got it and learned I should assign an IP, I googled that, found this page:
https://www.asus.com/support/faq/1000906/
and followed the directions for method 2, specifically: In the router, go to Advanced/LAN/DHCP Server/Manually Assigned IP around the DHCP list, and select a device to put on the list.

b. Again, on the router, under Network Map, LIst devices, my Denon AVR Client IP address shows as "Static." If I hover on the word "Static" it says "Static IP." The Denon, and all the the devices with the word "Static" above are NOT listed in the router Advanced/LAN/DHCP Server/Manually Assigned IP around the DHCP list" so there must be another method through which they got a static IP. Does this info come from the device itself via some autoconfiguration on the device?

c. On my Hubitat, under settings, Network Setup. there is the option to "Switch to static IP" On this screen, there is no IP address in the field for IP address.

So, noting that I have absolutely no understanding of this stuff and am just blindly following directions (although trying to learn):
1. Should I assign a Static IP to the Hubitat via the method in c above?
2. If yes, should it be the same IP that is manually assigned on the router?
3. On my router, what is the IP assignment difference between Hubitat connected devices that show the Client IP address as "Manual" vs those that show the IP address as "Static?" Is one preferable to the other?

Note: I have googled this, but the only marginally meaningful link I found contains a discussion that is WAY beyond my understanding.

2

Ok. So you want to use a DHCP reservation to assign the ip to Hubitat and any other IOT devices Hubitat deals with. This is done by assigning an ip to the mac in your router.

A static ip is set directly on the device itself.

2 Likes
3

Static implies you set in an IP address on the device itself. A reservation is when you use the DHCP service to bind a particular mac address to an IP address. The recommended method is to use the DHCP server reservation method. Its is the easiest to implement and manage. You are correct with the Asus router visit the LAN, Then DHCP, then see that enable manual assignment is on then find your device in the drop down list. Once it is added every time the ip address lease is renewed, the same mac address will be reassigned the same ip address. As far as the individual clients are concerned, they won't know they have a reservation as it is all the same DHCP to them. Asus will list them as Manual. If it is listed as static, it is saying it has detected an active IP address it has no influence over. So it is being helpful by stepping around that address and letting you know.

4

This works great for me to keep track of things.

5

Is that different than static or manual IP?

Ok, that seems like what I did with what on the Asus is called "Manual." If I hover on that word, I get a pop up stating "Mac and IP address binding"

Thank you. So is this correct?:
a. if a device, either automatically or via user interface on the device, has the IP set on the device, it is called "Static IP"
b. if a router owner, in the router settings, sets a specific device to have a specific IP, it is called "Manual IP" , or maybe also referred to (per @croweflight 's post) as "Reservation"?

I think this is saying Manual = Reservation and the way I have Hubitat set up with Manual is correct...?

PS: Thank you for helping me understand this better.

6

I use Advanced IP Scanner (free) to keep track of IP and MAC for my network.

7

@Ranchitat Not sure I need a google sheets like that.
My router lists every device with it's Mac Address and IP address...
Maybe not all routers do that...

8

Can you please share what info that gives you that is not already available on the router?

9

For me, it lists MOST of the names of the devices and the manufacturer. My router page does not show some of this. I don't know where Advanced IP Scanner gets that information. I wish I could edit "something, somewhere" to complete a list like this...

2024-10-25_15-59-33
2024-10-25_15-59-331430×383 12.9 KB

10

Ah. My Asus router provides that in Network Map/View List. It includes the Name, IP, the type of IP (thus this post), MAC address, if the device is connected to the Internet, how long the device has been continually connected to the router, what type of connection to the router (ethernet, wifi and if wifi if it is 2.4 or 5), the connection speed and some other info.

The info in the "Name" section is usually from whatever the user has named the device, and if not named, it usually has the mfg within a cryptic name in the Name column. There are a few devices that initially had absolutely NO info in the Name column other than a repeat of the MAC address, but I can figure out quickly what they are by locking them out of the network and waiting for a complaint from a household member...

1 Like
11

A static IP is one assigned on the device, DHCP has nothing to do with it, but you should make sure that it's outside the range from which DHCP assigns addresses.

"Reservation" is commonly used to refer to what's technically called a DHCP manual assignment. The address is from the DHCP server, but via manual configuration which tells it to associate a specific IP address with a MAC address.

12

Static is set by the device.
Reservation is set by your DHCP server.

If possible, you'd want to use a reservation. Setting static IPs can lead to IP conflicts, and are a pain if/when you update your router or your network scope. (think of if you change ISP, you can go from 192.168.0.X to 192.168.1.X. If you set a static on your hub, you'll now have to finagle your way into the hub to update the IP to the new subnet)

Setting the reservation let's the DHCP server know not to hand out that IP address, even if the device is off

13

A loose definition...

Let's say I'm the device, or as my wife says "You are such a tool." :wink:

Static IP:

  • I decide where I'm going to sit

DHCP Reservation:

  • My wife tells me where I'm allowed to sit

:wink:

6 Likes
14

I first used it when switching from Netgear to Unifi, but have found it to be very convenient since when adding/deleting/swapping IoT devices.
And it's easy to add notes.

15

I disagree. The problem with manual assignments is that the DHCP server must be functioning for them to work. That creates a single point of failure for the entire network. Conflict would only occur if you're doing it wrong, and manual assignments also have to be updated when devices get changed.

think of if you change ISP, you can go from 192.168.0.X to 192.168.1.X. If you set a static on your hub, you'll now have to finagle your way into the hub to update the IP to the new subnet

If you're letting your ISP control your inside networking, you're really doing it wrong. And either of those networks are terrible choices because they're the default networks for so many devices. If you change ISP, no change is needed if you have your own router, and if you're replacing one, you just reconfigure it to match your network. You also have to configure it with all your manual assignments, if your DHCP server is bundled into the router. Static IPs require no action.

1 Like
16

yes

2 Likes
17

If one has a Local Area Network (LAN), unless there is a DHCP service, the only other choice to use IP addresses is to configure each host on the LAN with a static IP. And the mask (which defines the number of hosts available plus the network and broadcast addresses) and the gateway address. This contingency is why devices have the ability to configure an ip address directly. Lucky for us our home router has a dhcp server which greatly simplifies the assigning of IP addresses. The easiest method is to simply allow the dhcp server to issue a lease to a host then Mark any addresses which must not ever change as reserved. A DHCP server should first check if a supposed address is occupied before assigning it. If it finds one, that address is assumed to be statically configured and will not participate in DHCP. So it marks it as static.

18

Yeah SHOULD but typically don't, even in large corporate network using either linux or windows for DHCP servers. I see all the time where an address was assigned from the pool only to bump heads with a statically set ip on a device. Or even with another device who didn't honor it's expiration (I'm looking at you certain google phones!)

19

This would all probably be slightly less confusing if router manufacturers were more careful with their use of the words static, fixed, reserved, etc.

While they are synonyms in the traditional sense, they can mean different things when it comes to IP networking protocols.

This article is pretty easy to understand and explains a bit about what static IPs and DHCP reservations are:

ETA: For OP’s purposes (and pretty much anyone in this forum who isn’t already a networking expert at their day job), I agree with most others that DHCP reservations are absolutely the way to go.

2 Likes
20

This ^^^

Over the years I've seen any number of different ways of referring to DHCP reservations & static IPs, probably well-meaning attempts by UI/UX team to help users out that end up muddying the water, especially when you move from one vendor to another over time.

Doesn't help that @marktheknife keeps calling hotels and asking for DHCP reservations... :wink:

3 Likes