0.117: Quick Bar, compact header, a YAML editor, XBox and Template types

[fribse (Kenneths Teknik)]

[TheFes]

I use this script (see last post) for resuming both TuneIn and Spotify on my Google Home device after a TTS broadcast.
Volume is not included, but shouldn’t be to hard to add as an extra variable.

TTS to media_player and resume stream

2020-09-23 - I’ve edited this post because I could simplify the script a bit, and added the part on how to call this script from another script or automation 2020-11-06 - Another small edit, because I noticed that service: media_extractor was not needed, and media_player.play_media could be used I’ve also added a wait template instead of the fixed delay of 8 seconds which was previously included. Left in a 2 second delay because the media player is idle shortly before the TTS starts, and other…

[kippuh]

After updating to 117.0, the webinterface was not working anymore. If someone else has the same issue, this is how i “solved” it (don’t know the correct messages anymore) via CLI::

• run command “core restart” gives a 500 error with some message like “containerID is marked for removal” and it wont restart
• run command “core update” gives a processed successfully, there after a 404 error.
• run command “core restart” works

there after 117.0 was starting, but my zigbee sensors did not work anymore, but i was able to start the webinterface again and restore 116.4 backup.

[ludeeus]

Yes, for the Supervisor, the plugins and eventually the add-ons it will change, it’s mentioned here https://developers.home-assistant.io/blog/2020/10/29/supervisor-update#releases

[stban1983]

Hi!
since the update, rest sensor is not working anymore.

Platform rest not ready yet. Retrying in 150 seconds.

Am i the only one?

[tom_l]

I have many rest sensors, all working.

[DavidFW1960 (David)]

That’s pretty cool Ludeeus… great info.

[stban1983]

ok so it might be me…

[guixop]

Hello,

Same problem for me, after updating from 0.116.4 to 0.117, HA no longer works, a reboot does not work, it looks like a problem with OZW, I had to restore a full image.

[Ralfkroon (Ralf)]

Looking forward to the Tasmota integration. But after updating I lost all my unused entites!! ;-( I had about 20 of them and after updating 0.

[stban1983]

Go back to 116.4 and rest sensor are working…
How can i enable more logs for rest sensor ?

[icaballero]

How can I downgrade to 0.116.4? I have access to IDE and commands like:
hassio homeassistant update…

[carsten_h (Carsten Friehe)]

I am getting these strange errors (at the end of the log) when onboarding on a fresh installed Hassos 5.4:

...
09:30:50 All core tasks are scheduled
09:30:50 Started Supervisor hardware monitor
09:30:50 Supervisor is up and running
09:30:50 Home Assistant setup
09:30:50 Updating local host information
09:30:50 Updating image homeassistant/raspberrypi4-64-homeassistant:landingpage to homeassistant/raspberrypi4-64-homeassistant:0.117.0
09:30:50 Downloading docker image homeassistant/raspberrypi4-64-homeassistant with tag 0.117.0.
09:30:50 Updating service information
09:30:50 Updating local network information
09:30:50 Updating PulseAudio information
Failed to load cookie file from cookie: No such file or directory
09:32:29 Stopping homeassistant application
09:32:34 Cleaning homeassistant application
09:32:34 Home Assistant docker now installed
09:32:34 Starting Home Assistant
09:32:34 Update pulse/client.config: /data/tmp/homeassistant_pulse
09:32:34 Starting Home Assistant homeassistant/raspberrypi4-64-homeassistant with version 0.117.0
09:32:34 Wait until Home Assistant is ready
09:32:44 Updated Home Assistant API token
09:32:44 Detect a running Home Assistant instance
09:32:44 Cleanup images: ['homeassistant/raspberrypi4-64-homeassistant:landingpage']
09:56:26 Successfully imported 4bdcec99
09:56:35 Partial-Restore 4bdcec99 start
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.
TypeError: Verbindung zum Server konnte nicht hergestellt werden.

That is running for half an hour now.
What can I do?

[eyalco]

How do I activate the compact header in 0.117 or is it by default?

[mcarty (Arturo)]

By default. Uninstall before upgrading the old cc.

[compacthack]

My cameras have stopped too, they don’t appear as entities anymore, so don’t show up in my lovelace UI and automations that use camera/snapshots fail

Error executing script. Service not found for call_service at pos 1: Unable to find service camera/snapshot

[compacthack]

Not sure if this applies to the others having issues with their cameras, I was running ‘BOM’ radar as a camera, The BOM platform is no more, so I commented out the BOM radar camera in my config and rebooted, now all my other cameras have come back to life. Hope this helps.

[Mariusthvdb (Marius)]

that wouldn’t have to do with CH. It’s still working as before, beautifully I might add.
don’t suppose this the intermittent buggy left-side menu has anything to do with that … ?:

, after a page reload it all appears normal again:

[Mariusthvdb (Marius)]

Am I really??
Homeassistant OS
at first believed this to have to do with the beta versions, but now this is on release, should be all ok?

[tom_l]

@icaballero

How can I downgrade to 0.116.4? I have access to IDE and commands like:
hassio homeassistant update…

ha core update --version=0.116.4