Static IP-Adress, why is this not a function in HP23 or HP19?

Hey,

Have anyone asked Athom why it is not a opportunity to set a static IP-address from the Homey app/web? I have set a static from the DHCP, so that is not the question. But I find it usefull to set a static from the equipment itself, and not in the DHCP server.

Regards
Marius

2 Likes

I think this is because Athom considers this to be too advanced for regular Homey users.

@robertklep , Okey. Weird thought from Athom if they really think that.

you’re teasing but you made me laugh :grin:

1 Like

I find it useful to define such things at a central place - the DHCP.
I can understand if a company does not support this. Tech users should know that DHCP ist the right place and not a client device.

4 Likes

I think we have to agree, to disagree.

While I agree it should be in the DHCP, it’s not always simple to implement with simple consumers network devices. Definitely more manageable with more advances solution such as Unify or solution that supports DHCP backup. An example that is annoying with more basic network devices is when you change your Wireless AP, Router, Switch and coffee maker machine all in one device :grinning:

Some basic network devices don’t even let you change the IP before you can make a reservation.
For those cases I see a point of having a way to set a static IP address. Maybe I’m missing other use cases as well

Ok. I agree that it could be a way for ugly LAN router.
But the chance is high that users with less technical knowledge can break their LAN if they insert a wrong or duplicated IP.

1 Like

That is true.

I do think that @robertklep is mentioning something important:

Even though we disagree about DHCP/Device @RonnyW

Athom simply doesn’t want post like “my Homey broke my LAN/router :sob:”

1 Like

Out of curiosity, why not in the DHCP?

:sweat_smile:

@Didier_SmartHome , To ensure the reliability.

If you can’t backup / restore your DHCP scope or don’t use IPAM then I got it for the reason I listed above otherwise I don’t and we will have to agree to disagree as you said :grin:. I never had issue with reservations. Don’t get me wrong I think Homey should provide the flexibility of manually setting a static IP address like almost any other network devices on the planet

1 Like

Instead, they want users to use their (usually much more advanced) router configuration, so that when they screw up there, Athom can blame someone else :man_shrugging:t3:

It wouldn’t surprise me if in some parts of the world users are stuck with routers that are so closed that they can’t configure anything on them, including DHCP reservations.

It’s not only about DHCP availability. It’s more of network design - I have all home related devices on separate VLAN and I do not want to run DHCP there, because from design point of view it doesn’t make sense to have broadcast enabled there. But Athom forced me to have it only for one device even with static reservation…

I’ll vote for static IP if someone asks…

1 Like

I am a tech user and I disagree. DHCP is for dynamic allocation, not static for known equipment.

Not everyone even want to run DHCP on the IoT-VLAN and others may not have enough control over their DHCP server (like many using their ISPs CPE for this.) and cant set static leases.

RFC2131:

DHCP supports three mechanisms for IP address allocation. In “automatic allocation”, DHCP assigns a permanent IP address to a client. In “dynamic allocation”, DHCP assigns an IP address to a client for a limited period of time (or until the client explicitly relinquishes the address). In “manual allocation”, a client’s IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client.

Static allocation on the client itself is outdated and prone to errors.

2 Likes

If that’s the case, you can’t change the DHCP range (that covers the whole subnet as default). That means you have no “safe” range where you can set static IPs manually and the DHCP server can easily reuse your static IP.