Display shows the wrong IP address

[Ithrios]

When ussing Hassos the display shows the incorrect IP address. The ip address of my device is 192.168.30.42 and it shows an address of 172.30.32.1

Hassos uses a network of virtual interfaces, which I suspect is the problem. When I type "ip a", this is the result:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether dc:a6:32:6b:ab:48 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.42/24 brd 192.168.30.255 scope global dynamic noprefixroute eth0
valid_lft 2686sec preferred_lft 2686sec
inet6 fd8f:1d3d:c553:4724:663:5872:cca3:6d1f/64 scope global dynamic noprefixroute
valid_lft 1744sec preferred_lft 1744sec
inet6 fe80::ca98:4223:7a6a:33c3/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN qlen 1000
link/ether dc:a6:32:6b:ab:49 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 02:42:42:e5:45:84 brd ff:ff:ff:ff:ff:ff
inet 172.17.232.1/23 brd 172.17.233.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:42ff:fee5:4584/64 scope link
valid_lft forever preferred_lft forever
5: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 02:42:f8:91:82:51 brd ff:ff:ff:ff:ff:ff
inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio
valid_lft forever preferred_lft forever
inet6 fe80::42:f8ff:fe91:8251/64 scope link
valid_lft forever preferred_lft forever
7: veth634c3d7@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether a2:9f:12:a0:15:da brd ff:ff:ff:ff:ff:ff
inet6 fe80::a09f:12ff:fea0:15da/64 scope link
valid_lft forever preferred_lft forever
9: veth542eeb7@if8: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master docker0 state UP
link/ether 6e:95:17:28:3e:5a brd ff:ff:ff:ff:ff:ff
inet6 fe80::6c95:17ff:fe28:3e5a/64 scope link
valid_lft forever preferred_lft forever
11: veth929d6c8@if10: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 2a:f0:3d:97:68:ef brd ff:ff:ff:ff:ff:ff
inet6 fe80::28f0:3dff:fe97:68ef/64 scope link
valid_lft forever preferred_lft forever
13: veth56cf0cb@if12: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 52:a4:71:bf:34:a8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::50a4:71ff:febf:34a8/64 scope link
valid_lft forever preferred_lft forever
15: veth2223261@if14: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 0e:3e:05:8e:29:b7 brd ff:ff:ff:ff:ff:ff
inet6 fe80::c3e:5ff:fe8e:29b7/64 scope link
valid_lft forever preferred_lft forever
17: veth5cb2056@if16: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether a6:51:9a:8c:0c:e9 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a451:9aff:fe8c:ce9/64 scope link
valid_lft forever preferred_lft forever
19: veth6987195@if18: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 2a:ac:aa:bb:4c:c9 brd ff:ff:ff:ff:ff:ff
inet6 fe80::28ac:aaff:febb:4cc9/64 scope link
valid_lft forever preferred_lft forever
21: veth73877c8@if20: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 3a:fb:e9:df:7a:91 brd ff:ff:ff:ff:ff:ff
inet6 fe80::38fb:e9ff:fedf:7a91/64 scope link
valid_lft forever preferred_lft forever
23: vethc82a303@if22: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio state UP
link/ether 9e:45:7f:f7:78:03 brd ff:ff:ff:ff:ff:ff
inet6 fe80::9c45:7fff:fef7:7803/64 scope link
valid_lft forever preferred_lft forever

It is pretty clear that it is using the ip address from 5: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> rather than eth0. Ideally it would select the eth0 or wlan0 address preferentially.

[tigertony21]

I have same problem. Any answer yet to this issue ?

[blainemincey]

Same problem

[djbouman]

Same issue for me

[jameswlane]

Also the same issue, any chance on a resolution?

[randomscot22]

I recall reading somewhere on another thread about this that it couldn't be done. Interestingly if I execute 'ip a' on a Raspberry Pi setup:

eth0 -> inet , contains the address that is displayed on my LCD, so in my docker setup eth0 is the 'virtual IP' that docker is using and that is pulled from the code (eth0 -> inet is what is parsed to get the IP address).