Isn’t the mushroom card guy working for NC now ? I seem to remember some announcement like this ? Would certainly explain the mushroom-like-but-not-quite design 
I already got that “it is not mushroom” - but since Paul is now working for NabuCasa it is clear, where the design came from 
And it would be nice - if we do have at least a “mushroom-alike” card, that the look and feel would match more closer to the original?
at least, what can be done:
In Mushroom Git an issue could be raised that the musroom cards to not apply to the themes font-design (regarding the bold entity status)…
Compared Mushroom / Tile Card with different themes:
2 Likes
Hi guys, I would also like to express my disappointment regarding the more info statistics graphs. No consistency and detailed information are getting lost. Please revert, there are so many other things which could be improved. I have one or two sensors which benefit from this, but this is the minority. A lot of sensor just look unsharp now:
19 Likes
Hi all!
Has anyone else had their power flow diagram fall apart after the update? Or am I the only one having this problem?
I noticed that with this release if you use the map card in a grid card that your home/device is not centered in the middle but centured at the bottom of the page.
Please reconsider the More Info change from history to statistics data by default.
I think it is great to have better access to the statistics data, but when I click for more info, I want to see the fine grained detail, especially for sensors that might change rapidly like power, voltage, (some) temperature sensors.
I want to know When something changed and often want to see how fast it changed.
If a value briefly dropped or spiked, I want to be able to easily see that. There have been times where casually glancing at More Info has alerted me to something that I didn’t know was happening. If I have to dig for it, I’d rarely find those.
The releases have been really great and over the last year or more. So thanks for all the care that has gone into them.
12 Likes
Found a bug. It’s related to a new longer name of CO2 Signal leaf in some languages such as Romanian.
Smart reloading of automations, Water usage, Gigajoule support, What a great release this is! Thanks 
please tell me:
What can you pick from the “old” history information, that you can’t pick from this statistics information?
In my opinion, the new statistics do provide a more detailed way for analysing any potential issues…
And I DO agree, that is doesn’t probably make much sense on all sensors…
But then, it could be considered, if it is required that these sensors have the state_class “measurement” or any other state_class that is writing long term statistics.
In fact, In my opinion, it does make sense to use this type of statistic on sensors that actually generating statistics with min/mean/max information.
For sensors, where I don’t want to use this, I can create templates - or, I haven’t really checked any history … at all…
The correct decission here can be pretty difficult I guess…
We are used to have the History with a clear “state changed from x to y” chart…
But on the other hand - I had to create a Dashboard with statistics card for each entity where I wanted to get such information… having that in the more information is a BIG improvement in my eyes…
What could the compromise be?
A parameter which you can use to decide what type of statistic can should be displayed?
Including both? and make it selectable?
Include a forth option into the graph for “state” - which can then be enabled or disabled?
1 Like
wtv1211’s comment is correct. It depends on the set language whether the figure falls apart or not. If I change the language to English, the graphics will be ok.
I meant with my example, that you easily can adjust Mushroom via theme.
I am getting the OS error and I am running Debian 11
Ok idk then. Submit an issue here and make sure to include your system information as per the instructions in the issue template.
Let me explain. Stats don’t show actual value of sensor state but statistics in a period of time (in 5 minute intervals from what I can see). You don’t know what were the actual values and that is what people are asking for. Example below:
and in reality there were a few measurements in that period of time:
Personally I don’t mind but the problem is that the reason why it was implemented, to load this view faster, is not visible at all. It does not load it faster than before. I have 14 days of history in recorder and not keeping all entities there (especially I’ve dropped motion sensors from my alarm system as they were flooding the db). Using MariaDB with a stable size of 2.3 GB.
9 Likes
Again: You cannot see, when the values occur anymore. Only ± 5 minutes. And you cannot see the real value, but only min max and mean.
If you like this and are not interested in the values but want only to see smoothed graphs which gives you only a trend or impression. Fine. But why do you want to educate the other users, that they can see everything there, what is not the truth. And why would you be against an option, whaqt to show. Leave it to the user. Everyone has another use case.
I will never understand the “I like it, so no option needed, the others have to like it as well”, as in your arguments.
16 Likes
I upgraded to 11.0 but I don’t see any of the new cards. Do I need to enable them somehow? Thanks (First post here. Thanks for all you guys do!)
I am not against an option to change the behave… that’s what I also suggested.
What I do question is the benefit of the old history compared to the new one.
Let me try other examples:
This is a Graph showing the “State” of a humidity sensor… before the update was done.
Am I able to get a real “value” out of the information given in that graph?
This is the same Graph, using the new Statistics history:
I can still see major “drops” or “peaks” in the graph - and I am still able to detect when it happened.
If I am using this for “debugging” - or for getting an insight if my sensors are delivering a wrong value, the timeframe when this happened is pretty much what I need…
Still in my eyes, the new graph does provide all the information I need to dig into an issue with one of my integrations or an issue with a Sensor.
But - the new Graph does still have values in my eyes…
It does clearly show, if a sensor was working in an expected area.
In this specific case for humidity of a terrarium:
If the hummidity drops to a lower value, it should start watering.
If the humidity reaches an upper value, it should stop.
When I am only focussing on the current state of the sensor, it could cause, that it will switch the raining-system on / off / on / off / on / off
Instead, I should use the mean value - and just define the upper and lower range where the mean should be in…
With this graph, I can easily see - if that condition was given or not…
Or am I wrong?
Again - I don’t say anything against an option to swith this on or off…
What I really don’t want is - that this feature will be removed because people are not used to the new statsitics although they could still get what they need from it
1 Like
Thank you so much
Yes. Every data point is the real value at the given point of time. Hover and see.
You have written a lot, but can you explain (shortly) where is the benefit for you in having only smoothed data instead of real value? If you only explain, the those, who like the past behavior are not losing anything, what is definitely wrong. If there are no differences in your point of view, where is the benefit? It looks the same, but delivers not the same real data.
I like long term data, but not to see the last 24 hours. This is the oposite of long term and in this time I’m interested in real values.
3 Likes
are you serious now? those 2 lines don’t need any publishing…? just add them to your theme(s) and be done with it
I really wonder what you are saying here. working in an expected area?? trying hard to see your pov, but that’s hardly what most people want from their system: see if its round and about a valid state, ok, well it’s not too far off, so its probably alright…
No, I for one would love to be 100% certain when I check a state. I need it to be exact. and not 3 derivative values that blur the facts.
But honestly, what I don’t get at all, is why you are making such a fuzz about people experiencing the new troubles in more-info, when you yourself wrote you don’t use the LTS on the majority of your entities?