2021.12: New configuration menu, the button entity, and gorgeous area cards!

Thank you Prodigyplace for you answer.
Finally, I restarted my HA OS several times and wait around 1 hour. Then my problem is resolved.
All the missed entities are there and my automations are working again.
To be honest i don’t know what happened.

Hope this could help some of you :slight_smile:

Maybe I’m overseeing some things. I was happy to see that a “push button” was added. But seems it’s only for certain devices or actions?

I would like to see a “push action” option to add to the “tap action” of a button. I have some WOL devices integrated and I’m opperating them now with the “toggle action”, which is a bit annoying because it’s showing an “on/off state”. So now I need to toggle first. But I would like to just “push” to start a WOL device.

any one else having issues with 2021.12.6 with Hue Tap switches events not coming through to HA. While Hue app registers the button presses i have no luck getting all my automations running with the hue taps.

I am seeing something similar.

e.g
An automation turns my speakers off if the media player is idle for a set time. I heard the speakers turn off, but lovelace dashboard still showed them as on.
When I checked the state of the entity ( by clicking on it in the dashboard) it was off, so the state machine knows about the transition, but lovelace still shows it as on.

When i refreshed the browser lovelace showed the correct state.

Not ideal.
EDIT
I just upgraded from 2021.12 .4 to 2021.12.6 so I don’t know if this is an issue with 2021.12.6 but it was ok in 2021.12.4

1 Like

Thanks @denisbondar for your very detailed explanation. It took me a while to narrow down the issue to that MikroTik add-in and solved it for now by first removing all devices from the integration and then removing ALL Mikrotik devices from my ‘core.device_registry’. Didn’t had that topic with the ‘deleted_devices’. Need to invest more time to fix it your way.

It’s a bug with 12.6. See: Problem with values not updating in frontend since update to core-2021.12.6 · Issue #11039 · home-assistant/frontend · GitHub

I had the same experience with Android (though I think all browsers/devices are affected). I downgraded back to 12.5 and I’ll wait for 12.7 with a fix.

Edit: it’ll be fixed with 12.7: Bump HAWS to 6.0.1 by balloob · Pull Request #11042 · home-assistant/frontend · GitHub

2 Likes

Since this version it seems that either the property allow_unreachable: true has no longer an effect or at least does not what it should, therefor my OSRAM plugs are mostly unavailable within home assistant but can be controlled via hue app. Inside of hue app they are marked as unavailable.

1 Like

Since 2021.12.6 after a Core reboot the popup is stuck on " wrapping up startup".
Like here: https://community.home-assistant.io/t/never-ending-startup-after-update/357028

Log seems fine and everything seems to work, could this be an issue with 2021.12.6?

Weird, after some more reboots it seems to work normal again.

Yes I get that too. And sometimes all the sidebar entries don’t appear
I think everything works as normal though because if I refresh the browser it goes back to how it should.

But it is annoying…

Also I have restarted a few times and still get the issue.

Updating to 2021.12.7 appears to have fixed the “wrapping up startup” problem.

1 Like

2021.12.06
Just updated and found tplink switch status is not being updated. Switch will turn on but status still show is off, and if is on inital when HA is loaded it show on but never change to off status even if it turned off via call service.

Update to 2021.12.7

Hi, cant install Update to 2021.12.7 :

Blockquote
21-12-30 00:37:05 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2021.12.7
21-12-30 00:37:05 INFO (SyncWorker_5) [supervisor.docker.interface] Updating image ghcr. io / home-assistant / qemux86-64-homeassistant:2021.12.5 to ghcr. io / home-assistant/ qemux86-64-homeassistant:2021.12.7
21-12-30 00:37:05 INFO (SyncWorker_5) [supervisor.docker.interface] Downloading docker image name with tag 2021.12.7.
21-12-30 00:37:16 ERROR (SyncWorker_5) [supervisor.docker.interface] Can’t install name qemux86-64-homeassistant:2021.12.7: 404 Client Error for http+docker :confused: /localhost/v1.41/ images/ghcr. io/home-assistant/ qemux86-64-homeassistant:2021.12.7/json: Not Found (“no such image: name 2021.12.7: No such image: ghcr.io /home-assistant/ qemux86-64-homeassistant:2021.12.7”)
21-12-30 00:37:16 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed

It’s there, maybe whatever mirror you are being sent to has yet to catch up.

Can i check it from ha cli ?

Same here. Lovelace page would reload after the startup.

However… Somehow my history page keeps loading. Is anyone seeing the same? How do I troubleshoot this / where do I start?
(This is ~5 minutes after I click the “History” from the left panel.)

Any update on that? Or at least a workaround? Really bad, that a lot of my things are no longer working, because I cant control the osram plugs.

I can get the Jellyfin integration configured and it sees the music library I set up, but the music doesn’t actually play. It does not seem to work in the web browser on my computer or in the Home Assistant Android app. I have the player set as ‘Web Browser’ but all I get is sound player controls with 0:00/0:00

Without a github issue, nobody will look into this. Did you check if someone already created a github issue for this, and created an issue yourself if applicable? If not, kindly go to github to check that out.

3 Likes

cant see Allow_unreachable as an option for osram integration

Osramlightify - Home Assistant (home-assistant.io)

and doing a search with allow_unreachable shows that the only entries with it are to do with HUE