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

**URL:** <https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506>\
**Category:** Ideas & Suggestions\
**Created:** [October 18, 2024, 4:46pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506 "2024-10-18T16:46:17Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 18, 2024, 4:46pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/1 "2024-10-18T16:46:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 18, 2024, 4:51pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/2 "2024-10-18T16:51:13Z")

</div>

> [@Marius\_Stensrod](#):
>
> Have anyone asked Athom why it is not a opportunity to set a static IP-address from the Homey app/web?

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

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 18, 2024, 5:24pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/3 "2024-10-18T17:24:06Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Didier\_SmartHome](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_smarthome/32/97365_2.png) [@Didier\_SmartHome](https://community.homey.app/u/Didier_SmartHome)\
**Post date:** [October 18, 2024, 5:42pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/4 "2024-10-18T17:42:59Z")

</div>

you’re teasing but you made me laugh 😁

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 18, 2024, 7:21pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/5 "2024-10-18T19:21:34Z")

</div>

> [@Marius\_Stensrod](#):
>
> But I find it usefull to set a static from the equipment itself, and not in the DHCP server.

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.

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 18, 2024, 7:22pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/6 "2024-10-18T19:22:51Z")

</div>

> [@RonnyW](#):
>
> Tech users should know that DHCP ist the right place and not a client device.

I think we have to agree, to disagree.

---

<div class="post-metadata">

**Author:** ![Didier\_SmartHome](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_smarthome/32/97365_2.png) [@Didier\_SmartHome](https://community.homey.app/u/Didier_SmartHome)\
**Post date:** [October 18, 2024, 7:38pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/7 "2024-10-18T19:38:12Z")

</div>

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 😀

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

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 18, 2024, 7:46pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/8 "2024-10-18T19:46:19Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 18, 2024, 7:47pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/9 "2024-10-18T19:47:49Z")

</div>

> [@RonnyW](#):
>
> break their LAN if they insert a wrong or duplicated IP.

That is true.

I do think that @robertklep is mentioning something important:

> [@robertklep](#):
>
> this to be too advanced for regular Homey users

Even though we disagree about DHCP/Device @RonnyW

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 18, 2024, 7:51pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/10 "2024-10-18T19:51:03Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Didier\_SmartHome](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_smarthome/32/97365_2.png) [@Didier\_SmartHome](https://community.homey.app/u/Didier_SmartHome)\
**Post date:** [October 18, 2024, 7:51pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/11 "2024-10-18T19:51:04Z")

</div>

Out of curiosity, why not in the DHCP?

---

<div class="post-metadata">

**Author:** ![Didier\_SmartHome](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_smarthome/32/97365_2.png) [@Didier\_SmartHome](https://community.homey.app/u/Didier_SmartHome)\
**Post date:** [October 18, 2024, 7:51pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/12 "2024-10-18T19:51:28Z")

</div>

😅

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 18, 2024, 7:55pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/13 "2024-10-18T19:55:35Z")

</div>

@Didier_SmartHome , To ensure the reliability.

---

<div class="post-metadata">

**Author:** ![Didier\_SmartHome](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_smarthome/32/97365_2.png) [@Didier\_SmartHome](https://community.homey.app/u/Didier_SmartHome)\
**Post date:** [October 18, 2024, 8:02pm UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/14 "2024-10-18T20:02:59Z")

</div>

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 😁. 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

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 19, 2024, 4:51am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/15 "2024-10-19T04:51:01Z")

</div>

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 🤷🏼‍♂️

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 19, 2024, 4:56am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/16 "2024-10-19T04:56:03Z")

</div>

> [@RonnyW](#):
>
> I find it useful to define such things at a central place - the DHCP.

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.

---

<div class="post-metadata">

**Author:** ![Zimo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zimo/32/16621_2.png) [@Zimo](https://community.homey.app/u/Zimo)\
**Post date:** [October 21, 2024, 6:26am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/17 "2024-10-21T06:26:53Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![thomasez](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thomasez/32/81910_2.png) [@thomasez](https://community.homey.app/u/thomasez)\
**Post date:** [October 21, 2024, 7:44am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/18 "2024-10-21T07:44:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 21, 2024, 8:10am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/19 "2024-10-21T08:10:11Z")

</div>

> [@thomasez](#):
>
> DHCP is for dynamic allocation, not static for known equipment.

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.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 21, 2024, 9:11am UTC](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506/20 "2024-10-21T09:11:46Z")

</div>

> [@thomasez](#):
>
> may not have enough control over their DHCP server (like many using their ISPs CPE for this.)

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.

[Next page](https://community.homey.app/t/static-ip-adress-why-is-this-not-a-function-in-hp23-or-hp19/118506.md?page=2)
