I tried this
pip3 install homeassistant==0.76.2
it seemed to work, but the ha_version file still shows 77.3, and of course I still cannot get to my system. 
I’ve managed to get to my previous versions, but Still unable to get on.
I’m finding my zwave is not working at the moment, but who knows why??? No UI access
WISH I had not done this upgrade. I held off, and should have stayed on 76.
Well I’m off to bed with what seems to be a 50% unusable system
When I try to access UI I Get the the following 100% of the time
``
2018-09-07 21:28:28 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 378, in start
resp = await self._request_handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_app.py”, line 341, in _handle
resp = await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 88, in impl
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/static.py”, line 66, in staticresource_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py”, line 34, in real_ip_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 67, in ban_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/auth.py”, line 66, in auth_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/view.py”, line 113, in handle
result = await result
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/data_validator.py”, line 47, in wrapper
result = await method(view, request, *args, **kwargs)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 77, in handle_req
resp = await func(view, request, *args, **kwargs)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py”, line 160, in post
return self.json(_prepare_result_json(result))
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py”, line 116, in _prepare_result_json
data[‘data_schema’] = voluptuous_serialize.convert(schema)
AttributeError: module ‘voluptuous_serialize’ has no attribute ‘convert’
Legacy and Home assistant local give that error
First time in a long time I’ve missed smartthings, haha. Not really, and I appreciate all the hard work here, but I have been pretty much standard config since the beinging and these last two major releases have been painful. Regretting upgrading now, but the tide sensor lured me in. 
i’m 50% back (reverted to76), but have lost all my zwave… 
You have outdated voluptuous_serialize lib installed, check your config/deps folder
I’m gettin this aswell. I can access overview but that’s it. Everything else 404s.
Iv checked deps, mines empty is that right?
I’m having a similar but opposite problem. I can access the front end UI, but oddly my theme disappeared and the backend is inaccessible.
Can someone explain the best way to get this upgraded. I ended up speding 4-6 hours to get my system back to where it was before I started. I upgraded, could not access UI, legacy or homeassistant, ended up deleting .storage, still unable to get on, downgraded to 76.2, but now had no entity registry. Pulled down an old copy, but the device IDs were now different, so that did not work. I ended up having to line by line compare each of my locks, lights, switches, dimmers, fans, etc, to make sure they were named properly. On top, several devices just took multiple times of healing, etc to get them back and stable.
OK, enough complaining, I love HA, but the last two upgrades have been painful. Although others have had issues, I have to assume that most have not had issues like this. Basically I have not had any success with the new auth in version 76 or 77.
I’m just looking for things that could be my issue, I feel like I’m a pretty out of the box install. Running HA on ubuntu, no node red, dockers, etc. No custom UI, just a bunch of yaml.
Having an issue is ok, but having an issue that leaves you down for hours, is something I want to avoid for a third time. Any suggestions are appreciated.
1 Like
You need resolve your root cause, not downgrade. Basically, any downgrade is not supported by us, we only consider backwards compatibility when we write code, e.g. upgrade, not downgrade.
Especially in your case, you system is already up and running on new version, lots of data migration already done. A downgrade at this point will only bring your more problem. A better approach is make a backup before upgrade, restore your backups if upgrade failed.
For your original issue regarding “voluptuous_serialize”, I already replied you in previous comment, you should look [your_config_dir]/deps folder, clear it.
so /home/homeassistant/.homeassistant/deps, right?
it’s empty. Yeah, Agreed, downgrading is not something I will do again, I get it.
Can you give me some recommendations on other area’s to check? Although I’m not in an immediate need to upgrade, I dont want to be stuck at 76.2 using legacyapi auth. But I also dont want to go through this issue again. Again, Understood this was self inflicted, but man, still finding odd and ends in my zwave device names I’m having to fix.
help me please
In general, pip freeze will list all package installed, then you can compare it with https://github.com/home-assistant/home-assistant/blob/0.77.3/requirements_all.txt
God helps those who help themselves
Thanks, its a long list, but I’ll have a look and see. I do see the holidays is the wrong verion (different issue I’m having with workday compoent not being able to update
aenum==2.1.2
aiohttp==3.3.2
aiohttp-cors==0.7.0
aiohue==1.5.0
asn1crypto==0.24.0
astral==1.6.1
async-timeout==3.0.0
attrs==18.1.0
bcrypt==3.1.4
beautifulsoup4==4.6.0
bellows==0.6.0
bitstring==3.1.5
boto3==1.7.4
botocore==1.10.4
certifi==2018.8.24
cffi==1.11.5
cffi-utils==0.79
chardet==3.0.4
click==6.7
click-log==0.2.0
colorlog==3.1.4
cookies==2.2.1
crccheck==0.6
cryptography==2.3.1
curve25519-donna==1.3
Cython==0.24.1
distro==1.3.0
docutils==0.14
ecdsa==0.13
ed25519==1.4
emulated-roku==0.1.4
envs==1.2.4
ephem==3.7.6.0
future==0.16.0
gmpy2==2.0.8
google-api-python-client==1.6.4
googlemaps==2.5.1
gTTS-token==1.1.1
ha-ffmpeg==1.9
HAP-python==2.2.2
hikvision==0.4
hkdf==0.0.3
holidays==0.9.5
home-assistant-frontend==20180820.0
homeassistant==0.76.2
homekit==0.6
homematicip==0.9.8
httplib2==0.10.3
idna==2.7
idna-ssl==1.1.0
Jinja2==2.10
jmespath==0.9.3
keyring==8.7
keyrings.alt==1.3
libnacl==1.6.1
lxml==4.2.1
magicseaweed==1.0.0
MarkupSafe==1.0
multidict==4.4.0
mutagen==1.41.0
netdisco==2.0.0
netifaces==0.10.6
numpy==1.15.1
oauth2client==4.0.0
pandas==0.23.4
pexpect==4.6.0
PlexAPI==3.0.6
protobuf==3.5.2.post1
ptyprocess==0.5.2
pure-pcapy3==1.0.1
pushbullet.py==0.11.0
py-noaa==0.3.0
py25519==0.13.28
pyasn1==0.4.3
pyasn1-modules==0.2.2
pyatv==0.3.9
PyChromecast==2.1.0
pycparser==2.18
pycryptodome==3.3.1
pydeconz==36
PyDispatcher==2.0.5
pyfttt==0.3
pyharmony==1.0.20
pyHik==0.1.8
pyicloud==0.9.1
PyJWT==1.6.4
pyotp==2.2.6
PyQRCode==1.2.1
pyserial==3.4
pyserial-asyncio==0.4
python-dateutil==2.6.1
python-ecobee-api==0.0.18
python-forecastio==1.4.0
python-jose-cryptodome==1.3.2
python-magic==0.4.15
python-openzwave==0.4.9
python-pushover==0.3
python-songpal==0.0.7
pytz==2018.5
PyYAML==3.13
requests==2.19.1
responses==0.9.0
rsa==3.4.2
s3transfer==0.1.13
samsungctl==0.7.1
shortuuid==0.5.0
simplejson==3.16.0
six==1.11.0
sleekxmpp==1.3.3
soco==0.14
SQLAlchemy==1.2.10
srptools==0.2.0
tlslite-ng==0.7.4
tqdm==4.23.0
typing==3.6.4
tzlocal==1.5.1
ua-parser==0.8.0
uPnPClient==0.0.8
uritemplate==3.0.0
urllib3==1.23
user-agents==1.1.0
voluptuous==0.11.5
voluptuous-serialize==2.0.0
wakeonlan==1.0.0
warrant==0.6.1
WazeRouteCalculator==0.6
websocket-client==0.47.0
websockets==6.0
xmltodict==0.11.0
yarl==1.2.6
zeroconf==0.20.0
zigpy==0.1.0
zigpy-xbee==0.1.1
i luckily had a 5 month old back up on 64.2 so flashed that an dropped the config/components on. Just put 77.2 on again and its all good now.
That is the version we need.
I saw that. And that’s the version I have installed. Any sort of things i should look at as to why it’s not liking it
So, I’m considering moving forward again, and want to set myself up for success, not get locked out of my UI again. I’m still not 100% sure what I should do for my configuration.yaml
So what should it look like. I noticed I had two areas relating to auth
# auth_providers:
# - type: homeassistant
# - type: legacy_api_password
#auth:
http:
api_password: !secret http_password
So If I want to be able to use the new Auth, but also want to have the legacy auth enabled for stuff like IFTTT, what do I need to have enabled/disabled??
Thanks
Did you ever have the new auth_providers: enabled in your previous install?
If you didn’t then you shouldn’t have to do anything at all.
I think either way you shouldn’t have to do anything.
I have two instances of HA running on my network. They were both on v76. On one I had the auth_providers: and on the other I didn’t (just the api_password:). I upgraded both to 77.3 and it went fairly smoothly.
Maybe it’s messing up because you had the new auth enabled at one point and then commented it out?
If that’s the case then maybe try to re-enable the auth_providers and complete the log in for that version then upgrade.
Either way MAKE A BACKUP! 
BTW, I don’t think I ever saw what install method you are using.
And lastly, while a downgrade might not be officially supported I’ve had to do it a couple of times due to breaking changes or bugs until those got fixed and I’ve never had an issue. Maybe since this is such a big upgrade it caused other problems. But I know a lot of other people have mentioned having to downgrade in the forum for similar reasons prior to this version and have been successful.
Oh and EDIT: this is situation is a definite vote for installing in docker. If you screw it up you just delete the container and re-create it. It literally takes seconds.