Share your current setup and future plans

Hi everyone. I am finally moving my HA over to a VM and looking to expand my knowledge regarding Nabu Casa and integrating HA with my Hikvision DVR (if possible) alongside running some Ewelink and Tasmotised units. I would also like to get 2 IR units for my older HiFi and TV systems but those seem to be easy to intergrate into HA.

Does anyone have time to post a bit more detailed information regarding how to install HA onto a VM and which Docker and other installers you run and why? I do get very confused when reading about Docker and Portainer and Mosquito (MQTT) etc etc
 
I only saw that after I used this graphing tool. Currently, I'm doing aggregation with the Utility Meter and integration platforms to work out daily/monthly PV/House/Utility use. The Goodwe inverter, believe it or not, does provide this information but it's wrong. I kid you not. So I had to manually aggregate the data for display in HA



It's a genuine concern. But I suspect Goodwe will never 'open up' their inverter UDP protocol. Most of the grunt work was done sniffing the packets over UDP, but the real breakthrough came when one of the guys managed to decompile the PV Master app. We were all pretty shocked at how bad the programming is, hence why I think Goodwe are too shy to open it up lol. It did help identify a few things I wasn't able to figure out by sniffing the packets.

Ugh, that's bad to hear. You're not doing Goodwe any favours -- hope they read this and get their act together.
 
Ugh, that's bad to hear. You're not doing Goodwe any favours -- hope they read this and get their act together.
I can write a book at my displeasure with Goodwe, or rather with the importers. Absolutely no support. It took months to get my inverter just right. Eventually. Without the help of Segen. Appalling I'm telling you. If I had to do it all over I'd go for Sunsynk.
 
Hi everyone. I am finally moving my HA over to a VM and looking to expand my knowledge regarding Nabu Casa and integrating HA with my Hikvision DVR (if possible) alongside running some Ewelink and Tasmotised units. I would also like to get 2 IR units for my older HiFi and TV systems but those seem to be easy to intergrate into HA.

Does anyone have time to post a bit more detailed information regarding how to install HA onto a VM and which Docker and other installers you run and why? I do get very confused when reading about Docker and Portainer and Mosquito (MQTT) etc etc
Hmmm, there's a lot of guys running HA in docker. In fact I'm pretty sure there's such a guide on HA website. I'm running on RPi4, so wouldn't even know where to start to help you.
 
Quick question:

I have 17 lights I want to automate in future.
Shelly 1 or Sonoff Smart Light Switches (5 x 3 Gang and 2 x 1 Gang)

Which would be better? Currently the place has all old switches and it would need to be replaced eventually
 
Not nearly as advanced as most the systems here, but I'm replacing my Sonoff for Shelly right now.

I'm almost done - just want to connect an outside temperature probe and Shelly EM for power consumption

1606303941524.png
 
Hi everyone. I am finally moving my HA over to a VM and looking to expand my knowledge regarding Nabu Casa and integrating HA with my Hikvision DVR (if possible) alongside running some Ewelink and Tasmotised units. I would also like to get 2 IR units for my older HiFi and TV systems but those seem to be easy to intergrate into HA.

Does anyone have time to post a bit more detailed information regarding how to install HA onto a VM and which Docker and other installers you run and why? I do get very confused when reading about Docker and Portainer and Mosquito (MQTT) etc etc


Hmmm, there's a lot of guys running HA in docker. In fact I'm pretty sure there's such a guide on HA website. I'm running on RPi4, so wouldn't even know where to start to help you.

There's two ways of running it in Docker.
- There's the standalone, officially supported version, where you run just Home Assistant Core. You don't get any add-ons (via the Supervisor) like this nor the snapshot functionality.
- There's the Supervised version, where a system has multiple Docker containers running simultaneously: Home Assistant Core, but then also the supervisor and a Docker container for every add-on you're running. You also get the snapshot functionality (backup of the whole system).

The latter is the way that it is done on the Home Assistant OS (in other words, what you will have if you run it on a Raspberry Pi) or if you run it within a VM.

