Hi,
If there was a option to change the IP Address inside the frontend, it would be much easier to setup HASSIO.
Copying files on a flash drive and booting HASSIO up with it in there just doesn’t do the job. Half of the time it doesn’t work, and the other half … doesn’t also.
You must almost summon a unknown entity in order for it to work. I managed it once, but the amount of work that I went through is ridiculous.
Changing the ip address from the front end makes no sense from networking perspective because you need network access to get to the front end. Changing from console CLI access may make sense since well designed servers do not have graphical interfaces for the console.
It appears your request is for Hassio/HassOs anyway which has no graphical console, if I recall correctly.
But when you first set up your HASSIO, it’ll become available on a dynamic IP by itself on Ethernet. From there it would be nice to access it and then change the IP.
And then the ip address would change immediately, breaking your Ethernet TCP-IP network session before it could be saved. What happens if you typo?
I am a Networking Engineer trying to figure out how else this could be done. The only way I can think of is directly plugging in to the Pi.
You could setup a static DHCP reservation on your router and the Pi would pick up the new address after rebooting.
You press save, it asks you if it is correct and only on “yes” it saves.
Do some quick checks before submitting, like: Is X in the same network (192.168.X.116 → 192.168.X.5)? Is the range valid? If not, warn the user before submitting, if he confirms, well, then it’s really not HASSIOs fault.
I heard that before, but it kinda “seems” wrong.
That is actually a standard way to do it in a DHCP environment. Otherwise you should reserve some network address space that is in the same subnet but outside the address list served by DHCP.
I’ve done quite a bit of networking and used to handle high level components which included larger scale and complex network environments spanning 255.255.48.0/24 (max 65534 nodes) with multiple vlans/failovers etc. If your router doesn’t support masking through regex by mac address, you have DHCP reservations. A high end consumer router will allow you to have custom VLANs where you can span components over multiple subnets and allow multiple IP assignments to a single interface. The industry standard is to use your scope manager (in this case the router) to limit the available IP pool to a selected group of mac addresses. The association for a business class DHCP server can handle a many to many association where roughly 99% of the consumer DHCP equipment can only handle one to one reservations. Also, if you statically assign an IP address within a DHCP scope, you will run into problems… the question isn’t if but when. Allowing someone to set the physical IP address at the remote frontend of a device which has no authority over the existing domain controller is only asking for disaster. I can see it available at a low level terminal operation, but not through any web interface.
If you are having any problems finding the device after it’s booted for the first time, just remember this simple tool:
arp -a