By static i mean assigned by dhcp but never changing (fixed).
Static is a homonym and interchangeable with fixed. The static/fixed IP is set in the device. Reserved IP addresses are set in the router.
I have explained what I meant with the terminology I used. There is no sense in arguing whether I’m using the “right” term or not, because you already know the underlying meaning. Accordingly, either you understood what I was trying to say or not. If you understood, great! If you did not understand despite it being explained already, then that is your problem now.
There is no need for arguing about this. Some integrations do need static ip address for device for work properly. On some devices you can set up ip address on some you can’t so you will use router to assign static ip for those devices. And that is all to it.
Such as ??
Pretty much anything you add manually via IP address to HA.
Be specific. What integrations REQUIRE a static IP?
Android debug bridge, frigate, home connect, midea, mqtt, samsung smart tv, ssh, syncthing, just to name a few that will need a static ip.
Esphome also is working much better with static ip, no matter mdns.
1 Like
Yes any ESP device will start faster, not “much better”, with static IP because the processor doesn’t need to negotiate with the DHCP server. Once the connection is established, static or DHCP makes no difference to the operation. The ESP processor by default will first try the last used IP, so if the IP is reserved then it will connect without a DHCP negotiation.
Frigate configuration requires the camera IP, so the cameras should have reserved IP. I don’t know if Frigate can resolve an mDNS address. I’ve never tried it because my cameras have a reserved IP.
An MQTT broker is a server and should have a static IP.
Again, you assert that integrations REQUIRE a static IP. Almost all will work just fine with DHCP.
This is going way off-topic, so drop it.
1 Like
I don’t think you get the central problem with DHCP. Sometimes, DHCP forgets an IP assignment and gives an existing device a new IP address. And when that happens, if the device was not added to HA using mDNS, it’s fucked.
THAT is why I insist on giving every device a known, fixed IP, whether DHCP-leased or not.
3 Likes
The only time I had an issue with DHCP was when two devices had the same MAC address. That is not supposed to be possible, and it took me weeks to figure out.
DHCP doesn’t “forget” an assignment. A DHCP server remembers an IP assignment for the lease time. Depending on the server, 1 to 24-hours. Once the lease expires, the IP address may be reassigned to another device. Every time a client is connected the lease renews again. A reserved IP is basically a permanent lease.
Static, AKA Fixed (sometimes) IP is set in the device itself. Hopefully in an address space outside of the DHCP pool.
Again, you are using a fuzzy description of “fixed” IP. Of my 50 or so WiFi devices, about a third of them have a reserved IP. That is not a fixed (static) IP.
Now, back to the OP’s question. Use DHCP as the default, reserved when necessary and static IP only if absolutely necessary. From your description it sounds like you may have two DHCP servers which will guarantee erratic behavior.
My intuition tells me you don’t have nearly enough networking experience. Otherwise you would not make that claim with a straight face.
Very rarely, DHCP servers can experience data loss leading to loss of the lease list. Then all hell breaks loose.
To avoid that issue (admittedly a rare one), I recommend assigning IP addresses via DHCP or configuring them by hand if DHCP won’t work. Sometimes it’s as simple as confirming in the router config that an initially dynamically-assigned address forever belongs to the device that got it.
Bonus from this approach: changing to a new router while preserving addresses and avoiding havoc is easy, cos you already have a complete list of all known IP addresses you can copy to your new router.