Then I updated the network settings in the VM and rebooted it). ![]() (I switched off wifi and made sure the ethernet connection was working. I thought that might be the problem, but I tried connecting the laptop directly to my router via ethernet adapter and got the same problem. Reading a bunch of posts on this forum and videos on YouTubeĪll of my devices (including the laptop running HA) are connected to my router via a Tenda Mesh3 home mesh wifi system.Switching off Windows Security Real-time protection and trying all of the above again.Installing Fing on my phone and trying the only IP address I couldn’t readily identify.In this instance I get an ERR_CONNECTION_REFUSED error instead. ![]() The following dialog is where many Windows 10 features can. Its a blue button in the middle of the page. If more advanced users want to run Docker for Windows, it will require Hyper-V instead of VirtualBox. This is the website from which youll download the VirtualBox setup file. The IPv4 Address according to ipconfig in command prompt (192.168.5.80) with :8123 on the end. Go to in your computers Internet browser.VirtualBox isnt quite as good on the whole, but for most people will be just right, and Oracles continued. Both homeassistant.local:8123 and homeassistant:8123/ Unfortunately on Windows 10 Home and Windows 11 Home you simply cannot use Hyper-V.Multiple browsers: Chrome, Edge, and Internet Explorer.I did a factory reset, then performed all the windows updates, installed VirtualBox 6.1, and then followed the steps on the Windows - Home Assistant installation guide until it asked me to go to homeassistant.local:8123, at which point I got a DNS_PROBE_FINISHED_NXDOMAIN error. I’m using an old laptop with Windows 10 with plenty enough grunt. Unless someone here can help I’m going to have to give up on HA before I even got started
0 Comments
Leave a Reply. |