2022.11: A heck of a release!

[zigomatic]

Hello , Great HA release, it’s again amazing work !

I see a change in automation mode: restart which now, not stoping the previous automation when automation start again with another trigger.
It’s appearing on automation using trigger with duration. I use motion start and motion stop (for duration:2min).

If a motion is start: light is on
if motion stop for 2min: light is off.

I see that motion start is appearing after 20sec of motion stop but the light is going off with the previous automation

Previously (2022.10.4), if a new trigger is coming, the automation is fired and the previous automation was cancelled (which is the purpose of restart mode).

[sanschaussure]

Thanks for the new release!

I’ve discovered one change in my own installation: All locally stored images/icons in my Picture Elements Cards are gone. Files are still in place (folder www) and I made no changes in my cards so far. No error messages in the log files.

Edit: Solution adding “width” as described in the issue below make the icons appear again.

[c1c3r0]

2022.11: A heck of a release!

I have a few Picture Elements cards configured to control my lights, but this is now broken - images on top of the picture are now gone and nothing happens if I click on the spot where the dots (images) should be. Resources (images) are locally accessible. I didn’t find anything noting why this could be broken (in breaking changes for instance). Anybody else with the same problem? This is my Picture Elements card config: [image]

I’ll open an issue on Github.

Picture Elements Card - missing overlaying elements

[wtv1211]

This update brings up statistics when clicking an entity that records statistics instead of the entity’s history and I don’t want that, it’s way less precise than it was. Any way to revert this behaivor without rolling back core update?

[cataseven]

Anyone get Invalid Config Error after restart?

Invalid config

The following integrations and platforms could not be set up:

• ssdp (Show logs)
• default_config (Show logs)

Please check your config and logs.

Logger: homeassistant.setup
Source: setup.py:357
First occurred: 11:24:11 (2 occurrences)
Last logged: 11:24:11

Unable to set up dependencies of upnp. Setup failed for dependencies: ssdp
Unable to set up dependencies of dlna_dmr. Setup failed for dependencies: ssdp

[arganto]

I love this release. Water uage, First Day of the Week. New cards. Esp. Icons in automationlist Just everything…

… BUT

Long-term statistics in the entity dialogs without giving he user the choice of having it, is really really not good.

During beta times there where a lot of complains about this from a lot of users. And at least I have seen only one user, who wrote, that there might be some cases, where this is helpful.

In all of my cases, it gives no benefits and only hides the real short history data, I’m interested in, when I click on the details. I want to see the raw data, the e,g, raw fuel prices, the raw power values, when it changed to exactly what and when and from what. And no mean or may or min in the used timeframe.

I respect, if the developer, who has implemented this likes this personally and implemented it because of this. But please please give the user the choice to have this or the really useful raw view as before.

[AlessandroTischer]

With this update my state-switch cards don’t work anymore (they don’t show anything at all). Here is an example:

type: custom:state-switch
theme: mashrooms
default: default
entity: user
states:
  Famiglia:
    type: weather-forecast
    entity: weather.openweathermap
    show_current: true
    show_forecast: true
    theme: Mushroom
  default:
    type: custom:weather-card
    entity: weather.openweathermap
    current: true
    details: false
    forecast: true
    number_of_forecasts: '5'

Any advice?

[CChris (Christoph)]

It does only show the “long term statistics” with min / mean / max for entities that have such history.

you can change the behave by disabeling the “min” / mean" values, for example:

full statistic:

disabled min & mean:

other sensors, that don’t have a long term statistic, will just show the “state history” as we know it:

I think, that’s a pretty good compromise - it could maybe be optimized… for example while providing the following in the yaml file:

default

tap-action:
  action: more-info

idea:

tap-action:
  action: more-info-statistics

[Mariusthvdb (Marius)]

@CChris

other sensors, that don’t have a long term statistic, will just show the “state history” as we know it:

sure, but the point is, that all of the sensors we are interested in are enabled in the LTS, so now show these graphs.

and they don’t convey what we are after: state changes… we can see the actual state changes by clicking on Show more though. But that is yet another click.

[arganto]

@CChris

I think, that’s a pretty good compromise

No! It is still only a mean and not the needed/wanted real data. What brings a mean of 5 if the values are in the timeline of the timeframe 00001111599990000.I wand to now, when it was 1 and when 9 for example.

