Perfect release on my end, no real issues. Loving the new log messages about renamed fields, MDI icons and automations that need adjustments. Will take some time to rethink some automations but the new modes are awesome!
Aqara relay support 
???
Use this command:
ha core update --version=x.y.z
1 Like
I am also getting the rollback.
I think it might be related to sensor templates.
I have for example this:
xiaomi_fan_speed:
friendly_name: "Xiaomi Fan Speed Level"
unit_of_measurement: "speed"
value_template: "{{ state_attr('vacuum.xiaomi_vacuum_cleaner', 'fan_speed') }}"
Value template works in template editor via UI, but the state of the entity is unknown.
After the update, that is the only thing I noticed not working, no error in log. It waits for 10 minutes with “Home assistant has not finished loading” message and then rolls back to 0.112.4.
rpi4 home assistant OS
1 Like
Upgraded from 0.112.4 but then needed to rollback because most of my camera feeds would not load and then the gui interface for supervisor would freeze up completely and not load. I had to run the ha snapshots restore command on the host to revert back to my last backup. Any ideas?
If you are seeing the Don’t wait anymore of Home Assistant startup and getting rolled back to the previous version or Home Assistant is starting up never finishes, add the following to your configuration.yaml and try upgrading again to 0.113.1.
logger:
default: info
logs:
homeassistant.core: debug
Look for log messages similar to 2020-07-23 23:31:31 DEBUG (MainThread) [homeassistant.core] Waited 60 seconds for task: <Task pending name='Task-585' coro=<async_setup.<locals>.wait_a_bit() running at /config/custom_components/block_startup/__init__.py:56> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fd56a717520>()]> cb=[_wait.<locals>._on_completion() at /usr/local/lib/python3.8/asyncio/tasks.py:507]> to determine which integration is the cause.
3 Likes
I tried to upgrade twice, each time rolled back.
Then saw this advice on the logger, added it, but after rollback the log did not contain the information from the time of the delay.
Tried to upgrade a 4th time, and this time was watching the log … and it succeeded.
Upgrade completed but just sits at “Home Assistant is starting, not everything will be available yet.”
This happened to me as well. No errors. Downgraded to 0.112.5 for the time being.
A few other notes, not sure if they are relevant. I have switch entities with icon templates, and many were displayed as open circles or lightning bolts (and the switch didn’t function properly). Also, zwave (I’m still on legacy, not the beta) did not start automatically. It would fire up if I started the network manually however.
Thanx for the tips regarding the zeroconf and cast issues.
I Tried to upgrade to 0.113.1 which includes the zeroconf fix. But my Google Cast integration is still failing.
I check the Google Cast in integrations and the devices are still listed, but when you click on them they’ve all gone to “Unavailable” and all scripts/automations start complaining that the media_players for the chromecasts audio and the google home mini’s cannot be found.
If I delete the Google Cast automation from the integrations and add it up again to rediscover them, the integration is added back to home assistant but the devices are not.
But when I check the mDNS for possible networking issues using avahi-browse I get all the google cast devices listed on their proper _googlezone._tcp on both the ethernet and hassio interfaces (I’m running home assistant in a docker container with network set to host as per instructions, so Home Assistant should be able to see the devices on the ethernet interface).
I’m kinda lost, as I don’t know if I’m the only one having this Google Cast Integration issue, and if its something I may have misconfigured and had been working up until now that 0.113 breaks it. The only changes I’ve seen for the Google Cast Integration on 0.113 is the upgrade to pychromecast 7.1.2.
So I’ve downgraded to 0.112 for the time being as in that version the Google Cast integration still works perfectly.
I’ve started an issue on the github https://github.com/home-assistant/core/issues/38188 hopefully whatever this issue is will get sorted out.
Is anyone having any issues with scenes I find sometimes they hang and don’t execute for 2 seconds or only exactute half the scene. Was working before the update.
Same issue for me, but tried a lot of time without success.
Thank you but this didn’t help I had 100’s of line but nothing said why at the time it failed.
Hi @KennethLavrsen, you mention that you like having a standard yaml structure as you have many remotes. I would like to offer this variation which works well if you have multiple remotes performing the same function. This uses the Trigger State Object from https://www.home-assistant.io/docs/automation/templating/#zone to determine which entity triggered the automation.
- id: '1595451341852'
alias: Kitchen Lights Remote
description: ''
trigger:
- entity_id: sensor.remote2
platform: state
- entity_id: sensor.remote4
platform: state
action:
- choose:
- conditions:
- condition: template
value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state == 'Button A' }}"
sequence:
- device_id: 5320c28c7c1e45c580aa9a5ad9bc4432
domain: light
entity_id: light.kitchen_lights
type: toggle
- conditions:
- condition: template
value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state == 'Button B' }}"
sequence:
- entity_id: input_select.kitchen_scenes
service: input_select.select_next
- conditions:
- condition: template
value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state == 'Button C' }}"
sequence:
- entity_id: input_select.kitchen_scenes
service: input_select.select_previous
- conditions:
- condition: template
value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state == 'Button D' }}"
sequence:
- device_id: 92c52b6d053e42e5a472e7b017c60032
domain: switch
entity_id: switch.sonoff03
type: toggle
Not a big deal but I’m seeing this error in my logs since upgrading to 0.113
I do have the Add-on installed for Visual Studio code. Looked every where to change the mdi to the right one. is anyone else seeing the same?
I had the same issue with home assistant never completing startup, so I rolled back to previous version.
I now suspect it was due to kodi in my config: https://github.com/home-assistant/core/issues/38160
There also seems to be an issue with 0.113 if you use tensorflow or onvif.
I’m guessing that is from the VSCode add-on being added to the sidebar. You will have to wait for an update.
I have the same addon but I have not added it to the the sidebar so don’t see the warning.
1 Like
Hi All,
I implemented the following automation using the new Choose action to turn on/ off lights based on a door sensor. I’m wondering if there’s a way to add a ‘for’ condition for the sensor on state to turn off the lights when the door is opened for 5 mins?
Right now I have it configured using a delay.
trigger:
- platform: state
entity_id:
- binary_sensor.laundry_door_sensor
action:
- choose:
- conditions:
- condition: state
entity_id: binary_sensor.laundry_door_sensor
state: "on"
sequence:
- service: light.turn_on
entity_id: light.laundry_lights
- delay: 00:05:00
- service: light.turn_off
entity_id: light.laundry_lights
- conditions:
- condition: state
entity_id: binary_sensor.laundry_door_sensor
state: "off"
sequence:
- service: light.turn_off
entity_id: light.laundry_lights
Thank you, this helped narrow down the problem.
I think it is related to onvif cameras.
I created ticket with logs here.
1 Like
Hi @all
I have a Problem with all the wonderful new features. In all the automations I received in visual studio the error message “property not allowed”. Uninstall and install again was no solution. When I check the configuration, the System display no errors. I guess the is a problem on my Visual Studio. Any Idea what can I do?
Many thanks
Frank
Correct. I added it to my sidebar as a test and it generated the error. Will probably be fixed with the next VScode update as mentioned.