They also support the Supervised version it on a generic Linux host -- but you have run a specific Linux Distro and there are some other specifications.

That being said - you can actually installer the generic Linux approach method on more Linux distros, but you're unsupported if you do it that way. Meaning, the developers from HA won't help you if something goes wrong. The community will likely still try and help you. I myself are running it with the Supervisor on an Ubuntu host running on an Intel i5 machine, so I'm technically "unsuported".

1606311011222.png

What am I really saying?
- if you want to run it in Docker and are happy with managing the other images (such as Mosquitto MQTT) in docker yourself, and not use the supervisor, then use the Core Docker approach.
- if you know Linux and want to run it in Docker with the full supervisor experience, then go for the Supervisor docker approach and prepare to spend some time on it, and know that it could break in the future.
- if you don't want to struggle too much, run it in a VM and use the VM images provided by Home Assistant. Yes you will lose some performance but probably won't be that much and it is supposed to be easier.
 
I'm running on RPi4, so wouldn't even know where to start to help you.
Be sure to backup your config. Started with a pi too...the SD cards really are prone to randomly dying as people say. Not a big deal re cost but gets old fast if you lose your config
 
Is there an easy guide that shows how to backup your configs to GitHub so that we can have version control

I have the snapshot running daily and being backed up to Google drive but feel the GitHub thing would help with f ups normally make in my yaml config.

Know nothing about GitHub
 
Be sure to backup your config. Started with a pi too...the SD cards really are prone to randomly dying as people say. Not a big deal re cost but gets old fast if you lose your config
I’m running it on ssd. I’m not 100% rigid on backups. I kinda do it when I make big changes. Yes, it’s gonna burn me still
 
There's two ways of running it in Docker.
- There's the standalone, officially supported version, where you run just Home Assistant Core. You don't get any add-ons (via the Supervisor) like this nor the snapshot functionality.
- There's the Supervised version, where a system has multiple Docker containers running simultaneously: Home Assistant Core, but then also the supervisor and a Docker container for every add-on you're running. You also get the snapshot functionality (backup of the whole system).

The latter is the way that it is done on the Home Assistant OS (in other words, what you will have if you run it on a Raspberry Pi) or if you run it within a VM.

They also support the Supervised version it on a generic Linux host -- but you have run a specific Linux Distro and there are some other specifications.

That being said - you can actually installer the generic Linux approach method on more Linux distros, but you're unsupported if you do it that way. Meaning, the developers from HA won't help you if something goes wrong. The community will likely still try and help you. I myself are running it with the Supervisor on an Ubuntu host running on an Intel i5 machine, so I'm technically "unsuported".

View attachment 959958

What am I really saying?
- if you want to run it in Docker and are happy with managing the other images (such as Mosquitto MQTT) in docker yourself, and not use the supervisor, then use the Core Docker approach.
- if you know Linux and want to run it in Docker with the full supervisor experience, then go for the Supervisor docker approach and prepare to spend some time on it, and know that it could break in the future.
- if you don't want to struggle too much, run it in a VM and use the VM images provided by Home Assistant. Yes you will lose some performance but probably won't be that much and it is supposed to be easier.
Running it on debian after following this guide, https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-10/200253

Have no issues at all as it is a supported os. As far as I know the only way of running it supervised other than with hassio os.
home.jpg
 
Last edited:
The only issue I had is that Debian and ubuntu is not the the same. Even thou ubuntu is based on Debian. Was also on ubuntu 1st, but was as simple as backup home assistant, install debian and home assistant, restore. Think it was done in 20 mins
 
The only issue I had is that Debian and ubuntu is not the the same. Even thou ubuntu is based on Debian. Was also on ubuntu 1st, but was as simple as backup home assistant, install debian and home assistant, restore. Think it was done in 20 mins

Yeah, that's why I think I should probably also take the plunge and do it.

That being said, I do run a couple of additional containers on mine (Unifi controller for example), so I'm guessing it will probably count as "additional software installed" which the HA guys do not approve.
 
Have a look on the supervisor, add-on store, there is unifi controller, https://github.com/hassio-addons/addon-unifi

