3 posts were merged into an existing topic: Journal issues with supervised install after updating to 2022.11
Read a few posts above
https://community.home-assistant.io/t/2022-11-a-heck-of-a-release/483295/252?u=sparkydave
Nevermind, after updating Mushroom theme all good.
A post was merged into an existing topic: Journal issues with supervised install after updating to 2022.11
A post was merged into an existing topic: Journal issues with supervised install after updating to 2022.11
This is misleading. You use heavily customised dashboards and views with third-party cards. Who knows what’s affecting your performance.
2 Likes
after updating to 2022.11.1 last night, my cameras only pop up on press the same size as in my dash lol.
1 Like
I already had it like this on 2022.11.0. Hope to have camera restored to previous behavior when it opened in full size.
BTW are there somewhere release notes regarding version 11.1 ?
EDIT
Ok, I see now
4 Likes
I have tested it in vanilla HA. Of course no difference. Where should it come from in average? Let’s say you have a sensor which is not changing. Then with history you have to read and display two datapoints and a line and 1-2 hover points with display text per 24 hours. For LTE min max and mean, you have read and draw 24*3 datapoints with at least 72 hover points. Where should this extreme example be faster?
If performance would be a reason, a display of a history graph in history work center for 20 days and 100 entities should not be possible at all. But it is. Since “forever” and displayed in microseconds.
Of course, this is extreme, but same the other way round. In average, there will not be any difference. This is unfortunately only a given reason to give any text.
haha, never short on hyperbolic statements you are aren’t you 
Of course, you didn’t realize or cared to ask if this was experienced on a test setup or not. Which, of course, it was and is. Added to that, even in my production instance, there’s an extensive Test dashboard.
So yes, I quite extensively tested this new feature in the last beta cycle. Did you?
Yet, since you mention the heavily customized dashboards (which practically everyone uses I suppose, considering the thousands of posts in the community/reddit/discord/Facebook using the many available custom cards), even on those, the now legacy state more-info panel graphs were instantaneous. (with a few mentioned exceptions).
So, if the move to statistics graphs is about backend efficiency (which I would applaud vehemently) or frontend speed, it yet is not visible nor ‘felt’ in handling the Dashboards.
If it has to do with a move away from ‘states’ centered backend, I could understand that too.
The dev/states page is the worst page in the system, and has been like that for a very long time. So things could be improved upon states handling, agreed on that. Not sure if this is related though.
Other than that, currently, personally, I do not experience any advantage in replacing the history state graphs with statistics graphs. And that’s an understatement.
1 Like
never really noticed that tbh, but, if I click that popup (on desktop), it expands to to full view
No, HHCC plant sensors didn’t make it into this release, the PR is not merged yet into xiaomi-ble.
1 Like
2 posts were merged into an existing topic: Journal issues with supervised install after updating to 2022.11
Great release. Now I can finally check if my neighbors brush their teeth often and long enough 
20 Likes
Is there any link to documentation on how to implement ‘Gigajoule’ in the energy dashboard? I have the ‘/golles/ha-kamstrup_403’ integration running, but i cannot select the energy sensor in the energy dashboard.
attribution: Data provided by Kamstrup 403 meter
integration: kamstrup_403
unit_of_measurement: GJ
device_class: energy
icon: mdi:radiator
friendly_name: Kamstrup 403 Heat Energy (E1)
I think the problem is it also needs the state_class to be total. Maybe try though customize to add that?
Thanks, just did so about several posts that continued that conversation
1 Like
I don’t need to prove anything, because I made no statement about dashboard performance. Burden of proof is on you, and you didn’t qualify what you said originally, but thanks for clarifying now. I think it’s now more helpful to others.