0.110: Speed! OpenZWave beta, HomeKit Cameras, ONVIF, Calendars

[frenck (Franck Nijhof)]

@Blair_Pollard

Headers on entity card show up if you edit the card then save but as soon aas you refresh the page they disappear again.

The Custom Header hasn’t updated yet. Disabling it the only option for now.

[Blair_Pollard]

I dont have custom header im on about this:

entities:
  - entity: light.hallway_light
  - entity: climate.heating
  - entity: binary_sensor.front_door_open_close
  - entity: binary_sensor.hallway_motion
  - entity: lock.front_door_lock
header:
  image: /local/hallway.jpg?v=8
  tap_action:
    action: navigate
    navigation_path: /lovelace/hallway
  type: picture
show_header_toggle: false
type: entities

the header image appears when saved but after refresh the images disappear again.

[Hagakurje]

@AJStubbsy

I have this same problem. If I enter in to configure UI and then close, it’s back to 3 columns but if I close and reopen in Chrome, it’s back to two. Did you resolve this? I’ve cleared cache, just in case.

Unfortunately no, 2 columns at all

[LongDono]

@sender

Might have nothing to do with 110, but since I wanted to use openzwave (beta) I uninstalled zwave2mqtt add-on but the left menu item is not going away. Any hint?

You manually added the menu option. Look for and remove it from your configuration.yaml:

panel_iframe:
  zwave2mqtt:
    title: Z-Wave to MQTT
    icon: mdi:z-wave
    url: https://yoururl//ip:8008

[Bram_Kragten]

Fix https://github.com/home-assistant/frontend/pull/5945

[sender]

Yes, that was it. so stupid… I have added my panels to
panel_iframe: !include panel_iframe.yaml

And therefor I couldn’t find it in my configuration.yaml…
Thank you!

[paddy0174 (Patrick)]

I have to ask, is this the “Starnberger See”? Great avatar!

[LongDono]

@KmanOz

My frustrations come out in my reposnses because I rely on Home Automation too much and it stresses me when it’s down. It’s my fault. I will turn off watchtower because I cannot control my environment with it turned on and surprising me with an update. I need a production and testing server though but my point is I shouldn’t really.

I can certainly sympathize, but as you said, you should not be using Watchtower on applications that are in rapid development. I don’t use Watchtower but also don’t deploy x.0 releases due to wanting to maintain stability and not wanting to restart HA/Z-wave network each day to apply the speedy fixes that usually follow.

[LongDono]

Aha, yes, I suspected you might have had an include but didn’t want to make my message too complicated, lol.

[Egoman]

Thank you for your response. I took it out and rebooted and it worked, so I added in arming_time and restarted and it seems to be working again now. Thanks for your help.

[bastienh]

How can I hide the calendar panel ?

[Esiravegna]

I got crashes every two minutes, with this error log:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/stream/worker.py", line 77, in stream_worker
    raise StopIteration("No dts in packet")
StopIteration: No dts in packet

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/util/thread.py", line 20, in run
    run_old(*args, **kwargs)
  File "/usr/local/lib/python3.7/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/src/homeassistant/homeassistant/components/stream/worker.py", line 81, in stream_worker
    hass.loop.call_soon_threadsafe(stream.outputs[fmt].put, None)
KeyError: 'hls'
2020-05-20 11:31:32 ERROR (MainThread) [root] 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

Anybody else?

[Michaukrieg]

I had the same problem with alarm_control_panel and I suspect the thing is that it doesn’t exist anymore on triggered state. This is based on:

The time the alarm stays at pending when triggered has changed from delay_time of the previous state + arming_time (previously known as pending_time ) of the triggered state to only the delay_time of the previous state.

The solution is to set delay_time on the armed_* state instead.

[sophof]

Fantastic release, congrats. I would suggest for most people to in general not upgrade straight away unless you see something specific of your interest in a changelog. This’ll prevent the frustration I see in this thread.

Imo the release schedule home assistant has is very satisfying, upgrades/new components can be released pretty quickly this way and stability is usually guaranteed after a few days.

[starob]

Yes it is.

Thanks

[Blair_Pollard]

thanks any idea when it will get pushed out?

[rsachoc]

If you’re using watchtower you must be using the docker instance, why not just downgrade back to 0.109, its easy to do with the docker image.

[KennethLavrsen]

General comment related how breaking changes are communicated and maybe also part of the YAMLGate noise.

This relates to some - not all - breaking changes which are deprecating and later removing YAML configuration of an integration and replace it by GUI config.
My evaluation is that the users are not always given a clear migration instruction how to go from YAML to GUI. And it is not always the same way it is done so you cannot assume it always works the same way

In some cases you cannot migrate, and have to setup the integration again. In some cases upgrading pulls in YAML content and YAML is from then on ignored and can be deleted. In some cases YAML wins over GUI in deprecation period, but then what when the YAML support is removed?

The migration is normally not described in the main documentation. And I agree with that because it becomes confusing word-cruft that confuses users that just start using the integration.
Best is to add the few lines of text in the release note. Then you have the info when you need it.

In this 0.110 release a GOOD example of how to write the release note is the Manual Alarm Panel. I use this and I am affected by this breaking change. The release note gives exactly the information I need to upgrade to 0.110. This makes the breaking change a little annoying but easy to live with and I will have forgotten the pain in an hour.

A less good example is Mill integration (which I do not use). The release note says that YAML is removed and the integration now uses GUI. But not a word about how to migrate. Not in release note. Not in documentation. Not even in the linked PR. If the migration is that the info is pulled over and you can delete the YAML after upgrading HA, then it should be stated in the release note. It takes less than 10 words.

Another almost perfect example is the breaking change for Blink. It says that the info is pulled in. And I assume you can delete the YAML after the upgrade. It could say that and there would be no doubt.

In general. Many of you do a great job with the release notes. But there are still some of you that could have a huge positive impact to upgraders by writing 1-2 lines of release note text describing how to migrate. And only the author of the code change knows this detail so it is difficult for the rest of us to help. I am sure you all try to do your best and simply do not think about it.

[MandM78 (Greg)]

I’m having the same sort of issues with my Lovelace cards. Had my home view set up 3 columns wide, upon refresh, it goes to 2 columns and requires scrolling. If it hit “Config UI”, then immediately x out, it goes back to the proper 3 column view. But if I reload the page, it goes back to 2 columns. I also have a map page that was supposed to be 2 columns wide, but upon reload goes to a single column.

[frenck (Franck Nijhof)]

That is good feedback @KennethLavrsen, thank you