Home Assistant Community

How to update your HA version on a QNAP NAS


Using the QNAP NAS ContainerStation app

In the list of Docker/Containers my running HA container is listed like this when at the “Overview” screen:

You need first to confirm your own settings with mine as a guide to compare.
Click “home-assistant-YourNumber” and then click “Settings” (top right)

Confirm the “Command” value is the same as mine is below…record if different.

Then click “Advanced Settings” and confirm all (IE: Environment Tab, Network Tab and Shared Folder Tab) settings are as per those listed for mine below…record accurately if different. Close out by clicking “Cancel” and then keep those values handy.

Step One:
FIRST…Don’t forget this step! “Stop” your existing running container. If you don’t then both containers (your new one and the existing one will be simultaneously reading your /config and connected devices as the new container completes. That has caused errors for me in the past.

Step Two:
Then choose “Create” and carry out a search for ‘homeassistant’
The first search may only deliver one result?
But the result may be for Recommended Local IoT AI Docker Hub in the search OPTIONS
while you want to choose
Recommended Local IoT AI Docker Hub in the search OPTIONS

After you choose Docker Hub option quite a few more results will appear for you.
My usual choice IE: ‘to get the latest versions’ is usually at the top of the list but it is the one named homeassistant/home-assistant
If you click that link you will visit an external website. From that page you can read detailed information for Docker Releases.

But for now…we need to click the “Create” link at the far right and when that opens you will have a choice of ALL THE PAST? HA versions released I believe? For me I chose 0.91.0 this time.

Choose your preferred numbered version (or just “latest” but I have found problems with doing that in the past) and click “Next” to move on.

Step Three:
First Screen in:

You will see the new container “Name” value has been filled in for you. If the “Command” value is also filled in leave it but if it is not use “python -m homeassistant --config /config” (without the quotes).

Then Choose Advanced Settings…see the “cog” in the above image at the bottom left.
In all future screens…PLEASE…Resist all temptation to click “Create” until you actually complete the next 3 steps and have double checked all is complete!

Step Four:
Choose the “Environment” TAB:
ADD all these…(or your own as determined in an earlier step?) one at a time as shown here:
Like Name: GPG_KEY Value: 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D

GPG_KEY 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D


PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin



variable TZ

value Australia/Queensland

Step Five

Choose the “Network” TAB:

choose…Network Mode: HOST (all the rest should be automatically filled in)

Step Six:
Choose the “Shared Folder” Tab:
On the “Volume from host” line Click the “Add” button

Then by clicking “Host Path” (choose from the Folder List - Either Your existing config volume OR the new one which you wish to use.

NOTE 1: On Clicking…This will be generated from the host reading your QNAP file structure) in my example I chose an existing one of two I am using presently “/Container/HomeAssistant01”

NOTE 2: To confirm that you can also add the choice of a new /or separate config folder from the working version you were using by simply setting that folder up earlier. Handy sometimes?

After choosing your /config volume and in “Mount Point” type ‘/config’ (without the quotes) and then tick read and write (if not already ticked)

Then (BUT have you double checked first?) go ahead and “Create” it and wait for the new container to be started.

There should be a task shown running in the background (see the below image in the top right corner IN BLUE beside the 3 vertical dots) which is your new container being downloaded and created…just wait between 5 and 20 minutes (depends on your local download speed and QNAP CPU speed)!

Once the new container appears and you confirm it is running either try to connect to homeassistant with your browser at your usual address OR if it was already open then you should be able to see (in Developer tools/Info) it is now running the new version you just created.

Minor Issues:
If you chose a new config volume you will have to setup the initial user again.
Sometimes my mosquitto and node-red (etc) containers may need to be restarted, but not every time.
If you have skipped a few versions or setup a new config I have found sometimes I will need to setup a new initial user and login again etc.

Major Problems:
If you have any major trouble with the new version you will either not even be able to connect
OR you may see lots of errors in Developer tools/Info which you can set about resolving the issues
OR if there are too many and you want to fallback to your old version you can simply “Stop” the new container and “Start” your old working version again. Too Easy!
See below I have four versions of HA in containers and that I am running version 0.91.0b5 at the time of screenshotting.

I have found that if you use this system it is very easy to quickly move up or down form various HA versions at will. You can then quickly make decisions on whether that next update is for you or not.

Hope that helps someone!
It’s a great community here help if you can!


Great job Wellsy! I followed this today as I did not know how the hell I could upgrade the standard QNAP 0.65 container. Lots more questions to come from Perth.


I’m glad it has been of use to you. What version did you update to?

Any questions are also very welcome.
Regards Steve Wells

1 Like

Next I am going to try and figure out this one.


What is the GPG Key?


Well I don’t know its real use. I only know that my original settings used it and that is how I continue to travel. Remember that the one you have quoted was how mine was setup…yours may very well be another value? Did you check all those settings and record first mate?

regards Steve Wells


Negative but I have homeassistant 1 I could always fire up again and check theoretically.


Haha…quick learner…and if its a problem ditch the second one and try again…its a problem free update if you think about it.


I have found with the later versions that some of the settings I write in that “Environment” TAB: will get overwritten in the new version. Might add that info above as well. I mostly(?) always recheck the new version settings each time I move on to a new version.



You may find this interesting to get more of a pi feel (most guides discuss hass.io).

Also you running a configurator container?



No configuration container for me. I like sticking with the basics theses days. Less to break when new releases have breaking changes.

I believe the developers are building in all that I need as time goes by so I’m happy to just progress that way.



I did miss hass.io for a short while after I moved from my pi…after I realised how much more useful yaml config was I stopped missing it.

Even node-red is losing its appeal now that I have become a little more comfortable with writing automations…I am keeping it for now though.

1 Like