I haven’t upgraded to 105.1 yet (still on 104.3). I’ve been around since about .86 I believe - and I’ve probably had to do the same (redo SmartThings integration) 2-3 times in all the upgrades between .86 and .104
Not a huge pain to do so, but figured I’d mention - you’re not alone 
@frenck
I’m having trouble with the new Spotify integration. When i add the integration everything looks fine up until the point where i play something. The integration then fails with the following error and doesn’t recover even when home assistant is restarted:
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 424, in _async_add_entity
await entity.async_update_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 327, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 793, in state_attributes
for attr in ATTR_TO_PROPERTY
File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 794, in <dictcomp>
if getattr(self, attr) is not None
File "/usr/src/homeassistant/homeassistant/components/spotify/media_player.py", line 160, in media_content_id
return self._currently_playing.get("item", {}).get("name")
AttributeError: 'NoneType' object has no attribute 'get'
Odd I have yet to run into needing to redo SmartThings, guess I’m lucky.
Could you please, please, please make a global option in configuration for the default state_color behaviour? I love the way my lights and switches turn on in yellow. I know the lights still getting yellow, but I have a lot of relays modules for my lights that act as a switch, so half of my installation will act one one and other half other way.
It is going to be painful if I have to go one by one adding the state_color configuration. Seriously I have a lot of entities…
Please…
I’m liking this update so far, but I’d really like to see a couple of things:
There’s also this little issue: the current version of Config Helper (1.5) for the VS Code Editor doesn’t yet know that state_color is a valid property. Everywhere you specify it in the file gets flagged as being a disallowed property.
It’s not a show-stopper but it does make the file appear to have a lot of errors.
In addition, in my personal opinion, the image used to explain the state_color change is not correct:
For me, all these entities are wrong. The correct would be:
So the coloured icon will be good in all cases.
Did I understand correctly that the following configuration in my ui-lovelace.yaml is no longer supported from version 0.107.0 on.
If yes, what is the alternative?
#Temperatur Wohnzimmer
- type: thermostat
entity: climate.wohnzimmer
- type: history-graph
title: "Temperatur"
entities:
- entity: sensor.temperatur_und_luftfeuchtigkeitssensor_temperature
You are using the correct Lovelace History graph, the deprecated one is the old States UI History Graph.
You can at least set state_color at the card level, so all entities within that card will be affected. I thought this was going to be bad for me, as well, but it only took a few minutes to get all of my cards updated.
I’d LOVE state_color to go one step further and allow you to define WHAT color a given state is…
- entity: switch.whatever
state_color:
- value: 'on'
color: #4C709D
- value: 'off'
color: #FFF
or
- entity: switch.whatever
state_color:
- on: #4C709D
- off: #FFF
or whatever the most logical way to do it is, I’m no expert.
Would be nice at the Card level as well.
Could go a step further and implement a state_icon which allowed changing the ICON based on state changes - currently I have to create a bunch of template switches to do this.
It can be defined at the card level.
Do I need to do something special with my zha configuration in this release?
I get the following error on 0.105.1 (works again when reverted to 0.104.3)
Error setting up entry /dev/ttyACM1 for zha
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 215, in async_setup
hass, self
File “/usr/src/homeassistant/homeassistant/components/zha/init.py”, line 103, in async_setup_entry
await zha_gateway.async_initialize()
File “/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py”, line 136, in async_initialize
await self.application_controller.startup(auto_form=True)
File “/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py”, line 138, in startup
await self.initialize()
File “/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py”, line 91, in initialize
await self._cfg(c.CONFIG_KEY_TABLE_SIZE, 8)
File “/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py”, line 231, in _cfg
assert v[0] == t.EmberStatus.SUCCESS # TODO: Better check
AssertionError
Running Homeassistant core with docker-compose on an intel nuc.
The Vera integration is no longer functioning in 105. Devices can not be updated via HA, even though their state seems to be correct. I had to downgrade to 104 to avoid divorce.
Or stick to the Home Assistant UI and display it similar as how automation entities are shown on an entity card.
Running HassOS 3.9 and trying to install Home assistant 105.1 but get this error on rasberry pi 4. 
20-02-06 20:03:19 INFO (SyncWorker_17) [hassio.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.105.1.
20-02-06 20:09:07 INFO (SyncWorker_17) [hassio.docker.interface] Stop homeassistant application
20-02-06 20:10:14 INFO (SyncWorker_17) [hassio.docker.interface] Clean homeassistant application
20-02-06 20:10:20 INFO (SyncWorker_14) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.105.1
20-02-06 20:10:45 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-06 20:12:25 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-06 20:20:34 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-02-06 20:20:34 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-02-06 20:20:35 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 0 new - 0 remove
20-02-06 20:22:27 WARNING (MainThread) [hassio.homeassistant] Don’t wait anymore of Home Assistant startup!
20-02-06 20:22:27 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
20-02-06 20:22:27 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.104.3
20-02-06 20:22:27 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.105.1 to homeassistant/raspberrypi4-homeassistant:0.104.3
20-02-06 20:22:27 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.104.3.
20-02-06 20:22:29 INFO (SyncWorker_3) [hassio.docker.interface] Stop homeassistant application
20-02-06 20:22:30 INFO (SyncWorker_3) [hassio.docker.interface] Clean homeassistant application
20-02-06 20:22:31 INFO (SyncWorker_18) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.104.3
20-02-06 20:22:56 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-06 20:24:31 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-06 20:24:41 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-02-06 20:24:41 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.104.3
20-02-06 20:24:42 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup images: [‘homeassistant/raspberrypi4-homeassistant:0.105.1’]