Is that some sort of custom card?
If so raise an issue with the developer.
A a side note, I would be interested in seeing any / all automations that rely on either the group of any of these individual booleans. Thank you.
Sorry I had a report of a new release of HA to download I go to configuration but I can no longer find the update button what happened?
Furthermore, before the localization of the car through BMW connected worked and I was able to locate the car on the map with the attributes on the card (which are now no longer visible) now neither the map nor the attributes work anymore. Can you help me?
No this is not anything custom at all. I am just setting up a value in the yaml that i just display on a card. The same issue happens with just a simple entity card. All values are still not known while if i click on them you clearly see there is a value.
Look at sensor.sun2000l_4ktl in developer tools states. What are itās attribute values?
Which integration generates this sensor?
Look in your log. What errors do you have related to this integration?
Which card are you using for that āviewā ? . picture-entity-card ? ā¦ and as mentioned above, a āsnippetā of code, and no logs, is not much to go on
PS: i had similar āissueā entity exist in configurations/entities and is reporting correct, cards donāt show
What really solved it, im not sure, as i did several things, and in between all the āstandardā things, like clearing browser, restart, reboot etc,etc. ā¦ and in Picture-entity-card i had to ācheckā Live instead of āautoā ā¦ iāve never noticed this setting before 
, but obviously 2022.4 changed some behavior, which getās reflected some places in Frontend, depending on Card, Settings etc. , beside the āAttributeā changes ( Read Release Note)
Edit: during my ātroubleshootingā 2022.4.1 + 4.2 also popped up( and i applied, no reason to continue troubleshooting if an update solves things ), might have solve some, and āchangeā others
Edit2: ā¦ Just for the record, im on 2022.4.3(since 04:AM), thou for this i had to Reboot system today, as it started(after an hour or so to Spew Errors of āpending messagesā (more than 3000 in 10 hours) ā¦ no idea what those mend
I resolved the issue. It seems the update did broke some things but i had already a long pending update of a custom component via HACS (huawei_solar) that i kept pushing back. I know update the component as well and reconfigured some of the sensors. Seems to be working again now.
1 Like
I really like them groups!
The one Iām missing though are notify groups. It would be really cool to also be able to create notify groups as helpers through the UI. Hopefully in 2022.5.
Hello everyone, I need help after the last update of the Home assistant 2022.4.2 release I find myself in the form that I am attaching the presence of a new release, the 2022.4.3 to be updated, but when I go to the āConfigurationā form that I am attaching later the update release function no longer appears as it did before and therefore I donāt know how to update the new release. Can you help me? have you also encountered this problem?
Have you tried the usual āstepsā, clear browser cache, refresh browser, close-open browser ?
Iām using the Blueprint: ZHA - Lutron Connected Bulb Remote, 4 buttons (On/Off, dim up, dim down). The dim buttons have failed with all 2022.4.x releases. Reverted back to 2022.3.7 and things are fine again. I see the latest releases include fixes for āZHA - IKEA five button remoteā that had similar problems, but the changes donāt seem to work for the or the Lutron Remote. Does anyone have a fix for this? Thanks.
2022.4.3 kills all zigbee devices conpletely after time using Conbee II, on version 2022.3.6 everything was working flawlessly, 3.7 broke hass completely, had to restore, groups are just more user friendly Scripts, basicly for people who has same problem with ZHA you can do groups in scripts and yaml (not that hard), at least until update fix will roll out
Had you made any changes to zigpy? Extra quirks or anything?
Not a single change for few months
I donāt mean for a few months, I mean forever!
Since 2022.3.6 not a single change, if that is what you mean
There is clearly a breaking change that is not mentioned in this release since everyone has issues with ZHA.
As far as I have seen it seems the message structure has changed and another argument is added, this has had the result that it fails for most people.
1 Like
I also read that if people had made changes to zigpy (I think to get new quirks) 2022.4 could upset their zha. I do not know much about zha. I do know that zigby is itās underlying library. So perhaps only breaking for people why had made changes to get additional stuff into zigpy. There is a lot about it in this very thread.
1 Like
Appreciate this doesnāt help people who are having issues, but I can confirm Iām running HAOS on barebone nuc, ZHA and Conbee II, Iāve had no issues with Zigbee on any of the 2022.4 releases. Iāve got 77 zigbee devices, and none have had any issues. For once I might just be the lucky oneā¦
1 Like
But do you also see the extra argument in the message?
If you listen for zha events and look at the array āargumentsā, does it have three or four items?
I think this is more related to sending zigbee devices (remotes)
1 Like