When I want give a device a static IP address, it would be nice to pre-populate known addresses.
Network-mask and Router’s IP are usually the same for each connected network, right?
Maybe there should be a way to store those IP addresses (the mask and router) in Shelly Cloud. This way it could be used to pre-populate the necessary fields in the apps
There are designated LAN IPs but I doubt you can simply pre populate it. That is why dhcp and ip reservation on routers exist. So all device IPs may be managed from a single device
Huh?
Static IP addresses are set in the client.
Prepoulate? Do you mean reserved IP addresses? Reserved IP addresses are set in the DHCP server, usually in the router.
What are “known addresses”? No two clients on your local network can have the same IP address.
Except for static addresses, the DHCP server handles all IP management for you. If you use static IP addresses, managing them is your sole headache responsibility.
When I set a static IP address via the web-interface, have to manually set the network-mask, router-IP and DNS-addresses.
If these addresses are already set, for other devices, it would be nice if they can be pre-populated.
In many cases (stability) it is good practice to have a static IP-address for some devices on a local network.
The Shelly-App developers could implement (already known) data into form-fields. That just helps the user
What you are describing makes little sense or we’re on different planets. Which web-interface? Are you talking about settings → network → Configure network interfaces?
The reason that the settings for static IP are all manual is because not everyone’s network configuration is the same. Not every device on the LAN needs to use the same gateway and you might have a reason to use a different DNS, for example a local DNS server.
Why do you want to make it needlessly complex? If you want things prepopulated, use DHCP. That’s what it is there for. Reserve the IP address in your router and it will always be the same. For almost all home networks, DHCP works just fine and only clients that should not change their IP address, like a server for example, need a reserved IP. (A reserved IP is not a static IP).
I have over 110 network clients - only two have static IP addresses because they are ESP devices that are sleeping most of the time. Having static IP addresses lets them wake and restart a few ms faster. (It saves a bit of battery life). All of my servers, 5 in all, use reserved IP addresses managed by the router. Everything else is free-range DHCP.
Maybe in the 1990’s when DHCP was still developing. If your network is so flaky that you need to use static IP on your devices, then fix your network.
If you mean the web-interface of the Shelly device, that is a feature request for Shelly, not for HA.
Hello Stephen Mann (YAML-challenged),
If you don’t set the static address in the routing device, the router can just reuse it anyway and give it to another device.
Setting a static in the device is only needed if there are problems with your DNS or you are using some non-standard configuration.
And I agree with Francis, I think none of this is HA related…
I am not sure I am following your logic here. The routing device (DHCP server) does not need to know anything about a static IP address.
A static IP must be outside of the DHCP pool. If it is outside of the DHCP pool the router will never assign it to a new device. If your device’s static IP is inside of the DHCP pool and when the device is offline, DHCP can and probably will assign the same IP address to a new device. This can create havoc and a reason to be very careful in assigning static IP addresses.
A reserved IP is inside of the DHCP address pool. The address is linked to the device MAC address. When the device with that MAC address asks DHCP for an IP assignment, it will always get the reserved IP address. As far as the DHCP server is concerned the device was never offline.
Yes, but people not knowing what DHCP is or or address pool is will set the number to whatever was picked originally, which is usually in the range. then they lock it in and it eventually messes up.
You who knows what to do can do whatever you want. If you are helping someone asking basic questions, you tell the the way that is most likely to help them succeed, and if they set the static in the router, the router will not re-assign it.
Yes I know rhings you could do, but you are helping people with a different level of knowledge. I suggest simple and foolproof as possible for answers unless you pick up on a more advanced user.
DHCP.
If you want simple, use DHCP on everything.
The vast majority of Home Assistant users are just fine with DHCP managing everything in the background.
You don’t set static in the router. You can reserve an IP in the DHCP pool of the router which for the end user acts like a static IP, but without the management headaches.
There are DHCP servers that exclude (“reserve”) IP addresses inside the DHCP pool, so the DHCP pool might go from 192.168.0.2 to 192.168.0.254 and then 192.168.0.200 can be excluded.
You might be able to store the information in your browsers autocomplete history.
A good quality router will allow you to completely exclude a range of addresses from being assigned by DHCP specifically for the purpose of manually assigning IP addresses.
Most DHCP servers allow for non-contiguous IP address ranges. This is needed if you have a device that has a static IP address that you can’t change which falls into the middle of the DHCP pool. But I seriously doubt the average Home Assistant user will run into this problem. But if they are doing network segmentation or load balancing, they aren’t the average Home Assistant user.
I could have said “A static IP must be outside of or excluded from the DHCP pool”, but that introduces more, not less confusion.
True, sometimes it is wrong if you do and wrong if you don’t. 