0.116: Entities card row editor, restore snapshots and performance metrics

[system]

Home Assistant Core 0.116!

So, how have you been? Fully processed the massive 0.115 birthday release yet?

Honestly, I haven’t. There was soo much in 0.115, and to me, it feels like that release was yesterday. 😅

So, today, a nice size, manageable release that brings some smaller things to the table. Lots of fixes, UI tweaks and improvements; hopefully a smooth sail!

The biggest changes can be found in the Supervisor. @ludeeus has been smashing on his keyboard to add the option to upload and restore snapshots during onboarding. A much-upvoted WTH. As a bonus, he also added performance metrics to the Supervisor UI. Nice work!

As always, enjoy the release!

../Frenck

Entities card editor

You can now edit the entity rows of your entity card. That means you can not only set an entity id, but also set the name, icon and secondary info.

You can now edit the entity row; adjust the name, icon and secondary info.

Also, using special rows will no longer force you use the YAML editor, however, you you can still use the UI editor and edit the special rows. UI editors for the special rows will come in the future.

User and person management combined

We combined the user and person UI, this means that the user configuration panel will only be visible for users that have advanced mode enabled.

The person detail dialog now has a toggle that allows you to give the person access to Home Assistant. If you toggle it on, you can set a username and a password for the person. If you toggle it off, the user will be removed.

This makes it easier to manage the people in Home Assistant, everything in one place.

The person edit dialog now has a toggle to allow a person to log in.

Restore snapshots

You can now upload snapshots from the UI and restores them. You can do this in the supervisor UI in the snapshots panel. But you can also do this during onboarding!

Screen recording of restoring a snapshot during onboarding.

This means you no longer have to set up Home Assistant, add and set up the Samba add-on to then restore your snapshot. Instead, you can just select your snapshot in the first step of the onboarding and it will be restored.

This makes moving to another system a breeze!

Performance metrics in the Supervisor UI

The Supervisor now shows performance metrics in its UI, so you’ll have a better idea of how much resources are used. Thanks @ludeeus!

Supervisor UI now shows performance metrics.

H.256 stream support for Android

@uvjustin added support for H.256 streaming in the Android app, it will use a native video player that is shown on top of the Home Assistant UI. This player will only work in the more info dialog, and can not be used In Lovelace cards.

Automation editor has now weekday support

@misiu added a nice feature to the automation editor. Using a time condition in the UI, now has the ability to select the weekdays the condition should test against.

You can now select the days to match in time conditions.

Python 3.7 deprecated

Python 3.9 has been released on 5 October. This means that Python 3.7 support is now deprecated and will be removed after two months (which will be effective in 0.118).

This is only a concern if you are running Home Assistant Core directly on Python. You can check the Python version Home Assistant uses by going to the information screen in Configuration -> Info.

If you run Home Assistant OS, Supervised or Container, you don’t have to worry about this, as the Home Assistant project takes care of this for you. As a matter of fact, if you use one of those methods, you are already running Python 3.8.

We are currently working on ensuring Python 3.9 is fully supported and tested.

Other noteworthy changes

• MQTT now supports tag scanning, thanks to @emontnemery.
• The Hyperion integration had a large overhaul by @dermotduffy, ensuring this integration now actually works!
• @Misiu ensured the OpenWeatherMap integration supports all languages it can provide.
• The utility meter now supports a bi-weekly cycle, thanks to @hareeshmu.
• @timkoers added uptime sensors for network clients to the UniFi integration.
• The Shelly integration now shows power and energy sensors for roller mode devices, thanks to @firstof9.
• You can now filter history by using glob matching filters. For example, you can now exclude sensor.*_temperature from being recorded. Thanks @bdraco!
• deCONZ has a new option; You can now disable the automatic addition of new devices. Furthermore, @Kane610 also added a service to clean up up orphaned devices. Thanks!

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat.

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

---

This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2020/10/07/release-116/

[Danielhiversen (Daniel Høyer)]

Tibber is now available in Germany . (In addition to Norway and Sweden): https://www.home-assistant.io/integrations/tibber/

If you use this link to signup for Tibber, you get 50 euro to buy smart home products in the Tibber store: https://invite.tibber.com/6fd7a447

[thebradleysanders (Brad Sanders)]

Thanks for another great release!

[p1ranha]

How does it compare to aWATTar with Discovergy?

[Danielhiversen (Daniel Høyer)]

Not familiar with aWATTar, but you can connect Discovergy to Tibber.

