After a steep learning curve - so don’t kill me if I use the wrong lingo - I have ended up with Home Assistant running on a Ubuntu (guest?) VM, which is running on VirtualBox, hosted on a Windows 10 machine. The machine will control a number of Switchbot Bots via Bluetooth. The Windows 10 machine has a static IP and the local network has no DHCP, and so because of this, I couldn’t use “Bridged Adapter” for the VM and instead had to use the “Host-only adapter”.
Everything works BUT I can’t figure out how to edit configuration.yaml Advanced Configuration - Home Assistant as all of these methods require an add-on, but I think because the Ubuntu VM is running in Host-Only mode, it has no internet access so can’t connect to the store.
Is there a way around this? I literally just need to add a dozen or so lines to configuration.yaml for the switchbots.
I’m also a newbie. But my setup is on a Rpi, in a docker container, and the HA sets up a form of SAMBA share, so I could access it by typing in the ip-address in to the address field in Windows Explorer (win + E).
See attached screen shot.
Dump that abomination of an install and start again with something simple. Like imaging an SD card for a pi3. They’re cheap. You can learn on it and easily change to an advanced install on more powerful hardware later if you need to.
Windows is a terrible host OS for your system. It will restart without warning for updates.
Ubuntu is not an ideal host for Home Assistant (Core?) either.
Then there’s your VM networking issues.
Home Assistant can have a steep learning curve and you want to make it as simple as possible. Your current setup is not going to facilitate this.
haha that’s fair enough I actually managed to find a way to get the add-ons! I borrowed an IP from another machine near me and managed to get on the internet and get the add-on to edit the file.
I now have some other issues so may just call it a day. Maybe getting a Pi is the way forward, but I’m realising I just don’t have the necessary skills for this stuff The Switchbots can actually just be put on a schedule mode to preemptively turn some thngs on/off rather than me trying to turn them on/off remotely when they have a nap.
EDIT: Success!! The switches were not showing on the dashboard after adding them into the config, but again, it’s because I had switched back to host-only and so HA couldn’t get the dependencies or something like that. It was in a log I noticed. So I got the VM back on the internet and the switches were there, and then I put the VM back to host-only and all is working fine