I have installed HAOS (9.5) on x86-64 platform with static IP address. Everything works fine unless I disconnect network cable. HA looses IP address even it is configured as static. ha network info doesn’t display IP address. When I plug the cable everything works fine again and ha network info shows correct static address.
My issue is that I need the IP adress even the network cable is diconntected (e.g. network router is not accessible for some time).
How to achieve not to loose the IP address in the case the network cable is not plugged in.
When the network cable is unplugged, what do you need the static IP address for?
If you want to reference the HA from inside HA, you can always use the loopback address “localhost” or “127.0.0.1”. This will always point to the machine itself and works the same on any computer.
Unfortunately knxd addon terminates. And KNX integration looses connection to KNX bus despite the bus is connected viac USB interface. As the KNX integration works only with IP Routing/Tunnelling to KNX bus, I need to establish this endpoint uxing knxd addon. But when I disconnect the network, IP adress is gone and knxd stops.
I am on cable. I tried loopback, but the result was the same. Watchdog feature is on, so the addon tries to connect.
Technically I want to achieve setup where I have only HA box with USB interface to connect to KNX. Automations do not need front-end. Sure those devices which are in IP world on the network are not accessible without IP connectivity. Frontend as well. But if knx is connected via USB, it should work. Unfortunately KNX integration is working only with KNX IP router, but knxd is stopping when the HA box looses IP address.
Your router not being accessible is not the same as a disconnected cable.
A network interface without a cable is marked as down and therefore it cannot have an IP address.
So if you’d place a switch between HA and your router, it will remain connected, and keep its IP.
Theoretically a loopback adapter would also work…(note that it is not the same as a loopback address), but since you run a supervised OS, i don’t think you could use that
Yes, it is practically network without interface as the network component connected to it is OFF.
It is intended to be switched off. Then the only way is to wait until the USB KNX interface is developed.
It is funny because my old environment worked in this scenario (centos 6.5). But may be it was an implementation of eibd adapter to KNX network. Unfortunately eibd is no more supported and knxd looks to work slightly different.