How to fix the IP address for a HomeAssistantOS installed on a VMWare virtual machine?

I installed HomeAssistantOS on a VMWare virtual machine on Windows 11 system. Now I need to fix the IP address of the HomeAssistantOS so that I don’t have to change the login IP after the system reboot.

I know that for the physical machine, I can do IP-MAC binding on the router, but I found that the MAC of the virtual machine is not recognized by the router, but it recognizes two identical MAC addresses (the IP of the physical machine) for two different IP addresses (one is the physical machine’s and another one the virtual machine’s).

Is there any approach for this? Thank you in advance!

The binding should be with the MAC address of the VM, not of the physical system.

But the router doesn’t seem to identify the MAC of the virtual machine…

Some of the options to overcome the router issue.

Download the below app and sccan the network. When you see your HA note down its MAC address.

Inside HA assign a static IP address (use your own IP addresses) Settings → System → Network:

2 Likes

Oh, Nice! Thank you very much! I’ll have a try! :handshake: :handshake:

By the way, may I ask another related question? Is it possible to use HA smoothly if the server and smart devices are on different network segments?

Specifically, suppose my HA server (a Windows PC or a Raspberry Pi) and one router (let’s call it R2) are connected to another router (named as R1), but all the smart devices and users are under R2. Will it be possible in this situation that the users access the HA server and control the smart devices smoothly? Or is there any good solution to this?

Thank you!

Perhaps the essence of the question is, can the HA server under R1 obtain an IP under R2’s LAN?

It is possible but not desirable as it will complicate your life as you grow with HA.

For example mDNS does not work across subnets and therefore device autodiscovery from HA will not be possible.

Also certain technologies like streaming is better when everything sits on the same broadcast domain.

If you decide to have two subnets you will have to pair devices manually in HA, and some might not even work.

I suggest you keep your IoT network on the same subnet.

1 Like

This second method seems better. When using only the first method, I found that some integrations did not load successfully.