[arganto]

@Mariusthvdb

and they don’t convey what we are after: state changes… we can see the actual state changes by clicking on Show more though. But that is yet another click.

And this removes the temporarily “saved” entities of the history view every time. If I put there 5-6 entities I want to monitor during the day, they are gone with every “show more”.

[Nazze.de]

Hi! Great release again. Will tiles support templates in the future?

[Mariusthvdb (Marius)]

Arganto, the devs have stated in #beta this is what it is now, and we will have to see what the future brings. Paulus doesnt like the ‘option’ idea (which I personally feel is too bad really, what’s HA without options…)

No matter how I have tried the last week, I can not find any generic use for the new statistics graph. The few occasions I do need them, I use a dedicated statistics-graph card.

The reason we have this is for frontend efficiency, supposedly this would be way faster. Honestly, there’s not a single card in my complete setup that draws faster now.

The few cards combinations using history that in fact cause trouble now and then are apex charts and minigraph cards combined.

the move from 1 hour to 5 minutes is a bit less cluttered, but I still find the graphs terribly unclear, and they dont hold the info I am after. Might as well not show them at all for that matter. But thats me ofc, as always ymmv.

[CChris (Christoph)]

sorry - I cannot really agree…
I don’t have much sensors providing / using the long term statistics… most of them are valid for my EV battery… and if I disable “min” and “mean” - and only use the “max” value on the graph, that does exactly match the statistics I had before…

max != mean
Maybe, you can exactly show, what you are meaning with “They don’t show state changes”?

Personally, I have to say, that everywhere - where the new Min / Mean / Max statistics are shown - it does totaly make sense to me …

[Mariusthvdb (Marius)]

@CChris

I don’t have much sensors providing / using the long term statistics

then you wont have the issue…

@CChris

here the new Min / Mean / Max statistics are shown - it does totaly make sense to me …

well, what are your seeing here then? the mean voltage isnt that useful? or the max/min for that matter. on a certain point in history you need the actual voltage, and not all of those derivatives ?

[arganto]

First. As I said. If you like it fine. Because of this I suggested the option. Currently you are (only) the second who likes this. But only, because you do not see the disadvantages until now?

Secondly, see above. 00001111599990000. If you have this values in the timeframe, you will not see, when it changed to 1 and when to 9, but only see 5. And you will see 0 and 9 for min max. but not that was a long time 1.

[CChris (Christoph)]

@arganto

Currently you are (only) the second who likes this

hm… probably, I am only the second one who replied here that I do like it
I think - most of the people just don’t care - and don’t reply at all…

The thing is:
When I need the history, I want to see a statistical view of Sensor values.
I don’t care, if my voltage was “0” for a second or two - three days ago.

If it is 0 for a time where I need to worry about, this will be reflected by the Min and max and also by the Mean value…

Every other “immediate” state change - can still be covered by automations, scripts and whatever else.
The “history” should provide a history and a statistic - and this is still the case, in my eyes.

But there’s an easy solution for that:
You can still create template sensors that use the state of your actual sensor - but don’t have “state_class:measurement”… then, you should get the history just as you are used to it.

For the majority of people, I still think, the long term statistics are still working great… and we already had to use templates if we wanted specific sensors to write them (but we were never able to see these without having a dedicated statistics card on the dashboard)…

[bjorn.sivertsen]

Getting insights into water usage

(…)
Although water is not strictly “energy”, it is still a valuable resource to track. It is often tightly coupled with energy usage (like gas) when using hot water, and the gained insight can help you reduce your ecological footprint by using less water .

Perhaps it would make sense to rename the dashboard to Utilities?

[Mariusthvdb (Marius)]

as said, it all depends on your wishes/needs.

Having a total of 4639 entities, of which 2225 are sensors. I curated my filters on recorder, so it only tracks about 230 or so. Of those, I might need max 10 statistics graphs. Which I added to my frontend.

The rest I ‘need’ the actual state changes. That is because I regularly check the more-infos on those. Power sensors for example, or temp/humidity. I want to check the immediate effect of opening a window etc etc. clouds on the solar panel…

I love the imagery of the statistics graphs, but for my usecase they are only beautiful to look at.