2021.11: Icon picker, device links and entity categories

Blog
286

New cosmetic issue in 2021.11.1 - some icons in Lovelace are bigger than the others. Clearing cache doesn’t fix it.

image
image1125×2436 228 KB

287

I had the exact same issue and this worked for me.

288

What did, resetting cache?

289

For mobile devices you can install this:

There’s a discussion topic here: https://community.home-assistant.io/t/lovelace-swipe-navigation/113806

2021.11.1 fixed the vacuum sensor values. I’m about to open an issue regarding it changing to seconds instead of hours. Are these the issues you are referring to?

290

I just found the culprit of my lovelace disappear after upgrade. Anything that have

  - type: media-control

will drop the entire lovelace from HA. 2021.11.1 did not fixed this problem

291

See above. Atomic Calendar card is known to cause the issue. Other than that, I don’t know.

292

There is a custom card (FORMERLY: an addon) for that. Searching HACS for “Lovelace Swipe Navigation”

1 Like
293

I did not used that card.

294

Other custom cards cause the problem too. Use the browser developer tools (F12) to identify the custom card that’s causing the problem and remove it (or update it, if there is a fix). IIRC mini media player is also a problem card. There may be others too.

295

custom card

1 Like
296

No, this was a reply to your post about the Tuya Integration. Changing the password to a new one and back again is what fixe that.

297

“This release has a more permanent fix for the issue, preventing it from happening. If you can’t upgrade to 2021.11 right now, we have also published Home Assistant 2021.10.7, which has the same bugfix included.”
Will the DST bug also be fixed in the 9.* branch? Since the energy dashboard has been broken ever since 10.* came out and is still broken in 11.*. → energy dashboard data moved up a place in most recent update · Issue #57340 · home-assistant/core · GitHub

298

No, there are no plans to do that.

299

Then please fix the energy dashboard.

300

Be patient.

301

Define patient, how long will I be stuck at 9.7? This bug was there the entire 10.* branch and were now up to 11 and no one has been assigned.

302

Until it’s fixed. This is the nature of bugs. Some things get fixed fast, some don’t. If it’s not reproducible, the wait is usually longer.

303

11.1 Brakes zwave js did not respond after added a device

304

tried your suggestion but I recevive still the same error in the front end.

In the log I see this


2021-11-05 11:54:39 ERROR (MainThread) [homeassistant.components.efergy.config_flow] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/efergy/config_flow.py", line 77, in _async_try_connect
    await api.async_status()
  File "/usr/local/lib/python3.9/site-packages/pyefergy/__init__.py", line 463, in async_status
    self.info[TYPE] = _data[LISTOFMACS][0][TYPE]
KeyError: 'type'
2021-11-05 11:54:42 ERROR (MainThread) [homeassistant.components.efergy.config_flow] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/efergy/config_flow.py", line 77, in _async_try_connect
    await api.async_status()
  File "/usr/local/lib/python3.9/site-packages/pyefergy/__init__.py", line 463, in async_status
    self.info[TYPE] = _data[LISTOFMACS][0][TYPE]
KeyError: 'type'

If I put a wrong api key I receive the error INVALID AUTHENTICATION
If I put a correct api key I reeive the error UNEXPECTED ERROR

305

Icon picker doesn’t come up in entity customisations