Awesome update! And a great year of updates too! Hard to believe how much has changed in just a year. Hone Assistant is responsible for getting me back into the Smart Home and greatly expanding the number of smart device I have.
And for what its worth, I like the new configuration menu. Especially the combining of the various config buttons on the sidebar.
Make a feature request, it’s a good idea
Is it me or the new Configuration menu is not yet translated? (My locale is IT_it, Italian, I see it in English). Thanks!
Thank you very much. This solution worked for me!
AFTER UPGRADE core_2021.11.5 icon mdi:hand-right not showed
Problem with Kodi integration after update 2021.12:
2021-12-12 19:03:17 ERROR (MainThread) [homeassistant.components.kodi.config_flow] Unexpected exception
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/kodi/config_flow.py", line 187, in async_step_credentials
await validate_ws(self.hass, self._get_data())
File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/kodi/config_flow.py", line 82, in validate_ws
await kodi.ping()
File "/srv/homeassistant/lib/python3.9/site-packages/pykodi/kodi.py", line 164, in ping
response = await self._server.JSONRPC.Ping()
File "/srv/homeassistant/lib/python3.9/site-packages/jsonrpc_websocket/jsonrpc.py", line 49, in send_message
response = await pending_message.wait(self._timeout)
File "/srv/homeassistant/lib/python3.9/site-packages/jsonrpc_websocket/jsonrpc.py", line 140, in wait
with async_timeout.timeout(timeout=timeout):
TypeError: timeout() got an unexpected keyword argument 'timeout'
It isn’t going to be across the board for any entity. A light is still a light. There will be no option to show it as a window for example.
But in the above image this cover entity can be a window, a door, or a garage door, depending on your needs.
Anything beyond that will require yaml config, which you would have had to minimally add in order to get the UI option available anyway.
Same here:
Component error: jq300 - cannot import name ‘HTTP_OK’ from ‘homeassistant.const’ (/usr/src/homeassistant/homeassistant/const.py)
What to do?
You read the Release notes first, right?
The following icons have been renamed:
* hand-right to hand-back-right
If not, you should not have posted. It is ALWAYS best practice to read the Release notes before upgrading, especially the Breaking Changes section.
When something does not go as expected, read the Release notes again & the forum thread to see if it is really a new, previously unknown issue.
After installing 2021.12, although I only have a single Shelly EM, my Shelly setup now a completre mess. Was originally using ShellyForHass and all OK. After update, ShellyForHass was disabled and the Shelly integration discovered. But after integration, the Shelly integration had only 5 entities whereas my previous ShellyForHass had many more ( + 10). After uninstalling both, the Shelly integration again discovered but fails with no config flow available. But then can install if by + ADD INTEGRATION but again only 5 entities and seems like the Shelly integration cannot make up its mind whether it is the official integration or ShellyForHass ! My sympathy to those with considerable Shelly devices and I hope a fix / guidance is rapidly forthcoming.
Did you ask their developer for support? All HASS addons are supported by their respective community developers, not the core team responsible for this thread.
But why isn’t this an identified breaking change as ther is now an official Shelly integration. I am not the only one that is suffering.
Ignore all dedicated integrations. Use MQTT integration instead. You will have everything in your hands. No more dependency on integrations development. It’s more flexible and more stable (mqtt development is not so active)
Because ShellyForHass is custom integration not being a part of Core. HA dev team is not able nor responsible to control all 3rd party integrations. Thus HA changelog/breaking changes list doesn’t contain information about 3rd party components compatibility. Authors of those integrations should take care about compatibility with HA incoming versions.
You answered your own question. The core developers expect you to use the official integration, not the community hellyForHASS one.
Somebody else in this thread also gave the same information Read the postings in a thread before reposting the same, answered issue.
You should move to the core Shelly integration, which works perfectly, or raise an issue with the developer of the 3rd party integration, ShellyforHASS.
I cannot agree with that. If it had been true, custom components api wouldn’t have been allowable.
I would rather ask: why every major release breaks 3rd party work so often. It’s rather general question than blame. API for sake of being api should be provided as stable as possible.
The third party developers do not test their work with the testing development releases. That is an issue to raise with the appropriate developer. Perhaps you should try supporting them or ask for a refund on their product 
My android app now crashed several times if I try to go to settings for in Home assistant.
Worked a few times.
Yup, I waited a few minutes extra.
Any new method to install the supervisor again? Looks like the installer.sh bash script isn’t available anymore.
This function SHOW AS is no available for all entities. Why ?
