Configure Static IP
Øyvind A. Drabløs
Hey, anything new here? This must! we ha.
R
Rikard Stjernman
What is the status of this issue? Are there any workarounds available as this is making my Futurehome hub unusable (I am also using it as a Zigbee broker and if the IP is constantly changing (due to MAC address change when restart) it has impact on all my zigbee devices. Please priotise this.
S
Simon Christiansen
Yes, this needs to be prioritized. So do I have to enter routers every time I'm going to use thingsplex because I have to look up DHCP leases?
Random MAC is a privacy functionality that is not needed on something like Futurehome (which should be in its own web). I see that it is already recognized. But it's nice if it's prioritized, because as of today my two options are:
- Look at the DHCP leases list every time I need the IP. However, this does not help if I want to develop automatics against some kind of API running on Futurehome
- Creating a dedicated VLAN with a DHCP pool of max 1 address (will work, but it's a ridiculous workaround)
Anders
Merged in a post:
MAC address of smart hub (2V0) changes on reboot
Torfinn Brokke
When restarting the smart hub (2V0), the MAC address changes. This makes it difficult to get to certain things on the network (set fixed IP, use MAC filtering, etc.). Vonar this host fixed soon.
Raymond Steffensen
Insted of using ip, try using "futurehome-smarthub" as dns name like:
http://futurehome-smarthub:8081 and see if it works for you :-)
Joar Thorbergsen
Have reported this to Futurehome and they write that this is a mistake.
“This is a known mistake with us unfortunately.
It is true that the MAC address is renewed every time you connect it.
I've also heard of internally regarding this issue.
What I can answer and know as of today is that we are working to correct the error.
Unfortunately, there is no estimated time on when the error will be corrected and sorry for the inconvenience you are experiencing with this.
I hope that this has answered your question.
Still wishing you a nice day ahead.
Sincerely
Lal Peng//FutureHome”
Ø
Øystein Karlsen
Totally agree that this is terribly frustrating. Hope it can be prioritized.
H
Håkon K. Olafsen
This is extremely frustrating when trying to have some control on your own network. Have had to lock IP to a port in the switch, and the Unifi controller simply gets confused when a device is holding on like that.
Hope this gets a high priority!
Trond V Bruun
Assigning a static IP through the DHCP server is the safest way to assign a static IP to a device.
If you set a static IP on the device itselves you need to be sure that this IP is excluded from the DHCP scope otherwise you may end up with conflicting IP's in your network and that will cause unpredictable problems in your LAN.
David Eriksson
Trond V Bruun: This doesn't work either today as the hub is changing the mac-adress on every boot. Doesn't make sense to have a local API with no option to set a static IP.
T
Thomas Lundquist
Trond V Bruun: No it is not. It's easier to know the scope and enter a static value outside it than find the settings on a router you may not even have access to do fixed mappings on.
How to find an address outside the scope if you don't have any access at all? Look at a DHCP given IP when there are few items on it. If it's in the 100s, which is most common, use an address under 10 except 1 which is most common for the router itself.
And as the other reply mentions: This is even impossible as long as the Smartyhub changes mac all the time. Which is something I'd call a bug or "mis-feature".