Think they referring to the core os running addition software other than just hassio.
It's a good point, my hass.io running as a VM on my Windows laptop and it's rather good. I use a lot of the add-ons but not the ubiquiti controller which runs on a pi (with pi hole - my secondary DNS). The hass.io VM also runs adguard home which is primary DNS. Also have Plex running seperately on the same PC.

As my NAS died, I am currently in the process of upgrading a three year old i5 into a NAS/hass.io system.

Thinking I should make the plunge and maybe rather try out Debian? Was gonna go windows Pro

New 'PC' will have 16GB ram, I5, 500GB SSD, and 4TB external drive (for media)

Expect it to run :- Hass.io (in VM/docker with grafana , influxdb) and was going to run on host OS,. Plex and now possibly ubiquiti controller? Can debian handle all of this easily for a noob like me ?

If windows, I can allocate 8-12GB ram to the Hass VM and just run everything inside it, from the SSD

Is anybody running the controller and Plex with everything inside supervised Hass.io VM ? How is the performance of it? Plex will not be expected to do any transcoding.

Thinking I would like to keep the ubiquiti controller seperate on Pi, but with SD card unreliability, there is risk to entire house (I guess if it's not working)

The reason a VM appeals to me is that I can just backup the entire VM before big changes or regularly and have a way to go back without starting from scratch. I don't have to much faith the the snapshot system of hass.io


Damn design decisions
 
I personally don't like having all my eggs in one basket.... so here is what I do:

I run home assistant on a small 'nuc" like pc, with celeron, 4gb ram, 60gb ssd as it doesn't need anything more powerful, it runs on PI :D
I have another pc, that runs proxmox, that I create VMs on and each has between 2 to 4gb ram allocated to it running either ubuntu or debian server as os. One that just does downloads, one that is just media player(testing as my host doesn't support gpu/pci passthrough) and few other VMs for different task. They alll backup on weekly basis to my NAS.

The main reason for me to split tasks/software is that if one breaks, don't have to redo everything. Where if you run all the tasks on one machine, one breaks, you will end up reloading os and redo everyting.

Task being either hassio or unifi controller or mediaserver.

proxmox is like vmware, but opensource. https://www.proxmox.com/en/

 
Gonna try to OTA flash some Teckin SP23 smartplugs tonight. First attempt at tasmota. And last minute advice?


Def

Worth pointing out that you can install proxmox on top of a clean debian setup...that way you can get classic debian + virtualization.

I don't have a super beefy machine -- i5 6th gen with 8GB of RAM. Can upgrade the RAM to 16GB if I need to.

I'm considering moving HA back to a VM, in Proxmox. Not sure I would want to run everything else in Proxmox (I know the Docker image I use for person detection, using a Google Coral USB accelerator, has a lot of issues passing through the TPU to the script when using virtualisation).

So I guess your suggestion is
1) Install Debian
2) Install Proxmox
3) Run HA in a VM in Proxmox
4) Install Docker and run whatever else I want to run manually?

Not a bad idea.

Last - would you be able to virtualise Windows inside Proxmox, and primarily use it with Remote Desktop?
 
nope....

1) Install Debian
2) Install Proxmox
3) Run HA in a VM in Proxmox
4) Install Docker and run whatever else I want to run manually?

Proxmox is a stand alone OS, more like a hypervisor. You install it, connect to webgui and do everything from there. So your order of doing things would be:

1) Install Proxmox
2) Install Debian
3) Run HA in a VM in Proxmox

Or follow this guide will take you through the process: https://community.home-assistant.io/t/installing-home-assistant-using-proxmox/201835

From what I read there it will install the same version as on PI

Home Assistant Full installation of our all-inclusive home automation system. Best in class home automation is complemented with a UI for configuring your system, making backups and safe updates with automatic rollback.This method was previously known as “Hass.io”, and includes our Operating System (HassOS), the Supervisor, and add-ons. It can be run on various single-board computers or in a virtual machine.
 
Top
Sign up to the MyBroadband newsletter
X