No, I haven't. I've jsut pressed on create new netowkr in network section, named it home-assistant, left external as setting and that's it. It's identical to default one.
As usual, great video! It helped me a lot to swith HA install to VM. I just had issue with ssl, workaround was not to click the ssl box when configuring HA from the image. I know how much effort is to keep a channel like this running, you put a lot of work for the community, kudos for that.
Thank you very very much for the comment!!!! Really much appreciated. My bad, forgot to mention that you can restore partial thing from snapshot and possible problems with SSL.
Brillant!, just what I was looking for for a way to keep Hassio on Synology NAS and turns out, you are the point man for Home Assistant and keeping the Synology NAS relevant. Great work and THANKS....
Hello and very many thanks for creating and uploading this video. I’ve been tinkering with HA in a Docker container on a Synology NAS but couldn’t get very far as I didn’t have access to the Supervisor mode. I’ve not used VM before but your tutorial has got me up and running. As your video finished I got the log on screen for HA. As I’ve not created many entities within the Docker I’ve opted to start afresh. One useful addition is to click the ‘Connect’ tab in the VMM ‘Virtual Machine’ menu (second from top with ‘Overview’ above). It seems to display some useful diagnostic information. Mine tells me that the VM is ‘Waiting for the Supervisor to startup…’, which makes sense as this mode is not yet enabled in HA. I presume it’s accessing / downloading the additional bits. Anyway today is a good day at school!
Thank you verry match! After your instructions at last I have HA supervised on Synology DS220+ with extended 4GB RAM(not original Synology, but Crucial 4GB DDR4 2666 SO-DIMM), SONOFF Zigbee 3.0 USB Dongle Plus, and so far every thing is work find! Thanks!
So cool! It works like a charm. The only thing what was a little bump for me was this. After you restore your backup it would show an error "page not found". I reinstalled and again, same problem. BUT! The simple solution... I use https on my Pi backup and the initial installation runs on, yes... http. So, after accassing HA on the VM with https, tadaaaa, there it was. After grooming a few minor things it really works well for me on my DS720+. Bye bye RPi3, welcome Synology. ;-) Thanks for the nice and clear video!
Fantastic, I am so glad you made this video, really awesome. I was just in time too, because this week the Supervisor failed to start up so no latest snapshot for me. Luckily I could use a 3 weeks old one for that (from the file system) without any problems. I struggled a little bit to connect to the VMM with Admin credentials while the standard usere credentials worked fine. Strange thing, but after finding the new IP adess it went smoothly from there. Super happy here!!
Great videos on HA. Another option, the one I have working is to use VM to install debian and the install on it HASSIO. You can install Synology tools with this option.
Thanks for the tip. Btw, in version of hassos 5.13 ova, this will be fixed. Error with id has been corrected by Fredrick and his pull request has been merged.
@@BeardedTinker if someone is interested install the lightest version of debian, only cli. Then install HASSIO on debian: sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y sudo -i apt-get install -y software-properties-common apparmor-utils apt-transport-https ca-certificates curl dbus jq network-manager systemctl disable ModemManager systemctl stop ModemManager curl -fsSL get.docker.com | sh curl -sL "raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh" | bash -s Configure reverse proxy and let's encrypt for https access. works like a charm, very fast on DS920+ ;) The question is, what is the lightest and most versatile solution ...
Thank you for this!!!! In regard to litest version - I think that still this should be pure Docker. It doesn't have any extra overhead that VM has with OS. But it's not as simple as running VM or HassOS
Again a great tutorial, if only I had this tutorial when I started with this half a year ago! FYI over the months my Home Assistant has gotten pretty big and it runs fine with 2GB Ram. Image recognition add-ons such as DOODs are pretty slow thought but I guess that's more CPU related.
If there is any update available, in Supervisor menu you will see it. No matter if it's HA, Supervisor or OS. You just click on update and that's it. Everything available from UI.
Hi, Great helpful video. I had issues with networking without having the guest agent running. While I understand that will be added to the ova package in a future version, I ended up getting it running with the linux VMware workstation image (.vmdk). If you import this into the VMM as an image first, and then create the virtual machine from the image, you get the guest agent running fine and it solved all my networking issues. Also, if your backup is greater than 1Gb, you cannot install directly from the setup screen (I have a decent sized database in the backup). The work around is to get HA running without restoring then set up Samba as you describe. You can then copy the backup into the backup directory on the VMM and restore from that file within the supervisor screen. Hope this helps anyone that gets stuck.
Thank you for the comment Brad! What kind of network issues did you have? Usually Guest OS agent will not resolve any issues, it will just give access to host to see inside info (such as IP address) and allow some further control (for ex. power down etc).
@@BeardedTinker The virtual machine was behaving as though it could not see the DHCP server and never got an ip address, even though I could see the VM MAC address from that server. I'm not sure what was causing that - whether synology was blocking the DHCP packets because the mapped ethernet port has a fixed ip or something. I ended up fixing it by pushing the VM onto the second ethernet port on my NAS and leaving everything on that port with DHCP. The guest OS agent may not have solved the issue but it makes a difference to trying to diagnose what is happening!
Great video. I have been trying to utilize the 2 ports on my synology, where they are on 2 different vlans. I have that set up in my vm on the server I am wanting to migrate from, but cannot figure it out just yet.
Sorry for a late replay. I don't use VLANs in my setup. As for ethernet ports, I did create two different setups. One is to use combine 2 ports into single IP to reduce possible bottleneck there. And on another setup, I have one port dedicated to Synology main services, while other port is dedicated to VMM.
Thank you very much for your comment and great question. To be honest, with HA image, I'm not sure... I know how to install it in other VM's but with limited access HA is giving to users on system level, not sure. Currently, the easiest way to do it would be to use image Fredrick has prepared that has guest tools active. So, make a snapshot of your installation and make sure to download it. Stop current VM, install image from this link (fisrt post): community.home-assistant.io/t/installation-on-synology-virtual-machine-managager/281608 Start it and import in it snapshot.
Thanks for the great video. I was able to set up a Home Assistant VM and get some add-ons working, but i have not been able to mount a NAS shared folder on the VM. For example, I want to run Plex and let it use my music library on the NAS which has a different IP. I have set up Samba and NSF sharing but still can't mount the library on the VM. Any advice would be appreciated.
You can try using shell command for this. This should work in both HA and with Synology: shell_command: mount_nas_folder: mkdir -p /media/music;mount -t cifs -o vers=3.0,noserverino,username=xxxxx,password=xxxxxxxxx,domain=xxxxxxx //xxx.xxx.xxx.xxx/music_folder /media/music/ This would create /media/music folder and map it with /NAS/music_folder This is not my command, but it should work.
I am learning a lot from your wonderful video. Thanks. Currently I have just set up HA core over docker. Would it be better for me to run on VM - synology to get the supervised version to start from the beginning? Shall I stop the docker HA core version first?
Thank you very much for your comment! This is excellent question. No, you don't need to stop it. VM will start in new machine, with new IP address, so you can keep your Docker version running until you are satisfied on how VM version is working. And yes, VM - if your system is powerful enough to run it, is definitely better option then Docker. Unfortunately, not all systems can run it or have enough resources. And you can copy your existing CORE version configuration to HA machine, after you finish installing it, so you can reuse all your configuration that you have.
You don't happen to have a tutorial on going from Synology VM to an x86 setup by chance, do you? Looking to move my HASS off Synology to my new Beelink mini PC. Your tutorials have always been helpful!
No, I don't have it - yet. Will have one in few weeks as I'm preparing to review one x86 based device. But the process should be the same. On x86 - you download and install ISO image from HA web site and just import backup from old system. That should be it! Or of course, if machine is powerful enough, get proxmox and run VM with HA on it. :D
@@BeardedTinkersmart man. Went the virtualbox route and I'm up and running but interested in proxmox as a lot of ppl bringing that up as of late. Look forward to the next vid!
Thank you very much for the super good instructions .... Even a dummy like me can move from a Raspberry to my Synology ... and only one server is running at home. Yeah ... Now the only thing missing is the Synology Guest Tool ... and it would be even more brilliant ... As information for someone who still wants to try it. I used a DS220 + with 6GB of RAM and currently 3GB of RAM for HomeAssistent ... and it runs great. But I will try to expand the RAM. That is probably possible. Thanks again for the great job.
Thank you for your comment - glad you got it working! I still haven't managed to play and try to get guest tools working, but that should be possible. Just have to get a bit of time to try. If you do get more RAM, that will be great - here RAM definitely improves overall performance. Just Google around a bit to insure you get one that is supported.
DS 415+ that’s the model I have. I was wondering how well it runs with 8gb RAM and DSM7? Any sluggishness slow downs etc. Also I couldn’t figure out why the VMM package wasn’t available. Perhaps it’s not recommended for the 415+ because of the hardware? You show a couple different Synology models in your videos what model would you recommend or are you using today? Thanks!
All my videos are recorded on DS415+ . Last 6 months or so it's running on VMM and it's also on DSM 7. Total amount of RAM is 10Gb RAM. It is not officially supported but installing is easy. You need to select similar model and download package for Synology site.
@@BeardedTinker Ok, so I just need to choose possibly a 918 or 920 As a comparable model for the VMM ? I’d like to eventually upgrade to a newer model but not sure what to choose. I like the 920 but it’s an older model I was going to wait for the 921 or go with 1621+ or xs. Would appreciate your input. Thanks !
@@markstanchin1692 my main setup is running on 920+ - that's 2020 model, that was release in mid of last year. 1621+ is about 500$ more expensive then 920+. I've added 16GB modul to mine and now run it with 20GB. 9xx version can have up to 9 drives (with rexternal drive bay), while 16xx can have total of 16 drives - 6 internal + 2x5.
Thank you very much for your video. Only one question, when use the HASSIo package the IP of HomeAssistant was the same IP of the NAS. Now when I crate a new VM I can assign the same address of the NAS? Or there is a conflict? Thank you!
No, you can't use same address as the nice - this is now separate machine and has to have different IP address. And when you install it, DHCP should be default give it new IP address. You can change that IP address, but it has to be unique to your network.
Hi Thanks once again for a wonderful video. I have migrated my home assistant from RPi to a Synology NAS. however my dcukdns ad don configure dont he pi is not working on the Synology VMM home assistant instance. Would you be able to suggest this? I have tried adding duckdns in DDNS menu however i have a message failed to register the ip the ip adress via ddns. My dsm is 7.0
I'm using same setup as yours - but I'm not using any addon on HA. Instead, I use Reverse proxy (in control panel - it's called Application portal) so that Synology is managing everything. That way, my local traffic is not encrypted and that resolved some issues with IoT devices, but everything external to my network is secured. You will need to add one line to configuration.yaml - trusted_proxy: - check documentation here for this: www.home-assistant.io/integrations/http/#trusted_proxies But if you want to use it like you wrote above, you'll need to froward 80/443 port on router to HA IP address/VMM IP, to be able to create certificate (I think). After it is created, you can point it back to Synology if needed, or just close them until you need to renew certificate.
@@BeardedTinker Thanks mate. I have tried the reverse proxy but I am unable to create a certificate which comes up as invalid domain . Is it possible for you to share me the instructions please. TIA
@@ajaygauravelly4030 hmm - not an easy task via comments :) First - are you using DuckDNS or do you have your own domain? I've seen some people using this with DuckDNS, but my only experience is with my own domain name. What you would need to do is following: In Login Portal - Advanced (that's how it's called in DSM7) - Reverse Proxy, create new one. Name it, select HTTPS. type your domain name (I have subdomain to my main domain here) with port 443. In destination, select HTTP, use your VMM IP address, and port 8123. Click on Custom hearder TAB and select web socket - 2 new lines should be added. Then you need to add new certificate in Synology - get certificate from Let's encrypt - and type in all the fields. In Subject alternative name, I use my subdomain, I've created in previous step - you can use DuckDNS domain name. You can test, if you can also use subdomain (for example my.domain.duckdns.org) or not.
@@BeardedTinker i was using duckdns. However none worked. I restored again from backup and dont know what i did differently this time. May be opened 443 of the haip on the vm. Or ticked the little box on dsm settings to send http traffic to https or not sure what done the trick but the external duckdns url is working fine. Or may be i also switched off the raspberry pi where my HA was running previously. However i stopped the server of HA so wasnt sure of the external url was getting the auth from that one. Eitherway it is working fine now but asusual a great installation video from you. Subscribing now. Please continue the good work
Thank you for this Video I was trying it myself but couldn't get it working I will try the way you showed I have just one question about all that How do you setup ssl certificate, because you can't do it like you used before with the synology automativ task ...
There are two ways you can do it - one is to use DuckDNS addon in Home Assistant, and go that route. Other option is to use Synology SSL and copy it using Samba share to /ssl folder in VM. I think that this can be done using Task scheduler, you just need to map permanently this folder to Synology. Still looking in how to do that.
To add on this - if you install samba addon in VM, make sure that in configuration of SAMBA addon you change compatibility_mode: true (default is false). Then in Synology in File Station, you can use Tools - Mount Remote folder - CIFS Shared Folder. There just type IP_ADDRESS of VM with ssl folder - for ex. \\192.168.1.201\ssl This will mape ssl folder inside VM to \volume1\docker\ssl - and that's it. You can use Task scheduler to copy certificate from Synology to VM.
You just connect with extension cable in any port. Click on edit VM. Make sure USB 3.0 support is enabled, and from the list of available devices select stick. This is all that should be needed to add it in VM on Synology.
Great video and loving all of your content. I have a Synology NAS that doesn’t support VMM and have been running core. I have found a compatible version of VMM that I can load, but Open vSwitch option is not available. Do you know how to work around this or enable on synology NAS DSM 7? Thanks.
Thank you for your comment Alan! 😃 What model do you have? You need vSwitch for VMM, that one of few requirements. Maybe for your model there is a workaround.
Check this thread - midway there is a command on how to enable it. community.synology.com/enu/forum/17/post/109425 It will not show in network configuration, but should be visible in VMM after you install it.
@@BeardedTinker Thanks i've read the post and it looks promising, but as a newbie i'm not sure I will be able to use ssh/Putty to change the config file. Hopefully a bit of further research will show me what commands I need to write and how to locate the file on the NAS.
Love your videos. Is there any reason why you're using the "Home Assistant" network and not the default VM one? If so, do you just add it in VMM with the '+' sign?
Thank you for your comment Glen! Really much appreciated 😄 Just had same question on Discord - for some reason a lot of people were recommending to create new network. I just didn't have to test it and went with that. But you are right - Default VM network is also external network, and it should work with it without a problem. And even if it doesn't, just adding it alter on is option (both creating new network and assigning to VM).
@@BeardedTinker I did create one as well, I see on here how to do that on step 4: community.home-assistant.io/t/installation-on-synology-virtual-machine-managager/281608
This is fantastic. Thank you very much!. All I need to do now is work out how to convert my DS415+ with 23.6TB and 13.6TB data to BTRFS. I'm dreading it.
Ohh, yes... That can be an issue... I did convert it - but I wouldn't call it conversion - moved all data OUT, killed config and started from scratch :( Thanks for the comment!!!
Yes, after you moved everything and it's working. You can go in package centre - stop there hass.io package, check in Docker that all related containers are stopped and then remove the package.
Now I have my HA running on RPI4. I want to upgrate its hardware, after I added a lot of automations, integrations and starting to get into Frigate and Deepstack (one camera at the moment). So I have Synology NAS 920+ with 4GB RAM. It is also used as backup server and a Plex server. My dilemma is if I should buy more RAM for the Synology, and install HA on it in VMM like in this video OR buy an Intel NUC and install HA on Proxmox, and also get into the world of home server and maybe have some more projects on it. What do you think? Thanks
I you want to got with Frigate, I would definitely recommend Intel NUC or similar device. I have run Frigate with Google Coral on DSM 6 and DSM 7 - but not in Docker - used VM HA with Frigate VM. It does work, most of the computing is done by Coral, but on DSM 7 in VM I have issues with Coral stick disconnecting.
Thank you, i followed all your steps, first installing HA core in a docker container, then installing HA supervised in a VM in synology. However I have a question about port forwarding. Currently I have port 80 & 443 forwarded to my synology VM, and have my synology https for my DSM. In HA i have NGIX running for its https, its been running fine for a month, but now i have to renew a certificate in DSM and it is becoming a bit painful. What would a better setup be?
Did you try using nginx in Synology? It has one that's already embedded in it? It should allow you to secure external access to HA, custom domain for it but also simpler way to manage SSL certificate for all services that require it?
Great Tutorial. I was able to migrate to VMM following your video. I am only missing one thing, the update of the SSL certificate for Home assistant. With Docker, I had a scheduled task which copies the certificate files from the synology folder to the hassio folder. ¿How can this be done with VMM without using an external PC?
I've completely removed SSL from Home Assistant. Instead, I'm using revers proxy on Synology that uses subdomain. That way I can access it both internally and externally via HTTPS connection, while I still can use internally in the network HTTP for some integration.
Thanks for sharing... hadn't realised the package development has stopped (not surprised, took a lot of effort to maintain. How have you found the performance since switching from native Docker to VM? Was was your CPU and RAM loads with your previous instance of HASSIO vs. running on a VM?
This is my recording setup - not Synolgoy but Xpenology on very old HW. I did see decrease in performance - everything is a bit slower then it was before. Waiting for new Synology to test there - and I'll definitely do comparison of Docker + hass.io (just for test) and VM.
@@BeardedTinker A quick update... I made the leap from Docker to VMM and really happy with it. Not much additional CPU power than previously and I used the opportunity to upgrade RAM... so all good... or nearly! I notice a lot of people are having Conbee II and other USB devices disconnect on reboot (further info community.synology.com/enu/forum/6/post/130745?page=2&sort=oldest ). Have you had similar issue and if so, how did you get around it? Thanks as ever!
Congrats! Nice... I really love how my system works. You are right on this one. After Synology reboot device is detached from virtual machine. I've seen some posted comments that if you change from USB 3 to USB 2.0, this doesn't happen. Haven't tested it But also, I don't reboot my Synology. It usually has very long time between reboots. DSM updates are usually reason for reboot.
I've stopped using it. A year or so back HA optimised database, introduced long term statistics and I didn't see a reason to keep external database anymore. I did use MariaDB package and it worked well up to that point, but it's been removed since and, as I said, I'm not using it anymore.
Not really sure - I see a lot of people on forums with same question in regard to bluepy. Intention of HassOS is to keep everything clean to ensure that it's stable. You could try using terminal addon to access OS and install by hand.
I'm struggling with this. I was hoping to learn how to migrate. I see how to download and perform a complete fresh install. I also see how to import the snapshot. You emphasise that it's the snapshot I create previously, that I did create it previously and download it to my PC. Further back in the video you emphasis how important it is to create the snapshot. But I can't find anywhere that you create the snapshot, or copy it to the PC. So, I get the immigration, but not the emigration. Where's my Snapshot saved, please? Can you help?
When you go to Supervisor and tab Snapshots, all snapshost are there. In folder structure, it's usually /hassio/backup folder inside Home Assistant - you should see it if you browse folder where HA is installed. I download it to my PC as backup or precaution not to delete snapshot and lose what I have.
Thanks for the help , I have it running now on a VM 👍🏼. How can I now apply a certificate to the VM using my current domain and cert that I have on my NAS? I’m using namecheap for my domain and ssl cert.
Still haven't done it for my test setup, but it should be "easy". You need to map internal /SSL folder by using SAMBA to your Synology. And then, creat script (I use for that Tasks in Synology) to copy content of SSL folder to that folder. After you run it for the first time, you just need to enable it in Home Assistant. You can use parts of my Let's encrypt video for "guide" but it's missing SAMBA part.
@@BeardedTinker Thanks for your reply. I was able to do it yesterday using a reverse proxy on the synology and using the same certificate that I already have on the NAS from Namecheap. I'm dealing now with the Nest integration which is a nightmare. :)
BT with the new DSM7 update available, would running HA in VMM still be your recommended install? I'm still on DSM6 with HA core in docker and holding off at the moment due to the USB driver issue, but want to update when a good option is in place
If your Synology supports VMM - definitely. But, As you said, I'm still holding off upgrading to DSM 7 until USB problem is solved with more permanent solution (and also until there is availability of drivers for some Zigbee sticks). TBH - I'm not just waiting for that, usually there are some issues with new major releases that will show up in next few weeks in specific cases. This has been the case with DSM 6 and DSM 5 in past. I'll probably not update my main setup for months to DSM 7.
@@michaelbreitkreutz6257 me too. I never moved to Moments because it was not suitable for my (family) needs, I'll be testing it over the weekend in VM DSM7 just to check how it works and how are files and permission handled.
Hey man, great video - rly appreciate this one after seaching the whole web for complete guides. One question I haven't found an answer to yet - how do I backup my HA manually if I don't have the snapshot function. I already tried downloading the config-folder with everything in it out of my Docker folder from my NAS, zipped it to a .tar-archive but that just results in an error, when I try to upload it to my new VMM-HA-version. Do you know how to solve this? Regards
You can't create snapshot file by hand. I think. But process that you did is what should be done. Pack everything in tar/zip including hidden files and folders (starting with . too). Then you unpack by hand in config folder in VM. Just overwrite everything there. You can probably do that with Samba add-on.
@@BeardedTinker Thanks a lot - that worked quite well. Now I'm just struggling witht the remote access - I already watched your video about it, but kinda think there is smthn wrong with my router (or with me :D), since it just won't work. You don't happen to have knowledge dealing with a FritzBox, do you?
@@maximilian.guedelhoefer I've moved my setup to new Synology machine, and completely overhauled my setup in terms of external access. Instead of securing and using SSL directly on HA, I'm now using Synology Reverse proxy - this way, I don't need to open any (additional) ports for HA - just need to make 443 open (if you chose so) and traffic is then forwarded to HA internally. By doing so, you avoid any possible issues with router, as most of them allow you to forward port 443 to Synology.
@@BeardedTinker That's a good idea. I'll try that - hopefully that works. Also thought about using the Nabu Casa, bcs then the usage of Alexa is also pretty easy.
@@BeardedTinker Hey, I've tried many things untill I noticed that I don't have a public IPV4 anymore - thanks to my provider. So I think I'll stick with Nabu Casa - very convenient and works with Alexa like a charm. Thank you for you help very much :)
Hello, at my place, the installation went well, but there's an issue with disconnecting Conbee 2 from the virtual machine randomly. Do you have any idea how to deal with this? I see that many people online are facing the same problem, but I don't see any sensible solutions.
I've never had chance to play with Conbee. Other stick I've tries (sales.sh cc2652RB, SkyConnect, Sonoff Dongle-P) worked without any issue or disconnects. I had problem with Google Coral, but I was more of playing with it than actually needing it - and never figured out why it was disconnecting. Some say to connect via USB hub that' externally powered, but it didn't work for me.
Any idea on how to successfully move the HA datadisk to an external SSD? I'm running HAOS on a DS218+ VM. My Synology has 2 4tb ironwolf NAS hdds, which slows down HA startups, etc. Synology doesn't allow you to run a VM on an external drive. So I'm attempting to get around this by moving the datadisk to an external SSD. I attached a 240gb SATA SSD to the Synology Usb port and mapped it to the VM. I can see the SSD in HA supervisor listed as "sdb" and "sdb1." However, when I attempt to "move the datadisk" to the SSD, Supervisor doesn't recognize the external drive. I tried manually via the CLI as well to no avail. Running "os datadisk list" also doesn't show external SSD, and when I enter "os datadisk mov /dev/sdb" I get an error saying my ssd isn't a drive. Any ideas? The inability to use an SSD in VM is what is keeping me from migrating away from my RPI4.
Never tried, but you should be able to create second storage pool with sad connected to esata port. Than just use that second storage pool as VM drive. It should be fully support, but I haven't done this or tested it
@@BeardedTinker unfortunately, it appears you have to purchase Synology’s official expansion unit in order to create another storage pool via the esata port. Some one found a work around a few years back by using the terminal and editing DSM so it viewed the esata port as an internal drive, thereby allowing them to use ssd caching on an external drive, but I’m not adventurous enough to try it now that we’re on DSM 7.1. I’m also too cheap to shell out $500 on an expansion unit for a 4 year old NAS lol. Maybe I’ll purchase a 4bay unit when the new 2022 models are released and use 2 bays for hdd and the other two for ssd. We’ll see lol #firstworldproblems. Thanks anyway, and keep it up - I enjoy your tutorials!
@@BeardedTinker I decided to take the plunge and try the work around/hack. Happy to report that it worked, and was actually pretty simple thanks to some helpful tips on Reddit. All I had to do was make some very minor changes to these two files (/etc/synoinfo.conf /etc.defaults/synoinfo.conf). Upon reboot, the NAS detected my 1tb ssd connected to the esata allowing me to make another storage pool. Home Assistant VM is now up and running (much faster) on the ssd! Probably going to create another volume on the ssd and move my docker containers as well. Definitely making sure I have backups stored elsewhere as who knows what will happen when the next DSM update is pushed
Many thanks for the awesome guide. I hope to migrate my old Hassio this weekend. Still one question: at which point do you put the old Hassio out of order and how? I can imagine a conflict happening when you restore the snapshot in the old VM while the old Hassio is still running... Many thanks for the feedback.
Hi Robin! Thank you for your kind words! Really means a lot! In regard to hass.io - that's up to you. As this is VM and has different IP address then your Synology, you can even run them in paralel. My advice would be to get it up, check if all is OK and then shutdown/remove when you are satisfied on how all is working.
@@BeardedTinker , many thanks for the advice. I will start with the migration as soon as possible. I will keep you informed of the outcome. Kind regards
I tried the migration this evening. Everything went fine, until I restored the snapshot in it... For some reason I am no longer able to access my HA using the internal or the external URL... Do you know of any solution for this issue? Many thanks.
Can you access it by using home-assistant.local:8123 ? Or by accessing it via URL where you uploaded snapshot? In order to access it from outside you need to fix router configuration and point it to new IP address. Same for internal, you need to change it to match your new IP address, or change it in Supervisor.
@@BeardedTinker , I have tried both, but unfortunately I am not able to access it. I have removed everything again and am creating a new VM at the moment. Is it wisefull to stay on the same page where you upload the snapshot to be able to change all settings? Many thanks
Running a 718+ with 16gb ram. Also using docker (adguard, unbound, watchtower, heimdall, acme.ch, vaultwarden) Also im using synology photos and plex (with hardware acceleration). My nas has absolutely no problem running this stuff. Do you think it can handle a HomeAssistant VM with 4-6GB of ram? I don't want any slowdowns
You don't need 6GB for HA, 3-4 is more than enough. I can't tell you how it will behave on you rsystem. For me on 920+ with 20GB RAM it works great with bunch of addons + Surveillence, Photo and Emby running among others + bunch of docker containers. Difference between VM and Docker is that VM will reserve and not let other system parts use what you have given it - so depends on how many VCPU your system has and how much you've dedicated. Same goes for the RAM. With everything running, I dont see CPU usage over 60% and RAM is at max at 50%.
...but i made a mistake.The installation worked great but when changing the IP address in Supervisor i did something wrong (think i missed the /22) and i lost contact with HA. I assume i need to reinstall or do you see any other way? :-)
@@Novation681 can you ping it on old address or new one? Also, did you have SSL certificate enabled before in it or not? Depending on that, you maybe can access it by changing http to https and trying old and new IP address.
Do you know if there is a plan to create a Home Assistant Super Visor Docker Container? If there would be one in the works and released, would you go back to that?
No - it already exists, but only for supported environments. There is more to Supervisor then just Docker, other components of the environment are also crucial. But this is not the option you have to manual installation.
Fantastic! But the good news of seeing the title of the video came to a shock after realising I have to upgrade my RAM -I only have 2GB... 😳. That’s a whole week project for me (finding the correct RAM and doing the deed on a ds718+).
Hi there, there is one problem with vSwitch. Once docker instance is using macvlan to publish separate ip for adguard or pihole, switching on vSwitch deactivate the network adapter of Synology (no access). Rebooting Synology and switching off the vSwitch does help, but some network bridges on docker may not work unless they are recreated. Is there a tip on how to set macvlan and vSwitch to work next to each other? I've seen somewhere tip to name network ovs_eth0 instead of eth0 and it should work, but no manual on how to do so. So maybe this short movie next?
Hi Tom! Didn't know about that one, but I should have guessed or expected it. Can you check if now your network port has different name? For ex. instead of eth it is ovs_eth? If yes, you can/need to follow same process to create macvlan but this time use this newely created port. BTW - if you are using VM, you can use HA Add-on's PiHole or AdGuard and you will not need macvlan.
@@BeardedTinker After switching off the vSwitch, and bringing macvlan back to work, I can see eth0. Adguard addon within HassOS was not considered earlier, since I preferred separate docker images and direct access to AG. Too many dependencies. But... I'm using 720+ with 2 network adapters/ports, but so far I've been using only one (eth0). Wonder if separate network adapters can be an option: leave eth0 with current docker/macvlan setup, eth1 with vSwitch for VM? Can vSwitch be set for a single ethernet card only or both at once?
@@BeardedTinker Here is the solution: stop Adguard or Pihole container -> remove macvlan network -> turn on vSwitch -> identify new network addr (ssh to Synology - ifconfig command) -> most likely there will be now eth0 and ovs_eth0 (if you have two or more networ adapters you may find eth1 and ovs_eth1 respectively), those using link aggregation probably will find bond0 instead. Second one is your network adapter of Synology (before it was eth0) -> recreate macvlan with parent network ovs_eth0, -> change networks attached to adguard or pihole containers -> run your container -> the change should work like a charm. Next step -> install VMM. @BeardedTinker - I know it can be confusing, so if you find some spare time record a quick tutorial video how to run docker with macvlan and VMM at the same time for those who might want to migrate any container to VMM. Hopefully it helped. Have fun.
Hey man, some time ago I installed H.A. on my Synology NAS (DS716+II) with DSM 6 with your tutorial. It's been working for a couple of years without any problem, but I need to migrate the NAS to DSM 7 now. Will there be any problem with this or will the migration go smoothly? I would hate to lose my Home Assistant installation. Thank you
Hmm . 2021.9.3 - not sure that at that time there was a backup for Docker version of Home Assistant. It has been added, but I think it was newer version. But than again, if you run it in Docker, on Synology, you can create task to copy/archive contents of your configuration folder as that's all backup/snapshot does.
Help, I upgraded HA (installed on Synology/VMM) and Openzwave does not start anymore. Suddenly /dev/ttyACM0 (Zwave stick) not available anymore in HA. Did work untill the upgrade without any problems. Any ideas/tips?
Hey, what DSM version are you running? Did you make sure that you've enabled USB support and 7f yes, check if USB device is still listed and mapped to virtual machine.
If you want to run it in VM/VMM - you need btrfs - this is requirement for Virtual Machine Manager. From Synology documentation: Virtual machine data can only be stored on Btrfs volumes. And no, I don't know of a way to convert to it. I think it needs to be built from a scratch, which is a big issue of course.
It can take some time. Depending of course on the speed of the system (CPU, number of vCPUs and RAM). But I think it should finish in 60 minutes maximum. You can use Connect in VMM, to connect to console and there try commands "core info" or "supervisor info" to see what''s going on. Supervisor should be first to migrate, you'll see addons listed there.
@@BeardedTinker Thank you for the answer. Connect in VMM says ' Welcome to Home Assistant" :-). But no response on homeassistant.local:8123. What can be the problem?
@@hmaboes2226 try using IP address of Home Assistant (VM IP address) instead of homeassistant.local. When you connec to VM, and use root as name to login, it should show you first the IP address of the HA.
@@BeardedTinker well, after rebooting synology, stopping Hass.io from Frederike and starting Virtual HA my imported HA started and worked! However in your video you changed the IP address, why you do that? My 'old' HA-ip is the IP of the Synology itself, I expect problems changing the working IP into the 'old' one.
@@hmaboes2226 tht's strane - you can have both hass.io running and VM at the same time. But what puzzles me - are you saying that your Synology and VM both have same IP address - that shouldn't be possible and you must ensure that IP addresses are different. If using same IP address, you could and will see IP conflict - this can bring a lot of networking trouble.
For VM, using SSD cache slots are not recommended due to possible data loss. But you can use ssd drives in normal drive slots if you are concerned about the speed.
VM would benefit of cache slots if in read only mode. AFAIK read/write is not recommended as it can result, in case of power failure and write behind, to corrupted VM file But you also have option to add SSD instead of HDD in drive bay and create separate SSD only volume for VMs. That of course depends on number of drive bays you have free.
@@TwanJaarsveld1 officially, it's not possible. Hack version? Sure, but please be careful. It may stop working on update, if you have any other issues and contact support, you will receive no support until you remove this, etc. academy.pointtosource.com/synology/synology-DS920-nvme-m2-ssd-volume
Answer is yes, if you have VM running with OS that supports it. But the question really is, why? If you can run it directly on the host machine, that would be way to go.
@@BeardedTinker I have my docker and my VM on different Ip and I think as such when I installed the broad link manager on docker can’t find the devices. I am not sure how to solve this problem haha
If you are thinking about VM with HA, you can't run Docker there that is not already on the add-on list. Does broadlink manager show any devices? If not there is probably a network problem. Try solving that.
Hello. Everything worked very well but all the addons appear turned off and it doesn't allow me to start them. Yes I can uninstall and install but not start. They are all grey. Do you know how I can solve it? Thank you
Strange, but did you try to restart HA OS? Also, when you press start in AddOn, do you get anything in AddOn logs? Next step I would check is in logs - check to see if Supervisor has any errors (you can select what log is displayed in upper right corner)
There are few things you could do - first in VMM - if you click on Virtual Machine and in lower tab select Network, look there for MAC address and try to locate it on router. Next thing could be tro try and use homeassistant.local:8123 and/or homeassistant:8123 and after you finish configuring it you'll see IP address in supervisor: Third option could be to try and delete this image and download one from this URL: www.dropbox.com/s/1ev7g9xhck5bhw5/hassos_ova-5.11_syn-patch.ova?dl=1 This image contains fix and you will see current IP address both in network setting of VM and in General view.
Remembered one last thin - use Connect to connect to HA via terminal (in web) - there login - I think you need only to type root as username. There you can use 'network info' command and it will show you IP address.
Hello Bearded Tinker, I had reverse proxy working with docker. Now I switched to VM, I can't get it working again. I get a 400: bad request. Can you help?
That happens when you access it by IP address or via reverse proxy? Quick check. Did you change IP address in reverse proxy to new IP address that VM got? Did you enable reverse proxy in Home Assistant, as there was a breaking change in 2021.7 that requires it to be specified in configuration.yaml file? From notes: Home Assistant will now block HTTP requests when a misconfigured reverse proxy, or misconfigured Home Assistant instance when using a reverse proxy, has been detected. If you are using a reverse proxy, please make sure you have configured use_x_forwarded_for and trusted_proxies in your HTTP integration configuration.
@@BeardedTinker thanks for the help. I made a mistake, I used the File Editor after I copied all the files from docker to VM, the File Editor was working but I was editing the configuration.yaml of docker! I discovered it when the logs did not change no matter wat I changed in config.yam. Regards, Martin
Great video! I have done everything but still cant access my HA instance. There is no ip and when i search in my network there is no new ip joined either. Same ip with 8123 as port does not work aswell... I have tried this in a docker and that one is just the core and cant use supervisor and that sort of things. Anyone can help? Did something change in 5 months?
Thank you! It should work still without any change. Few questions: can you on your router or DHCP server see what address was assigned. Also in VMM, did you press Connect to try and connect to VM machine. It should then show you IP address of the server.
@@BeardedTinker Thats the whole problem. It does not sign any ip and when you connect it just fails. I have tried a windows 10 installation which works fine but this one does not. I have tried a few things. Old .ova file, your patched .ovs file in the commens which was corrupted it said and the newest .ova file on HA. I have also tried a .vdi but that one didnt work either.
@@Tmcmaster latest OVA image has fix for IP address, so you don't need to use one linked in description. Few things can be wrong in setup: - issue with vSwitch - but I believe that you have it enabled, so this should be OK - you selected wrong firmware - check that firmware selected is UEFI in VM settings - IPv6 - some routers will assign IPc6 address, and there were some issues with it It's very hard to debug without seeing what you have. You can try and use Angry IP scanner to see if IP address was assigned and if it's visible.
Update: I have watched your video again and did something different. I just started the image after it was fully imported instead of saying to start automatically. This time i received a IP and it is starting now? Thanks anyway for your fast respsonse your video helped me to install this! Gonna check later today if it is working or not :)
My Raspberry 4 died 4-5 days ago and now I have tried to learn virtulization; I already built Linux Mint with VirtualBox for testing. But there are also other solution (at least VMM, Hyper-V and Proxmox). Are you familiar with those and what you prefer? Anyway I need to buy second hand mini pc during weekend. What would be the specs? I have idea to buy old Lenovo ThinkCentre M920q Tiny: 6 CPUs, 16 GB, 512 SDD, Wifi + Bluetooth.
Depends on what you want to do with it - but in community, Proxmox seams to be most preferred choice. In terms of specs, this looks good. For any virtualisation platform, most important in number of cores/threads and RAM. But again, if you want to run just 1 or 2 VMs, this is OK depends, what else besides HA you'll run on it. I would prefer 8 cores and 32GB RAM as this has a LOT of extra capacity for other VMs. For just HA, this is way more than enough.
Sorry for late reply - busy Sunday. It depends a lot on the speed of the internet - I think it downloads around 1-2GB from the Internet. So it depends on speed you can get. But I think 2 hours is long enough. Not sure if this still happens, but it can sometimes hang and not refresh screen when everything is done - you can try refreshing web page or just remove everything from URL and use IP_ADDRESS:8123 to try and force load HA.
@@BeardedTinker thanks for the reply. Tried all that. Was going all day. Deleted it in the end. NAS only had 2GB memory so was wondering if that was causing it. Looked online for more memory and ended up buying a raspberry pi instead 🙈😂
Can you help me? My DS VM log: The network interface [Syno] [BOND 1] has been disconnected. The virtual network interfaces on [Syno] [haos] are disconnected. In web browser "400: Bad Request" On phone app HA work.
Hard to help with just this info. Check if Open vSwitch is enabled. Also in configuration for VM, check what network is selected. But if it works on the phone, it should work from any device. See if maybe your IP address is banned on Home Assistant.
@@Qruxat as I said previously, this can be that IP address from your PC is banned. Check IP_BANS.YAML file if there is a IP address or not there. If it is, than this can be the issue. Other possibility but I doubt it, could be that you are using reverse proxy and didn't check breaking changes for 2021.7 - but as I said, I doubt as error would be different and it would also stop working on your phone. Bond disconnected error is usually shown when cable from network is disconnected (or you turn of the switch).
I attach a few comments: - if you use the correct * .ova snapshot, the Guest agent will also be installed. This Guest agent will ensure that you can correctly shut down VM-HA directly from the VMM environment and not just from the HA environment as shown in the video - it is also possible to use the image * .qcow2, but you must first import it in VMM via the Image section and then use the Virtual machine Import from disk image ... - on the official page www.home-assistant.io/installation/alternative is a *.ova file without Guest agent but a file * .qcow2 is OK( with Guest agent )
Hey Andrej, thanks for the comment! 5.13 version of HassOS has fix for this (but it's not out yet) as fix from Fredrick for ova was pulled. Problem was that ovf:id used had an error (wrong ID number) and because of that Synology couldn't correctly identify OS and install Guest OS. github.com/home-assistant/operating-system/pull/1233
Hi! Thanks for your videos. They are great and very useful... Could you record video how to migrate (database of) InfluxDB from 1.8 to 2.0? After update by watchtower when i open url of InfluxDB i see initial configuration :( I know that i have to migrate DB (docs.influxdata.com/influxdb/v2.0/upgrade/v1-to-v2/), but it's too difficult to me. Thanks in advance. Greetings from Poland!
Great video, I set everything up previously by watching this video of yours th-cam.com/video/jtVelxopKTM/w-d-xo.html I have finished setting up everything in the VM but how do I uninstall everything I installed in the docker container using putty like Home-assistand, Influxdb, nodered, portainer and watchtower? I want to install nodered for sure but not exactly sure at this point if I need the others listed?
Thanks Justin! If you've already setup VM and moved everything there, cleanup is simple. In Synology Docker UI - Containers - just remove all containers you don't need anymore. That will deactivate them and delete configuration. Also in Docker UI - images, you can delete all downloaded images you don't need. You have to do this as second step as it shouldn't allow you to delete image if there is Docker container running. And as last step, in File Station, delete subfolders (probably under /docker folder) that you don't need anymore. You can also leave them for now and do this at later date, just to have files (configuration files) available for now, but you can remove them too.
Hello, at 9:50 you made a reference to "already created home-assistant" did you cover this in previous videos ? Or Am I just missing anything :)
No, I haven't. I've jsut pressed on create new netowkr in network section, named it home-assistant, left external as setting and that's it. It's identical to default one.
@@BeardedTinker Thanks! I had the same question going through setup just now.
As usual, great video! It helped me a lot to swith HA install to VM. I just had issue with ssl, workaround was not to click the ssl box when configuring HA from the image.
I know how much effort is to keep a channel like this running, you put a lot of work for the community, kudos for that.
Thank you very very much for the comment!!!! Really much appreciated.
My bad, forgot to mention that you can restore partial thing from snapshot and possible problems with SSL.
@@BeardedTinker No worries, good for me to play around and learn a little instead of following idiot proof procedures! Thanks again
Brillant!, just what I was looking for for a way to keep Hassio on Synology NAS and turns out, you are the point man for Home Assistant and keeping the Synology NAS relevant. Great work and THANKS....
Glad it was helpful! Thank you for your comment very much!
Great video. Explanation was very clear. Managed to install home assistant 2021.6.2 with a Synology DS218+. Thank you!
Glad it helped! Thank you for the comment!!!!!
Hi, is it running well on DS218+ ?
Thanks
Hello and very many thanks for creating and uploading this video. I’ve been tinkering with HA in a Docker container on a Synology NAS but couldn’t get very far as I didn’t have access to the Supervisor mode. I’ve not used VM before but your tutorial has got me up and running. As your video finished I got the log on screen for HA. As I’ve not created many entities within the Docker I’ve opted to start afresh. One useful addition is to click the ‘Connect’ tab in the VMM ‘Virtual Machine’ menu (second from top with ‘Overview’ above). It seems to display some useful diagnostic information. Mine tells me that the VM is ‘Waiting for the Supervisor to startup…’, which makes sense as this mode is not yet enabled in HA. I presume it’s accessing / downloading the additional bits. Anyway today is a good day at school!
Glad you liked it. Yes, it will take some time after you start installation process until login screen shows up - it can be 30-60 minutes.
Thanks for showing it without docker!
Thank you verry match! After your instructions at last I have HA supervised on Synology DS220+ with extended 4GB RAM(not original Synology, but Crucial 4GB DDR4 2666 SO-DIMM), SONOFF Zigbee 3.0 USB Dongle Plus, and so far every thing is work find!
Thanks!
Great!!! Nice you got it working!!!
So cool! It works like a charm. The only thing what was a little bump for me was this. After you restore your backup it would show an error "page not found". I reinstalled and again, same problem. BUT! The simple solution... I use https on my Pi backup and the initial installation runs on, yes... http. So, after accassing HA on the VM with https, tadaaaa, there it was. After grooming a few minor things it really works well for me on my DS720+. Bye bye RPi3, welcome Synology. ;-) Thanks for the nice and clear video!
Glad you got it working! Thanks for the comment Richard
Fantastic, I am so glad you made this video, really awesome. I was just in time too, because this week the Supervisor failed to start up so no latest snapshot for me. Luckily I could use a 3 weeks old one for that (from the file system) without any problems. I struggled a little bit to connect to the VMM with Admin credentials while the standard usere credentials worked fine. Strange thing, but after finding the new IP adess it went smoothly from there. Super happy here!!
Really glad to hear it and best thing is that you are now on supported system 😉
Great videos on HA. Another option, the one I have working is to use VM to install debian and the install on it HASSIO. You can install Synology tools with this option.
Thanks for the tip. Btw, in version of hassos 5.13 ova, this will be fixed. Error with id has been corrected by Fredrick and his pull request has been merged.
@@BeardedTinker if someone is interested install the lightest version of debian, only cli. Then install HASSIO on debian:
sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y
sudo -i
apt-get install -y software-properties-common apparmor-utils apt-transport-https ca-certificates curl dbus jq network-manager
systemctl disable ModemManager
systemctl stop ModemManager
curl -fsSL get.docker.com | sh
curl -sL "raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh" | bash -s
Configure reverse proxy and let's encrypt for https access. works like a charm, very fast on DS920+ ;)
The question is, what is the lightest and most versatile solution ...
Thank you for this!!!!
In regard to litest version - I think that still this should be pure Docker. It doesn't have any extra overhead that VM has with OS. But it's not as simple as running VM or HassOS
Again a great tutorial, if only I had this tutorial when I started with this half a year ago! FYI over the months my Home Assistant has gotten pretty big and it runs fine with 2GB Ram. Image recognition add-ons such as DOODs are pretty slow thought but I guess that's more CPU related.
Thanks 😂 Adding RAM can help if you have extra. For DOODS extra RAM but also faster CPU will definitely help.
Thanks again for this video. I am wondering how this setup handles updates. Does HA update itself or it's some kind of a manual process?
If there is any update available, in Supervisor menu you will see it. No matter if it's HA, Supervisor or OS. You just click on update and that's it.
Everything available from UI.
@@BeardedTinker perfect, enjoying it so far
Hi, Great helpful video.
I had issues with networking without having the guest agent running. While I understand that will be added to the ova package in a future version, I ended up getting it running with the linux VMware workstation image (.vmdk). If you import this into the VMM as an image first, and then create the virtual machine from the image, you get the guest agent running fine and it solved all my networking issues.
Also, if your backup is greater than 1Gb, you cannot install directly from the setup screen (I have a decent sized database in the backup). The work around is to get HA running without restoring then set up Samba as you describe. You can then copy the backup into the backup directory on the VMM and restore from that file within the supervisor screen. Hope this helps anyone that gets stuck.
Thank you for the comment Brad! What kind of network issues did you have? Usually Guest OS agent will not resolve any issues, it will just give access to host to see inside info (such as IP address) and allow some further control (for ex. power down etc).
@@BeardedTinker The virtual machine was behaving as though it could not see the DHCP server and never got an ip address, even though I could see the VM MAC address from that server. I'm not sure what was causing that - whether synology was blocking the DHCP packets because the mapped ethernet port has a fixed ip or something.
I ended up fixing it by pushing the VM onto the second ethernet port on my NAS and leaving everything on that port with DHCP. The guest OS agent may not have solved the issue but it makes a difference to trying to diagnose what is happening!
Great video. I have been trying to utilize the 2 ports on my synology, where they are on 2 different vlans. I have that set up in my vm on the server I am wanting to migrate from, but cannot figure it out just yet.
Sorry for a late replay. I don't use VLANs in my setup. As for ethernet ports, I did create two different setups.
One is to use combine 2 ports into single IP to reduce possible bottleneck there. And on another setup, I have one port dedicated to Synology main services, while other port is dedicated to VMM.
Great job with this video. One question. How would you go about installing the Qemu guest agent?
Thank you very much for your comment and great question. To be honest, with HA image, I'm not sure...
I know how to install it in other VM's but with limited access HA is giving to users on system level, not sure.
Currently, the easiest way to do it would be to use image Fredrick has prepared that has guest tools active.
So, make a snapshot of your installation and make sure to download it. Stop current VM, install image from this link (fisrt post): community.home-assistant.io/t/installation-on-synology-virtual-machine-managager/281608
Start it and import in it snapshot.
Thanks for the great video. I was able to set up a Home Assistant VM and get some add-ons working, but i have not been able to mount a NAS shared folder on the VM. For example, I want to run Plex and let it use my music library on the NAS which has a different IP. I have set up Samba and NSF sharing but still can't mount the library on the VM. Any advice would be appreciated.
You can try using shell command for this.
This should work in both HA and with Synology:
shell_command: mount_nas_folder: mkdir -p /media/music;mount -t cifs -o vers=3.0,noserverino,username=xxxxx,password=xxxxxxxxx,domain=xxxxxxx //xxx.xxx.xxx.xxx/music_folder /media/music/
This would create /media/music folder and map it with /NAS/music_folder
This is not my command, but it should work.
@@BeardedTinker Thanks, I will give it a try.
I am learning a lot from your wonderful video. Thanks. Currently I have just set up HA core over docker. Would it be better for me to run on VM - synology to get the supervised version to start from the beginning? Shall I stop the docker HA core version first?
Thank you very much for your comment!
This is excellent question. No, you don't need to stop it. VM will start in new machine, with new IP address, so you can keep your Docker version running until you are satisfied on how VM version is working.
And yes, VM - if your system is powerful enough to run it, is definitely better option then Docker.
Unfortunately, not all systems can run it or have enough resources.
And you can copy your existing CORE version configuration to HA machine, after you finish installing it, so you can reuse all your configuration that you have.
@@BeardedTinker Thanks so much for your advise. U r a gentleman and a scholar.
watching your video I think my sonology nas should be ok. I am using the DS920+ with 12G Ram
It should be perfect.
since "shutdown Host" does not exist anymore what is the new alterntive?
It's still there - in power menu - advanced options. Shutdown system.
@@BeardedTinker okay so now it's called shut down system instead of shut down host. Got it. Thank you! You're awesome!
@@quasimodo1427 Thank you :)
You don't happen to have a tutorial on going from Synology VM to an x86 setup by chance, do you? Looking to move my HASS off Synology to my new Beelink mini PC. Your tutorials have always been helpful!
No, I don't have it - yet. Will have one in few weeks as I'm preparing to review one x86 based device.
But the process should be the same. On x86 - you download and install ISO image from HA web site and just import backup from old system. That should be it! Or of course, if machine is powerful enough, get proxmox and run VM with HA on it. :D
@@BeardedTinkersmart man. Went the virtualbox route and I'm up and running but interested in proxmox as a lot of ppl bringing that up as of late. Look forward to the next vid!
Thank you very much for the super good instructions .... Even a dummy like me can move from a Raspberry to my Synology ... and only one server is running at home. Yeah ...
Now the only thing missing is the Synology Guest Tool ... and it would be even more brilliant ...
As information for someone who still wants to try it. I used a DS220 + with 6GB of RAM and currently 3GB of RAM for HomeAssistent ... and it runs great.
But I will try to expand the RAM. That is probably possible.
Thanks again for the great job.
Thank you for your comment - glad you got it working! I still haven't managed to play and try to get guest tools working, but that should be possible. Just have to get a bit of time to try.
If you do get more RAM, that will be great - here RAM definitely improves overall performance. Just Google around a bit to insure you get one that is supported.
DS 415+ that’s the model I have. I was wondering how well it runs with 8gb RAM and DSM7? Any sluggishness slow downs etc. Also I couldn’t figure out why the VMM package wasn’t available. Perhaps it’s not recommended for the 415+ because of the hardware? You show a couple different Synology models in your videos what model would you recommend or are you using today? Thanks!
All my videos are recorded on DS415+ .
Last 6 months or so it's running on VMM and it's also on DSM 7.
Total amount of RAM is 10Gb RAM. It is not officially supported but installing is easy. You need to select similar model and download package for Synology site.
@@BeardedTinker Ok, so I just need to choose possibly a 918 or 920 As a comparable model for the VMM ? I’d like to eventually upgrade to a newer model but not sure what to choose. I like the 920 but it’s an older model I was going to wait for the 921 or go with 1621+ or xs. Would appreciate your input. Thanks !
@@markstanchin1692 my main setup is running on 920+ - that's 2020 model, that was release in mid of last year. 1621+ is about 500$ more expensive then 920+.
I've added 16GB modul to mine and now run it with 20GB.
9xx version can have up to 9 drives (with rexternal drive bay), while 16xx can have total of 16 drives - 6 internal + 2x5.
Thank you very much for your video. Only one question, when use the HASSIo package the IP of HomeAssistant was the same IP of the NAS. Now when I crate a new VM I can assign the same address of the NAS? Or there is a conflict? Thank you!
No, you can't use same address as the nice - this is now separate machine and has to have different IP address. And when you install it, DHCP should be default give it new IP address. You can change that IP address, but it has to be unique to your network.
@@BeardedTinker Thank you very much! All works like a charme!! Great job man!
That's great - congrats!! And thanks for the comment 😉
Hi
Thanks once again for a wonderful video. I have migrated my home assistant from RPi to a Synology NAS. however my dcukdns ad don configure dont he pi is not working on the Synology VMM home assistant instance. Would you be able to suggest this? I have tried adding duckdns in DDNS menu however i have a message failed to register the ip the ip adress via ddns. My dsm is 7.0
I'm using same setup as yours - but I'm not using any addon on HA. Instead, I use Reverse proxy (in control panel - it's called Application portal) so that Synology is managing everything. That way, my local traffic is not encrypted and that resolved some issues with IoT devices, but everything external to my network is secured. You will need to add one line to configuration.yaml - trusted_proxy: - check documentation here for this: www.home-assistant.io/integrations/http/#trusted_proxies
But if you want to use it like you wrote above, you'll need to froward 80/443 port on router to HA IP address/VMM IP, to be able to create certificate (I think). After it is created, you can point it back to Synology if needed, or just close them until you need to renew certificate.
@@BeardedTinker Thanks mate. I have tried the reverse proxy but I am unable to create a certificate which comes up as invalid domain . Is it possible for you to share me the instructions please. TIA
@@ajaygauravelly4030 hmm - not an easy task via comments :)
First - are you using DuckDNS or do you have your own domain? I've seen some people using this with DuckDNS, but my only experience is with my own domain name.
What you would need to do is following:
In Login Portal - Advanced (that's how it's called in DSM7) - Reverse Proxy, create new one.
Name it, select HTTPS. type your domain name (I have subdomain to my main domain here) with port 443.
In destination, select HTTP, use your VMM IP address, and port 8123.
Click on Custom hearder TAB and select web socket - 2 new lines should be added.
Then you need to add new certificate in Synology - get certificate from Let's encrypt - and type in all the fields.
In Subject alternative name, I use my subdomain, I've created in previous step - you can use DuckDNS domain name.
You can test, if you can also use subdomain (for example my.domain.duckdns.org) or not.
@@BeardedTinker i was using duckdns. However none worked. I restored again from backup and dont know what i did differently this time. May be opened 443 of the haip on the vm. Or ticked the little box on dsm settings to send http traffic to https or not sure what done the trick but the external duckdns url is working fine. Or may be i also switched off the raspberry pi where my HA was running previously. However i stopped the server of HA so wasnt sure of the external url was getting the auth from that one. Eitherway it is working fine now but asusual a great installation video from you. Subscribing now. Please continue the good work
@@ajaygauravelly4030 glad you got it working! And thank you for the comment! :)
Thank you for this Video
I was trying it myself but couldn't get it working
I will try the way you showed
I have just one question about all that
How do you setup ssl certificate, because you can't do it like you used before with the synology automativ task ...
There are two ways you can do it - one is to use DuckDNS addon in Home Assistant, and go that route. Other option is to use Synology SSL and copy it using Samba share to /ssl folder in VM.
I think that this can be done using Task scheduler, you just need to map permanently this folder to Synology. Still looking in how to do that.
To add on this - if you install samba addon in VM, make sure that in configuration of SAMBA addon you change compatibility_mode: true (default is false).
Then in Synology in File Station, you can use Tools - Mount Remote folder - CIFS Shared Folder.
There just type IP_ADDRESS of VM with ssl folder - for ex. \\192.168.1.201\ssl
This will mape ssl folder inside VM to \volume1\docker\ssl - and that's it. You can use Task scheduler to copy certificate from Synology to VM.
Hi, great video. How connect sky connect USB? with VM
You just connect with extension cable in any port. Click on edit VM. Make sure USB 3.0 support is enabled, and from the list of available devices select stick. This is all that should be needed to add it in VM on Synology.
Great job ! Thank you for all the nice videos of your channel !
Thank you for your comment!!
Great video and loving all of your content. I have a Synology NAS that doesn’t support VMM and have been running core. I have found a compatible version of VMM that I can load, but Open vSwitch option is not available. Do you know how to work around this or enable on synology NAS DSM 7? Thanks.
Thank you for your comment Alan! 😃
What model do you have? You need vSwitch for VMM, that one of few requirements. Maybe for your model there is a workaround.
@@BeardedTinker HI Thanks for the quick reply, the model is a DS418Play. Thanks for your assistance.
Check this thread - midway there is a command on how to enable it.
community.synology.com/enu/forum/17/post/109425
It will not show in network configuration, but should be visible in VMM after you install it.
@@BeardedTinker Thanks i've read the post and it looks promising, but as a newbie i'm not sure I will be able to use ssh/Putty to change the config file. Hopefully a bit of further research will show me what commands I need to write and how to locate the file on the NAS.
I used this to do a first install, but i can't see the supervisor. How do i get that?
With version 2021.12 - Supervisor has been moved to Configuration panel - it's called Add-ons, Backups & Supervisor.
Love your videos. Is there any reason why you're using the "Home Assistant" network and not the default VM one? If so, do you just add it in VMM with the '+' sign?
Thank you for your comment Glen! Really much appreciated 😄
Just had same question on Discord - for some reason a lot of people were recommending to create new network. I just didn't have to test it and went with that. But you are right - Default VM network is also external network, and it should work with it without a problem.
And even if it doesn't, just adding it alter on is option (both creating new network and assigning to VM).
@@BeardedTinker I did create one as well, I see on here how to do that on step 4: community.home-assistant.io/t/installation-on-synology-virtual-machine-managager/281608
Yes, I have same thing in video, but I'm not 100% sure that it's needed...
This is fantastic. Thank you very much!. All I need to do now is work out how to convert my DS415+ with 23.6TB and 13.6TB data to BTRFS. I'm dreading it.
Ohh, yes... That can be an issue... I did convert it - but I wouldn't call it conversion - moved all data OUT, killed config and started from scratch :(
Thanks for the comment!!!
Worked perfect! ! Can I shutdown all the containers for home assistant in the docker and remove Hass.io from synology?
Yes, after you moved everything and it's working. You can go in package centre - stop there hass.io package, check in Docker that all related containers are stopped and then remove the package.
Now I have my HA running on RPI4. I want to upgrate its hardware, after I added a lot of automations, integrations and starting to get into Frigate and Deepstack (one camera at the moment).
So I have Synology NAS 920+ with 4GB RAM. It is also used as backup server and a Plex server. My dilemma is if I should buy more RAM for the Synology, and install HA on it in VMM like in this video OR buy an Intel NUC and install HA on Proxmox, and also get into the world of home server and maybe have some more projects on it.
What do you think?
Thanks
I you want to got with Frigate, I would definitely recommend Intel NUC or similar device. I have run Frigate with Google Coral on DSM 6 and DSM 7 - but not in Docker - used VM HA with Frigate VM. It does work, most of the computing is done by Coral, but on DSM 7 in VM I have issues with Coral stick disconnecting.
Thank you, i followed all your steps, first installing HA core in a docker container, then installing HA supervised in a VM in synology. However I have a question about port forwarding. Currently I have port 80 & 443 forwarded to my synology VM, and have my synology https for my DSM. In HA i have NGIX running for its https, its been running fine for a month, but now i have to renew a certificate in DSM and it is becoming a bit painful. What would a better setup be?
Did you try using nginx in Synology? It has one that's already embedded in it? It should allow you to secure external access to HA, custom domain for it but also simpler way to manage SSL certificate for all services that require it?
@@BeardedTinker Thanks that was the first thing i tried it with reverse proxy, it works on DSM but not HA, probably config problem on my side.
@@derekchan6972 it should work. I've tested it few times and will be using it in future.
Currently migrating my setup to new device.
@@BeardedTinker Thanks I think i have it working, I was missing websocket from the custom header tab.
@@derekchan6972 glad to hear it!
Great Tutorial. I was able to migrate to VMM following your video. I am only missing one thing, the update of the SSL certificate for Home assistant. With Docker, I had a scheduled task which copies the certificate files from the synology folder to the hassio folder. ¿How can this be done with VMM without using an external PC?
I've completely removed SSL from Home Assistant. Instead, I'm using revers proxy on Synology that uses subdomain. That way I can access it both internally and externally via HTTPS connection, while I still can use internally in the network HTTP for some integration.
Thanks for sharing... hadn't realised the package development has stopped (not surprised, took a lot of effort to maintain. How have you found the performance since switching from native Docker to VM? Was was your CPU and RAM loads with your previous instance of HASSIO vs. running on a VM?
This is my recording setup - not Synolgoy but Xpenology on very old HW. I did see decrease in performance - everything is a bit slower then it was before.
Waiting for new Synology to test there - and I'll definitely do comparison of Docker + hass.io (just for test) and VM.
@@BeardedTinker thanks for info and great work on the channel :-D
@@rossicullen thank you very much 😊
@@BeardedTinker A quick update... I made the leap from Docker to VMM and really happy with it. Not much additional CPU power than previously and I used the opportunity to upgrade RAM... so all good... or nearly! I notice a lot of people are having Conbee II and other USB devices disconnect on reboot (further info community.synology.com/enu/forum/6/post/130745?page=2&sort=oldest ). Have you had similar issue and if so, how did you get around it? Thanks as ever!
Congrats! Nice... I really love how my system works.
You are right on this one. After Synology reboot device is detached from virtual machine. I've seen some posted comments that if you change from USB 3 to USB 2.0, this doesn't happen. Haven't tested it
But also, I don't reboot my Synology. It usually has very long time between reboots. DSM updates are usually reason for reboot.
Did you have any issues setting up MariaDB?
I've stopped using it. A year or so back HA optimised database, introduced long term statistics and I didn't see a reason to keep external database anymore. I did use MariaDB package and it worked well up to that point, but it's been removed since and, as I said, I'm not using it anymore.
@@BeardedTinker great info!!! Thanks very much
Great tutorial! I'm missing a python library called bluepy. Going nuts here - how do I install it in a VMM?
Not really sure - I see a lot of people on forums with same question in regard to bluepy.
Intention of HassOS is to keep everything clean to ensure that it's stable. You could try using terminal addon to access OS and install by hand.
I'm struggling with this. I was hoping to learn how to migrate. I see how to download and perform a complete fresh install. I also see how to import the snapshot. You emphasise that it's the snapshot I create previously, that I did create it previously and download it to my PC. Further back in the video you emphasis how important it is to create the snapshot. But I can't find anywhere that you create the snapshot, or copy it to the PC. So, I get the immigration, but not the emigration. Where's my Snapshot saved, please? Can you help?
When you go to Supervisor and tab Snapshots, all snapshost are there.
In folder structure, it's usually /hassio/backup folder inside Home Assistant - you should see it if you browse folder where HA is installed.
I download it to my PC as backup or precaution not to delete snapshot and lose what I have.
Thanks for the help , I have it running now on a VM 👍🏼. How can I now apply a certificate to the VM using my current domain and cert that I have on my NAS? I’m using namecheap for my domain and ssl cert.
Still haven't done it for my test setup, but it should be "easy".
You need to map internal /SSL folder by using SAMBA to your Synology.
And then, creat script (I use for that Tasks in Synology) to copy content of SSL folder to that folder.
After you run it for the first time, you just need to enable it in Home Assistant.
You can use parts of my Let's encrypt video for "guide" but it's missing SAMBA part.
@@BeardedTinker Thanks for your reply. I was able to do it yesterday using a reverse proxy on the synology and using the same certificate that I already have on the NAS from Namecheap. I'm dealing now with the Nest integration which is a nightmare. :)
@@charlesromney yes - that works great too and no need to sync certificates between VM and host!
i dont get supervisor with that image? What am i doing wrong
Yes you do. But supervisor doesn't exist as menu item anymore there. It is in Settings > System now
@@BeardedTinker oh ok, thanks :D where do i find the shut down button haha
Check in Settings - System - Hardware and than 3 dots on top right menu.
@@BeardedTinker thank you :D
BT with the new DSM7 update available, would running HA in VMM still be your recommended install? I'm still on DSM6 with HA core in docker and holding off at the moment due to the USB driver issue, but want to update when a good option is in place
If your Synology supports VMM - definitely. But, As you said, I'm still holding off upgrading to DSM 7 until USB problem is solved with more permanent solution (and also until there is availability of drivers for some Zigbee sticks).
TBH - I'm not just waiting for that, usually there are some issues with new major releases that will show up in next few weeks in specific cases. This has been the case with DSM 6 and DSM 5 in past. I'll probably not update my main setup for months to DSM 7.
@@BeardedTinker Yeah true, doesn't hurt to wait so will do the same, although I'm eager to start using synology photos!
@@michaelbreitkreutz6257 me too. I never moved to Moments because it was not suitable for my (family) needs, I'll be testing it over the weekend in VM DSM7 just to check how it works and how are files and permission handled.
@@BeardedTinker great idea! Interested to hear what you think
Hey man, great video - rly appreciate this one after seaching the whole web for complete guides.
One question I haven't found an answer to yet - how do I backup my HA manually if I don't have the snapshot function.
I already tried downloading the config-folder with everything in it out of my Docker folder from my NAS, zipped it to a .tar-archive but that just results in an error, when I try to upload it to my new VMM-HA-version.
Do you know how to solve this?
Regards
You can't create snapshot file by hand. I think.
But process that you did is what should be done. Pack everything in tar/zip including hidden files and folders (starting with . too).
Then you unpack by hand in config folder in VM.
Just overwrite everything there. You can probably do that with Samba add-on.
@@BeardedTinker Thanks a lot - that worked quite well. Now I'm just struggling witht the remote access - I already watched your video about it, but kinda think there is smthn wrong with my router (or with me :D), since it just won't work. You don't happen to have knowledge dealing with a FritzBox, do you?
@@maximilian.guedelhoefer I've moved my setup to new Synology machine, and completely overhauled my setup in terms of external access.
Instead of securing and using SSL directly on HA, I'm now using Synology Reverse proxy - this way, I don't need to open any (additional) ports for HA - just need to make 443 open (if you chose so) and traffic is then forwarded to HA internally. By doing so, you avoid any possible issues with router, as most of them allow you to forward port 443 to Synology.
@@BeardedTinker That's a good idea. I'll try that - hopefully that works. Also thought about using the Nabu Casa, bcs then the usage of Alexa is also pretty easy.
@@BeardedTinker Hey, I've tried many things untill I noticed that I don't have a public IPV4 anymore - thanks to my provider. So I think I'll stick with Nabu Casa - very convenient and works with Alexa like a charm. Thank you for you help very much :)
Hello, at my place, the installation went well, but there's an issue with disconnecting Conbee 2 from the virtual machine randomly. Do you have any idea how to deal with this? I see that many people online are facing the same problem, but I don't see any sensible solutions.
I've never had chance to play with Conbee. Other stick I've tries (sales.sh cc2652RB, SkyConnect, Sonoff Dongle-P) worked without any issue or disconnects.
I had problem with Google Coral, but I was more of playing with it than actually needing it - and never figured out why it was disconnecting. Some say to connect via USB hub that' externally powered, but it didn't work for me.
Any idea on how to successfully move the HA datadisk to an external SSD? I'm running HAOS on a DS218+ VM. My Synology has 2 4tb ironwolf NAS hdds, which slows down HA startups, etc. Synology doesn't allow you to run a VM on an external drive. So I'm attempting to get around this by moving the datadisk to an external SSD. I attached a 240gb SATA SSD to the Synology Usb port and mapped it to the VM. I can see the SSD in HA supervisor listed as "sdb" and "sdb1." However, when I attempt to "move the datadisk" to the SSD, Supervisor doesn't recognize the external drive. I tried manually via the CLI as well to no avail. Running "os datadisk list" also doesn't show external SSD, and when I enter "os datadisk mov /dev/sdb" I get an error saying my ssd isn't a drive. Any ideas? The inability to use an SSD in VM is what is keeping me from migrating away from my RPI4.
Never tried, but you should be able to create second storage pool with sad connected to esata port. Than just use that second storage pool as VM drive.
It should be fully support, but I haven't done this or tested it
@@BeardedTinker unfortunately, it appears you have to purchase Synology’s official expansion unit in order to create another storage pool via the esata port. Some one found a work around a few years back by using the terminal and editing DSM so it viewed the esata port as an internal drive, thereby allowing them to use ssd caching on an external drive, but I’m not adventurous enough to try it now that we’re on DSM 7.1. I’m also too cheap to shell out $500 on an expansion unit for a 4 year old NAS lol. Maybe I’ll purchase a 4bay unit when the new 2022 models are released and use 2 bays for hdd and the other two for ssd. We’ll see lol #firstworldproblems. Thanks anyway, and keep it up - I enjoy your tutorials!
I was thinking about that workaround to enable the esata port. But yes, it's more of a hack if you are not going for Synology drive bay.
@@BeardedTinker I decided to take the plunge and try the work around/hack. Happy to report that it worked, and was actually pretty simple thanks to some helpful tips on Reddit. All I had to do was make some very minor changes to these two files (/etc/synoinfo.conf
/etc.defaults/synoinfo.conf). Upon reboot, the NAS detected my 1tb ssd connected to the esata allowing me to make another storage pool. Home Assistant VM is now up and running (much faster) on the ssd! Probably going to create another volume on the ssd and move my docker containers as well. Definitely making sure I have backups stored elsewhere as who knows what will happen when the next DSM update is pushed
Nice, congrats!!! Glad you got it working!
Many thanks for the awesome guide.
I hope to migrate my old Hassio this weekend.
Still one question: at which point do you put the old Hassio out of order and how?
I can imagine a conflict happening when you restore the snapshot in the old VM while the old Hassio is still running...
Many thanks for the feedback.
Hi Robin! Thank you for your kind words! Really means a lot!
In regard to hass.io - that's up to you. As this is VM and has different IP address then your Synology, you can even run them in paralel. My advice would be to get it up, check if all is OK and then shutdown/remove when you are satisfied on how all is working.
@@BeardedTinker , many thanks for the advice. I will start with the migration as soon as possible. I will keep you informed of the outcome. Kind regards
I tried the migration this evening. Everything went fine, until I restored the snapshot in it... For some reason I am no longer able to access my HA using the internal or the external URL... Do you know of any solution for this issue? Many thanks.
Can you access it by using home-assistant.local:8123 ? Or by accessing it via URL where you uploaded snapshot? In order to access it from outside you need to fix router configuration and point it to new IP address. Same for internal, you need to change it to match your new IP address, or change it in Supervisor.
@@BeardedTinker , I have tried both, but unfortunately I am not able to access it. I have removed everything again and am creating a new VM at the moment. Is it wisefull to stay on the same page where you upload the snapshot to be able to change all settings? Many thanks
What do you mean with agent? what's the problem with agent?
Guest OS agent doesn't automatically start and is not available with current HassOS image. Fix for it has already been implemented, but not available.
Running a 718+ with 16gb ram.
Also using docker (adguard, unbound, watchtower, heimdall, acme.ch, vaultwarden)
Also im using synology photos and plex (with hardware acceleration).
My nas has absolutely no problem running this stuff. Do you think it can handle a HomeAssistant VM with 4-6GB of ram?
I don't want any slowdowns
You don't need 6GB for HA, 3-4 is more than enough. I can't tell you how it will behave on you rsystem. For me on 920+ with 20GB RAM it works great with bunch of addons + Surveillence, Photo and Emby running among others + bunch of docker containers.
Difference between VM and Docker is that VM will reserve and not let other system parts use what you have given it - so depends on how many VCPU your system has and how much you've dedicated. Same goes for the RAM.
With everything running, I dont see CPU usage over 60% and RAM is at max at 50%.
@@BeardedTinker so it takes for example 2 cores for itself? Other applications can't use those cores?
I thought only ram gets reserved
@@Kevin-rf9sx yes, whatever you select in for VCPU's in VMM and give it, it will take.
Awesome! Can't wait to convert my ext4 disc to btrfs and then I will follow the masters guideline :-)
:) Thank you :) I still need to convert other one from ext4 to btrfs too...
...but i made a mistake.The installation worked great but when changing the IP address in Supervisor i did something wrong (think i missed the /22) and i lost contact with HA. I assume i need to reinstall or do you see any other way? :-)
@@Novation681 can you ping it on old address or new one? Also, did you have SSL certificate enabled before in it or not? Depending on that, you maybe can access it by changing http to https and trying old and new IP address.
@@BeardedTinker No, no luck so I'm currently reinstalling....not to complicated following your guide :-)
All working fine now, bit more careful this time entering the IP address, thanks :-)
Do you know if there is a plan to create a Home Assistant Super Visor Docker Container? If there would be one in the works and released, would you go back to that?
No - it already exists, but only for supported environments. There is more to Supervisor then just Docker, other components of the environment are also crucial.
But this is not the option you have to manual installation.
Fantastic! But the good news of seeing the title of the video came to a shock after realising I have to upgrade my RAM -I only have 2GB... 😳. That’s a whole week project for me (finding the correct RAM and doing the deed on a ds718+).
Believe me, it will be worth it in a long run. I have 415+ with 8GB for years now and it's such an improvement 😉
Hey I have extra original 4 GB from DS918+ which I've never used since I've replaced them with 16GB.
@@GrimSpec thanks you, but I just completed the order for a kit of 2x 8gb...
@@GrimSpec where are you from? interested in the Ram because i will upgrade to for the migration.
@@andriessyx5225 EU
Hi there, there is one problem with vSwitch. Once docker instance is using macvlan to publish separate ip for adguard or pihole, switching on vSwitch deactivate the network adapter of Synology (no access). Rebooting Synology and switching off the vSwitch does help, but some network bridges on docker may not work unless they are recreated. Is there a tip on how to set macvlan and vSwitch to work next to each other? I've seen somewhere tip to name network ovs_eth0 instead of eth0 and it should work, but no manual on how to do so. So maybe this short movie next?
Hi Tom! Didn't know about that one, but I should have guessed or expected it.
Can you check if now your network port has different name? For ex. instead of eth it is ovs_eth?
If yes, you can/need to follow same process to create macvlan but this time use this newely created port.
BTW - if you are using VM, you can use HA Add-on's PiHole or AdGuard and you will not need macvlan.
@@BeardedTinker After switching off the vSwitch, and bringing macvlan back to work, I can see eth0. Adguard addon within HassOS was not considered earlier, since I preferred separate docker images and direct access to AG. Too many dependencies. But... I'm using 720+ with 2 network adapters/ports, but so far I've been using only one (eth0). Wonder if separate network adapters can be an option: leave eth0 with current docker/macvlan setup, eth1 with vSwitch for VM? Can vSwitch be set for a single ethernet card only or both at once?
Needed to check it on my machine. vSwitch is per machine not port, so if you enable it - it's up on machine and all ports are influenced.
@@BeardedTinkerThat's what I supposed. Any advice and support on this topic will be highly appreciated.
@@BeardedTinker Here is the solution: stop Adguard or Pihole container -> remove macvlan network -> turn on vSwitch -> identify new network addr (ssh to Synology - ifconfig command) -> most likely there will be now eth0 and ovs_eth0 (if you have two or more networ adapters you may find eth1 and ovs_eth1 respectively), those using link aggregation probably will find bond0 instead. Second one is your network adapter of Synology (before it was eth0) -> recreate macvlan with parent network ovs_eth0, -> change networks attached to adguard or pihole containers -> run your container -> the change should work like a charm. Next step -> install VMM. @BeardedTinker - I know it can be confusing, so if you find some spare time record a quick tutorial video how to run docker with macvlan and VMM at the same time for those who might want to migrate any container to VMM. Hopefully it helped. Have fun.
Hey man, some time ago I installed H.A. on my Synology NAS (DS716+II) with DSM 6 with your tutorial.
It's been working for a couple of years without any problem, but I need to migrate the NAS to DSM 7 now.
Will there be any problem with this or will the migration go smoothly? I would hate to lose my Home Assistant installation. Thank you
Hi, how do I make a snapshot on Home Assistant 2021.9.3 that runs in docker on a synology ds 920+?
Hmm . 2021.9.3 - not sure that at that time there was a backup for Docker version of Home Assistant. It has been added, but I think it was newer version.
But than again, if you run it in Docker, on Synology, you can create task to copy/archive contents of your configuration folder as that's all backup/snapshot does.
So maybe i need to update and then make a snapshot?
@@michaelhauch8189 that's good way to go!
Help, I upgraded HA (installed on Synology/VMM) and Openzwave does not start anymore. Suddenly /dev/ttyACM0 (Zwave stick) not available anymore in HA. Did work untill the upgrade without any problems.
Any ideas/tips?
Hey, what DSM version are you running? Did you make sure that you've enabled USB support and 7f yes, check if USB device is still listed and mapped to virtual machine.
@@BeardedTinker the mapping was gone..... Now OK, thank you very much!
You're welcome! This happens sometimes, I still haven't seen it on my setup, but lot of people have.
on my DS420+ I have volumes in ext4. Can I convert to btrfs and how ? OR, will Home assistant run even without btrfs ?
If you want to run it in VM/VMM - you need btrfs - this is requirement for Virtual Machine Manager. From Synology documentation: Virtual machine data can only be stored on Btrfs volumes.
And no, I don't know of a way to convert to it. I think it needs to be built from a scratch, which is a big issue of course.
Hi, what is the average time for the new HA (on VMM) to be migrated and working again?
It can take some time. Depending of course on the speed of the system (CPU, number of vCPUs and RAM).
But I think it should finish in 60 minutes maximum.
You can use Connect in VMM, to connect to console and there try commands "core info" or "supervisor info" to see what''s going on. Supervisor should be first to migrate, you'll see addons listed there.
@@BeardedTinker Thank you for the answer. Connect in VMM says ' Welcome to Home Assistant" :-). But no response on homeassistant.local:8123. What can be the problem?
@@hmaboes2226 try using IP address of Home Assistant (VM IP address) instead of homeassistant.local.
When you connec to VM, and use root as name to login, it should show you first the IP address of the HA.
@@BeardedTinker well, after rebooting synology, stopping Hass.io from Frederike and starting Virtual HA my imported HA started and worked! However in your video you changed the IP address, why you do that? My 'old' HA-ip is the IP of the Synology itself, I expect problems changing the working IP into the 'old' one.
@@hmaboes2226 tht's strane - you can have both hass.io running and VM at the same time.
But what puzzles me - are you saying that your Synology and VM both have same IP address - that shouldn't be possible and you must ensure that IP addresses are different.
If using same IP address, you could and will see IP conflict - this can bring a lot of networking trouble.
is it possible to run Home assistant on a ssd, separate from the storage drives
For VM, using SSD cache slots are not recommended due to possible data loss. But you can use ssd drives in normal drive slots if you are concerned about the speed.
@@BeardedTinker i have 2 M2 slots in my Synology Nas can those be used ?
(Sorry see now that those are the cache slots)
VM would benefit of cache slots if in read only mode. AFAIK read/write is not recommended as it can result, in case of power failure and write behind, to corrupted VM file But you also have option to add SSD instead of HDD in drive bay and create separate SSD only volume for VMs. That of course depends on number of drive bays you have free.
@@BeardedTinker can't the M2 Cache slots be used for a Volume ? Would be nice to have the drive bays free for future expending
@@TwanJaarsveld1 officially, it's not possible. Hack version? Sure, but please be careful. It may stop working on update, if you have any other issues and contact support, you will receive no support until you remove this, etc.
academy.pointtosource.com/synology/synology-DS920-nvme-m2-ssd-volume
Just a quick question, can i install docker on virtual machine and if so, would it recommend it?
Answer is yes, if you have VM running with OS that supports it. But the question really is, why? If you can run it directly on the host machine, that would be way to go.
@@BeardedTinker I have my docker and my VM on different Ip and I think as such when I installed the broad link manager on docker can’t find the devices. I am not sure how to solve this problem haha
If you are thinking about VM with HA, you can't run Docker there that is not already on the add-on list.
Does broadlink manager show any devices? If not there is probably a network problem. Try solving that.
@@BeardedTinker thanks. I will do that.
Hello. Everything worked very well but all the addons appear turned off and it doesn't allow me to start them. Yes I can uninstall and install but not start. They are all grey. Do you know how I can solve it? Thank you
Strange, but did you try to restart HA OS? Also, when you press start in AddOn, do you get anything in AddOn logs?
Next step I would check is in logs - check to see if Supervisor has any errors (you can select what log is displayed in upper right corner)
i can't find the ip adress of HA in virtual machine, in my router dosn't exist, why??
There are few things you could do - first in VMM - if you click on Virtual Machine and in lower tab select Network, look there for MAC address and try to locate it on router.
Next thing could be tro try and use homeassistant.local:8123 and/or homeassistant:8123 and after you finish configuring it you'll see IP address in supervisor:
Third option could be to try and delete this image and download one from this URL: www.dropbox.com/s/1ev7g9xhck5bhw5/hassos_ova-5.11_syn-patch.ova?dl=1
This image contains fix and you will see current IP address both in network setting of VM and in General view.
Remembered one last thin - use Connect to connect to HA via terminal (in web) - there login - I think you need only to type root as username.
There you can use 'network info' command and it will show you IP address.
@ did you try to press Connect in Synology VMM? It should open direct connection to VM in browser.
Thank you! It Works!
Glad it helps!
Hello Bearded Tinker, I had reverse proxy working with docker. Now I switched to VM, I can't get it working again. I get a 400: bad request. Can you help?
That happens when you access it by IP address or via reverse proxy?
Quick check. Did you change IP address in reverse proxy to new IP address that VM got?
Did you enable reverse proxy in Home Assistant, as there was a breaking change in 2021.7 that requires it to be specified in configuration.yaml file?
From notes:
Home Assistant will now block HTTP requests when a misconfigured reverse proxy, or misconfigured Home Assistant instance when using a reverse proxy, has been detected.
If you are using a reverse proxy, please make sure you have configured use_x_forwarded_for and trusted_proxies in your HTTP integration configuration.
@@BeardedTinker thanks for the help. I made a mistake, I used the File Editor after I copied all the files from docker to VM, the File Editor was working but I was editing the configuration.yaml of docker! I discovered it when the logs did not change no matter wat I changed in config.yam. Regards, Martin
😂 can't confirm that I did similar thing 😂
Great that you got it working again!
Great video! I have done everything but still cant access my HA instance. There is no ip and when i search in my network there is no new ip joined either. Same ip with 8123 as port does not work aswell...
I have tried this in a docker and that one is just the core and cant use supervisor and that sort of things. Anyone can help? Did something change in 5 months?
Thank you! It should work still without any change.
Few questions: can you on your router or DHCP server see what address was assigned.
Also in VMM, did you press Connect to try and connect to VM machine. It should then show you IP address of the server.
@@BeardedTinker Thats the whole problem. It does not sign any ip and when you connect it just fails. I have tried a windows 10 installation which works fine but this one does not. I have tried a few things. Old .ova file, your patched .ovs file in the commens which was corrupted it said and the newest .ova file on HA. I have also tried a .vdi but that one didnt work either.
@@Tmcmaster latest OVA image has fix for IP address, so you don't need to use one linked in description.
Few things can be wrong in setup:
- issue with vSwitch - but I believe that you have it enabled, so this should be OK
- you selected wrong firmware - check that firmware selected is UEFI in VM settings
- IPv6 - some routers will assign IPc6 address, and there were some issues with it
It's very hard to debug without seeing what you have. You can try and use Angry IP scanner to see if IP address was assigned and if it's visible.
All is ok i think except for ipv6. I am using unifi usg than it should appear in my clients list right?
Update: I have watched your video again and did something different. I just started the image after it was fully imported instead of saying to start automatically. This time i received a IP and it is starting now? Thanks anyway for your fast respsonse your video helped me to install this! Gonna check later today if it is working or not :)
My Raspberry 4 died 4-5 days ago and now I have tried to learn virtulization; I already built Linux Mint with VirtualBox for testing. But there are also other solution (at least VMM, Hyper-V and Proxmox). Are you familiar with those and what you prefer? Anyway I need to buy second hand mini pc during weekend. What would be the specs? I have idea to buy old Lenovo ThinkCentre M920q Tiny: 6 CPUs, 16 GB, 512 SDD, Wifi + Bluetooth.
Depends on what you want to do with it - but in community, Proxmox seams to be most preferred choice. In terms of specs, this looks good. For any virtualisation platform, most important in number of cores/threads and RAM. But again, if you want to run just 1 or 2 VMs, this is OK depends, what else besides HA you'll run on it. I would prefer 8 cores and 32GB RAM as this has a LOT of extra capacity for other VMs. For just HA, this is way more than enough.
I’m at the preparing home assistant stage and it’s been going for over 2 hours? How long does it take?
Sorry for late reply - busy Sunday. It depends a lot on the speed of the internet - I think it downloads around 1-2GB from the Internet. So it depends on speed you can get.
But I think 2 hours is long enough.
Not sure if this still happens, but it can sometimes hang and not refresh screen when everything is done - you can try refreshing web page or just remove everything from URL and use IP_ADDRESS:8123 to try and force load HA.
@@BeardedTinker thanks for the reply. Tried all that. Was going all day. Deleted it in the end. NAS only had 2GB memory so was wondering if that was causing it. Looked online for more memory and ended up buying a raspberry pi instead 🙈😂
🤣🤣🤣 2GB is not enough in my opinion, 4GB should be minimum. But raspberry pi is great option too. Did you get RPI 3 or 4?
@@BeardedTinker raspberry pi 4. 4gb with an ssd card. I was going to buy 8gb but I was pushing it with the wife as it was 😂 😂
@@gavinmorgan8861 I know the feeling... I know the feeling 🤐 😂
Despite the pr being merged, the guest assistant still does not launch, any other solutions?
Nvm, i see its only merged in unstable, bleeding edge dev build time it is i suppose.
There is an option to download image from Fredrick. He shared image with guest tools enabled.
@@bitwolfy here is the link: www.dropbox.com/s/1ev7g9xhck5bhw5/hassos_ova-5.11_syn-patch.ova?dl=1
@@BeardedTinker Yeah, I saw that, but I just went with a unstable dev build, might bite me in the ass but thats what im here for :)
@@bitwolfy you should change nick to Daredevil :) It should work
Can you help me? My DS VM log:
The network interface [Syno] [BOND 1] has been disconnected. The virtual network interfaces on [Syno] [haos] are disconnected.
In web browser "400: Bad Request"
On phone app HA work.
Hard to help with just this info.
Check if Open vSwitch is enabled.
Also in configuration for VM, check what network is selected.
But if it works on the phone, it should work from any device.
See if maybe your IP address is banned on Home Assistant.
@@BeardedTinker I check all divices and only my pc have problem with connect.
@@Qruxat as I said previously, this can be that IP address from your PC is banned. Check IP_BANS.YAML file if there is a IP address or not there. If it is, than this can be the issue.
Other possibility but I doubt it, could be that you are using reverse proxy and didn't check breaking changes for 2021.7 - but as I said, I doubt as error would be different and it would also stop working on your phone.
Bond disconnected error is usually shown when cable from network is disconnected (or you turn of the switch).
you are great!!! thx a lot!
Thank you for the comment 😉
Well done, thanks.
Thanks for watching and comment!
I attach a few comments:
- if you use the correct * .ova snapshot, the Guest agent will also be installed. This Guest agent will ensure that you can correctly shut down VM-HA directly from the VMM environment and not just from the HA environment as shown in the video
- it is also possible to use the image * .qcow2, but you must first import it in VMM via the Image section and then use the Virtual machine Import from disk image ...
- on the official page www.home-assistant.io/installation/alternative is a *.ova file without Guest agent but a file * .qcow2 is OK( with Guest agent )
Hey Andrej, thanks for the comment! 5.13 version of HassOS has fix for this (but it's not out yet) as fix from Fredrick for ova was pulled. Problem was that ovf:id used had an error (wrong ID number) and because of that Synology couldn't correctly identify OS and install Guest OS.
github.com/home-assistant/operating-system/pull/1233
you are GOOD, thx :)
Thank you!!!
Hi! Thanks for your videos. They are great and very useful...
Could you record video how to migrate (database of) InfluxDB from 1.8 to 2.0?
After update by watchtower when i open url of InfluxDB i see initial configuration :( I know that i have to migrate DB (docs.influxdata.com/influxdb/v2.0/upgrade/v1-to-v2/), but it's too difficult to me. Thanks in advance.
Greetings from Poland!
I'll be making it soon. Need to recreate Docker influxdb first as I deleted my old setup.
@@BeardedTinker Great!
He did not create the network... I mean he did but he did not show but ended up referring to it like something he has done. NOPE :D
Yes, but you can use default network. That's the one I'm using in my setup😉
15:53 ye..yess ss, s ssir.. y.. y....yyeess I did
Runs away
😂😂😂
Great video, I set everything up previously by watching this video of yours th-cam.com/video/jtVelxopKTM/w-d-xo.html I have finished setting up everything in the VM but how do I uninstall everything I installed in the docker container using putty like Home-assistand, Influxdb, nodered, portainer and watchtower? I want to install nodered for sure but not exactly sure at this point if I need the others listed?
Thanks Justin! If you've already setup VM and moved everything there, cleanup is simple.
In Synology Docker UI - Containers - just remove all containers you don't need anymore. That will deactivate them and delete configuration. Also in Docker UI - images, you can delete all downloaded images you don't need. You have to do this as second step as it shouldn't allow you to delete image if there is Docker container running.
And as last step, in File Station, delete subfolders (probably under /docker folder) that you don't need anymore.
You can also leave them for now and do this at later date, just to have files (configuration files) available for now, but you can remove them too.
@@BeardedTinker Thank you! I did already remove the containers but i will do the rest as you suggest