[Martinvdm (Martin)]

Nice release ! Small typo: h256 must be h265 stream

[jwoodard80]

Thank you, Thank you, Thank you for making adjustments for allowing seperators to not force YAML!!! Cannot wait to actually be able to add these from the frontend!

I was seriously about to ask a question about that this week, but ya’ll already on it!

[Burningstone]

Update was smooth as butter Great additons and I appreciate all the new features in the UI. Every time I update, I feel more tempted to switch to a Supervised install

[Spartan.II.117 (.Jordan)]

H256 should be H265 throughout the post!

Other than that this looks great!

[123 (Taras)]

I have a few questions regarding the new System Metrics feature.

What is the reason that its appearance on my system differs from what is shown in the blog’s example? This version lacks the bar charts shown in the example. (EDIT: Appears to be due to browser type.)

I’m using the System Monitor integration and it currently reports the following, specifically that processor_use is 1%.

System Metric reports Core CPU usage is 1.1%. I assume this corresponds to System Monitor’s processor_use?

How does Supervisor CPU usage of 6.3% correspond to System Monitor’s processor_use?

---

EDIT

Added: Bar charts not visible using Firefox 81.0 on Ubuntu 18.04.5 (and cache was cleared)

Charts are displayed using Microsoft Edge:

.

[firstof9]

@frenck I’m sorry I didn’t have anything to do with the shelly integration showing power and energy sensors

[anon43302295]

Bar charts working here FYI.

[ludeeus]

For missing bars create a issue in the frontend repo.
As for the stats themselves, that’s provided directly by docker for the core and supervisor containers

[123 (Taras)]

Will do.

How do those stats correspond to processor_use? For example, Supervisor CPU usage is reporting a value (6.3%) that’s higher than total processor_use (1.1%). How does that work?

[Dolores]

I love the “new” format for breaking changes. It makes it sooo much easier for me to scan for ones that pertain to me!

[ludeeus]

The integration probably only looks at the core container 🤷

[mamoel]

Just upgraded from 115.6 to 116.0.

Sadly my Nuki Smartlock 2.0 stopped working.
This is the error message from the log:

During handling of the above exception, another exception occurred:



Traceback (most recent call last):

  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 193, in _async_setup_platform

    await asyncio.shield(task)

  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run

    result = self.fn(*self.args, **self.kwargs)

  File "/usr/src/homeassistant/homeassistant/components/nuki/lock.py", line 80, in setup_platform

    devices.extend([NukiOpenerEntity(opener) for opener in bridge.openers])

  File "/usr/local/lib/python3.8/site-packages/pynuki/bridge.py", line 238, in openers

    return self._get_devices(device_type=const.DEVICE_TYPE_OPENER)

  File "/usr/local/lib/python3.8/site-packages/pynuki/bridge.py", line 199, in _get_devices

    for l in self.list(device_type=device_type):

  File "/usr/local/lib/python3.8/site-packages/pynuki/bridge.py", line 128, in list

    data = self.__rq("list")

  File "/usr/local/lib/python3.8/site-packages/pynuki/bridge.py", line 103, in __rq

    result = requests.get(

  File "/usr/local/lib/python3.8/site-packages/requests/api.py", line 76, in get

    return request('get', url, params=params, **kwargs)

  File "/usr/local/lib/python3.8/site-packages/requests/api.py", line 61, in request

    return session.request(method=method, url=url, **kwargs)

  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 530, in request

    resp = self.send(prep, **send_kwargs)

  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 643, in send

    r = adapter.send(request, **kwargs)

  File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 529, in send

    raise ReadTimeout(e, request=request)

requests.exceptions.ReadTimeout: HTTPConnectionPool(host='192.xxx.xxx.xx', port=8080): Read timed out. (read timeout=20)

I have HASS running in Docker (Synology NAS).

[tom_l]

Ah. That might explain my occasional runaway temperature rise with flat and low system monitor CPU use.

[ttaidapos]

Can anyone for the love of god please point me to a solid command by command guide on how to update python on Home Assistant Core. Probably on my 4th deprecated milestone and everything i’ve tried has always failed. I always end up building a brand new instance and spending hours moving everything over. Please help

Current Version: 3.7.3
Hass Version: 115.6
Platform: Rpi4 4GB

[Codec303]

Nice update, everything seems to be working OK for me.

Looks like I need to update from Python 3.7, is there a recommended way of doing this on Raspbian?