Yes it force to downgrade the miltidict to 4.7.6
Again, I’m no Linux exper here. Running Ubuntu 20.0.4 and HA in Docker. Just went into the console in my homeassistant container and ran:
pip show multidict
results:
Showing I have 4.7.6, but Config Checker saying I have 5.0.0?
im not so into programming. But did you do it on the Ubuntu OS or inside the docker?
I did it on the OS itself…(Debian for me)
I did it inside Docker - guessing I need to stop all containers and try it on the OS side directly. Also guessing that future OS updates are going to continue to overwrite this until it’s fixed? Haven’t seen anyone devs or such chime in and realize this is ‘unsupported’ install. Feeling like I’m going to have to handcuff my NUC into HassOS sooner than later… 
I run HAss supervised with the standard image in RasPi 3b (so the maxium supported way I guess) and I still get this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing...
starting version 3.2.9
[10:20:01] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:20:01] INFO: Setup udev devices
[10:20:04] INFO: Don't worry, this temporary installation is not overwriting your current one.
[10:20:04] INFO: Installing Home Assistant: latest...
[10:20:04] INFO: Please be patient, this might take a few minutes...
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
aiohttp 3.6.2 requires multidict<5.0,>=4.5, but you'll have multidict 5.0.0 which is incompatible.
[10:22:25] INFO: Installed Home Assistant 0.117.2
[10:22:25] INFO: Making a copy of your configuration for checking...
[10:22:31] INFO: Checking your configuration against this version...
[10:28:45] INFO: Configuration check finished - no error found! :)
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
I can’t imagine the 0.117 update breaking the standard supervised installation so I guess I’m getting something wrong here as there doesn’t seem to be a massive shitstorm… 
Did you try this command to downgrade?
pip3 install --upgrade --force-reinstall multidict==4.7.6 command
Hassio does not support this command:
_ _ _ _ _
| | | | /\ (_) | | | |
| |__| | ___ _ __ ___ ___ / \ ___ ___ _ ___| |_ __ _ _ __ | |_
| __ |/ _ \| '_ ` _ \ / _ \ / /\ \ / __/ __| / __| __/ _` | '_ \| __|
| | | | (_) | | | | | | __/ / ____ \\__ \__ \ \__ \ || (_| | | | | |_
|_| |_|\___/|_| |_| |_|\___| /_/ \_\___/___/_|___/\__\__,_|_| |_|\__|
Our command line:
$ ha help
~ $ pip3
-bash: pip3: command not found
~ $
Also: I can’t imagine that every RasPI user (including everyone who does the first installation) has to do this?
But maybe I haven’t understood what aiohttp is needed for?
I did the command on OS itself (im using Debian)
As far as I know this is not possible with HassIO as it doesn’t a fully fledged accessible Linux below the Supervisor. This is why I can’t imagine that millions (?) of users now need to run a command after every update… But I might be wrong…
The new update 0.117.3 is out. Did the check again and this popup:
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
aiohttp 3.6.2 requires multidict<5.0,>=4.5, but you'll have multidict 5.0.0 which is incompatible.
Very strange because i started this topic with same error… did the command:
pip3 install --upgrade --force-reinstall multidict==4.7.6
And the whole problem was solved…
Now back with the whole problem…
Did the command again:
pip3 install --upgrade --force-reinstall multidict==4.7.6
Did the check again… and now the error is gone again…
If this is the case, and it’s reporting this error on a SUPPORTED installation method - has anyone opened a ticket on GitHub to report? Definitely seems like it should be ‘fixed’ if it’s causing errors on a Hassio / HassOS.
There is now:
3 Likes
Just a thought: Does the update break anything if you don’t do the downgrade with the pip3 command before?
Quick push: The issue on GitHub does not seem to get any feedback. Anyone here who can point me in the right direction or shall I just do the update, see what happens and then roll-back if it breaks?
I did the update to 117.2 a while back and it starts in safe-mode. I had to restore from a snapshot. I’m in a holding pattern until this gains traction. I’m thinking about installing the virtual appliance fresh and restoring that from a snapshot.
That command to force a downgrade, where would I enter that? Not sure if I have access to the OS using the official virtual appliance. Can I use the SSH and Web Terminal add-on?
Same error message here. Running HassOS directly on an Intel NUC.
Using above downgrade command gives me the following error in the terminal:
Collecting multidict==4.7.6
Using cached multidict-4.7.6.tar.gz (50 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Building wheels for collected packages: multidict
Building wheel for multidict (PEP 517): started
Building wheel for multidict (PEP 517): finished with status 'error'
Failed to build multidict
I now did the update on the fully supported / supervised RasPi setup, went through without error and is running for 24hrs now. So it seems there is no direct implication for these installs.
Solved it as well: first update the host os to 4.15 and then run the config check again. Problem solved 
Interesting, I was on HassOS 4.15 and seeing the error with Config Checker. Did the update from 0.117.0 to 0.117.5 and it went fine.
