Monday is the first day of the week according to the international standard ISO 8601, but in the US, Canada, and Japan, it’s counted as the second day of the week. So we have to add the Middle East to this list 
1 Like
i have this issue too. Restart of HASS every 10 minutes or so.
Uncaught exception
Traceback (most recent call last):
File "av/container/output.pyx", line 22, in av.container.output.close_output
File "av/container/core.pyx", line 267, in av.container.core.Container.err_check
File "av/error.pyx", line 328, in av.error.err_check
File "av/container/pyio.pyx", line 39, in av.container.pyio.pyio_write_gil
TypeError: 'NoneType' object is not callable
It’s just starting the depreciation so do yourself a favor and wait until the version where they remove it entirely. By then all kinks and gotchas will be documented by other users and you can safely and confidently remove it before upgrading.
Can you create an issue in the front end repo? When you create the issue if possible to remove anything custom from it and show a screen of this happening.
I am not seeing these issues and would like to know the details of the device you are on as well
looks like this “speed improvment” release broke my KNX wind speed sensor (irony?). It worked just fine in 0.109.6. Any ideas? Didn’t read anything about a breaking change in xknx
Error while setting up knx platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/src/homeassistant/homeassistant/components/knx/sensor.py", line 32, in async_setup_platform
async_add_entities_config(hass, config, async_add_entities)
File "/usr/src/homeassistant/homeassistant/components/knx/sensor.py", line 53, in async_add_entities_config
value_type=config[CONF_TYPE],
File "/usr/local/lib/python3.7/site-packages/xknx/devices/sensor.py", line 34, in __init__
after_update_cb=self.after_update)
File "/usr/local/lib/python3.7/site-packages/xknx/remote_value/remote_value_sensor.py", line 219, in __init__
raise ConversionError("invalid value type", value_type=value_type, device_name=device_name)
xknx.exceptions.exception.ConversionError: <ConversionError description="invalid value type" device_name="Wind speed" value_type="speed_ms"/>
thanks
edit: looks like the knx type changed from speed_ms to wind_speed_ms. Maybe worth a mention in the breaking changes.
2 Likes
I have another issue…ALL codes placed in CUSTOMIZE.YAML file are not running.
Thanks,
Jose Henrique.
1 Like
Well, what do you mean removing everything custom… then nothing left but weather card and dividers ?
Well, that is a first for me… Tried updating tot .110 and got the following:
“Error: Unknown Error, see logs”
IN the logs is see
20-05-20 16:37:02 ERROR (SyncWorker_8) [supervisor.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.110.0 → 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.110.0: No such image: homeassistant/raspberrypi3-homeassistant:0.110.0”).
404 usually means that there is not enough free space left on the device.
That is a custom card, please report it with the author of that card.
Thanks 
1 Like
Hmmm ok. That is strange. Will look into it. Thanks.
Excellent upgrade!
1 Like
Correct. To make sure nothing custom is messing with the card.
Feel free not to if that is too much to ask it just eliminates any outside of core stuff from our debugging
“for 0.110, we have upgraded all integrations that didn’t support it yet!”
Still can’t get rid of Heos…
After updateing to 0.100 I am having to probles:
First problem: I am using mopidy media player and google TTS in order to announce different information. That is no longer possible. I don’t use SSL. I have restarted mopidy palyer. Also i have tested the player with radio stream and it is working.
My second problem is related to the picture entity card. I have configurations that determinates color of some icons. I am using: ‘–paper-item-icon-color’ prop, but it is not working anymore.
Hmmm… apparently missed HEOS 
Could you report an issue about that?
https://github.com/home-assistant/core/issues
Thanks 
1 Like
docker logs (name or container id)